Nakatomi2010

I actually did 'Shift+F10', when it asked me for it, went to the directory it was in, typed 'notepad sysprep.inf', put it up on the screen, typed in what was written there into the boxes in the mini-setup, then verified itagainst the sticky, character per character match, and when I hit next it worked... It just didn't want to use the one in the file.... The method I'm using to do this is a bit convoluted so I'll explain a bit.... First I stick in my Multi-Boot DVD, which has Bashrat's driverpacks and RyanVM's update packs integrated. I boot from that CD which uses a WINNT.SIF file to perform the setup unattendedly. DURING the setup it asks for the CD key because I do not specify one in the WINNT.SIF file. At the end of the setup WPI is called, comes up and I select the software to install and install it, at the end of the software installs the system reboots and I update AVG, Ad-Aware, Microsoft Antispyware, and finally Windows itself, then reboot again. At THIS point I would like to run Sysprep to reseal the system so that the next time it's started the customer can read over the EULA, choose whether or not to register with Microsoft, as well as create their own user accounts, if they should so choose. However, the problems I run into is that there are files missing, which is a small issue I've learned how to resolve, and that it asks for the CD key, which I don't want it to.... So yeah.... I used the setupmgr.exe to create a sysprep that had the CDkey in it, but it still asked for it... It's XP Home OEM... Thoughts?

Just did half a minute ago, and while it DID half a** solve the problem, it still asks me for the CD key.... Despite it being typed into the sysrep.inf... One thing that changed is it asking for the location of file, it found the specific .nls file it was looking for, but now had a s*** ton of problems trying to find a font, which made me have to redirect it to C:\windows\fonts.... Even if I copy the contents of that directory to \Sysprep\i386, it wont do it....

Alright, so I do a complete install, and when it's done I awnt to reseal the system... Iv'e found that the WINNT.SIF file gets turned into the $WINNT$.INF file in the system32 directory which then becomes the Sysprep answer file is Sysprep is run and needs to be deleted to do what I want it to do.... However, once I reseal the system and boot it up again I get prompted for the XP CD, and it wants two files which ARE on the system, I can point them to where the files are, but when a customers receives a system, they wont know that, so I want to know how I can tell the thing where the files are at... One of them is a font file, and the other is a .cls file... The other thing I get prompted for is the CD key, idealisticly I'd like it to not ask for that, how would I go about doing that? Edit: Just a quick side note, the reason I don't want to have to retype the CDKey each time is because basically I use a completely unatended install CD to instal the OS, then I'd probably have WPI copy information over, or a GUIRUNONCE command, or some such, which lets me update the virus scanner, spyware scanner and Windows, THEN reseal the system, since we build systems on a per request basis, so I figure since I do the sysprep on each individual system, having it not prompt for the CDkey wouldn't be critical because it's going to be configured for THAT system.... Let me run some of this thought out loud.... Let's say the sysprep.inf file becomes the unattend.txt, or WINNT.sif file... So that would mean that if I followed the commands of the WINNT.SIF, then I could integrate the CDKey into the answer file, so all I'd need then is a script which could be called by WPI where I can type in theproduct key, and it would edit the sysprep.inf file with the appropriate information, so that when I reseal the system, all the right information is input where it needs to be.... So assuming that's possible, how would I do it?

You know, it occurs to me that even if we do bolt MCE into XP x64 edition, there's virtually no point as there are no x64 remote control drivers are there? Be like adding a set of hybrid car batteries for a hybrid car in a full gas powered car... Doesn't work right if you can't properly connect them togehter....

Do: Start>Run>Cmd navigate to the i386 directory of your source. Do: expand nlite.in_ nlite.inf notepad nlite.inf (Notepad will open) Once notepad is open find the line that says something about Admin autologin, I can't remember what it is, but delete the entire line, and just that line... Then save it and exit... Go back to the CMD window that should still be open and do: makecab nlite.inf nlite.in_ And voila... Now whenever you install it should stop the auto login... If you want to make the change for now simply do: Start>Run>Control Userpasswords2 Select your username, uncheck the box at the top, hit ok, type in your password, if needed, then hit ok, ad fixed... Edit: I learned that for some reason nLite will make it auto-logon for you, so I had to go in find the setting and go from there. I did NOT check the box during the setup, and it made the decision on its own, throughout my ten copies of XP.... Had to fix each one suing the method above, then it never auto logged on as admin again

Follow the guide, I'm running 4 PE's off my DVD, ERD Commander 2005, Syamntec's Recovery Disk, UBCD For Windows, and a PE from a collegue of mine... Just follow the instructions on the flyakite site... I called mine ERD1, SYM1, BPE1, and CPE1 respectively

You be trippin'

It's no typo, it's the original release name for 98SE, it was just delayed 5 years... You know Microsoft... He must have an Alpha release...

Dunno how to put this exactly, but I want to test how a computer is receiving information. It's got a problem of intermitten netwok failure, and when I have it pull 700mb files from my guinea pig machine it kills network connectivity on that machine, so I want to download 700mb, or larger, files from online... Anyone know where I can do this free, where I don't need some special installer, or pop-up windows or something?

I've got a a machine here running Mistake Edition, and everytime it boots it want's to run a thorough scandisk, I've edited the MSDOS.SYS file to say autoscan=0, but it still boots wanting to do a torough scan... How do I stop this?

I want the setup to copy over the OEMInfo and OEMlogo files during the setup, but I don't want to use the $OEM$ folders, because once you add a WINNT.sif file it seems the option to do a repair install goes away, and I'd like to keep that option on my CD.... So, which part of the txtsetup.sif would allow me to have the two files copied into the system32 directory?

**** straight.... closest thing I've got right now is a Corporate key tester... Or at least, I had one.... But I don't want to test JUST corporate keys.... Removed - Listed program is not appropriate for discussion on MSFN.

So, let me get this straight..... If I edit the .dat file (Bootsector) so that it says SETUPLD1.BIN instead of SEUPLDR.BIN, then opened up the corresponding SETUPLDR.BIN in the boot folder and edit every WINNT.SIF reference to say WINN1.SIF, I should be able to have it run with more than one install option?

I'm not trying to find out if the key is a "Home" or "Professional" key, I'm trying to determine if the key is Retail, OEM, or VLM...

Is there a program out there that'll test XP keys and determine which version of XP it's for? I'm a tech at a local computer store and use tools to recover CD keys when we're not given it, and although we can determine which it's corporate, OEM, or Retail, it helps to know without hunting too hard, testing the key would also ensure we have the right one... Thank you...

I was asking for a comfimation that that would do what I want it to do... It takes about 2 hours to make a new image everytime I make a change, and if I'm going to spend 2 hours to burn an image because of a single line of code, I would like to be sure it's accurate... All I was looking for was "Yes, the /noskins command will not install the wallpaper and stuff like you don't want it to"

I know what the switches are, what I'm asking if it's the right switch to do what I want it to do....

Well, I'm using WPI so I'd like to know which command to use so I don't need the installer to pop up....

I'm trying to fine tune a few things on m end, and I was wondering.. I'd like to install Xpize on the MCE 2005 machine I'll be building soon, but I want to keep the background and stuff from MCE 2005... I still want the icon enhancements, and .dll fixes, but I'd like the background and general theme to be the MCE 2005 default... Is all I need to do simply add the /noskins command, or would it be easier to just no install Xpize?

When I set it to transparent in Photoshop, then save it as a bmp, it adds a background when saved... Or am I missing something?

I'm maing an OEM Logo and I'd like it to go seamlessly with the background of the System Properties windows... What are the RGB values of the color you've got it set to?

Alright.... I decided to just go around that limitation.... I exported HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment to 'env.reg' Then, I opened up the file and saw a bunch of stuff... So I figured, alright, well that stuff's there by default... So I removed everything except for.... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment] "Garfunkle"="D:\\" Why Garfunkle? Because if you're looking for what setting gets changed as a result of a modification you'd better hope you don't have more than one entry, and I figured if I did a search using Regedit for 'Garfunkle', I'd have a higher chance of finding the right 'Garfunkle' than 'CDROM' So, now that the above code is all that's contained in the env.reg file I opened up the command prompt and typed in 'REG Import C:\env.reg' and blammo, %garfunkle% is now D:\... Now... There are limitations to this, which I need assistance with... First, it makes %Garfunkle% be 'D:\', the result is that if a machine has more than one hard drive, suddenly that's useless... SO, I need a way to have the thing search for a file, for example 'wpi.ico', which is the WPI icon, once it finds wpi.ico it edits D:\ in the env.reg file to say E:\. which is the CDROM drive, and then imports that, thus making the change permanent..... Or, if someone knows of an easier way....

Alright.... Through a rather clever exercise I've discovered that the environment variables are set at the following registry location: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment Now.... From what I can tell typing in the following at the command prompt should add 'CDROM' as the variable... REG ADD HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment /v CDROM /t REG_EXPAND_SZ /d D:\ The above line should make the change, but I keep getting 'Error: Too many command-line parameters'.... What's wrong?

WRONG FORUM! Please move this to proper forum, and I apologize... I'm tired.... Alright, so if you type 'set CDROM=D:\' then everytime you type %CDROM%\command it'll look at the D:\ drive for that command... for that session only, once you reboot that is lost... My question is how do you set it to be permanent? For example, if you open up system properties and click aadvanced>Environment Variables and then click new, then type CDROM in the top box, and D:\ in the bottom box, now %CDROM%\command it's bound to that drive letter permanently.... So, my question is how do you set it to be permanent? And then how could you have it look through all the drives looking for a file on the drive, THEN have it set that drive as a certain variable...? Why? Because I want to run WPI from the CD, not the hard drive... And setting the CDROM variable permanently would allow some future flexibility....

You've helped me to realize a massive flaw which explains precisely why it does not work... When I created the setup.iss I installed it to a copy of Windows XP which resided on a D drive, and as a result th .iss file recorded a D drive installation.... So everytime it installs after that it wants to install to D:\program files\cyberlink\powerDVD, which does not exist... I want to thank you for making me realize WHY it was not working by telling me to go find the uninstaller.exe and discover it was really installe don the D drive....