View Single Post
  #4  
Old September 21st 05, 09:59 AM
Jeff Richards
external usenet poster
 
Posts: n/a
Default

Perhaps you should start your question over. Is the problem with the IDE
controller or the USB controller?
--
Jeff Richards
MS MVP (Windows - Shell/User)
"PeteV" wrote in message
...

"Ron Martell" wrote:

"PeteV" wrote:

Hi!

Please, if there is anyone familiar with this problem ...

I do have IBM ThinkPad 570/Win98SE with Intel 440 chipset, and now after
a
Windows repair "re-upgrade" round I have lost the Generic Disk Drive
entry
from the Device Manager due to the IDE Controller loading problem.

I have already been loading the current "infinst_enu.exe" package from
Intel's pages and tried to update the Standard Bus Master IDE Hard Disk
Controller, but for some strange reason I have not been succeeding with
this
so far ...

The machine is otherwise in all good working condition, on the net etc.,
but
the USB connection is reacting somehow but not working properly, and
this IDE
controller and the hard drive seem not to be properly installed on
Windows.

Could there be some problem on the Intel's drivers, or some .inf or .sys
or
other small driver part missing, or maybe some problem on the mshdc.inf
from
MS?


Does your machine have a 3.5 inch diskette drive?

If so then boot it up with a Windows 98 Startup Disk (get one from
www.bootdisk.com if you don't have one already) and see if the hard
drive is readable from their.

If it is not then you have a hardware problem not a software one.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm

Hi!

Thanks Ron for the hint, but sorry, the system and disk are working all
fine, the main problem is USB not working and another one the missing
drive
in the Device Manager due to the disk controller prolem.

I have been tracing this so far somehow to some resource conflict on the
Intel 440 dependant drivers, but what may cause this problem ... bad Intel
drivers or maybe the Microsoft drivers involved in this same ...


Best regards,

Pete V.