I'm assuming this problem doesn't occur when you de-activate CrossDOS?
Yes that is correct.
Well, as I said, my GVP 030 combo's SCSI controller would 'hang'. What I didn't mention is this caused plenty of read errors. Your Maxtor drive may not be as crappy as you think (slow though, I have a Maxtor 270 and it's no speed demon). It may simply be down to the GVP SCSI controller. This may also have been caused/compounded by your adding the Toaster, Studio 16, DPS PAR, etc., etc. The A2000 power supply was the beefiest of all the desktop models, but it was only 200W. I doubt power would be a problem now that you only have the GVP 040... But then again, the power supply maybe flagging and just has died yet. Do you have a voltmeter?
Yes I do.
Instead of reformatting it, see how well it operates... Unless, that is, you re-prepped the drive and the RDB is non-standard. You may be able to use the GVP prep software to record the drives various parameters and then use HDToolBox (or the Supra controller's software if it came with any) to create anew RDB... I've never done this, so perhaps some one else here can better advise you. Anyway, if it's stable, you have another indication there is something wrong with the A2000 your GVP 040 is in now. Then try adding the GVP 040 to the "other" A2000, but keep the drive on the Supra Controller. If thing are still OK, then try attaching the drive to the GVP. If the problems you've experience manifest, you know it's the GVP 040. If they don't materialize, you'll know there is something amiss in the 'original' A2000.
As much as I hate tearing into the other 2000 at the same time I think you are right. I guess it's the old "You gotta break some eggs if you want to make an omlett" thing.
Well, I'd recommend you find at least one drive you can do a clean, plain vanilla, install on. As your problems may be down to incompatible software or corrupted files. You could even use a Syquest cartridge if push comes to shove. This would be invaluable for troubleshooting what's going on. And as I said, there are ways around the RDB problem... I just can't help you too much there... If you could get software off the net and on to your Amiga. I'd recommend backing up your drives on to SyQuest carts with ABackup from the Aminet... Better yet, onto your IBM PC or CD-ROM. You could then fiddle around with impunity. This can be done in one of several ways. But they're all pretty much predicated on your getting software from your IBM PC onto your Amiga...
I think I can get the software there if I can get the CDROM working because I can burn the stuff I need on a CD on my PC and then read it on the Amiga.CDROM
Strictly FYI, you can mount Amiga formatted hard drives in Windows NT4/2k/XP (using WinUAE) and Linux... And a SCSI controller in your IBM PC (to mount your current Amiga hard drives. Just want to mention this in case it turns out to be something worth attempting. I haven't attempted this myself (yet) BTW. Perhaps some other WinUAE or Linux users could advise you. BTW, what are the specs of your IBM PC?
I do have a SCSI controler in my PC that is used for a flatbed scanner and a slide and film scanner. That is only two devices so there is room on the chain for more.
Heh, heh, heh... You and everybody else. GVP-M is notorious for their lack of customer support. Don't know what it was like back when GVP was just GVP (long story), but I may have gotten one reply about problems I was having with the GVP T-Rex II I had in my A2000. As it turned out, the oscillator crystal was loose (hell it eventually would fall right out of its socket!) and this caused my A2000 to lock up constantly. And here's where I suggest you try reseating any and all socketed chips in your A2000. Including those on the GVP combo.
If it looks like the 040 is a problem I will try again to contact them. Maybe it takes a phone call. Hey, mabe it's just some guy running GVP out of his garage now. Websites can be deceiving you know.
[
You'll have to look in the startup-sequence or user-startup (I think it's in the startup-sequence though). Start ed or any text editor your comfortable with. Open S:startup-sequence and/or S:user-startup. You should see lines like ";BEGIN AsimCDFS" and ";END ASIMCDFS". The lines in between will need to be commented out with semicolons, as the "BEGIN" and "END" lines are. That will disable AsimCDFS. I would recommend you try re-installing it if you have version 3. I've used it on and off with little or no problems (I'm using CacheCDFS now, only because it came with 3.5/3.9).
I wonder if you have a 'full' copy of AsimCDFS. I don't recall there ever being a special OEM version, but I could be wrong... I didn't get into Amigas until just before Commodore's collapse. Does the disk mention which version of AsimCDFS you have (v2 or v3)?
I will give this a try. I checked the floppy, it's version 2.0 for the AsimCDFS. It's all on one disk if that helps
The more information the better. The more you provide the better I, and others here on Amiga.org, can help. Though Wayne may disagree. After all, it's his storage space :-D.
Yea, you gotta point there. With these long posts it does burn up the space. Of course it's all text and probably doesn't take all that much space. If worst comes to worst we can always go to email but that precludes anybody else from seeing this and making suggestions.
In that case, I'd strongly recommend you do the following. First, verify that your floppies are still good! I'd hate for you to start the process and then find 'disk 3 out of 4' is bad. Then make a partition and install a plain vanilla OS install and leave it alone; next make another partition and install the OS again and use it as your 'production' SYS: partition; or vice versa. That way you'll be able to use the Early Startup menu to boot from your backup boot partition if things get dicey again. Trust me. It's worth the effort. After that, you can divvy up your drives anyway you like.
I try to follow all theis the best I can and do these things. Some of this is stretching the limits of my skill envelope but maybe I will learn.
