Welcome, Guest. Please login or register.
May 21, 2013, 05:26:28 AM
Pages: [1]   Go Down
  Print  
Author Topic: no booting in windows95  (Read 210 times)
Saloei
Veteran

Posts: 279

Join Date: Jul, 2003


« on: July 26, 2003, 11:50:24 AM »

 no booting in windows95
Logged
Saloei
Veteran

Posts: 279

Join Date: Jul, 2003


« Reply #1 on: July 26, 2003, 11:50:24 AM »

hello,
my problem: windows 95 welcome screen loads but the operating system doesnt load. i get to the c:\ prompt. i typed WIN.exe and windows still will not load.
what triggers the o\s to load?
could it be a missing boot.ini?
Logged
Intuit
Ace

Posts: 10,355

Join Date: Oct, 2002


« Reply #2 on: July 26, 2003, 10:49:52 PM »

Actually, it should be "Win.Com" or just "Win" versus "Win.exe".

The OS normally is launched by IO.Sys immediately after the AutoExec.Bat file finishes, so long as the "" parameter is set to "Auto" in the Config.Sys file.  You can manually place "Win" at the end of your AutoExec.Bat file if the OS was configured to load Command.Com versus Win.Com.

If for some reason, the "Path" statement is not set, you may need to go to the "Windows" directory before "Win.Com" will launch.

Type:

"CD C:\Windows" [enter]
"C:" [enter]
"Win" [enter]

That should get Win95 going, assuming there aren't any other problems.
Logged
Intuit
Ace

Posts: 10,355

Join Date: Oct, 2002


« Reply #3 on: July 26, 2003, 11:01:18 PM »

Here is my old "MSDOS.Sys" file.  It is configured to DISABLE load of Win.Com.  Deleting (back it up first) the [Options] parameters listed in your MsDOS.Sys file should restore DOS to the default of loading Windows on boot.

Ignore what was mentioned before about the "DOS" parameter having to be set to "Auto".  That I believe is only relevant for Win98 and not Win95.  The easiest way is to do what was mentioned previously... just add "Win" to the end of your "AutoExec.Bat" file using the "Edit.Com" program.:


MsDOS.Sys
Quote


[Paths]
WinDir=C:\WINDOWS
WinBootDir=C:\WINDOWS
HostWinBootDrv=C

[Options]
BootMulti=0
BootGUI=0
WinVer=4.10.1998
BootKeys=1
;Changes added by me 6/30/98
Network=0
BootWin=1
BootMenu=1
BootMenuDefault=1
BootMenuDelay=1
BootDelay=0
BootConfig=1
BootSafe=0
Logo=1
DisableLog=1
LoadTop=1
SystemReg=0
;End Changes added by me 6/30/98
;Begin Changes added by me 10/28/00
DoubleBuffer=0
AutoScan=2
BootWarn=1
DblSpace=0
DrvSpace=0
;End Changes added by me 10/28/00
;
;The following lines are required for compatibility with other programs.
;Do not remove them (MSDOS.SYS needs to be >1024 bytes).
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxa
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxb
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxc
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxd
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxe
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxf
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxg
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxh
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxi
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxj
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxk
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxl
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxm
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxn
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxo
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxp
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxq
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxr
;xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxs


Logged
Saloei
Veteran

Posts: 279

Join Date: Jul, 2003


« Reply #4 on: July 27, 2003, 01:56:30 PM »

thanks for the info. ill keep you posted on the results. this problem exists on someone elses computer.
they "THINK" a virus was the cause of this problem.
Logged
crosscourt
Game Guru

Posts: 22,215

Join Date: Dec, 2001


« Reply #5 on: July 27, 2003, 10:56:32 PM »

Could be a hardware issue as ram problems,wrong settings or incompatible ram could cause the same issue. You probably have already but check the bios settings and maybe test the ram sticks seperately.
Hopefully no files have been corrupted or damaged causing these issues,CC
 
Logged

Viahardware.com first moderator
Saloei
Veteran

Posts: 279

Join Date: Jul, 2003


« Reply #6 on: July 28, 2003, 11:01:55 PM »

 
Logged
Sparbag
Ace

Posts: 1,104

Join Date: May, 2002


« Reply #7 on: July 31, 2003, 08:01:42 PM »

Registry may have become corrupted and boot to reg edit mey be the only option.

Turn on
F8
choose 6 nothing except DOS prompt
scanreg.exe - enter
choose an earlier registry.

reboot

HTH
Logged
Saloei
Veteran

Posts: 279

Join Date: Jul, 2003


« Reply #8 on: August 01, 2003, 12:57:24 PM »

i found that the problem was with the harddrive itself. formatting the disk was not an option, as i recieved LOCATING SECTORS throughout the format process. disk is screwed!

thanks for the suggestions. i write these suggestions down for future problems.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to: