win95 reinstallation

win95 reinstallation

Post by elenamaria » Sat, 27 Nov 2004 18:19:13


Hi,
it's the first time I write to this group but I don't know what else
to do.
My PC had some problems and I decided to format the HD and reinstall
Win95. The problem is that I had never formatted an hard disk before
and probably I did something wrong...In fact I didn't do fdisk before
formatting, as I thought it was unnecessary as I had only one
partition (c:). So, from the boot disk I gave the command format c:
(without any options) and then reinstalled Windows95 from the original
CD. Apparently all went well as I got no error message, but when the
computer restarted for the first time after the installation was
completed, it blocked with an error on VXDLDR driver. I wonder if the
problem can be caused by the fact that I didn't do fdisk before
formatting, or else can be some hardware failure (I got errors on
vxdldr even before formatting, or the pc restarted every few minutes
while working, that's why in the end I decided to reformat c: and
reinstall Windows. But now I'm starting to think there are hardware
problems). In case it's the fdisk, can it be done now (and then
reformat and reinstall again?)? Or there would be no difference, as I
don't have many partitions on my HD?
Thank you for any help...
Elena
 
 
 

win95 reinstallation

Post by Ben Myer » Sun, 28 Nov 2004 02:04:59

Try removing and reseating the memory boards on the problem computer.

Ben

 
 
 

win95 reinstallation

Post by Mike Wals » Sun, 28 Nov 2004 03:38:19


You don't have to run fdisk before reinstalling Win95, you don't even have to format. You can reinstall Win95 over an existing installation to fix many windows problems as this will reinstall all system files.
In some cases you might have to format to remove all traces of viruses, spyware, etc., as you have done. You will not gain anything by repartitioning. Since you are still having problems after a clean install it is likely that you have a hardware problem, e.g. memory or hard drive.




--
Mike Walsh
West Palm Beach, Florida, U.S.A.
 
 
 

win95 reinstallation

Post by Johnny B G » Sun, 28 Nov 2004 07:42:09

The message < XXXX@XXXXX.COM >
from XXXX@XXXXX.COM (rossiele) contains these words:


A 'quick format' (format c:/q) should suffice. You neglected to say
whether the hardware involved a cpu faster than an intel P233MMX.

Win95 will install ok for CPUs no faster than the AMD K6/2/266 (the
"3DNow!"(tm) series). You'll see problems with the K6/2/300 and faster
chips, which will require the "amdk6upd.exe" patch to be applied.

Of course, you might be in a catch 22 situation if, for whatever
reason, you can't slow the cpu clock down to 266MHz or less, but you can
always google for instructions on how to get round this problem.

Of course, it might simply be due to a problem with the memory. Try
running memtest86 to verify the memory. If you do find errors, try
reseating the modules[1] and test again before looking for replacements.

The other likely source of trouble is the hard disk. It might be an
idea to do a surface scan for bad blocks[2] which, if any are found, can
then be mapped out to avoid causing further problems.

[1] It's always a good idea to reseat the memory modules in any case but
it might be more useful to run memtest86 first before doing so
regardless of the outcome. It would be more useful to know whether any
intermittent memory errors were due to a poor contact in the slot or
likely to be faulty memory module.

[2] If any bad blocks are found, especially if there are a large number,
it's worth retesting to confirm whether you are dealing with a 'One Off'
event or an ongoing problem.

--
Regards, John.

To reply directly, please remove "buttplug" .Mail via the
"Reply Direct" button and Spam-bots will be rejected.
 
 
 

win95 reinstallation

Post by elenamaria » Tue, 30 Nov 2004 20:31:13


Thank you all for your answers...My ps is old and slow (180Mhz), so I
think the problem should be memory. I reseated memory modules but
nothing changed...I think some of them is faulty (is there a way to
discover which one?). I didn't run memtest86 because I didn't
understand how to run it from a diskette (I found instructions to make
a bootable CD-ROM, but I have no CD burner), anyway I don't know if it
would make any difference...Thanks anyway
Elena
 
 
 

win95 reinstallation

Post by Johnny B G » Wed, 01 Dec 2004 12:21:21

The message < XXXX@XXXXX.COM >
from XXXX@XXXXX.COM (rossiele) contains these words:

----snip----


The memtest86 download is a program that creates a (linux based) boot
floppy which automatically runs the memtest program on boot up. You
simply boot from the memtest86 floppy. It couldn't be simpler (once
you've created the floppy :-) and made sure to configure the bios to
boot from the floppy before it tries the hard drive.

HTH

--
Regards, John.

To reply directly, please remove "buttplug" .Mail via the
"Reply Direct" button and Spam-bots will be rejected.
 
 
 

win95 reinstallation

Post by elenamaria » Wed, 01 Dec 2004 21:02:16


Oh, really...What a fool I am! I thought you needed linux in order to
run it...Anyway I prepared the floppy and I'll run the test. Thank you
again!
Elena
 
 
 

win95 reinstallation

Post by elenamaria » Thu, 02 Dec 2004 19:22:20

Well, I run memtest86 twice yesterday but I'm even puzzled than
before...
The first time it run ofr about 20 minutes without giving errors, when
suddenly crashed with the message 'Unexpected interrupt- halting'.
I tried again and the same thing happened after about 10 minutes...
Have you any idea what can this mean? Maybe it's a CPU problem, not a
RAM one?

Elena
 
 
 

win95 reinstallation

Post by Johnny B G » Thu, 02 Dec 2004 21:00:44

The message < XXXX@XXXXX.COM >
from XXXX@XXXXX.COM (rossiele) contains these words:


It's quite rare to see such errors but not unkown. Whilst most memory
errors *are* faulty memory/timing or compatability issues, it's worth
bearing in mind that cpu faults can also *** such 'bad memory'
reports.

In this instance, it seems unlikely to be a memory issue since the test
is geared specifically to deal with such in a more meaningful way than
that indicated by the phrase. 'Unexpected interrupt- halting'.

It could be an indication of a cooling problem. Have you checked to see
if the cpu cooling fan is still spinning and the state of cleanliness of
this and the heatsink itself?

Whilst memtest86 isn't in the same league as "CpuBurn" with regard to
thermally stressing the cpu, it does add some extra stress which varies
according to the individual test being applied.

HTH

--
Regards, John.

To reply directly, please remove "buttplug" .Mail via the
"Reply Direct" button and Spam-bots will be rejected.