Amiga A1200T/040, is my Cv64/3D borked?

[wobbly]

 i havent fired up my miggy in ages - well years perhaps.
last time i fired it up all was fine.

just found all my cables again, fired it up and while the amiga itself and the drives all seem to operate, i get a black screen.

there seems to be a signal, as theres considerable 'plink'-ing when i disconnect the cable that connects the Cv64/3D output to the monitor.

now, the only other thing i can think to check my amiga is to somehow disable the cv64/3d retargetting when it boots.

anyone remember how - if possible - you can do that?



..or just take out my cv64 from the amiga?

thing is, with everything geared towards being on the retargeted screens, i dont know what will happen on the native screenmodes or if theyll get messed up by whatever codes and commands i had in my startup drawer or startup-file..

any ideas?
have cv64's gone belly up alot in the past?

i just looked in my old amiga mags - this thing cost me about 300 quid.. and the 040 was probably about 280 quid.. heh, i weep if i have to shell out that amount even these days..


==========================<>==========================
Commodore Amiga A1200 (Micronik Tower)
Blizzard 68040/fpu/40mhz - Micronik 6860 Busboard - 32+8mb FASTram
(scsi cd-rom, 4gb hard drives, Cybervision 64bit 3D 4mb graphics card, Macrosystem V-Lab...

[wobbly]

Update:

Remembered how to get to the early startup sequence.

So i definately know my amiga booted fine.

the cards are all reported as working.

drives all appear to be okay.

i selected 'boot with no startup-sequence' thinking that this would get me the standard amiga screen modes.

instead it went blank.

Tried other chipset modes, still comes out blank.

Aside from the early startup screen i cannot get anything else to show up on either the cv64 side or the amiga native side.

[wobbly]

hmmmmm.. my ability to get the Early Startup Screen seems to be random, unless my old mouse is wonky..

Ah well, I've come to the conclusion, even with the Cv64 and other cards taken out, the Amiga is still not playing ball.

Its been hooked up to my multivitec, and my tv, and neither shows me getting beyond the few previous times I've successfully got the Early Startup Screen.

I guess its kaput..

 :-(
shame as i had a pretty decent spec..

[wobbly]

?

i use a switcher box to switch between inputs to my monitor..

the unplugging of the cable was done only a coupl eof tmes, and the early startup screen had come after those times.
 i hadnt unplugged it in that way since.

i'll give Argus' suggestion a go in a bit.

[wobbly]

Yes, with the prices of Amiga's these days, its probably a better option to buy one than to get this repaired..

[wobbly]

Development!

Okay, i tried to see if the ROM's had misplaced, but i pressed on them anyway, took everything off my amiga so it was the basic mobo, and tried it again.

So my current situation is:

I can guarantee the Early Startup Screen and Floppy-Intro screen when: My System hard drive is not attached.


With System hard drive attached:
Early Startup Screen can sometimes come on [although I still dont know i this is dodgy hardware in my old Commodore Mouse] - But even when I get the Early Startup Screen and select Boot-with-no-Startup-sequence, the screen goes blank.

The drives seem to function normally, and it sounds like everything gets loaded from the hard drive as per normal.
I just cant see anything.

After about ten minutes of waiting my Cybergraphics intro graphic pops up but the Amiga seems to hang here, and no further progress happens.

So, I can now surmise that everything is present, correct and functioning, aside from:

Something to do with the hard drives...

Now, even if something like the startup-sequence was corrupted [but how can it be? its just a text file..]
 - it should surely go straight into the CLI screen?

Mine just goes blank.

So, despite it sounding like my drives are fine, and load everything as normal, is there something wrong with my hard drives?
or is it the ide cables?
or the ide adapter?

or software thats called upon in the startup sequence has failed..?
[But then that doesnt make sense when it fails with the Boot-without-startup-sequence function]

So i'm a bit stuck here..