Search options (Page 3 of 4)

I'll be work on this today. If I can get the laptop up and running, I'll get you guys the HWIDs.

I attempted the suggestion to disable onboard sound. Unfortunately there is no such option in my BIOS settings.

I remember something similar happening with this same laptop back in '07. It's the reason I decided to only slipstream textmode drivers. I kept getting blue screens and whatnot when I tried the full pack(s). I got it working last time by finding my original hologram OEM disc and installing that. I can't find that anymore. If I do find it, is there anything off of it that I should send to you guys?

What do you mean by this? I posted a PhysX installer a couple weeks ago and noted that it follows "RogueSpear's multimode installer" standard. Is that what you're talking about? Or did he actually make one of his own as well?

edit-
Here is the one I posted: http://xp.xpdnc.org/PhysX.exe

That should follow the same [ -ai / -ai1 ] syntax that RogueSpear has in his installers. I don't have an nVidia card to test this, but if you have any issues, let me know and I'll see what I can do it.

Doing an admin install and recompressing with 7zip reduces PhysX file size. It went from 32.8 MB to 8.36 MB.

Download: http://xp.xpdnc.org/PhysX.exe

It could be reduced even more if one were to take the initiative of removing runtimes and whatnot as well. There are also some redundant text files (which would yield infinitesimal differences in file size) that could be removed if one felt like tidying up the installer. I'm not one such person as I don't own an nVidia card, nor would I even be using the PhysX drivers if I did have an nVidia card.

I just read your post in that other thread. How dare you berate me with accusations of "diminishing" people's work after your behavior in this discussion.

Plus it incorporates RogueSpear's naming scheme and doesn't require that I use DriverPacks BASE to do it.

I didn't care to address M1 because I don't use M1. Besides, M1 utilizes the $OEM$ folders, which is what I prefer to avoid. This code wasn't written for DriverPacks, necessarily. I'm offering feedback on how I improved presetup.cmd, and I'm not positing this as a request to add my code to your program (to be honest, I wouldn't want you to do that anyway since that would also likely require my assistance in modifying code in the future).

This also has many more fail-safe methods for individuals that shift their files around and like to customize their layout a bit more than what DriverPacks allows by default. Rather than having to modify Presetup.cmd directly, it will automatically find those files now, which is useful if you're building a disc with multiple operating systems on it (e.g., a universal OEM and VLK disc would require at least two copies of Windows). DriverPacks could also be placed, decompressed, directly on the disc and my script will automatically find the "D\" directory and pass that as an argument into DevPath before running either WatchDSP or DSPdsblr, which I think also means that it supports M1 (but I'm not sure since I don't know anything about M1 other than that the drivers are already decompressed from the 7zip files).

In short, my script is a lot more functional than the one that comes with DriverPacks, and it isn't intended to be "faster" since it serves more use, but at the same time, it will not hang if necessary DriverPacks files are not found. Also, mine has an intuitive log file. That makes mine awesome.

Using 7zip compression of the default XP drivers would be more efficient anyway. I support this man's movement. lol

Overflow, there is a much more efficient method for creating log files. I used it in my Presetup.cmd file that I posted here. Here is an example:

@Echo Off
Set LogFile=%SystemRoot%\MYAWESOMELOGFILE.LOG

@Call :MainScriptRoutine>"%LogFile%"
@REM * More stuff here if you want...
Goto :EOF
Exit

:MainScriptRoutine
@REM * put all of your above stuff in here (sans references to %LOG%)

Goto :EOF

Notice that I suppress the STDOutput of the pseudo-function that is being Called and stick it into a log file?
I suppose if you want that information to also be echoed back to the user, you could use Type %LogFile%.

This method will not work if your routine requires user interaction. If user interaction is required, I would recommend breaking up the routines and appending the log file using the same method, but with user interactions between each of the Calls to the routine. Personally, I put all user interaction at the beginning of the script and call the variables as needed once the script begins running.

Not saying you have to use that method, but it's a lot easier to manage than the deprecated DOS method.

I was actually just coming here to post about some compatibility problems with IDT audio codec. I was thinking it was a SP3 issue, but when I downloaded the drivers from Gateway (I have a Gateway laptop), the drivers installed just fine.

Anyway, I'll wait for this updated version to come out before I bug you guys with the issue.

I use flyakite's as well. It's pretty old, though. I'm not sure if it's the best anymore.

Hey, that's a pretty clever idea. I'm still trying to develop a method for installing all of the different flavors of Windows XP without having any duplicate content on the disc. I might have come up with a solution, but we'll see. *shrug*