Bâshrat the Sneaky

Are you guys still having download problems?

Err... It's working here... EDIT: just retried... and things are working just fine here! Can anyone else confirm the working/not working of the new UpdateChecker?

**** that! The main downloadserver went offline for a moment yesterday (DDoS attack, MSFN was hit too), so I moved the files to other servers. Apparently I entered the server's ID not correctly, which caused this.... Problem solved now. EDIT: problem was solved 2 hours 15 minutes ago.

Yes, this is your root. Check this page for detailed info about RunOnceEx (ROE). GUIRunOnce is in fact the same (it gets executed concurrently with RunOnceEx), but it has no screen output. Short & simple: a HWID is used to identify a type of device, i.e. this is NOT a unique ID for each device (so not like the MAC address of a NIC). example: PCI\VEN_0A1B&DEV_2C3D&SUBSYS_4E5F&REV_06 => PCI device => VENdor's code: 0A1B => brand e.g. ATI, nVidia, NOT ASUS, Point of View, Sapphire => DEVice's code: 2C3D => the device e.g. ATI's RV350 = 9600 series => SUBSYS' code: 4E5F => the device's subsystem: again a device is split up in more categories, this can be a small adaption to the original device or a device that's been built/optimized for a specific brand (e.g. ASUS, Sapphire) => REVision code: 06 => the device's revision I hope this cleared things up for you!

Errr... is to late to still sign up?

What do you mean by this? It does not work for the 6.66? Which version did not work for you? The older ones, I presume? Since they did not yet have that filter driver...

OK, it seemed the download server is down now :'(... I thought I finally had reliable hosting, but some ghost seems to be stalking me!! :'( All DriverPacks have been moved to alternative servers. (exception: DriverPack Graphics B: still uploading, 60% complete)

G*DDAMNIT For some odd, unknown reason this server has WENT OFFLINE! I assure you, the admin will hear my opinion on this one! I'm FURIOUS! :realmad: @kelsenellenvian (or something like that, I thought I had a long nickname...): Please contact me, I can temporarily upload it to another server, I just didn't download WPI 3.6.1 yet...

The unnamed feeling - Metallica is also a masterpiece!

Please post your HWID!

Then you've installed a utility that disables your referers somehow. Or masks them...

I forfilled my promise right away: the new UpdateChecker is up and running (No changes required to the current system!)

@muiz: errrr.... how in the world is that possible! I downloaded that driver the day before I have put DriverPack CPU online! Well.... I'll just update it.... :wacko As for the updating mechanism: that is still dependant of the DriverPacks BASE, i.e. I have to update the DriverPacks BASE if I want to update the 'Updater'. In another post somewhere here I already said I'd change this. So soon you'll get rid of this annoyance!

Could you please tell me on which motherboard this is? BTW... the 'hpt3xx.sys' driver is being used by default... NOT the rhpt3xx!

Well... if you really want to leave this board, you could ask to be banned. In fact I've always been thinking someone would post something like you just did, someday. That day has finally come. I know this project looks not professional at all. But what do you expect? This is not an 'obligated-pay-project' and therefor I cannot guarantee consequent updates, consistency etc. If I'd have asked you to pay let's say EUR 500 for a one-year license... then I'd give you the permission to come over to my place and beat me up personally. But did you (have) to pay such a sum? I didn't think so. And I KNOW that there are many projects also free-/donationware that are stable and have outstanding documentation & support. But... then you have to be honest at all fronts: can you possibly compare those projects with this one? As for the 'programming' part: YES. And I admit it, there have been too much (read: alot) errors that should NOT have been there! As for the 'content' part (the drivers themselves): you CAN'T compare this with any other project... As you know, the one problem that will probably never be solved, is the one at TEXTMODE setup: the mass storage drivers. Never be solved? That's right! With adding/updating one driver, another one will not work properly anymore. BLAME THE VENDORS! It's not that I'm a magician of some kind.... I wish I were... I've spent countless hours on this project. So please if you criticize me - I've got no problem with that - involve all aspects of the story. If you were trying to save money by using my Driverpacks, then you should have taken in consideration that this still is a relatively small project. You are a professional, having alot of problems with the DriverPacks. There are other professionals here, having few problems, too! And last but not least: as you said "So, a big thank you to all of you guys here and your help!!": why would you like to delete your account here then? I hope I gave you a complete answer and I'd be pleased to continue this... discussion. It can help to improve this project. P.S.: where is the documentation 'bad'? What is missing?

m for mobile 2 for 2k/2000 x for XP the code after that is set by the driver itself errr... the file is included... it's the same as atioglxx.dll (drivers are NOT case sensitive when it comes to filenames)

Update is complete. Will be put online tonight.

Get the driver out of the original Windows XP installation disc. Then add it like any other driver or by making a small DriverPack... Nothing special is required I think. EDIT: Though, if you want to use it DURING setup, you'll have to slipstream the driver as if it were a mass storage driver!

Wow 500 already NICCCEEEE!! :) <{POST_SNAPBACK}> 750 and still rising... (with that .1 update of you ) P.S.: you still have to update your sig!

How are you trying to download? You have to click the download link, otherwise it just won't work! (Hotlink prevention... )

Do you also know whether this forces the specified .inf file to be installed either there is a compatible HWID or not? If it just gets installed when it's necessary, then this might be a great solution! P.S.: where did you find the information about this method???

There is no fix (yet). Checking now. EDIT: the files ARE included. I think the problem lies in method 1's CAB compression in the DriverPacks BASE. Maybe it handles filenames with only a 2 character extension faulty. Checking that now.

You removed it with nLite... So nlite your UWXPCD again, without removing the floppy driver!

There's nothing wrong with it... You just left it the way it was, THAT's what's wrong! Remove these lines REM +=======================================================+ REM | Prepare later installations (optional) | REM |-------------------------------------------------------| SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY%\998 /V 1 /D "%CDDRIVE%\OEM\bin\t-13_install.cmd" /F REG ADD %KEY%\999 /V 1 /D "REG ADD %KEY%\zzz999 /V 1 /D %CDDRIVE%\OEM\bin\postinstall.cmd /F" /F REM +=======================================================+ If you don't want that pop-up anymore that you mentioned in your first post.

Try my DriverPack MassStorage and you'll have to use the DriverPacks BASE to slipstream it in a painless way. Read more about it at http://www.BTSunattended.net/Projects/DriverPacks