Code: Select all
ERROR: The specified URL has been redirected to a non-supported protocol
Code: Select all
ERROR: The specified URL has been redirected to a non-supported protocol
Principle of Wadseeker is not different from principle of GetWad. Wadseeker also sweeps preset number of pages, just like GetWad, plus also /idgames archive and wadarchive sites. Wadseeker doesn't go to Google because, as you've all noticed, it's pointless. All in all, both WAD discovery tools rely heavily on site URLs provided by game servers. If server host doesn't care about providing a proper site, then both tools will have problems in finding some WADs.Gul Dukat wrote:Edit: Nevermind, there's wadseeker but I seriously hope bond removes GetWad because it's a very archaic system.
False. Wadseeker does care about this setting.Konar6 wrote:There is a server setting that tells GetWAD where to search for the wad. If GetWAD can't find the wad, it's the fault of the server host and his laziness to properly setup the server. I prefer GetWAD, because Wadseeker on the other hand doesn't care about this setting very much, and instead of downloading my wads at the speed of light from the specified server, it grabs them at a few kBs/s from some generic wad hosting websites.
Also, why would anyone want to download wads over https? Just serve the wad directory with http...
This was done on purpose to circumvent server limitations on simultaneous downloads from the same client IP. Some servers still live in limited bandwidth era where they will outright refuse your request to download a file if you're already downloading another one. This is supposed to block file download managers that circumvent transfer speed limits per download by splitting one file into many parts and using many simultaneous connections to download them. However, it also blocks legitimate users who want to download more than one file simultaenously using normal, web-browser download method.Konar6 wrote:Not that much. If I tell it to download like 10 wads, it gets the first wad from the specified server, but at the same time it searches the other sites for the remaining wads and unfortunately starts downloading them. It should ONLY look at those slower sites if the wad can't be found on the provided site. That''s what GetWAD does.
Why not just check if a particular server does that by trying to simultaneously download more than 1 wad? If it blocks the second connection, then proceed with searching for the second file on other sites.Zalewa wrote:Some servers still live in limited bandwidth era where they will outright refuse your request to download a file if you're already downloading another one.
Have to ask Sean that. I don't do any of the website stuff, I'm... just the Admin guy. Sure, I can do SSH and stuff, but don't know jack about websites. As far as I know, every bit of TSPG is running on HTTPS. I think at one time MiFU did ask Sean to remove the HTTPS from the wad url's at least, but he said it would be too much of a hassle.Konar6 wrote:... Also, why would anyone want to download wads over https? Just serve the wad directory with http...
quality DoomExplorer hackeringFilystyn wrote:Do you know what windows.h is? It's D, DWORD.
From getwad.h:DevilHunter wrote:Konar6 wrote: Which reminds me, someone here (or maybe back in the skulltag era) made an updated to getwad, where it has filters and junk... Called ZGetWad but sadly, it don't work with the new DE as itself has an updated getwad where it grabs bex files now.
Code: Select all
* Written by Hippocrates Sendoukas, Athens, Greece, June-December 2003
* Version modified by Zalewa, January 2009
http://doomutils.ucoz.com/load/doom_explorer/4Doom Explorer updated, version 1.37:
added support for new ZDaemon v1.10 features:
new gamemode Duel (old deathmatch with 2 players is now denoted as 1-on-1)
support new demo format
added new dmflags
added support for https links in the WadURL server parameter (W shortcut)
fixed bug with initial addition of ports
fixed bug with start port in StartServer