WHDLOAD issues......

  • Author Author CrazyC
  • Create date Create date
  • Blog entry read time Blog entry read time 2 min read
Now that I write that title I am not sure I shouldnt have worded it differently, but given almost no one reads these blogs except me I shall let it remain....
[EDIT -I have now changed the title from performance issues to WHDLOAD issues, as that is what it has turned out to be]

Anyway....

So I have my nicely setup wedge A1200, with its Indy Mk3, Freeway USB and B1230MKIV. My floppy drive is a bit iffy but I will look at that when I have time and I have an external drive here as well.

I do seem to have an issue with this setup however, and I am not sure if this is because I have just been spolit as both my other setups run full 68060s, or what. Now I have run B1230MKIVs in the past, and whilst obviously not an 060 it has been plenty for what I wanted. The workbench seems quite snappy - no issues there. When I run Igame there is a bit of a delay, but this is a combination of it not being an 060 and also the slow read speeds on the main IDE (1.8mbs per sysinfo - my other machines are a bit quicker). But I can live with that. Where the issue is is that after selecting a game in Igame, it says running whatever in the corner, but basically then takes ages before it accesses the hard drive and calls up the WHDLOAD screen. I mean long enough to question if its doing it at all. The same issue occurs without Igame in the mix, so its not that.
I will play around with disabling the network etc next I think, but am open to suggestions.

Comments

Well, its only an issue when the network is connected. I will attach a snoop dos screen and it hangs temporarily after line 283 and again after line 288.
20230222_190259.jpg
 
I get the same delay when I start iGame but I assume that's because of it reading the games list.

I've just tried it and get a delay once I've selected the game.

I haven't tried it with the network turned off.
 
I get the same delay when I start iGame but I assume that's because of it reading the games list.

I've just tried it and get a delay once I've selected the game.

I haven't tried it with the network turned off.
if you could try with your network disconnected and see if that makes a difference it would be much appreciated- its the pause between selecting the game and the whdload splash screen coming up that seems to take forever - I dont remember it taking anything this long when I last used a non 060 accelerator.
 
WE040 with 3.2.1 OS on 4000D IDE CF takes 6 seconds from saying it's running the game to the splash screen showing on 1943

I'd turned off the Posiedon stack

I'll now try it with the stack on

It now takes just over 7 seconds so not a lot of difference
 
Cheers - Just to check, did you turn off your network or USB? (I dont know about an a4000, but poseidon only does my USB on my a1200) - It was turning off the network that made the difference - it shouldnt take over 60 seconds to go from clicking in igame to the splashscreen coming up which it does on mine if the network is connected.
Maybe there is an issue with my setup then, not sure if the RTC on my B1230 still holds time, dont know if that affects it? I did correct the time and date before testing just in case.
 
I'm currently only using the Poseidon for a USB stick for transferring stuff backwards and forwards
 
I'm currently only using the Poseidon for a USB stick for transferring stuff backwards and forwards
So do you have an active TCP/IP stack running and active when testing? I use Roadshow. Disconnecting via Roadie (Roadshow) removes most of the lag.
 
Actually I have just gone out to the mancave and booted up my checkmate a1200, and having the network online introduces a 60 second delay there as well. I am wondering if its something on the whdload end when its checking for updates. I am sure this delay wasn't there before on that machine.
I might post this over at eab or something.
 
Reading the WHDLoad Docs (unusual I know) it talks about checking the WHDLoad site for updates

WHDLoad is able to use a network access to check if there exists a newer version of WHDLoad and the Slave file specified. All network activity is done using the HTTP-protocol.

Is it this that is causing your delay?
 
It seems to be, but I have used this feature for ages and certainly never remembered anything like the delay I am seeing now, especially not on my 060 based machines. I do wonder if something has changed on the other end of things with the WHDLOAD site.
 
And the answer from Bert (Wepl) himself:
I'm currently investigating this problem.
The problem exists since Dec 21st, 2022 where the shared hosting of whdload.de/net moved to another server. With this move also the http-server changed from apache to ngix.
My current understanding is, that this is a problem of the http-server.
The first connection timeouts. Subsequent connections are working normal.
I have opened a support ticket.
If someone has ideas about the problem please tell...

 
This seem to be an issue again. At least for me.
I have to shut down the network interfaces in Roadshow to be able to start anything with whdload.
 

Blog entry information

Author
CrazyC
Read time
2 min read
Views
1,425
Comments
14
Last update

More entries in Member blogs

More entries from CrazyC

Back
Top Bottom