GH> I can not get Win95 to run on my 486 DX 100.  It crashes everytime I try
 GH> to install it.  I even changed from my SCSI hard drives to IDE drive, 
nd
 GH> changed video cards, and tried all sorts of CMOS changes. No matter what 
I
 GH> do, I install it, and it gets to the part where it actually begins to
 GH> run 95, and crash.....  I did get it to actually (sort of) install once.
 GH> I did so by disabling ALL cache, both internal, and external.  I still 
got
 GH> at least one GPF during the installation, but it did install.  However, 
it
 GH> ran so slow, it literally took about 3 minutes to load the box and icons
 GH> from MY COMPUTER icon.
Most likely you have a hardware problem, in your RAM memory or in your cache 
memory. W95 is more stressfull on a system than DOS/16 bit windows. Try 
testing your memory with HIMEM.SYS by using DEVICE=C:\WINDOWS\HIMEM.SYS 
/TESTMEM:ON and see what shakes out. 
Also, if you put this message in the Windowss95 conference, you will probably 
get a lot better and more thorough reponse. Most of the people that hang 
around these parts have been running Windows NT for so long they have a 
difficult time relating to 16 bit WIN or Windows 95 problems.
--- Maximus/NT 3.01b1
---------------
** A related thread FOLLOWS this message.

FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: F23K2054 Date: 02/03/98
From: GEORGE HORSEMAN                                       Time: 04:34pm
\/To: CHRIS HOLTEN                                        (Read 3 times)
Subj: R: CANT RUN WIN95, BIOS PROBLEM ??

CH>Most likely you have a hardware problem, in your RAM memory or in your c
CH>memory. W95 is more stressfull on a system than DOS/16 bit windows. Try
CH>testing your memory with HIMEM.SYS by using DEVICE=C:\WINDOWS\HIMEM.SYS
CH>/TESTMEM:ON and see what shakes out.
CH>Also, if you put this message in the Windowss95 conference, you will pro
 
CH>get a lot better and more thorough reponse. Most of the people that hang
CH>around these parts have been running Windows NT for so long they have a
CH>difficult time relating to 16 bit WIN or Windows 95 problems.
CH>--- Maximus/NT 3.01b1
 
-------------------------
Thanks for the help, as you can see, I get on here seldom 
Anyhow, I think you are right, it appears that there is a problem
with my system, cuz even Win 3.1 tends to suddenly drop to DOS for no
reason, at times.
 
I'll do the hardware checks as you said.
I thought Win95 was a 32 bit OS.  Guess I was wrong !!!!
 
Anyhow, Thanks.....
---------------
>>>>>>>>>>>>>>>>>>>>>> LAST Message In Thread <<<<<<<<<<<<<<<<<<<<<<

FIDO MESSAGE AREA==> TOPIC: 206 WINDOWS 32BIT Ref: EFP00001 Date: 11/18/97
From: CHRIS HOLTEN                                          Time: 06:29am
\/To: FRANK RAMSEY                                        (Read 4 times)
Subj: Re: Combo WinNT Server & Workstation

 CH> You can have local security as each NT system (Wks or Srv) 
 CH> can have it's own user data base and that will work from 
 CH> within an NT Domain just fine.  I do know when I have my 
 CH> DC server down that NT 4.0wks caches the local user 
 CH> profile. It doesn't cache the Domain User data base with 
 CH> users and pw's that have been accessing the Wks resources. 
 FR> Even if the userid's are the same, a domain account and 
 FR> a local account use different security identifiers. 
 FR> Without some type of privs, or modifications to the 
 FR> workstation's permissions, and assuming you're using 
 FR> roaming profiles, not mandatory ones, the doman account 
 FR> and local account will not share the same profile. 
 FR> Basically, if a DC is not available, you're hosed until it comes up.
Hmm...It doesn't -seem- to happen this way on my setup Frank. As you mention, 
I have the same local user and domain account, but when I log in I log into 
the domain, not the local account. If the DC is down, I get a message about 
the domain controller not being available and that the system is using cached 
settings, which is the desktop I get when I log into the domain (IE chris 
from CowboyCountry Domain). If I log in using the local account (IE Chris 
from Old Red) then I get different desktop.  The local user and the domain 
user are the same name with the same password. S'why I know the user profile 
(desktop settings) are cached. Don't know how it would work with different 
passwords or users names that aren't in the local user database. But as 
described above, that is the way it works here.
Obivously if the DC is down, a user cannot log on to other resources in the 
network that are setup to use the DC for security. You statement as being 
"hosed" is on the spot in that instance. I only intended to refer to the 
local user profile/desktop, which I thought was the essence of the original 
message I replyed to.
--- Maximus/NT 3.01b1
---------------