Re: OT: USB sub-system: more observations and some conclusions
- From: Victor Bien <me@xxxxxxxxxxx>
- Date: Wed, 04 Jan 2006 17:48:42 +1100
William L. Hartzell wrote:
[big cuts]
Before you run off to flash the bios of the windows machine, go to Sourceforge and get the ClamAV program for Windows and update it with the latest AV file. Burn that to a Win bootable CD and start the windows machine with it and scan that windows machine. This could fix the problem without running the risk of having two dead computers.
I will be trying to flash the doze bios to try to fix the problem there but will have to make a bootable CD to do it since with a sick floppy system I might finish up with the doze bios getting wrecked as well!
Such is computing life!
As the following posting to another group shows I think the problem is not in the BIOS of the W computer so I won't be trying to flash it with attendant risks...
I'm not sure that ClamAV would show things which PCCillin I use could miss.
--- Begin OT quote ---
My system is a WinXP Pro SP2 with all patches up-to-date. It is protected by PCCillin which is up-to-date. Scans do not detect any viruses.
Recently I used it to copy a flashbios file onto a floppy to flash up-date another computer. The flash process apparently went thru fine, the Gigabyte QFlash system congratulated me that the process was "successful" but when the mainboard tried to reboot it beeped indicating that there was a problem with it and refused to come up again. The mb was toast!
Poking around in the days following chkdsk found that the floppy used to transfer the BIOS file was corrupt! It had cross linked files!! Doing an FC on the bios file on the diskette with the one on the hard disk from which it was copied showed screen-scrollfulls of "differences"!!! Bugger, hell, damn and all that!
While the computer was in this state it could not format any diskettes. It said that every one of them had a bad sector 0. A freshly formatted diskette from another computer which chkdsk OK would come up with cross linked files after a file was copied in the problem computer and checked again.
Sometime previously I had strange behaviour with the floppy drive when upon clicking on a filename in the Windows Explorer window would cause the filename to get corrupted. In some cases non-ascii characters in the filename would appear in place of the character previously there.
At that time I found the problem was not the floppy drive itself established by substituting it with a couple of other ones. At that time I got the problem to go away by switching the CMOS setting for the FD drive to none, saving it, going back into the CMOS screen and resetting it to 1.44 MB etc.
Now I got the above disaster!
I then did the following checks:
* put an old HD in and booted up to DOS (6.2). Formatting and copying worked OK. This seems to show that my problem is not due to faulty hardware or a problem in the BIOS;
* I reconnected the working HD and booted to Safe Mode and tried formatting and copying. Result OK. Did (does) that suggest the problem was (is) in WinXP normal mode?
* I rebooted to normal mode and tried formatting and copying. Strangely, the problem has gone away!!!!!! Will it creep back in when I'm not watching????
I looked up Google about this and did not find anything. Has anyone else experienced this?
--- end OT quote ---
--
To reply by e-mail edit this address to the correct form: vbien at attglobal dot net
.
- References:
- Re: USB sub-system: more observations and some conclusions
- From: Victor Bien
- Re: USB sub-system: more observations and some conclusions
- From: William L. Hartzell
- Re: USB sub-system: more observations and some conclusions
- Prev by Date: Re: USB sub-system: more observations and some conclusions
- Next by Date: IBM T30 BIOS MiniPCI
- Previous by thread: Re: USB sub-system: more observations and some conclusions
- Next by thread: os/2 cmd.exe loop problem
- Index(es):
Relevant Pages
|
