I've had trouble getting some drives to "talk to the system" as a slave.
I would not try to boot from or run the system from the old (Win3.11) drive
AND write to the new drive (if FAT32??) since that would not work...
Since this is a DOS program you want to move, it should be possible
to just copy """all""" its files to the new system.
I would suggest jumping both drives as standalone, one on each of the
two IDE channels, and forget the CD-ROMS, Zips, etc., for the time being.
I would boot from the new drive and get the program running from there,
and then put the system back to the finished configuration.
PS: I never had to move a DOS program like this, so there may be some
unforeseen problems with .ini files etc. You may have to re-install the program
to the new drive, test it, figure out where it stores its DATA and move that
over -- (as if it were acting like a Windows program.)
   Good luck, and let the list know how you make out.  Rick Glazier
----- Original Message -----
From: Jim Phillips <[log in to unmask]>
> After building a new Pentium system, the person wanted to save the Autobody
> Database program she had on the old system.The program is called Q&A from
> Symantec(no longer supported) and is DOS based! She was running WIN
> 3.11(non-networked). I took her old 840MB Quantum HDD and made it the slave
> off of the 1st IDE(I tried both slave and CS jumper positions) but when the
> new drive boots up to win98, I cannot see this slave drive? I can
> auto-detect through the BIOS and the correct C/H/S info is shown for each
> drive. If I reverse the situation and make the Quantum the master and the
> 6.4GB fugitsu the slave, then I'm prompted for the boot disk....would this
> be a DOS or Win 3.11 boot disk? I have neither of these. How can I transfer
> the program over to the big drive? Will a Zip Drive work in this situation?

         The PCBUILD web site always needs good submissions.  If
          you would like to contribute to the website, send any
               hardware tech tips or hardware reviews to:
                           [log in to unmask]