CompuServe Messages

Bill, There has been a revision release to 5.04 and it's around here in one of the LIBs. However, if the installation went through without a hitch, then there shouldn't be a problem with the creation of the drive. I wonder if perhaps it's a problem with MSDOS. Which version are you using? If you are using 5.0, then you might try to get a copy of 3.3 and try installing the drive with it to see if it will autoboot. When I got DRDOS I had a problem getting my C drive to autoboot on the bridgeboard. It turned out that the DRDOS FDISK and FORMAT commands had minor bugs which would not correctly install a bootblock on certain drives. Although that may not be your problem, it never hurts to try with 3.3 just to see. I never could get MSDOS 5.0 to install on a bridgeboard using the pseudo-drive, although there was no obvious reason why it shouldn't, but it just wouldn't. What SCSI controller do you use? Maybe there's a problem with CrossPC and that controller. CrossPC will not install a drive on my Nexus controller or my IVS controller, although it works just fine on my A3000. I'm sort of stumped, though, on what further suggestions to make.