WHDLoad problem

[starf81]

Ok, thank you... but it was already set on 15khz.

[starf81]

I've restored a backup of some days ago.
It is the same backup from which I've recovered folders during my tests... well, now WHDLoad works.
I've tried to recover folders from my latest WB (the one that doesn't work). I've copied C, S, Prefs, WBStartup and WHDLoad still works!

So... now it's ok, I'd have discovered what was the matter but I had no success.

I'm going to backup again my sys partition...

[starf81]

Another news: after restoring sys partition as described in my previous post, everything worked well.
After I've launched MiamiDX but it coudn't go online (it happens sometimes, I've to reboot and try again 3-4 times). So, I've rebooted and WHDLoad doesn't work again!
I can't understand why the stack creates conflicts also after rebooting. WHDLoad has been the first app I've launched.

What has done MiamiDX???

[starf81]

Another news again... this is THE DEFINITIVE one!!!

I've discovered the cause: the Ethernet cable!

It is an absurd story.
If the is connected, WHDLoad will not work.
If the cable is NOT connected, WHDLoad will works perfectly.

Does anyone get similar behaviours?

I know that stack TCP/IP could create conflicts with WHDLoad but I can't understand why it crashes also if I don't start MiamiDX. Just a connected Ethernet cable can hang up the program??