Computer Problem...Again. *sigh*

[ReadyOne]

Some computers -- notably Dell, Compaq and HP inmy experience -- store the setup information that other computers store in CMOS or Flash-Ram in the boot sector of the hard-drive. They only have enough information in the BIOS to find and load the information from the boot sector.

Those kinds of machines don't work right when booting from a floppy or CD unless they also have the setup info in the boot sector -- i.e. are especially provided as emergency boot disks for that particular machine.

Haven't seen one of those for years... When I worked for IBM and we got the first PS/2 machines, we all cringed because a broken hard drive meant all the BIOS settings were lost.

We thought it was stupid, as did most of the rest of the manufactures, but IBM never listened to internal customers, even when they used us for beta testing.

I haven't seen information stashed on the hard drive since EEPROMs (Flash Memory) came into use a decade ago.

 

[Weird Harold]

I haven't seen information stashed on the hard drive since EEPROMs (Flash Memory) came into use a decade ago.

I just recently junked out a four year old HP Pavilion because the setup info was on the harddrive and the system wouldn't boot from any other drive I tried. It wouldn't even recognise the recovery CD because the setup couldn't be changed to boot from it.

The problem isn't really the information on recent HP's but the program that changes that information is still on the hard drive i.e. it isn't possible to get to the bios setting without a HP formatted HD installed -- unlike my ASUS MB/AMI Bios which only requires a video card and keyboard to get to the BIOS setup program and restore the setup defaults. (actually, I don't even think the video card is required; I just can't see what I'm doing without it. )

 

[MagicFingers]

I hate Compaqs

Reminds me of a compacted tooth!
I've never had a good experience working on one. They have to do things differently from everyone else in the world.

It's sad to hear HP are doing that sort of thing now too.

So, if we have a Compaq that won't boot because of a virus or worm, we could just be SOL?

Thanks for the info, guys.

 

[je404ucd]

How often do you delete your temporary files? Just go to "Tools -> Internet Options" and click "Delete Files"

The first time I deleted my temporary files it took like 10 minutes... And that was before I REALLY got into looking at porn. I delete them after every porn session and it seems like it sped up my system performance by 200%. It started as a way to keep my system looking clean.

 

[Weird Harold]

Re: I hate Compaqs

It's sad to hear HP are doing that sort of thing now too.

So, if we have a Compaq that won't boot because of a virus or worm, we could just be SOL?

HP has always had proprietary quirks similar to Compaqs. Now, they've merged and are just different brand names for the same computers.

Probably not -- Compaq service centers and many independent computer repair shops have bootable Compaq diagnostics disks and the BIOS can be reset to it's basic defaults with a jumper -- if you've got the manual that shows you where it is.

A few HP and Compaq motherboards have the BIOS reset jumper labeled on the board, but many do not.

 

[ReadyOne]

How often do you delete your temporary files? Just go to "Tools -> Internet Options" and click "Delete Files"

The first time I deleted my temporary files it took like 10 minutes... And that was before I REALLY got into looking at porn. I delete them after every porn session and it seems like it sped up my system performance by 200%. It started as a way to keep my system looking clean.

You can also set a limit on the temporary file space at that same place.

Contrary to expectations, more is not better. I wouldn't allocate more than 1/2 meg or so.

 

[sheath]

This has turned into a very, very helpful thread. Thank you for your expertise, guys...and keep going! I'm learning.

S.

 

[JoseIsWild]

Well I suspect I'm having problems with my memory too.. Windows keeps crashing with an error stating its having problems writing to Address <some long hex addr> and it shuts down. Yesterday I took my SIMM out (its a PC133 256MB SIMM) and I wrapped it in aluminum foil to carry it around town. No one seem to have a SIMM tester. So I ended up bringing it back home and putting it back into the computer. So far now, it hasn't crashed once and it seems to be running a little faster.

Strange eh?

 

[Weird Harold]

No one seem to have a SIMM tester. So I ended up bringing it back home and putting it back into the computer. So far now, it hasn't crashed once and it seems to be running a little faster.

Strange eh?

Not all that strange. One of the first "fixes" to try when memory apparently goes bad is to pull it out and clean the contcts with a pencil eraser. It doesn't take much oxidation to break the connection and often simply reseating the SIMM is enough to remove it.

 

[sheath]

Okay, computer buffs...

It happened again, and this time, I wrote the whole thing down.

On the Blue Screen of Death:

***
A fatal exception has occurred at 0028:C02987A8 in VXD VWIN32(05) + 000012D0. The current application will terminate.

Press any key to continue...
***

Immediately afterward, I got this little message pop-up box.

***
Msgsrv32

This program has performed an illegal operation and will be shut down.
***

Under "Details":

***
Msgsrv32 has performed a general protection fault in module KRNL386.EXE at 0001:00001236.
***

At that point, my computer locked up completely and I had to restart.

Does this help? Anybody know what to do with the mumbo jumbo?

S.

 

[ReadyOne]

I'm curious why msgsrv32 was running.

It's frequently used to launch a task like some item in the control panel or a "windows is installing new hardware" type dialog.

It's also sometimes used by virus/worms.

 

[sheath]

I'm curious why msgsrv32 was running.

It's frequently used to launch a task like some item in the control panel or a "windows is installing new hardware" type dialog.

It's also sometimes used by virus/worms.

It has happened more than once.

Is there any way to disable it? Or should I even try?...

*sigh*

S.

 

[ReadyOne]

It can be good or bad. Disabling it will break things.

I assume youu've run the Anti Virus with current definitions?

An interesting execersize is to hit Ctlr-Alt-Del and look at the list of runing tasks, then identify each one. Most will come from the start-up entries in teh registry and startup folders.

Ocassionally you find some that is a virus or hijacker.

Kill it and see what happens...

 

[sheath]

It can be good or bad. Disabling it will break things.

I assume youu've run the Anti Virus with current definitions?

An interesting execersize is to hit Ctlr-Alt-Del and look at the list of runing tasks, then identify each one. Most will come from the start-up entries in teh registry and startup folders.

Ocassionally you find some that is a virus or hijacker.

Kill it and see what happens...

Okay...explain to me how to do that? Ctr-Alt-Del shuts my computer down completely. Maybe I'm thinking of the wrong thing, but I admit I'm a little lost with that post there.

S.

 

[Weird Harold]

An interesting execersize is to hit Ctlr-Alt-Del and look at the list of runing tasks, then identify each one. Most will come from the start-up entries in teh registry and startup folders.

The pop-up notice with the details button is a DrWatson critical error trap. If you choose advanced when displaying the log file DrWatson created with that snapshot, there are tabs that will tell youwhat was running at the time, what loaded it from where, and which are sixteen-bit drivers and which are 32 bit drivers.

Drwatson cn lso be used to take a similar "snapshot" manually by double clicking on the DrWatson icon in the system tray.

A search for *.wlg with the find files function will turn up where DrWatson stores it's log files. Double click on one to open it and you'll get this sort of information (this is the starupt tab of the most recent log file on my system.)

Note: Drwatson must be started in the startup menu or manually before it will trap errors like sheath's machine did. If you haven't been running it, you should be -- the second error would have also been a BSOD without DrWatson Running.

 

[Weird Harold]

It has happened more than once.

Is there any way to disable it? Or should I even try?...

*sigh*

S.

Yes, you can disable it, but if you do, you may have problems with your e-mail -- it's Windows Message Server function. See attached screen capture for more info on MSGSRVR32.

 

[Weird Harold]

***
A fatal exception has occurred at 0028:C02987A8 in VXD VWIN32(05) + 000012D0. The current application will terminate.

Press any key to continue...
***

Immediately afterward, I got this little message pop-up box.

***
Msgsrv32

This program has performed an illegal operation and will be shut down.
***

VXD VWIN32 (05) is probaly the fifth instance of VWin32, the "Win32 Subsystem Driver" according to DrWatson. It's loaded from the registry as one of the "kernel drivers" -- in other words, it's an integral component of windows.

If DrWatson was able to save the log from the Msgservr32 error, VWIN32 probably isn't in the Kernel Drivers list at that point and that's why Msgsrvr32 crashed -- it was trying to pass information to VWin32 and Vwin32 was no longer functional.

It's a good example of how problems can cascade -- what looks like a total meltdown will turn out to be a single flawed program that is cusing others to crash when it doesn't respond properly.