Bâshrat the Sneaky

When the C++ version of the DriverPacks BASE is finished, it will be possible to select the drivers (or groups or brands or...) you wish to slipstream.

Yes, everything should be working now (well it seems the UpdateChecker is still broken, but I'll fix that when I get home). Let's hope the hosting keeps healthy the next year! *siggghhhh

Do you have the HWID now? If you don't have it, I really can't fix it!

Sorry for the late reply. Could you please post the HWID for that GPU? When I have it, I can compare yours with the Intel 855 GPU with 32MB & 64MB memory and if necessary, add your specific HWID to solve the conflict.

Eh??? I must have overlooked that one! Thanks for letting me know!

There is no easy solution. Unless there's someone with very good batch regexp skills, I'm not willing to invest my time into such a rare and useless matter. This problem will be resolved by the C++ version of the DriverPacks BASE anyway. Why don't you just create your own mini-DriverPack (check the sticky for a tutorial)? It's not difficult at all! And it makes your installation more manageable and modular: if you create it once, you can continue using it for any UWXPCD you create afterwards.

Do you have administrator rights?

That's right. The DriverPacks BASE is there to slipstream the DriverPacks (or any custom (additional) DriverPacks you made for yourself) into a Windows XP distribution.

Yep, should work just fine.

You *COULD* name it anything. BUT if you want to use the OemPnPDriversPath in the winnt.sif, you're limited to a 4096-character value there. If I had kept the root folder named 'Drivers' (as it WAS originally), all drivers in the part after the 4096 'valid' characters would not be available during the installation. That's the one and only reason. It's also the reason for naming all subfolders as short as possible. So if you want to use the DriverPacks at any time AFTER the installation, do this: -download all DriverPacks -extract them all to the %WinDir% folder -rename the 'D' folder to 'Drivers', or anything else you'd like -download SetDevicePath.exe (google for it, you can find it at http://www.uawiki.org) -execute this command: SetDevicePath.exe %WinDir%\Drivers Et voila, all drivers included in the DriverPacks are now available as Plug 'n Play drivers by default! If you have any more questions... feel free.

It WILL exist in the future.

Same problem here, same solution as muiz.Also, I changed line 48 in the renamed UpdateChecker_V60111.cmd from SET VGA=V601to SET VGA=V6011and that cleared the problem with wrong Driverpacks Graphics_A version. SP Probably I haven't uploaded the correct file when moving everything (I could not simply transfer everything through FXP because the old server's account was suspended. The save_hwids.exe file isn't working either, I still have to upload that one too. When I get home, it'll be the first thing I do.

Please use CTRL+R to do a hard refresh, probably your browser is still loading the error page from its cache. Topic closed & unpinned now.

That's not true. We are on dedicated server for almost 4 years. We just advertise eMaxHosting. Very well, I don't know the details, so please forgive me that error. I've bought an account at www.websitesource.com, because they offered DDoS protection. So far the only affordable host with DDoS protection! And as you can see, driverpacks.net is back online! (for about 36h already)

This cannot be caused by the DriverPacks! Please try to narrow down the issue to one of the other tools you've used!

I've already got a DreamHost account... but I thought I'd better host the website elsewhere, since I've read their uptime & support isn't always that good: they place often too many customers on 1 server. How was your uptime the last year? I was thinking about going with eMax Hosting, the hosting provider for MSFN, nLite, etc.

http://www.msfn.org/board/index.php?showtopic=66062

http://www.msfn.org/board/index.php?showtopic=66062

Currently the server that's hosting the webpages, has been suspended. The reason for that is that there are continuous DDoS attacks, targeted at my website. This causes an enormous load of traffic, which slows down the entire server (thus including all other websites hosted on it). Therefor, my account has been suspended: to prevent other customers from the consequences of an overloaded, malfunctioning server. I'm hopeful that this problem will get resolved in the next 24 hours and if not, I will have to buy some alternate webhosting. Whatever the result will be, maybe someone amongst you could point me to a webhosting service that meets the following requirements: *uptime that's better than 99.9% *hosting service that does not put too many customers on 1 server, which causes the whole **** thing to get annoyingly slow *15-25GB bandwidth/month *PHP4, preferably PHP5 *MySQL (>1 databases) *hosting of multiple domains *possible to use an external domain registrar and point to the hosting service's nameservers My sincere apologies! Though this is not really in my power... (ok it is, but who thought someone'd target DDoS attacks at my website???) P.S.: that's the requirements for the webserver only... I've just bought additional bandwidth (yet another download server). I had ~600GB of bandwidth available each month until a couple of days ago: now it's almost 2000GB (2TB). The 600GB of bandwidth didn't have enough headroom...

When you used DriverPack Chipset V6.01, which components did not properly install?

@feca: I must have forgotten to update one entry in the UpdateChecker. Fixed already. @gilesw: I use it too and it works just fine.

The VIA chipsets and especially their mass storage controllers are known to cause alot of headaches. If you could post some HWIDs, the problem might get resolved!

Thanks for you devoted, detailed log! If you'd only posted the HWID, it'd have been sufficient though But then you know that for the nex time. You must keep in mind that we're using alot of drivers here, that have not completely unique HWIDs (the DEV codes match for the hpt366, hpt370 drivers and several others). That's why these issues exist: the hardware manufacturers are reluctant when it comes to providing drivers that install ONLY for a specific device, often you could manage to install them for other devices that are only partially compatible. That's exactly what's happening here. I'll assign your HWID to the hpt3xx driver in the txtsetup.sif file and then it should be working just fine!

Fixed download link.

Fixed download link.