Need a book? Engineering books recommendations...

Return to index: [Subject] [Thread] [Date] [Author]

Re: COMP - AISC Autocad Files

[Subject Prev][Subject Next][Thread Prev][Thread Next]
F8 key doesn't work at bootup. But the real question is, why would I want
to do any of this? I've waited a long time to get DOS small in my rear view


> From: Dennis S. Wish PE <wish(--nospam--at)>
> To: seaoc(--nospam--at)
> Subject: Re: COMP - AISC Autocad Files
> Date: Sunday, September 07, 1997 4:05 PM
> >Maybe mine is different (I believe it is if you are referring to Win95A
> >before). First of all, F8 doesn't do anything for me. Next, my Win95 CD
> >does not have a directory called "OLDDOS". I can open a MS DOS window
and I
> >can reboot in MS DOS mode. But, I believe in my case, windows is
> >"emulating" DOS. In either of these two cases when I type "ver" the
> >response I get is "Windows 95. [Version 4.00.1111]. There is nothing on
> >system that I have found that will tell me anything about a DOS 8.0. If
> >there is any other place that you suggest I check, please let me know. I
> >know that my version of Win95 is not commercially available and it was
> >intended to be shipped with new machines. However, a colleague of mine
> >recently (after Win95B was available) bought a computer with Win95
> >only has Win95A (Win95 w/service release 2).
> >
> >
> >
> >Thanks,
> >Bill Allen
> >
> Bill,
> First, you need to tap the F8 key after you boot - as soon as you see the
> CMOS information about your computer. Keep tapping until you get a menu
> screen that asks if you want to start in safe mode, normal mode or MS-DOS
> mode. If you choose number 6 (I think that is the number) you will be
> presented with your old friend the C:> and black screen.
> You can also exit Windows and choose start in MS-DOS mode which takes you
> the DOS screen.
> You have one more option, you can modify the msdos.sys file which
> the following lines:
> [Paths]
> WinBootDir=C:\WINDOWS
> HostWinBootDrv=S
> [Options]
> BootMulti=0
> BootGUI=1
> Network=1
> This is followed by embedded code and the last two lines read:
> BootWarn=1
> Logo=1
> There are a couple of choices under options and a few more that you can
> (curtesy of Microsoft Windows 95 Resource Kit):
> BootMulti=0
> Enables dual-boot capabilities. The default is 0. Setting this value to 1
> enables the ability to start MS-DOS by pressing F4 or by pressing F8 to
> the Windows Startup Menu. You can still use F8 with BootMulti set to 0.
> BootGUI=1
> Enables automatic graphical startup into Windows 95. The default is 1.
> to 0, I believe would start you in MS-DOS mode and you would need to type
> Win to start windows 95.
> BootDelay=n
> Sets the initial startup delay to 'n' seconds. The default is 2.
> disables the delay. The only purpose of the delay is to give the user
> sufficient time to press the F8 key after the Starting Windows message
> appears which would bring up the Startup menu from which you can choose
> mode you wish to work in.
> BootKeys=
> Enables the startup option keys (that is, F5, F6, and F8). The default is
> Setting this value to 0 overrides the value of BootDelay=n and prevents
> startup keys from functioning (I suspect that Bill has this value set to
> in his Msdos.sys file if he can not launch the startup menu).
> BootMenu=
> Enables automatic display of the Windows 95 Startup menu so that the user
> must press F8 to see the menu. The default is 0. Setting this value to 1
> eliminates the need to press F8 to see the menu.
> For those that care to play around with Windows, I suggest a copy of the
> Resource Kit - about $50.00 at Crown. Also there is an excellent book
> the only one I know of ) that deals only with the system registry that
> you understand how programs store important information - similar but yet
> much different than the INI files used in 3.1. I'll try to find the book
> let you know.
> I can't recommend enough the ability to learn how Windows Works. I have
> spent hours and days tracking down problems with GPF errors and crashing
> machines only to discover that I needed to simply change the location of
> swap file to allieviate a corruption in the swap file. Rebooting and then
> replacing the swap file to it's original location (after defragmenting my
> disk) eliminated most if not all of the problems and had me up and
> in minutes. Now I don't have to waste a day tracking this type of error,
> have a feel for where it originates and I know how to fix it fast.
> Hope the information helps.
> Dennis Wish PE