Killgore

Yes, I can copy patches after each update to each of these folders, modify HFSLIP ini files not once but a few times each time I want to change some settings. I could even apply each of these patches manually after installation of Windows. I only think that when it's possible to automate some tedious tasks it's better to have them automated then not. That's why I started using your tool among other things. And that's why I proposed these changes - it's simply easier for me to maintain one HFSLIP directory structure then four of these. I think that potentially many people can take advantage of this change, especially those that use many Windows versions in the same language. Of course there are many that won't, but in my opinion it's always better to have a choice. But I don't want to force anyone into doing anything. As I said, I can modify script for myself. I only proposed some solution which, I think, makes this tool a little more flexible.

I only meant that it's enough to replace all appearances of SOURCE with e.g. %SOURCE%. OK, but this way you also have to keep copies of all patches in each of these directories in the respective HF directory. When all these windows versions are in the same language and have the same service pack number (and that’s my case) it’s unnecessary waste of space, because all these patches are the same.

It's simple: I have multiple Windows discs (Home, Pro, Eval etc.) in multiple directories and I'd like to update each of them. When input directory is hard-coded into script I have to change name of each input directory to SOURCE before update and after update rename it back to some sensible name. I have to rename output directory also, so I can update another copy of Windows. It’s not very user friendly. Well it's only two "replace all" commands in text editor. In fact I can do it myself, but I’ll have to do it after each update of HFSLIP. And what kind of bloat are you talking about?

Hi! Very useful program. It would be nice if it allowed putting source and destination directory as command line parameters (could be 1st and 2nd parameter). Now there is too much hassle with renaming directories if you have multiple Windows discs. And this way it could be scriptable. And maybe in the future you could implement only updating Windows with new patches instead of applying them all each time you have new update? It could be possible with some flag files with the patch number in destination directory or maybe one hfsslip.lst file in the same directory? Thank you for your great work

Hi! If there is no "DriverPack Graphics C" on CD, BTS_DPs_finish.cmd enters infinite loop, because of this code :DPGB2 IF NOT EXIST %C%S\1 GOTO DPGB3 IF EXIST %S%sisgrp.sys ( %C%S\1\UVGA3.exe -y -o%DPS_TMP% START /WAIT %DPS_TMP%\setup.exe -s RD /S /Q %DPS_TMP% ) :DPGB3 REM #################################### REM DriverPack Graphics C REM #################################### SET C=%DPS%\G\ REM ######################## IF NOT EXIST %C%A\3 GOTO DPGB2 IF EXIST %S%atioglgl.dll ( %C%A\3\CPanel.exe -y -o%DPS_TMP% START /WAIT %DPS_TMP%\Setup.exe /K RD /S /Q %DPS_TMP% ) I guess that, according to Bashrat terminology, it lacks :DPGC2 label after this fragment and line IF NOT EXIST %C%A\3 GOTO DPGB2 should look like IF NOT EXIST %C%A\3 GOTO DPGC2 After this change it worked fine for me.

Hmm, maybe it's because I'm using Polish version of XP? Anyway I'll try starting from scratch. Thanks for fast reply.

... into CD-ROM drive" - I get similar message whenever I install XP on a machine with HD Audio (Intel and AMD). When I press OK installer says that it can’t find hdaudbus.sys. But when I browse to it manually everything installs fine. I tried to locate cause of this error, but I found nothing. hdaudbus.sys appears in TXTSETUP.SIF and dosnet.inf just like other files from KB888111. I noticed that this error started a few versions of DP Base ago (but I don’t remember exactly when). XP SP2 DP Base 6.02.4 and 6.02.5 (I know there is newer version, but didn’t notice anything about this issue in changelog) DP Sound A 6.02 and B 6.02.1 and other current DPs. Can someone confirm this?

Hi! @Bâshrat Thank you for your explanation. It even wasn't necessary, but shows that you are simply polite. As for posting updates of DPs – it’s not that I have any demands of some kind in this area, because I fully understand voluntary nature of this project and appreciate it as it is. Really, thank you for your hard work. @RogueSpear I don’t know what you are trying to achieve with insulting posts like these. I have started only four topics on this forum (listed below), each of them being detailed description of a problem. Even if they didn’t fit into your vision of Realcrap (as you call it) or Via being guilty of every imaginable bug, it doesn’t give you right to treat me like this. Maybe it’s time to look critically at your own reactions and attitude towards other people. http://www.msfn.org/board/index.php?showtopic=66390 http://www.msfn.org/board/index.php?showtopic=64452 http://www.msfn.org/board/index.php?showtopic=62697 http://www.msfn.org/board/index.php?showtopic=62874

@RogueSpear "incomprehensible level of rudeness"??? Did you mean that remark about "no new DPs" after Bashrat post that problems are fixed? If he fixed it I thought he will publish updated DPs, but maybe forgot - hence this reminder. To be honest I'm very surprised with your reaction. Talking about aggression… “at least one frequent visitor to these forums has noticed” And what’s next? Mailbomb?

Hmm, there are no new DPs...

Hi! This bug seems obvious and easy to fix. And now quite old. Why isn't it fixed yet?

Jeez, man, are you trolling? Didn't you read Bashrat post? Burn freaking D or S directory on a CD and run autodetection.

@Seraph: That's what I described as manual method. I'd like something that I could put in a script. "Fire & forget".

I’m starting to wonder whether my question was so hard or so stupid?

Hi! I've already made a short script, that unpacks all DPs to hard drive and runs setupcopyoeminf.exe. My question is how can I force automatic installation and even update of applicable drivers? Because now I have to manually run driver autodetection for each device, which is neither fast nor comfortable. TIA

Hi! I'd like to point out, that it's the same issue that I described here. One of HWIDs is exactly from the same mainboard - K8M800.

Well, I agree with that, but as you see this is not the problem in this case. These mobos worked fine with standard ViaHyperion drivers.

Hi Bashrat! Maybe you noticed but just in case you didn't: In this thread I wrote about the same problem (among other things) with, as I think, an explanation. To make a long story short: portcls.sys is not copied, because there is no code to copy it. In your script only compressed files are copied from KB888111 to i386 directory and portcls.sys is not.

@RogueSpear Well, these mobos don't have any extra features. As for HWIDs - aren't they included in inf file for each driver? And these specific HWIDs were recognized by appropriate generic drivers from chip manufacturer - I had no problems installing them manually.

As for me, disabling sound never helped. Funny, that I also deal with Gigabyte mostly. In this case problem turned out to be quite different than Realtek drivers and I moved it here.

What's your point? Regarding this topic and my first post.

Hi! I did a lot of XP installations (with integrated DPs) before holiday season, some of them failed (freeze after last restart or continous restarts). Every that I had a chance and time to try without MassStorage DP (but with other DPs) succeeded. I attached these HWIDs. Three of them are Gigabyte mobos, one is Biostar. I noticed that K8NE from Gigabyte has the same problem. As you see these HWIDs are from different platforms and it clearly shows, that MassStorage is still very problematic. Method 2, GuiRunOnce, NoKTD. Most current DPs (base - V5.11.8, MassStorage - V5.10). No other modifications. hwids_k8nf9_2.txt hwids_k8nf9.txt hwids_biostar_p4m800_m7.txt hwids_k8m800.txt

Knock, knock. Maybe now, when Bashrat is back, he will refer to these issues himself?

But look at run_me.cmd code. I don't see any place there, where portcls.sys _could_ be copied. In :KB888111 part only compressed files (with .??_ extension) are moved to I386 from KB888111 directory. portcls.sys is also there, but uncompressed, so it's not moved. REM ### The part where KB888111 (and KB829559 to be correct) get slipstreamed. ### ROBOCOPY KB888111 I386 *.??_ /MOV %RS%>NUL ROBOCOPY KB888111\SVCPACK I386\SVCPACK KB*.ca_ /MOV %RS%>NUL

Misunderstanding – I was talking all the time about KB888111 directory in M2\. It isn’t copied anywhere from there during slipstreaming of DPs. So I have portcls.sys after installation, but it’s an old version from sp1 or sp2.cab. This is slightly worrying. Please can you tell me if you're using a plain Windows XP SP2 CD? If you've done any other modifications before applying BTS driver packs then please state. Thanks. The same here. I’m talking about KB888111 directory. And not, I haven't done any other modifications.