>
> The problem here is that the older versions of DOS do not read FAT32.
> However, the 'DOS' that comes with WIN98 does read FAT32, and will do
> anything that DOS 6.22 does. To create a win98 dos boot disk, boot into
> windows98, and use the command "SYS a:" at a command prompt, or
> right-click on the floppy drive in windows explorer and choose format,
> where it gives you the option "Copy system files only". You can then
> create your own config.sys and autoexec.bat files on the floppy, etc,
> etc. When you boot up with it it will leave you in DOS mode.
>
> Another option is upon bootpu of your system you may see the message
> "loading windows" right after your bios finishes its system checks.
> Press F8, and you will be given a menu with the option to boot into
> command line mode, which is effectively the same as booting to dos,
> except that config.sys and autoexec.bat on the hard drive will be run.
> I usually start pressing F8 once I know bios is done checking the hard
> drives and memory, and press it several times in case the bios empties
> the keyboard buffer before starting the boot process.
>
> Try f5 as well as f8. F5 skips the autoexec and config.sys files, I
> don't recall if it dumps you to dos though.
>
> -Adam
>
> Do not meddle in the affairs of sysadmins, for they are quick to anger
> and have not need for subtlety.
>
> Ruben Jvnsson wrote:
> >
> > If you find any solution to this I would appreciate it if You could
> > share it with the rest of us (who have to use both DOS and W95).
> >
> > I have the same problem with a 10GHD. I also have a small HD (200M)
> > which i thought I could set up as FAT16 and boot from a floppy when I need
> > to run pure DOS. The primary drive is C: which is 10GB FAT32 and the
> > secondary drive is D: which is 200M FAT16. The problem is that when I boot
> > from my DOS6.22 diskette drive C: disappear and drive D: is now C:. This
> > is a problem since I use DOS for programming and can mostly do this under
> > W95 but sometime I need DOS 6.22 (No virtualized peripherials) and all my
> > paths in the development environment is pointing to D: which now doesn't
> > exist.
> >
> > Perhaps It works if I have the small HD as drive C: with FAT16 and
> > the large one as drive D: with FAT32. Dos 6.22 is installed on C: and W95
> > boot files is installed over DOS in this drive but its main components
> > (W95 dir) is installed on D:. This way I should be able to reboot to my
> > old DOS with D: now invisible to DOS but with all paths for my DOS
> > programs in C: the same as when run from W95.
> >
> > I didn't have time to try this out, instead I partitioned my HD as 4 2.1G
> > blocks (loosing approx. 2G) and now it's too much trouble to try it.
> >
> > >
> > > My absence from the list (OK, so who noticed?) most of this week has
> > > been due to the mind-bendingly challenging task of trying to replace my
> > > uncomfortably-full 3 GB main drive with a brand spanking new 15 GB one.
> > >
> > > Do you think there's a good tutorial somewhere on the 3 GB or so DOS/
> > > Windoze95/ partition table limitation and how one overcomes it? M$ are
> > > as helpful as ever.
> > >
> > > I am back to the 3 GB drive for now - I could get the larger one to
> > > run under Windoze but not under DOS (which is of course required to boot
> > > Windoze!). --
> > > Cheers,
> > > Paul B.
> > >
> >
> > ==============================
> > Ruben Jvnsson
> > AB Liros Elektronik
> > Box 9124, 200 39 Malmv, Sweden
> > TEL INT +4640 142078
> > FAX INT +4640 947388
> >
ruben
spam_OUT2.sbbs.se
> > ==============================