Siginet

Where can I get that?

Enjoy!

Thx for the mirror. I updated the post with the mirror as well.

You beat me to it. I also reccommend you use the latest beta build of the Integrator: Siginets: RyanVM Integrator v1.0RC13Beta4

Sorry forot this server doesn't allow downloading of cab files for some reason. Just extract it from the zip file.

Hmmm... maybe someday I will make it compatable with 144dpi... but for now it seems to be fine. What else would you reccommend other than Tri-Pack or Original?

Well it only integrates it... it doesn't slipstream it to your disk. But I made a simple addon that will add the silent exe (made by RyanVM) to your svcpack directory and it will add the file to the svcpack.inf file for installation. SiginetAddon_NETFXSP1_1.1.CAB Mirror Integrate it using Siginets: RyanVM Integrator v1.0 RC13Beta2 or better. Found at RyanVM Forums. This pack is not useable through NLite yet.

I like HFSlip too... but for some reason I have issues with my Windows XP Home edition whenever I use it. But HFSlip and RyanVM's update packs are my favorites. Because they not only update your disk... but they slipstream it to the disk... so it saves a lot of space. Ryan is releaseing a new UpdatePack later in the week that should work very well. The only issues with his last pack was that he used a lot of Beta hotfixes in his pack as well... which pushed the cat limit over the edge. Windows XP only allows 150 cats to be signed and Ryans pack was over that limit. Turning off Windows File Protection is the easiest way to bypass this. Ryans new pack will mainly just be the publicly available hotfixes so it should work very well. I have also updated the RyanVM Integrator a lot in the past week with new features and ease of use. You have to get it on RyanVM's forum though... he has not added it to his front page yet. But even though I helped make RyanVM's integrator... I do like HFSlip just as much. It is very cool. It is somewhat the same concept as Ryans packs... but it allows you to easily customize what hotfixes to install. Do check out the RyanVM forums though. People have begun making custom addon packs of just about anything you can think of. One member made a custom addon that integrates the RoyaleTheme into your windows xp disk.

Thx! Me Too!

Very Nice!

You have all of the driverpacks plced in the driverpacks folder? You have copied all of the contents from within the UWXPCD_ROOT folder to the directory containing I386 (Not inside i386) right? Make sure your files are not readonly. (Just incase) Once there you must run RUN_ME.CMD. You should now have $OEM$ and OEM at the root. Inside OEM you should see all of the DriverPacks. If you have done all of this correctly you shouldn't have a problem. If you do... try to post some screen shots of what you have.

I can almost read it. Thanks for the scan. If you can get higher res scan of it... it would really be great. I can't wait to read the article. Thanks again prathapml!

And the program has come a long way since the version that they reviewed.

I would appreciate that a lot! Thanks!

http://www.msfn.org/board/index.php?showtopic=57581

WOW! That is awsome!!! Anybody want my autograph?? LOL! BTW... Do they sell this magazine in American stores? I got to get a copy somehow.

You need to use the setupldr.bin file from a 2003 server disk (Pre-SP1). Also... Windows XP PowerPacker does have the capability of creating a Windows 2003 Server multiboot pack. Just read this here: http://www.msfn.org/board/index.php?showtopic=53750

You may want to play around with Bashrat's DriverPacks. It is a bunch of packs of drivers. Like all LAN drivers, Graphics, Sound, etc... It let's you integrate them into the Windows Setup disk. Also it has an option to Keep the drivers on the system after they have been installed. You may be able to use a DriverPack integrated system as your image. But you will have to run some tests... because I haven't played much with using one image on multiple systems. Let me know if you find anything.

The easiest way to get it working is using my app windows XP PowerPacker. It does exactly what you need. Except at this time it does not directly support Media Center Edition yet. (Only because I do not have it to test with and I am not sure how much differently it installs.) But basically you can follow through all of the steps and select Tri-Pack to create the 3 seperate packs as you listed above. If it is not recognising presetup.cmd or setuporg.exe check to make sure those files are in the BOOT folders and in the I386 dirs. Also check txtsetup.sif for those entries.

So in the 64 bit version it looks like certain instances of AMD64 are changed to STR64. Also I386 is changed to ST6R. So in the 64 bit versions we have to change those same instances of AMD64 and I386 right? The I386 portion... does it need to follow the same pattern? STR64=ST6R APT64=AP6T? Or am I looking at it all wrong? I want to start playing around with this... but I need a version of VMWare that can do 64bit stuff.

I think the file you posted is a setupldr.bin file from an original 2k3 disk not a sp1 setupldr.bin. Because the one you posted is 273KB which is the same size as an original. The SP1 version is 292KB. I also opened an original and the one you posted and they are the same.

Are you sure it's EN3R? By looking at it in a hex editor it looks like it refers to ST3R. Like the dat file you posted.

I'm curious too. How do we use those? Also... anybody have the 64Bit ones?

As long as the old disk is not using an older mass storage driverpack. You may be able to get away with it. If new Sound or video ControlPanels have been added you will not have those either. Basically just replace the newer DPs in the OEM directory and try it. It may work fine.

That is because you put the RVM files in your ExtraPack Files directory. You do not need them in there. Just use the PREPACK.BAT file to point to where your files are at. Everything in the ExtraPackFiles directory is copied to the root of the pack. The PREPACK.BAT file is what needs to be in the ExtraPack Files directory. Because it needs to be copied over to the root of the pack. Then after it is executed PowerPacker deletes the PREPACK.BAT file.