Siginet

Did your install complete? Or does it never finish setup? what tweaks or addons did you include? Are you using any driverpacks? What hardware are you installing to. There can be a million different reasons. We need a little info.

They advertise 1mbps... so you have a max dl speed of 125KBps. Yeah it is confusing. Like Zxian said. Watch for the capitalization. When you download it should be rated with a capital "B". There are 8 bits in a Byte. Like 8 nibbles on a sandwitch equals a Bite.

There is no difference except the licensing. It only has about 7 files that are different. All of the files are dealing with the type of license. A slipstream should not change any of the files.

I have actually been working on my own Preventive Computer Maintenance Program for about 2 years now. Actually teamed up with vier of msfn on it as well. It actually will automate many Antispyware/AntiVirus utilities, chkdsk, defrag, memTest, Windows Updates... and so on programs. It has a built in scheduler as well. I plan on using it for my computer company, on maintenance contracts with other businesses. So I'd really like a package of worms, viruses, malware, zombieware.... and whatever else you guys can put together. Kinda funny to actually find others interested in blowing up their computer for fun! LOL!

Beta 29 is online now.

Yeah that's it Booogy. You are such a smart fellow aren't you. Mind showing me the old content I allways point people too? I did point out it was old. The guy asked if their was an UpdatePack for x64. There was. He can use it as a stepping stool to creating one or build upon it. BTW ... I see your reply was very helpful wasn't it? Like usual.

Windows XP PowerPacker also allows you to do simular to Gosh's method as well. Just use the Advanced Tab to specify multiple Boot Options. One of the options you do not specify a winnt.sif file and that is the boot option that will allow you to perform a repair option.

There actually was an x64 UpdatePack created a while back. But it hasn't been updated in quite a while. http://www.ryanvm.net/forum/viewtopic.php?t=282

In my opinion if you have many different computer types your best bet is to use the RVM Integrator, Windows XP PowerPacker, and driverPacks. With these 3 utilities you can make a Multiboot Windows XP disk which is fully updated and has all of the drivers as well. RVM Integrator can be used to create a fully up to date disk with many different "addons (programs)" slipstreamed to the disk as well. Windows XP PowerPacker is usefull if you need to make multiple "winnt.sif (unattended settings) files for each type of OS deployment, and/or if you need to use multiple types of XP (Pro Retail, OEM, Corp) all on one disk. The Driverpacks allow you to slipstream almost every driver possible to the disk so that you have a truley universal disk that works on any computer. Deploying images are great if each computer has the same hardware and needs to have the exact same settings. But my method allows you to setup many different settings for your disk so that when you pop the disk into the system it can give you a menu to choose what type of install you are doing. Like: Windows XP Pro OEM - Secratary Windows XP Pro OEM - Boss Windows XP Pro Retail - Engineering Department Windows XP Pro Corp - Designers ... and so on. I can help you with this method if you decide to try it. Just ask. I designed the RVM Integrator and Windows XP PowerPacker and I am an avid user of the driverPacks. I use this exact method everyday for my computer business. Which I install MANY different types of computers. Latest RVM Integrator Beta Latest RVM UpdatePacks and a forum for many Addons Windows XP PowerPacker Bashrat The Sneaky's DriverPacks

That depends on the Software creators. If the software originally was able to upgrade to a pay version there should not be an issue. In certain cases if the Addon Creator created the Addon as a "True addon (Meaning not a switchless installer)" I suppose it would be possible for the addon creator to mess this feature up... but I think it is highly unlikely. For the most part I think it is very well likley you could upgrade as long as that feature exists in the original software.

Also if they are the same adapters... try swapping the adapters on the machines to see if it gets slow and unstable on the other computer. If it does then that would point to the adapter being bad.

I think VMWare Tools are only meant for a VMWare system. Not on a real PC.

The reason your Themes do not work is because you were using a patched uxthem.dll file. In SP2 there is a new uxtheme.dll file that was installed so your custom themes stopped working. You will need to get an updated patched uxtheme. as for your desktop not showing up. I have a feeling you had some sort of flaw with explorer allready and you did not know it. And updating to sp2 showed the flaw. You may have had other hacked system files which caused a problem when you updated. It may be a good idea to try to check if their is maybe a program that boots up when your computer boots up that is causing the issue. type msconfig and disable any startup programs then reboot. If you still do not get a desktop... I would recommend you make a backup of your files and reinstall windows xp with a slipstreamed sp2 disk. Because I think then your system is too messed up to attempt repairing (unless you get lucky). It would be beneficial to integrate the RVM UpdatePack as well. http://ryanvm.net/msfn Good Luck.

Hide console: http://www.msfn.org/board/index.php?showto...184&hl=hide Or I made a simple Autoit file that allows you to do this as well: http://siginetsoftware.com/forum/showthread.php?t=18 Enjoy!

I have gone through many Flash drives. They just don't last. You are lucky it came back! But be careful.

I own a Seagate Freeagent 500gb. But mine does do eSata... so I guess it is different. so far I have no issues with it. The software it comes with sucks... but I didn't need it anyways. But I am a seagate fan. You can't beat their warranty! and if it is $20 cheaper then the WD with less warranty... then I think your answer is simple. Have fun fighting the crowds though! I hear Circuit City is one of the most popular places this black Friday.

Ummm... from the looks of your replys... i have to disagree.

I've actually seen computers I had to resort to installing XP SP1 to instead of XP SP3. Don't ask me why... but it has happened. It could possibly be your Optical drive or disk as well. I usually have a dvd burner I swap on certain computers cause I know it is reliable.

That is true... but that doesn't mean he shouldn't obfuscate it. Obfuscation will keep most people away. The bad thing about obfuscation is it will more than likley make your code larger which makes your files larger. It also can slow your program down a little. I know Autoit3 is not in your list... but it has a decent obfuscator. http://www.autoitscript.com/forum/index.ph...p;hl=obfuscator

I don't think setup allways loads usb drivers. I actually created a disk once before that would search for files on a usb drive. It worked on most computers but some would fail because the usb drive was not detected. I could be wrong... but I am almost positive that you can install windows using a different winnt.sif file by calling winnt32.exe and a parameter to your winnt.sif file. Allthough I don't know if that is exactly what you want. what exactly are you wanting to accomplish? I suppose you want to be able to create a custom winnt.sif file for each computer you install? Or is it a specific winnt.sif file for some computers and another for some other computers? If you need to use a few (or more) winnt.sif files on a bunch of computers you can actually use Windows XP PowerPacker to accomplish this. It has the ability to make multiple winnt.sif files for use with your install disk. To do this manually you just need to hex edit setupldr.bin. search for any instances of winnt.sif and replace the name with a new file name. Make sure the name is the exact same amount of characters as winnt.sif like "mynnt.sif". Make multiple copies of setupldr.bin with different winnt.sif names in them. like... "MyLoader1.bin", MyLoader2.bin", "MyLoader3.bin" and so on. Use BCDW to create a menu that points to the different Loader files and then you will have a disk which allows you to select different options. Enjoy!

for %%i in (C: D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: W: X: Y: Z:) do if exist %%i\Path\To\File\anyname.txt set CDROM=%%i Place that at the beginning of your batch file. Change: "Path\To\File\anyname.txt" To whatever the path on your disk to a specific file is. For instance if you had a file named Office2k7.dat at the root of your disk your code would look like: for %%i in (C: D: E: F: G: H: I: J: K: L: M: N: O: P: Q: R: S: T: U: V: W: X: Y: Z:) do if exist %%i\Office2k7.dat set CDROM=%%i Enjoy!

I used to use version 7 too. I agree it is a lot less resource hungry. But there are some really helpful tools in cs2 that I do enjoy. Allthough it still was pretty simular to version 7. So upgrading to CS2 wan't a must for me. But I did take the plunge and I got addicted. CS3 is the same for me. It doesn't bring a lot more to the table than cs2. But it does have it's benefits. My favorite new CS3 tool is The Quick Select tool. It is very easy to use. Cuts the time way down when you want to extract something from a pic. Also the ability to edit RAW pics is awsome. The way I look at it... If you are going to spend the money go for it. If you allready have Version 7 or CS2 then it isn't really something to go out and spend money on because it isn't really all that much of a difference. computers are getting cheaper and faster... so the extra resources aren't much of an issue. Of course with anything new it has it's kinks. But I haven't seen many issues yet and the ones I have seen were very minor.

CS2 and CS3 are pretty simular. But CS3 does have some pretty nice new tools. I would say if you are gonna spend the money get cs3.

%CD% is not a settings file. It would need to point to a settings file. like "%CD%\integrator.ini"

Autoit can do this very simply. The Built in Macros: @OSVersion Returns one of the following: "WIN_VISTA", "WIN_2003", "WIN_XP", "WIN_2000", "WIN_NT4", "WIN_ME", "WIN_98", "WIN_95" @OSType Returns "WIN32_NT" for NT/2000/XP/2003/Vista and returns "WIN32_WINDOWS" for 95/98/Me @OSBuild Returns the OS build number. For example, Windows 2003 Server returns 3790 @OSServicePack Service pack info in the form of "Service Pack 3" or, for Windows 95, it may return "B"