Asusprobe startup question

  • Thread starter Thread starter David Wells
  • Start date Start date
D

David Wells

Iset asus probe to auto execute each time in boot up. Now when I start
my system running XP home quite often I get there following


Can't open kernal driver aslm75.sys click ok then it says can't load
asmihwIol.dll and pc asus probe does not load. If I stop it loading
at startup system comes up fine then start ASUS Probe from the start
menu all is ok. Can anyone help me. Appears be a timing thing.
 
David Wells said:
Iset asus probe to auto execute each time in boot up. Now when I start
my system running XP home quite often I get there following


Can't open kernal driver aslm75.sys click ok then it says can't load
asmihwIol.dll and pc asus probe does not load. If I stop it loading
at startup system comes up fine then start ASUS Probe from the start
menu all is ok. Can anyone help me. Appears be a timing thing.
Click to expand...
Yep, I just had this happen to me too on a pair of recent P4C800-E Deluxe
builds (Stay tuned for a build report once it's all bedded in nicely).
But I'd expect to see this on any ASUS board that uses the Intel CSA Gigabit
chipset.

You'll find that for ~1 minute after boot you'll be unable to load anything
like PC-probe, CPU-Z, Speedfan, etc. Some, like PC-Probe generate an error
and bomb out. Others like CPU-Z will wait one minute and then pop up. I
even had the ASUS motherboard CD refuse to autoload in this 1st minute after
boot. A bit of a puzzle! As these were both new machines I'd allocated
quite a bit of time to figuring out any driver issues that cropped up :) and
started isolating drivers and settings.

The fix for me was: The Intel Gigabit driver was set for DHCP, but no DHCP
server was found on the segment it's attached to, so that the driver holds
onto some resource (DMI, Winbond chip?, dunno really) until the OS times out
and allocates the alternate configuration. The simple fix was to set the
Gigabit port to a static address. The Gigabit port seemed to work just fine
provided there was a speedy DHCP server available though. It also worked
fine if it was unplugged altogether - I assume in that case it doesn't even
try to get an address. This was all discovered on a vanilla XP install with
only the Gigabit drivers and PC-Probe loaded - nothing else to interfere
with it.

I didn't notice this issue at first as I'd put the Gigabit port on the cable
modem, where it got an address, no worries! When I decided to put another
LAN card on the cable modem and use the Gigabit port on the internal LAN is
when it started playing up. Easy in retrospect ... but took a couple of
hours, many bourbons and a few WINXP re-installs to nut it out.

Hope this helps ya ...

Cheers,
Anthony
 
Yep, I just had this happen to me too on a pair of recent P4C800-E Deluxe
builds (Stay tuned for a build report once it's all bedded in nicely).
But I'd expect to see this on any ASUS board that uses the Intel CSA Gigabit
chipset.

You'll find that for ~1 minute after boot you'll be unable to load anything
like PC-probe, CPU-Z, Speedfan, etc. Some, like PC-Probe generate an error
and bomb out. Others like CPU-Z will wait one minute and then pop up. I
even had the ASUS motherboard CD refuse to autoload in this 1st minute after
boot. A bit of a puzzle! As these were both new machines I'd allocated
quite a bit of time to figuring out any driver issues that cropped up :) and
started isolating drivers and settings.

The fix for me was: The Intel Gigabit driver was set for DHCP, but no DHCP
server was found on the segment it's attached to, so that the driver holds
onto some resource (DMI, Winbond chip?, dunno really) until the OS times out
and allocates the alternate configuration. The simple fix was to set the
Gigabit port to a static address. The Gigabit port seemed to work just fine
provided there was a speedy DHCP server available though. It also worked
fine if it was unplugged altogether - I assume in that case it doesn't even
try to get an address. This was all discovered on a vanilla XP install with
only the Gigabit drivers and PC-Probe loaded - nothing else to interfere
with it.

I didn't notice this issue at first as I'd put the Gigabit port on the cable
modem, where it got an address, no worries! When I decided to put another
LAN card on the cable modem and use the Gigabit port on the internal LAN is
when it started playing up. Easy in retrospect ... but took a couple of
hours, many bourbons and a few WINXP re-installs to nut it out.

Hope this helps ya ...

Cheers,
Anthony
Click to expand...
I have a asus K8V delux board and a AMD 3200+ chip. Am using the built
in chip for my cable modem. Instead of settting asus probe to auto
exec in the program I have put a shortcut to the program in the
startup folder and this seems to be ok. Will know for sure in a few
days .
 
Just uninstall ASUS Probe. It is a fairly useless piece of software.
Click to expand...
1. Shut down Asus Probe
2. Go to the C:\Program Files\ASUS\Probe\Record
3. Delete all files {Re: 20031231}
Re-start Asus Probe and all should be well.
Cheers



eTrust EZ Antivirus Protection
Version 6.1.7.0
©2003 Computer Associates International, Inc
Major dat file v4008
Minor dat file v5286
Macro data file Mar 6 2004 (VMD Ver 1.6)
 
1. Shut down Asus Probe
2. Go to the C:\Program Files\ASUS\Probe\Record
3. Delete all files {Re: 20031231}
Re-start Asus Probe and all should be well.
Cheers



eTrust EZ Antivirus Protection
Version 6.1.7.0
©2003 Computer Associates International, Inc
Major dat file v4008
Minor dat file v5286
Macro data file Mar 6 2004 (VMD Ver 1.6)
Click to expand...

I when to the above folder but there is no Record directory. I will
just start pc probe after the system boots. Then it seems to load ok.
As if I want it to start up automatically I get the error

Can't open kernal driver aslm75.sys click ok then it says can't load
asmihwIol.dll and pc asus probe does not load. Same as before.
 
Back
Top