Am I the only person not smart enough to gain access to the UUP Dump website. I times out and says 'Non-reachable.'
at Paul Mercer, If I continue not gaining access to UUP Dump, I saw your sight as an alternate for UUP files. I noticed you upgrading it, is there anything I should know about accessing/using it in an idiot proof way? I can't even spell UUP. THANKS
@luzea , uupdump website speaks ERR_CONNECTION_TIMED_OUT now. I use uupdump local server too, but I wish website work well.
I wish someone could fix UUPDump. It takes at least 30 seconds to time out. Paul Mercer just said his local server could easily take 10 minutes or more to give results
It was kinda-like that, Post 5154 " ...~40 builds from Windows Update in ~10 minutes, ..." You didn't use the word "easily", I did. Bad use of an artistic license. I forgot to thank you for the instructions on the way to do it. Thank You.
take 10 minutes to bring builds information and finish the fetching process. Then you can use the Local Server the same way you used the website that is now offline.
i'm new to the uupdump server after i run update.cmd and when i try run.cmd i received this message Parse error: syntax error, unexpected 'private' (T_PRIVATE), expecting variable (T_VARIABLE) in C:\Users\sa****\Desktop\dev-server-master\dev-server-master\src\api\shared\cache.php on line 22
I was thinking how to speed up builds auto fetch with uupdump-get-fileinfo+packs.cmd script first run might be too long for new users, so it's better to fetch fileinfo only how it works now: 1. run packsgen.php first to get packs - new users are not affected because database is epmty, but useful if WU is unstable and packs weren't generated previously 2. run fetchdetect.php to get fileinfo and packs for that build - very long operation, new builds should be processed one by one so, here's the plan: 1. run packsgen.php first to get packs - new users are not affected because database is epmty 2. run fetchupd.php to get fileinfo only - this step should be much faster, you can see a lot of builds in DB after a minute or so 3. run packsgen.php again to get packs - all stuff from the 2nd step will be generated (5-7 minutes), but you can close it and generate metadata manually on the website with one click second run of uupdump-get-fileinfo+packs.cmd: 1. run packsgen.php first to get packs - if user closed the window then all packs will be regenerated at this step 2. run fetchupd.php to get fileinfo only - fast check of new builds if MSFT released something new I think it would be better for new users but the trade off is overall it's faster to get fileinfo+packs at the same time in 7-10 minutes with fetchdetect.php
Maybe just uupdump-get-fileinfo.cmd to detect builds, then the user generate metadata manually on demand for his chosen build and uupdump-generate-packs.cmd to generate metadata for all builds in database
users want all in one solution because they're lost in 3 scripts uploaded v1.5.1 with changes above for now
Actually that can be in that GUI cmd we discussed when this all started, where you can setup the server with the desired UUP packages?