midiboy

Hi Bashrat, apart from the error in fast edit, which I posted above, here are my observations slipstreaming the new version including the last fix available currently using method 1: First, thanks for integrating my suggestions regarding making files uppercase and asking for the runonceex execution number ! Also, thanks for your continuing work on this. Looks really professional by now .. A few "problems" though apart from the Fast edit error: 1. cmdlines.txt As you can see in the attached pic, I now have lots of empty lines between each of the entries there (that were not there before) AND you seemingly did not check for the existance of an earlier "BTS_DPs_ROE.cmd" entry because I have two now. Other than that, cmdlines.txt is fine. 2. BTS_DPs_ROE.cmd: Still one small error: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001 /V 1 /D "CMD /C %SystemDrive%\D\BTS_DPs_finish.cmd /f" should be: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001 /V 1 /D "CMD /C %SystemDrive%\D\BTS_DPs_finish.cmd" /f The difference is the " at the end should be after BTS_DPs_finish.cmd and not after the /f switch. 3. winnt.sif Winnt.sif suffered the same "empty lines" problem as the commands.txt. There are now 2723 lines in winnt.sif, most of them empty, which is a pain to edit !! There are also now a few new winnt.sifs inside the i386 directory: WINNT.SIF694020180 WINNT.SIF711769655 WINNT.SIF712366540 WINNT.SIF712774935 Never saw them before although maybe I just did not notice them earlier ... 4. BTS_DPs_autocopy.cmd It does not work yet. After setting autocopy to Y and adding the path, it will just quit. I then added "pause" after the robocopy command and the error message was: Invalid parameter #1: "" I tried a few things like deleting the "" or exchanging them with ' ' but I only got other error messages .... I am not trying to boot from this DVD yet, better wait for a fix ... Bye, Alex

Hi ! Just wanted to post the same error thing .... I downloaded the last fix before doing so ... The result ... see pic ... I am using Method 1 by the way Bye, Alex

As a suggestion to Bashrat ... instead of collecting HW ID`s from people and then integrating them yourself wouldn´t it be easier for you (and for us) if you created a script that would let US integrate additional HW ID`s into the driverpack ourselves ? Seemingly you do know how to add those ID´s to the DP, you do know how to modify txtsetup.sif etc. You could ask the user in this script for the HW ID and for the matching controller and then integrate that into the DP. If you want to collect those ID´s to keep your driverpack up to date you could maybe upload the ID/controller combo to your server or ask the user to supply it ... It would be quicker for us and maybe easier for you (less "userspecific" updates ... ) How about it ? Bye, Alex

Hi ! A friend of mine owns an Asus A7V880 board (KT880) containing the VIA 8237 Southbridge and he is having trouble installing windows on the SATA drive connected to that VIA controller. Windows always bluescreens on him if he installs the drivers via F6 floppy method. He tried with the latest VIA drivers and with the drivers supplied by Asus on the mainboard CD. I gave him my installation DVD including the latest Driverpacks (with massstore) but the result was the same. Windows finds the controller during the partitioning dialog and lets him install on that SATA drive but will bluescreen after reboot. The only way he was able to install Windows was to install on a PATA drive, then install the drivers in Windows and then clone that Windows installation to the SATA drive. Would it help in this case if I gave you his HW ID´s or is this another problem altogether? Thanks for your help ! BYe, Alex

Hi Bashrat, another small problem: THis line REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx /V TITLE /D "Finishing BTS DriverPacks" won´t overwrite an existing entry as you predicted, however it stops the installation and asks if it should overwrite or not. See picture Bye, Alex

Since your are downloading ... there are newer drivers available for the Nforce 4 chipset: Driver 6.53 And speaking of Nforce 4 ... does your LAN driverpack install the Hardware firewall for the nforce 3 and 4 boards that comes with the nforce drivers ? Bye, Alex

Hi Bashrat, it is Alex aka midiboy I am testing your new fix2 as we speak ... just a few minor problems again: 1. Your script now added TWO entries of "BTS_DPs_ROE.cmd" into commands.txt. I think one is enough 2. Your "BTS_DPs_ROE.cmd" does not work YET because you need to drop the "" at the beginning and end of each command. It should read like that: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx /V TITLE /D "Finishing BTS DriverPacks" REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001 /VE /D "BTS DriverPacks: finishing..." /f REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\001 /V 1 /D "CMD /C %SystemDrive%\D\BTS_DPs_finish.cmd" /f 3. PLEASE ! Could you please add a small routine to ask for the execution number ? Your number 937 will not work for me because Wihu runs before that and then reboots the PC so your number will never be executed or be interupted. So I would like to use number 001 for that. It would really be nice if you could ask the user for the execution number ... Anyway, thanks a lot ! Bye, Alex

No problem, I will. As for the other problem I had when filenames were not all uppercase ... you did not comment on them ? After all this problem makes the installation useless. I think you might argue that this is something that should be handled by the image/CD writing application or would you consider writing all filenames you changed/added in uppercase to avoid any problems ? Seemingly Windows is very sensitive to that and does not find files that are not all uppercase ... Bye, Alex

This works but ONLY from runonceex.cmd directly, not when started in commands.txt Bye, Alex

Hi Bashrat, will you include the latest Intel chipset drivers 7.x in your next update (instead of the 6.x drivers) I am sure you will, just asking ... Also there are new massstore drivers available for the ICH7 southbridge I think ... Bye, Alex

Hi again, I THINK I know why it did not work. I will be testing this shortly. I guess it did not work because you did not add the CMD /C command to the command like this: I am gonna test this now and report back soon ! Bye, Alex

Hi Bashrat, a "small" observation .... if you modify the winnt.sif you seemingly do not check for existing entries ?? Look at my winnt.sif after your dp integration (see pic) There are now 3 double entries ... The first ones are from me (initially). The second ones were added from you. It still works but why not simply leave the entries as they are if they are there already ? Bye, Alex

HI Bashrat, I though I might continue the discussion regarding your runonceex support here ... it does not work. I have tried two times now ... The first time I left your entries in command.txt the way you set them. The second time I edited your third command to the correct path: Both times it did not work. No entry in runonceex was made and I also did not see the "BTS DriverPacks: finishing..." entry togethere with my other entries ... I am guessing here, but maybe you are not allowed to add those commands to command.txt ? Maybe you have to add them to runonceex.cmd directly ? All my other commands inside runonceex.cmd get processed. But please, if you add something to an existing runonceex.cmd could you ask the user for the execution number in the script before simply adding it as 937 ? Thanks, Alex

Hi ! Those are my settings: I am using the -d switch (that prevents the forced conversion from lower to uppercase) because I don´t want all my various folders on the DVD to be converted to uppercase if just Windows needs that for the i386 folder. As far as I know, Windows needs uppercase. But if my settings for cdimage are wrong, please tell me. I am not using the "-j1" switch either (as most people will probably use) because that would convert all my long filenames to 8.3, right ? In the meantime I have also confirmed that the "broken txtsetup.sif" problem that happened if I install the driverpacks a second time is also happening only if I do not convert all files to uppercase again after each integration of the driverpacks. txtsetup.sif was lowercase after integrating the DP´s a second time, probably thats why Windows did not find it .... Bye, Alex

WAIT A SECOND .... I just found the reason for my first problem (the missing dac960nt.sys). I have looked inside the i386 folder and the dac960nt.sy_ was in there. However, contrary to most other files inside the i386 directory, it is NOT in uppercase but lowercase. If I leave it like that, Windows Setup will not find the dll. If I convert the whole i386 folder to uppercase before burning the DVD, THEN it works!! I will now test if it still works fine if I integrate the driverpack again a second time (before that would corrupt the txtsetup.sif) Bashrat: couldn´t you add a command to your script to convert all changed files to uppercase. I am using a utility called filecase.exe for this: Bye, Alex

Bashrat: I think you are mixing up things. I did not have this error, Bam did. I have written a long post on page 2 of this thread. Please read that again ! I have a much more serious problem with your driverpack (massstorage an/or base) and I have tried the whole integration process 4 times already ! (twice from a fresh i386 folder, twice with the pack integrated): THe first time Windows setup breaks up because it reports that dac960nt.sys is missing, and the second time it breaks up because my txtsetup.sif is broken. I have attached this txtsetup.sif in a post on page 2 of this thread Bye, Alex

Hi Bam I did just that. I reedited my post. But this confirmed that this is an error with the DP´s installation. I started again from a fresh untouched i386 folder. I then applied the driverpack once. The result was that setup ended because dac960nt.sys was missing. I then applied the DP again and then the txtsetup.sif ends the way I posted it. Bye, Alex

my txtsetup.sif after 2nd driverpack integration

HI Bashrat, I integrated all your driverpacks into my DVD for the first time today (you may remember my observations thread). I am having a serious problem: Windows XP has a problem with the txtsetup.sif after the integration (this is with VMWare 5). Translated from German the error message was: The inf file txtsetup.sif has errors or is missing, Status 14 Setup cannot be continued. Txtsetup.sif is there however (in the i386 folder) This is on a German Windows XP with integrated SP2. I have first installed all your driverpacks from today, then I repeated the whole thing because I did not integrate your fix for the 5.05 basepack. EDIT .................... I tried everything again (this time without the "double integration of the DP´s) and now it worked fine (the error did not appear) However, now I get the following error message during the first part of the setup: The file "dac960nt.sys" could not be found .... After that setup ends. Can you fix this please ? EDIT 2 ............................ I now repeated the integration of the DP´s again and guess what, the first error message appears again ( txtsetup.sif is broken or missing, status 14) So it seems this is a bug that can be reproduced ... On the first DP installation the file dac960nt.sys cannot be found. Then, if I integrate the same driver packs again something goes completely wrong, rendering either the txtsetup.sif or anything else useless. I am just glad I have a backup of my i386 folder so I can go back to the start. Seemingly the "removal" of an earlier MassstoreDP does not work correctly yet. Do you need any help from me to fix this ? Bye, Alex

Hi Bashrat, I have succeeded in integrating your driver packs into my DVD. Thanks, you did a great work, honestly ! Here are a few observations I made during the process ... maybe you can change that in future revisions if you feel those are bugs or not the optimal behaviour: 1. In your Knowledgebase on building a driver pack you mention: That should be "D" I guess. I am sure it is just a typo because the image below shows "D" ... but I followed your guide and ended up with DP, which of course was not working. 2. I am using Method 1 (please keep it) and I decided to use the RunOnceEx method to install the various Control panels in your script. This decision adds the following in my command.txt: That would be fine IF I did not already have a RunOnceEx.cmd. I do have one so your additional lines (especially the first one) will probably overwrite mine ? No ? Just to be safe, I deleted those lines and added them manually to my runonceex. There is another problem: You specified a very high execution number (937) probably to be sure to come as the last command. However, this is not good for those of us who use tools like Wihu as the last command to install more software and/or users. Those tools will reboot after they are finished so your last command will not be processed or maybe interrupted. Maybe it would be better to use a very low number (000?) ... I guess many people will start their numbers with 1 ... but of course I have no idea WHAT people use ... You could also ask the user for that number in your script maybe ?? Last thing ... are you sure that Windows will find the "BTS_DPs_finish.cmd" using the above command ? After all, this cmd is inside the folder "D" which will probably end up in %SYSTEMROOT%\D during installation ... If you do not specify the path to that cmd how will Windows know where it is ? Have not tried it yet though ... 3. I decided to not keep the driver files after installation. Your script then added a cmd file named "BTS_DPs_cleanup.cmd" again inside the "D" folder: Why the third command ? That file got deleted already anyway duing integration of your driverpacks. (from my install location) I don´t understand that command inside this cmd. If I am installing this DVD on another computer that path will not even be there ... Thats all for now .. Gonna try it out now ... Bye, Alex

Never mind, I did the whole thing again and now it works. I have the feeling the error was because the WIN51IP*.* files were not in big letters .... could that be ? Anyway, works now, Thanks, Alex

Hi Bashrat, well, I don´t have a SIS chipset board but I have noticed that SIS released a few drivers lately that could not possibly be on any Windows XP version yet because they were released after SP2 came out. For instance, on the Sis Download Page you can see at the bottom (under top and latest downloads) that there is a new AGP GART driver dated April 2005. Also there are various Audio, Wifi and Lan drivers there but I have not checked if you have them integrated in the relevant driverpacks or not. Bye, Alex

HI Bashrat, fair enough :-) Keep up the good work ! Bye, Alex

HI Bashrat, are the various SIS chipset drivers (AGP etc.) integrated in your Chipset drivers ? I don´t think so. Any reason why you left them out ? THanks, Alex

Hi Bashrat, I am just starting to integrate your driverpacks into my DVD so I may not be worthy of posting a suggestion yet but it came to my mind so I thought I might give it a try. Currently updating your driverpacks is not as straight forward as it (maybe) could be if you changed a few things ... 1. If you did not change the name of the driverpacks with every new release but simply named them "Driver_Pack_Sound_A.7z" (without the version number) then one could simply download them and thereby overwrite the earlier one without having to manually search for the old one and then delete that. In doing so you would also not have to manually edit the download links each time you update one of your driver packs. 2. You could integrate the downloading of newer driverpacks into your update.cmd similar to the downloading of the base pack. 2 is just a bonus, but 1 would really make things a bit easier (for your and us I guess) Thanks for your work ! Bye, Alex PS: I did not find much information on how Method 3 works and what it´s advantages, disadvantages are ....