Bâshrat the Sneaky

ATM codejunkie's solution a few posts higher is the best I have to offer you

@simpleman: I hope to release them Saturday. @imdos: if you'd say what method you using.... and what problems did you have? (sorry, but I don't keep a log of each user...)

Unless you need a higher compression ratio (smaller files), you could use hp38guser's compress.cmd That would be the easiest solution.

Your txtsetup.sif entries are NOT correct, it should be: [SourceDisksFiles] UlSata.sys = 1,,,,,,4_,4,1 [HardwareIdsDatabase] PCI\VEN_105A&DEV_3375 = "UlSata_xp" [SCSI.load] UlSata_xp = UlSata.sys,4 [scsi] UlSata_xp = "Maxtor SATA/150 PCI Card" You'll see it works that way

It's not normal... it should be fixed in the next version of the DriverPacks BASE.

63%, to be correct

Fixed that Larger lists of devices would be very nice and welcome, if it's not asked too much. Regarding that ATI card in that laptop: that's possible, and I can explain it: ATI Mobility Radeons aren't supported YET. In the upcoming version they will be supported! P.S.: I guess that's written correctly (merci voor de aanmoediging - thanks for the encouragement )

hehe You should include those drivers as any other driver using the OemPnPDriversPath in your winnt.sif. This only happens since SP2 and in fact it's a bug if I remember well. This heavily relies on my not-so-top-notch memory, but I think there was a hotfix available for it, though only available for 'gold members'. I think adding the monitor drivers would be less work.

@Toolman: what 'fixes' do you mean? Thanks for the submit. @Telenut: great! The GPU of the Dell Latitude is an Intel onboard graphics one? There is no progress bar indeed. But it will come customizable, fancy if you'd like... but that's not for now... @anonim1979: I've been thinking that for some time now. I'll make that one too. It would be the tiniest DriverPack anyway @all: Unfortunately I did not manage to get everything online by tonight... Because my webhost is down AGAIN. I'll try to switch within a month (the current webhost contract expires in 2 months), not only you, but I too, am sick of this uptime-nightmare!

@besnia: you're welcome @codejunkie: But for some it DOES work :s Have you any idea why it isn't working? And please note that your AutoIt script will ONLY work for an English version of Windows XP! (Would the word 'Hardware' in the title be kept in all langues? In that case that could solve it...)

Start with reading this part of the guide!

@ZileXa: driver.cab (or an alternative cab file) is no option because many filenames are identical... it just wouldn't work. What SetupCopyOEMInf.exe does? Check this topic for detailed information. @Cartoonite: thanks And I doubt the D-Link ethernet adapter and the SB Live! 5.1 would be supported. And without DP Graphics A you would be stuck with an ancient driver for your ATI Radeon 9200 (Not that it would make much of a difference for that 'hi-end' card ) I agree with your last point

Could you please make a list of removed components/services? Or maybe better in this case, a list of which are kept? Nice work

I'd be amazed if the commercial price would be so low If you also need to split up the network - which you probably don't have to - you could of course simply but switches in between... But I think you already knew that...

You are using the 'KtD' function, right? Please disable it for now... A work-around for that problem still has to be found... Though it is working for some of us :s

1) That's normal. But you don't have to reboot... Just restart explorer START explorer.exe As a test, you could do this: end explorer.exe in Task Manager and then using the 'File > New Task (Run...)' menu to enter 'explorer.exe' and you will see you will get your desktop back 2)-taskkill is included in Windows XP by default -pskill is a more advanced version of it and is part of the PStools, which includes several other very useful command line tools.

It might be useful for you to read the guide first and then post questions... You'll see that it is very easy

Me? None mate. I'm trying to create something myself. <{POST_SNAPBACK}> In that case... You might have want to read the first post.... there you'll see schalti has edited his post and has targeted Pyron's executable versions of schalti's scripts. They can be found here.

LOL Didn't notice though

I agree with Zxian. It has to do with signal interference and not high enough signal strength for such distances. If you could use more power on the cable, it might work just fine. Only you'd have to hack your NIC for that

Welcome to MSFN, Styxke (where are you from? - I mean which city) @both of you: which versions of the DriverPacks are you using? The latest, I presume???

Not exactly I'll label it as 'UNKNOWN' then :)

If you use method 1+KtD, then it will *only* (lol ) be ~250 MB...

I guess you could. But there are also Chipset, Graphics and Sound DriverPacks

It deletes everything in C:\ Who told you to use that?