Siginet

There are programs which will help you change the system drive letter. I don't remember which app it was though. But there is a way to fix it I am sure.

Or newsgroups would be even better.

I think all you need to do is extract the drivers with 7zip. You shouldn't need to run the slipstream. I don't know if my PathChanger.exe works or not. From what I understand of SetDevicePath.exe my app should work as stated... but I haven't had the luxury of anyone testing it for me. hehe. I tried it myself... but I got tired of waiting for the drivers to install... it was taking a long time to search. But in theory it should work.

I can confirm I have wittnessed this error as well. I thought it may have been something I did wrong. But now I think it is an issue that should be looked into. I didn't try method 3 on that computer. I don't have that system anymore so I can't be of anymore help. sorry.

if($bashrat_the_sneaky = 'back'){ $finished_his_exams = 'true'; $behind_his_pc_in_an_almost_obsessive_way = 'true'; $expect_updates_soon = 'true'; } if($finished_his_exams = 'true'){ $test_scores = 'A+'; $driverpacks = 'perfection soon'; $need_to_get_drunk = ' '; } I finished the script 4 ya Bashrat. Just my way of adding some support! BTW: Smilies do work in scripts right..!!??

These methods would allow you to point to the driverpacks as the path for windows to search for drivers. So if you needed to install an ethernet driver you could set the path to the lan directory containing all of the ethernet drivers. Isn't that what you were looking for? If not... can you be a little more specific? I'm curious as to what you want to do.

I think this post will help you. Here Also my tool Driver Search PathChanger.exe may come in handy as well... as it basically does the same thing... but gives you a simple gui interface. You can find a link to it in my signature.

@gilesw What is the CRKXProject.7z about? And did you know the downloads have a .z instead of a .7z? What would I have to do to edit the registry if I come into a modem issue like you stated? Thanks for releasing these extra packs. It would be nice if more people would help release packs like this. I will help test your packs and when I get back from vacation I will help you make more packs if I get some free time.

Yeah... I relized I only named the zip file cmdlines_fix.zip But please grab the new version. It should work much better... and it can be run from a script within another directory. without having to use "CD /D $OEM$" The new one will make an exact copy of the original and place the BTS entries to the top. Instead of the 25 line limit of the old one.

Hehe... actually the original name was cmdlines.exe there was a flaw in it so I released a second file to bashrat called cmdlines_fix.exe so that he would not mix them up. Bashrat is welcome to name the file whatever he wishes. BTW I am attaching the cmdlines.exe file with a new icon for anyone who wants it. You must name it cmdlines_fix.exe to be compatable with Bashrats script... but the file can be named anything Bashrat wants to name it. Also... the cmdlines.exe file should be getting deleted anyways. It does not need to be on your disk after it has been run. So the name of the file doesn't make a big difference either way... except for the fact that it needs to be named whatever Bashrats scripts are calling. If it is not getting deleted then there is a problem somewhere. Please check the cmdlines.txt file inside of the $OEM$ directory and post what it has inside of it. It should look simular to this: [COMMANDS] "BTS_DPs_ROE.cmd" "RunOnceEx.cmd" With "BTS_DPs_ROE.cmd" as the first entry. Edit: I have actually re-written the cmdlines.exe code. It now does an even better job. @Bashrat please add this one to the next release. @All you may use this cmdlines.exe file instead of the current one. All you have to do is extract the .zip file attached, then rename the .exe file to "cmdlines_fix.exe" and overwrite the one in your "M2" folder inside the "UWXPCD_ROOT" folder created by the DriverPack_Base. Let me know if it has a problem. dp_cmdlines.zip

I will change the icon. I was thinking the same thing as well. I only used that icon because it was the only one I could grab quickly at the time. The icon dosen't fit it anyways. I'll post a new one later today. BTW... the cmdlines_fix.exe file should be deleted after the DPs have fully been integrated. If it is not deleted then the integration may not have finished correctly. I think Bashrat has it dumped to the root... then later deleted after it has been used. When I get time I'll look into it. What method are you using? Because when I use method 2 it gets deleted.

I'm not positive yet... but I think there may be missing entries in the dosnet.inf file... because the first time I tried to boot I got an error that it could not find "hptmv6.sy_" so I placed it in my boot folder... then I got the error could not find "RHPT3XX.SY_". When I placed this in the boot folder setup seems to run fine so far. I am not positive this error is caused by the driverpacks. It may have been caused by bootfolder.exe. I am doing further tests to find the problem. Just thought I would post to see if anyone else notices the same issue. This error would probably only show up if someone uses winnt32.exe to install... or is createing a multiboot disk, as am I. Edit: Dosnet.inf has 2 instances of "hptmv6" but I belive they should be "hptmv6.sys". Also "RHPT3XX" is nowhere in the Dosnet.INF file.

Is this pack still available anywhere? I clicked the link but it didn't work for me.

Great! Now I finally have something to do! LOL! I have been waiting for the new release impatiently. lol! Thanks BTS! and thx for the thank you too. But you are the genius behind it all.

Ummmm.... Maybe you should post a screenshot of what you have.

From what I understand... he will have 2 versions of the DPs. One for regular users who use it for personal use etc... which will be free. And one for company's to use which will cost. I think Bashrat deserves any profit he makes from it. He has done a lot of hard work on it.

He is studying for his finals. So he had to postpone the next release. He may be releaseing a new version very soon.

@Bashrat Just a suggestion... if you release the DP without releasing the base you could always use letters instead of numbers on the release. For instance: Driverpack Lan V5.05.1a Then when a new base is released you could go to the next number.

I would be interested in getting a copy of the dell pack that you create when it is finished. Sounds like a good idea. Dell drivers are the ones that I seem to have the most trouble with when using the previous driverpacks.

Great indeed! My mouth waters with anticipation!

I plan to add many things to this program. I have never used Xpize... but I will try it out and see if it can be used in PowerPacker. What I did do to help people add certain things is I put a section called "Extra Files". Inside of "Extra Files" is a section called "Extra Pack Files" with it you can easily add extra files into each "Pack" (Read the help file for my definition of "Pack".) Another section in there is called "Extra Root Files" which you can use to add files to the root of the entire package.

It is definatly a false positive. Som antivirus/antispyware programs will call just about any script a virus/spyware. Panda is one of them. Panda sees that my program is editing files and it is flipping out. Just tell panda to allow it and you shouldn't have any more popups from it. I use symantec antivirus and it doesn't do that.

I am currently in the process of testing a tool that I made to help people install RyanVM's XP Update packer. I was wondering if I could get some of you to help test it out and bring some suggestions/comments? I think we have worked out all of the major bugs in it... but I'd like to know for sure. This tool will also help people install Ryans XP Update Pack unattended. Once this tool is 100 % functional... I will be adding it to my Windows XP PowerPacker program as well. The beta thread for the tool is at RyanVM's forums in this thread: RIGHT HERE Or you can directly download it from: HERE The tools I make are my way of saying thank you to MSFN.ORG and it's many helpful members!

I have noticed before that in XP SP2 when you can not optain an IP through your nic that boot times get a lot longer. That was a flaw in SP2 that I used to hate. But we are talking about 2003. I'm not sure if that pertains to 2003. BTW... So do the driverPacks work well on 2003? I never tried that.