I have a PQI disk-on module that originally had Windows C installed. I ran Fdisk and deleted one large partition and two small partitions. Then I created a primary Dos partition and had it marked active so it would boot as C drive. I ran Format C:\ /u /s to erase and install the system files. If I boot from a boot disk, the disk-on-module appears as C Drive. I can copy files to and from the disk-on-module. When I try to boot to the disk-on-module, I get a screen full of "010101010101s" without end. The boot process is normal until the point where it should boot Dos. Then 010101010101. Does anyone know what could cause this problem? Thanks much. IMWESO

What version of dos? How big is the drive? Does your 32 meg PC meet the hardware requirements for the drive? Since dos sees it OK but it won't boot I'm thinking the version you're using may not be adequate for the drive.

The disk-on-module is 16 meg. I used Dos 6.22 for Fdisk and Format. I set up another disk-on-module made by Emphase. Used Dos 6.22. It was a 256 meg module. It works OK. 32 meg of memory should be big enough to handle anything I want to Do. According to the PQI site, there is nothing special about this disk-on-module. My first thought was that I had deleted some needed software when I deleted the three partitions with with Fdisk. I can't get PQI to answer any of my E-mails. When the computer is trying to boot the module into dos, the initial jump must have the wrong jump info. Something Fdisk and Format can't fix. I can't imagine why it would print a screen full of 01010101010. IMWESO IMWESO

I've never had experience with them so I can only suggest general stuff. You might check the PQI site and see if they have any utilities for that model. I imagine they would if it needed to be set up in ways beyond what fdisk and format can do. Did you partition and format it in the computer in which you're using it? Sometimes that makes a difference with regular hard drives.

Yes. I used Fdisk and Format on the same computer. I'll go back to the site and look for more info on the module. Thank you, IMWESO IMWESO

For some reason BeOS used that once. They had a special driver for it, don't know why. It seems like it should read as a hard drive. Might be seen as a removable device to the bios and therefore to dos. Might even be an odd cylinder , head number not known to the bios. "Best Practices", Event viewer, host file, perfmon, antivirus, anti-spyware, Live CD's, backups, are in my top 10