Siginet

This is actually a very common mistake. I always tend to remember the drive sizes so I know which drive is what. Or while in windows I go to the properties of my drives and name them accordingly "System" for the drive I want to install to and "Data" for any of my other drives. Txtmode setup still sees these names... so it makes it simple to differentiate them. As for you getting your data back... you may have a rough time because you have allready overwritten the drive. Which means a lot of your data will be corrupt when recovering them. But I like to use GetDataBackNTFS for my recovering. You will need to make sure you recover any data to a seperate HD though. The less you use the drive that you want to recover from is the best. Good luck... and I hope you are able to get your most important files back.

I agree. Klite usually has most of the codecs needed to play most video/audio files. Unfortunately Windows does not come equipt with every codec needed. If you try klite or the vista codec pack found here at msfn and that doesn't fix your problem then I have no idea what may be wrong.

Yes I am aware of the issue. I haven't had time to move the forums to my new host. I had a lot of issues with dreamhost recently when my vbulletin board expired. Before I purchased a fully owned license dreamhost had completely removed my forum and they didn't back it up in any way. They gave me permission to put it back so I spent a lot of time putting it back online only to have it removed once again a couple hours later. Once they finally got their facts straight and allowed me to upload it again I didn't have much time so I kinda threw it together. I have had a rough couple of months and just haven't had the time to make the move to my new host. Sorry.

Hmmm... very weird. I had recently did a Mac Book install of Windows XP myself using a slipstreamed SP2 CD with RyanVM's UpdatePack and a bunch of addons with no trouble at all. I have however seen an xp disk act like an upgrade disk on a computer that had a faulty hard drive. As a matter of fact I had it happen to me today.

OK... I can say that this method DOES still work for Win2k3 SP2. I edited my setupldr.bin at hex address: 0x2060 and changed: "74 03" to "EB 1A". It isworking now. I don't know why others are having an issue. I know I use a slightly different method for my multiboot disks then the method most people use. But I don't see why it would work for me uding my method instead of the normal method.

Hmmm... maybe try a 2003 server sp1 file modded with the modifications needed for the sp1 file? Maybe it will be more compatable since it is a 2k3 file.

I know in the past when it wasn't possible to edit the 2003 SP1 setupldr.bin file we would just copy setupldr.bin from a windows xp disk and replace the 2003 setupldr.bin. It worked in the past. I have a feeling it will work for 2k3 sp2. I haven't tested the theory though. That could be a workaround for now until we find a better solution.

Yes I have just released one last week: http://integrator.siginetsoftware.com/inde...dons&id=189 Please let me know your experiances. Be sure to grab the latest RVM integrator. It has the ability to move files to the netfx.cab file.

Hmmmm... isn't it done the same way as x64 or 2k3 SP1 versions? This is the first I have heard that it was changed. I'll have to do some testing myself then. edit: Here is the link I use for x64/2k3 sp1: http://www.msfn.org/board/Solution-for-mul...l=x64+multiboot But I guess people are saying it doesn't work for sp2.

Thx Martin H! didn't see that. I fixed it. Must have looked like a double post. Yes there aren't any Home/Pro specific files in any of the critical updates. Ryans UpdatePack has a PRO folder in it for pro specific files. But it comes from one of the private hotfixes he includes. Please come back and let me know your success stories! Or if you have any issues I need to fix.

Basically all of the ideas posted by everyone in here accomplish the same thing. So it is your choice. They all will do Direct Integrations though. which is the most important part really. As for waiting for UpdatePacks... that might not be an issue from here on out. I plan on keeping my Set of UpdatePacks updated just after Patch Tuesday. But whichever method you choose I'm sure it will be fine. Evertone has their opinions. And each utility has it's strengths and weaknesses. I can help you if you need some pointers... so just ask.

It depends on the method you are installing. If you want to have a disk to install windows with all of the updates then you would want to use an UpdatePack. You can get RyanVM's latest UpdatePack here: RyanVM's MSFN files I have also just released a Critical UpdatePack which installs only the Critical hotfixes here: Windows XP Post-SP2 "Critical" UpdatePack It was just updated this week with the latest Patches from Tuesday. I reccommend you use the RVM Integrator to integrate these UpdatePacks to your disk. But there are other alternatives as well. Integrating UpdatePacks will save you tons of space on your install disk because it will overwrite existing files. So the end result will be almost the same size as before. Installation of windows will take relatively the same amount of time as your original disk. But when it is finished being installed you will have no updates to worry about. To top this all off you can even integrate Third Party utilities like Antivirus, Antispyware, Media utilities and tweaks... and much more. you can find many addon at these places: Integrator.SiginetSoftware.com RyanVM.net Forums Wincert.net Forums MSFN.org Forums If you are looking for a way to install the updates in a Windows system that is allready running then you would want to look into AutoPatcher.com.

Here is my second of many UpdatePacks. I have decided to release my own line of "Critical" UpdatePacks. Containing only Critical Updates (For The Most Part). The only Updates in this pack that are not Critical Updates are QFECheck. You can download it here: Siginet's Windows 2003 Server Post-SP2 "Critical" UpdatePack I will try to update it just after every Patch Tuesday. Also Available: Siginet's Windows XP Post-SP2 "Critical" UpdatePack comming soon: Windows XP / 2003 x64 Critical UpdatePack.

Here is my first of many UpdatePacks. I have decided to release my own line of "Critical" UpdatePacks. Containing only Critical Updates (For The Most Part). The only Updates in this pack that are not Critical Updates are Flash and QFECheck. You can download it here: Siginet's Windows XP Post-SP2 "Critical" UpdatePack I will try to update it just after every Patch Tuesday. Also Available: Windows 2003 Server Post-SP2 "Critical" UpdatePack comming soon: Windows XP / 2003 x64 Critical UpdatePack. If anyone can provide a good mirror that would be great too.

Malware infection, Hard Drive going bad, Network driver was updated with a bad driver, bad network cable, another computer on the network is infected and using all of your bandwidth. Many many reasons can cause this. definatly use RogueRemover, Ad-Aware, and spybot and see what it finds. Change your WEP key just in case gamehead is right too. Your modem or router can be faulty as well. Hope you figure it out. Good luck.

You should just put in the product key on the bottom of your laptop. If it still has a problem then you should be able to call microsoft and get the issue resolved.

Its not hard at all. Vista drivers work pretty much the same as XP drivers. I haven't had to do anything more than adding the Vista (Windows 6.0) support line and copy the DEV IDs into that section. Really??!! It's that easy? If that's the case I can throw a tool together... but only if someone pm's me detailed info and examples of how it is done. Does this method work for just about any drivers? Or just creative sound drivers?

I wonder how difficult it would be to make a program that can convert a winxp driver to be vista compatable. They wouldn't really be able to do anything if a tool was released that does this. People would still have to download the original drivers. And they would only be modding drivers they are using on their own systems. No one would be distributing any of their drivers.

That is a very well put together tutorial HJW! Very nice. I may use some of these ideas when I code the next release of Windows XP PowerPacker. a question... Are there any issues with any computers displaying graphic menus that you know of? I mean like older computers or something. It would be awsome if maybe you can help me put together a new boot menu system for powerPacker. I'm sure we could code it in a way where people can easily share themes and stuff.

Really no one can give you a valid answer to that question. That all depends on how many files you have on your system, how much temporary internet files it needs to scan, how fast the system is, how infected the system is... and so on.

AVG is my favorite free av. In the past Avast would give me too many false positives. AVG doesn't hog up too many resources either.

Congrats Wimb! It well deserves it! BTW... the RVM Integrator is about to go final any day now. So that will give me time to begin designing a gui for you. Sorry for the delays... but first things first. Plus I have been very sick for over a week. Hopefully this sickness will go away soon.

What type of Windows install is it? You need to create a txt file called "WIN51" and a file called "WIN51IP" If it is XP Pro or "WIN51IC" if it is home. Then a third file with the extension of the servicepack: "WIN51IP.SP3" (Pro) "WIN51IC.SP3" (Home) all 3 of these files belong at the root of your disk (Right next to the "I386" directory. If it is 2003 the files are different... but you can find the info on msfn.org.

Welkin Globe Royal Globe Blue Yonder Royal Blue Yonder Enchanted Globe Welkin Splash I figure the word Globe goes good with the logo.

Looks to me like 3 mapped shares. 2 point to an xbox through ftp and one points to "\\carol\c". In the registry it is showing double "\" which is common. It doesn't however show the drive letters. In autoit you can use DriveMapGet ( "device" ). where you could list each drive letter and it would return the mapped path. Like if the mapped drive letter was L: you would use: $Getpath = DriveMapGet ( "L:" ) Which would make the variable $GetPath = "\\carol\c".