Hello,
I currently maintain a few Dell computers at work. When I use the Dell OEM Windows XP SP2 disc for a fresh install, I don't need to provide a serial number/key for the machines - it automagically recognizes the machine as a Dell.
I've manually slipstreamed a few hotfixes in, but I'm looking for a more complete solution like HFSLIP.
When I use HFSLIP 1.1.0, the standard "not original" error occurs but it manages to install all the hotfixes and the extra drivers that I need.
When I burn the ISO image and use it for a fresh install, everything works fine, but it does ask me for the key.
Is there a way to preserve the functionality of not requesting a key? It's a hassle to type in the 25-digit code which is usually stuck in the most inconvenient location on the machine.
Thanks!
Full Version: Trouble with slipstream Dell OEM Win XP
HFSLIP is for home users... unless your boss will pay the dev's.
QUOTE (tommyp @ Dec 2 2006, 01:30 PM) 
HFSLIP is for home users... unless your boss will pay the dev's.
That's fine, but these machines belong to me and I use them to host my own file servers. The same situation in the first post also applies for my home computers that are Dells.
QUOTE (bingho @ Dec 2 2006, 08:58 PM)
When I use HFSLIP 1.1.0, the standard "not original" error occurs but it manages to install all the hotfixes and the extra drivers that I need.
Who's complaining about that? Windows setup or HFSLIP?QUOTE (bingho @ Dec 2 2006, 08:58 PM)
When I burn the ISO image and use it for a fresh install, everything works fine, but it does ask me for the key.
To be honest, the only way I know to pre-insert the key is via WINNT.SIF. But HFSLIP doesn't touch, modify or create that file so I'm not sure how that could've happened.
he! he! very timely ... now that i see a topic for this, may i ask if there'd be a way to maintain an activation-free install? i recently used an old Dell OEM XP SP1a cd & it requests for activation upon getting to the GUI ... thanks! (
sad though ... testing is still temporary --- using my sister's PC for quick tests ... just so i could share something
have recenly purchased 2 Athlon XP cpus - 2200 & 2600 - compatible to my ECS K7VTA3 ver 7.0 mobo --- & both got fried! 
--- strange, although unsupported Sempron 2200 works but shows as Athlon 1200 only ... & doesn't get fried! oh well ... )
sad though ... testing is still temporary --- using my sister's PC for quick tests ... just so i could share something
have recenly purchased 2 Athlon XP cpus - 2200 & 2600 - compatible to my ECS K7VTA3 ver 7.0 mobo --- & both got fried! --- strange, although unsupported Sempron 2200 works but shows as Athlon 1200 only ... & doesn't get fried! oh well ... )
Kiki Burgh
may i ask if there'd be a way to maintain an activation-free install? Search for OEM transformation to VL (Volume License)
may i ask if there'd be a way to maintain an activation-free install? Search for OEM transformation to VL (Volume License)
I need to know how Dell keeps it activation-free before I can check out what's causing this. I don't think I have a Dell OEM lying around but I'll look in the box for my father's Dell laptop if I can find it again.
I'd leave a message on the Hardware subforum for your CPU problems. It looks to me like your BIOS doesn't pick up the correct FSB and/or multiplier by default (Sempron 2200 is 166x9). BTW... If you can afford 3 CPU's, why don't you take an Asrock ALiveNF6G-DVI for a motherboard and a Sempron64 2800+ AM2 or an Athlon64 3200+ AM2 for a processor? These don't get fried...
I'd leave a message on the Hardware subforum for your CPU problems. It looks to me like your BIOS doesn't pick up the correct FSB and/or multiplier by default (Sempron 2200 is 166x9). BTW... If you can afford 3 CPU's, why don't you take an Asrock ALiveNF6G-DVI for a motherboard and a Sempron64 2800+ AM2 or an Athlon64 3200+ AM2 for a processor? These don't get fried...
@TC, if you can't get the CD you want, just tell me : my father has one too.
Dell and other OEMs keep their CDs activation free through use of the OEMBIOS* files. There are four of them in \I386. I believe all you need is to copy the right ones to that folder and everything else should work. However, I would advise you to read up on it more as it's possible that my memory is failing me right now.
thanks TC for the concern ... been spending quite a sum on those CPUs ... my current board (ECS K7VTA3 ver 7) only supports Athlon series (or lower) & not Sempron ... it used to have Athlon XP 2000+ in there that got busted so i had to go through the lengths of finding alternate (& supposedly better) CPUs (Athlon XP 2200 & 2600) that got fried ... been attached to that old PC ... he! he!
i could burn 1 Dell OEM cd for you if you like & send it over there ... i think S-M in the right track as far as how Dell keeps it activation free ... perhaps this would help ... if i may quote from Dell internal article
... been spending quite a sum on those CPUs ... my current board (ECS K7VTA3 ver 7) only supports Athlon series (or lower) & not Sempron ... it used to have Athlon XP 2000+ in there that got busted so i had to go through the lengths of finding alternate (& supposedly better) CPUs (Athlon XP 2200 & 2600) that got fried ... been attached to that old PC ... he! he!i could burn 1 Dell OEM cd for you if you like & send it over there
... i think S-M in the right track as far as how Dell keeps it activation free ... perhaps this would help ... if i may quote from Dell internal articleQUOTE
Microsoft has introduced SLP (system locked preinstall) with Windows XP. The SLP technology verifies that the operating system is installed on a Dell computer on every boot. If SLP does not detect the string in BIOS that identifies the system as “Dell Computer Corporation” then it will decide it is not on a Dell system and will bring up the activation wizard.
QUOTE
Original Equipment Manufacturers (OEMs), like Dell, have the ability to pre-activate Windows XP software installed on new systems through a process known as System Locked Pre-installation (SLP). This prevents end users from having to activate the software during the setup process by typing in the product key found on the Certificate of Authenticity (COA) key.
If the Dell OEM version of Windows XP media is used to build and deploy an image, the end user who boots the newly-imaged system is prompted to enter a product key during mini-setup. The user types in the product key off of the COA label on the system, reaches the desktop and is prompted to activate their product. An attempt to activate the product key via the web will fail with a prompt to call the Microsoft Activation Call Center.
This failure is due to a change in Microsoft's Product Activation process implemented to combat worldwide licensing fraud. Microsoft has disabled online activation for COA Keys that are attached to PCs that have been pre-activated by OEMs. If you use Windows XP factory installed by Dell or have reinstalled Windows from the Dell OEM recovery media, you will not be prompted to activate the software. However, if you choose to build an software image using an OEM copy of the software, you will need to follow specific instructions for building images.
If the Dell OEM version of Windows XP media is used to build and deploy an image, the end user who boots the newly-imaged system is prompted to enter a product key during mini-setup. The user types in the product key off of the COA label on the system, reaches the desktop and is prompted to activate their product. An attempt to activate the product key via the web will fail with a prompt to call the Microsoft Activation Call Center.
This failure is due to a change in Microsoft's Product Activation process implemented to combat worldwide licensing fraud. Microsoft has disabled online activation for COA Keys that are attached to PCs that have been pre-activated by OEMs. If you use Windows XP factory installed by Dell or have reinstalled Windows from the Dell OEM recovery media, you will not be prompted to activate the software. However, if you choose to build an software image using an OEM copy of the software, you will need to follow specific instructions for building images.
QUOTE
Refer to Microsoft Technet for instructions on how to preserve SLP Product Preactivation in Windows XP images. For details on how to successfully create an image using Windows XP OEM media and preserving SLP pre-activation, refer to the following white paper from Microsoft's Technet website: http://www.microsoft.com/technet/prodtechn...y/oempreac.mspx.
hope this helps ...
Do you slipstream any service pack ?
If your CD has no SP and you slipstream one, you may lose activation since SPs change many things and even blacklist some product keys.
If your CD has no SP and you slipstream one, you may lose activation since SPs change many things and even blacklist some product keys.
hi Tux! it is already with SP1a & slipstreamed SP2 via HFSLIP
it is already with SP1a & slipstreamed SP2 via HFSLIP
@Kiki
That's some interesting reading, but if HFSLIP really causes Dell pre-activation to break then I'd like to know how that happened.
@bingho
In the Microsoft article that the page Kiki links to is linking to, they outline a possible workaround. Edit OOBEinfo.ini in the I386 folder and add the following to it:
[Version]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
...where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your product key. See if that gets you anywhere...
That's some interesting reading, but if HFSLIP really causes Dell pre-activation to break then I'd like to know how that happened.
@bingho
In the Microsoft article that the page Kiki links to is linking to, they outline a possible workaround. Edit OOBEinfo.ini in the I386 folder and add the following to it:
[Version]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
...where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your product key. See if that gets you anywhere...
QUOTE (Tomcat76 @ Dec 6 2006, 04:10 AM)
Edit OOBEinfo.ini in the I386 folder and add the following to it:
[Version]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
...where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your product key. See if that gets you anywhere...
could this be done via HFSLIP? do we still have to modify winnt.sif (if using it)? thanks! [Version]
ProductKey="XXXXX-XXXXX-XXXXX-XXXXX-XXXXX"
...where XXXXX-XXXXX-XXXXX-XXXXX-XXXXX is your product key. See if that gets you anywhere...
I've tested HFSLIP with a Dell XP SP2 CD and the pre-activation works like it should. No messing around with the product key and the OEMBIOS.* files are there. Works like a charm.
thanks for the confirmation clintb ... i didn't think HFSLIP could break the pre-activation install ... the only fact perhaps would be that you used it on a Dell system rather than a clone, right? ... bringing us back to the concern about not needing to activate it anymore (he! he! ) thanks!
... bringing us back to the concern about not needing to activate it anymore (he! he! ) thanks!
New guy here, just thought I would add my 2 cents. I use a Dell OEM disk and the first time I used hfslip I got the same prompt to enter the product key. The reason was because I used WINNT.SIF in the FIX folder without a product key in it. The product key on the side of the computer won't work either. All that has to be done is to look in the I386 folder of the original Dell OEM disk and copy the WINNT.SIF that's in there to the FIX folder hfslip creates. That's it. It already has the proper key in it. To my knowledge it is the same key for many Dell systems. No activation required. Hope this helps.
I don't understand this. HFSLIP copies all content of the SOURCE folder into SOURCESS, including WINNT.SIF if it exists. So putting WINNT.SIF in the FIX folder doesn't serve any purpose unless you make modifications to it.
So if WINNT.SIF in your SOURCE/I386 folder has the product key in it and you have WINNT.SIF in your FIX folder without a product key, which one will hfslip use? The one in the FIX folder right? Which without a product key required him to manually enter the key on the side of the case. The wrong key. The case key will install windows but XP will want to go through activation and that key will not activate. With the key in SOURCE/I386/WINNT.SIF no activation is required. That was the mistake I made. Does this make sense?
Homer_m is correct. You must copy the winnt.sif Product Key that is in the i386 dir to the winnt.sif that you put in the FIX folder. I have an OEM with sp1a and slipstream SP2 with no activation required doing it this way.
I know that, but you wrote:
Either way, if the OEM supplied a copy with a modded WINNT.SIF, just put it in SOURCE\I386 with the rest. There's no need to use the FIX folder unless you actually make a change that you don't want to use all the time (it's easier to remove something from the FIX folder than it is to remove something from SOURCE\I386).
QUOTE (Homer_m @ Dec 6 2006, 07:28 AM)
All that has to be done is to look in the I386 folder of the original Dell OEM disk and copy the WINNT.SIF that's in there to the FIX folder hfslip creates.
This confuses me. The SOURCE folder is supposed to contain a copy of the original CD. That would include the WINNT.SIF that's on the CD. So what's the point in copying the file into FIX too? I can't imagine anyone having done a "Select all" in the CD's I386 folder, deselected WINNT.SIF and then copied the selection into SOURCE\I386...Either way, if the OEM supplied a copy with a modded WINNT.SIF, just put it in SOURCE\I386 with the rest. There's no need to use the FIX folder unless you actually make a change that you don't want to use all the time (it's easier to remove something from the FIX folder than it is to remove something from SOURCE\I386).
well i have only used the Dell OEM XP Pro SP1a recently ... & i thought it would ask for the CD key ... however it did not ... i didn't even bother preparing a winnt.sif as i wanted to see if it would ... the only thing was it asked for reactivation once it got to the desktop ...
A bit of FYI: Mine worked by simply using the i386 folder from the CD as my \SOURCE\I386 folder. No copying winnt.sif to the FIX folder, no messing around with the product key.
If the product key is in winnt.sif on your CD in i386, there's no need to do anything else. You will have problems if oembios.* are missing.
If the product key is in winnt.sif on your CD in i386, there's no need to do anything else. You will have problems if oembios.* are missing.
I successfully slipstream all the updates using HFSlip on a Dell and Acer OEM CD. I think I understand the confusion here since I went through it myself.
1. There should be 4 OEM files that must exist in the source folder. When you copy the i386 folder from the Dell Cd, the 4 files, i.e., oembios.dat, oembios.cat, oembios.bin and oembios.sig should already be present. If it is a Acer cd, you have to go to to windows\system32 directory and copy the 4 files to your source. This is because Acer cd uses ghost to image the hard drive, and the i386 directory do not have these 4 files.
2. This is the confusing bit. There is actually 2 product keys. The one on the sticker at the side of your notebook or pc will always REQUIRE activation. It is legit and will activate, but it is a pain in the butt. There is another product key that ties in with the oem files, and if you use that product key, then it is pre-activated. To find this product key, go to the winnt.sif file in your installed windows, or search the ini files in the system cd. You can also use keyfinder.
My problem is that my Dell CD is quite new, and other than SP2, Dell has some pre-existing hotfixes in the svcpack directory. HFSlip will work, but will not integrate IE7. The Acer CD is older and have no other hotfixes other than SP2.
1. There should be 4 OEM files that must exist in the source folder. When you copy the i386 folder from the Dell Cd, the 4 files, i.e., oembios.dat, oembios.cat, oembios.bin and oembios.sig should already be present. If it is a Acer cd, you have to go to to windows\system32 directory and copy the 4 files to your source. This is because Acer cd uses ghost to image the hard drive, and the i386 directory do not have these 4 files.
2. This is the confusing bit. There is actually 2 product keys. The one on the sticker at the side of your notebook or pc will always REQUIRE activation. It is legit and will activate, but it is a pain in the butt. There is another product key that ties in with the oem files, and if you use that product key, then it is pre-activated. To find this product key, go to the winnt.sif file in your installed windows, or search the ini files in the system cd. You can also use keyfinder.
My problem is that my Dell CD is quite new, and other than SP2, Dell has some pre-existing hotfixes in the svcpack directory. HFSlip will work, but will not integrate IE7. The Acer CD is older and have no other hotfixes other than SP2.
thanks for sharing your find kenlau! this should shed additional light on the topic ... i actually found out about the 2 different keys ... i just couldn't recall though the exact result when i tried using the 1 declared in the winnt.sif (please know i didn't use the default winnt.sif) ... if memory still serves me right, when the part for the product key came up, it still prompted for the product key (despite it being already declared in the revised winnt.sif) ...
as for integrating IE7, there shouldn't be a problem as OEM OS is considered legit ... have you exhausted the special instructions outlined in Important things to know -- please read!?
... i actually found out about the 2 different keys ... i just couldn't recall though the exact result when i tried using the 1 declared in the winnt.sif (please know i didn't use the default winnt.sif) ... if memory still serves me right, when the part for the product key came up, it still prompted for the product key (despite it being already declared in the revised winnt.sif) ...as for integrating IE7, there shouldn't be a problem as OEM OS is considered legit ... have you exhausted the special instructions outlined in Important things to know -- please read!?
hi all! i just wanted to share these articles i came across while this may be a little late revival for this specific thread, i hope you guys will still find it useful:
Preserving OEM Pre-Activation when Re-installing Windows XP
Technical Details on Microsoft Product Activation for Windows XP
How to change the Volume Licensing product key on a computer that is running Windows XP SP1 and later versions of Windows XP
Preserving OEM Pre-Activation when Re-installing Windows XP
Technical Details on Microsoft Product Activation for Windows XP
How to change the Volume Licensing product key on a computer that is running Windows XP SP1 and later versions of Windows XP
QUOTE (Super-Magician @ Dec 5 2006, 07:22 AM)
Dell and other OEMs keep their CDs activation free through use of the OEMBIOS* files. There are four of them in \I386. I believe all you need is to copy the right ones to that folder and everything else should work. However, I would advise you to read up on it more as it's possible that my memory is failing me right now.
hi S-M! would these be the files: oembios.bin, oembios.cat, oembios.dat, oembios.sig?
hi TC/TP! would it be possible to provide support via HFAAO Siginet's tool (in 7zip format) found here: http://siginet.ryanvm.net/forum/viewtopic....asc&start=0? i think it would be great for those using OEM cds ... thanks in advance!
thanks in advance!
QUOTE (Kiki Burgh @ Jan 3 2007, 05:34 AM)
hi S-M! would these be the files: oembios.bin, oembios.cat, oembios.dat, oembios.sig?
You got it!
QUOTE (Kiki Burgh @ Jan 3 2007, 11:54 AM)
hi TC/TP! would it be possible to provide support via HFAAO Siginet's tool (in 7zip format) found here: http://siginet.ryanvm.net/forum/viewtopic....asc&start=0? i think it would be great for those using OEM cds ... thanks in advance!
Are you trying to push DOS to the limits? thanks in advance!
Check the latest test release...
QUOTE (Tomcat76 @ Mar 13 2006, 04:26 AM)
Changes:
- increased support for application addons with exotic entries (should cover Siginet's OEMBIOS addons among others)
thanks! - increased support for application addons with exotic entries (should cover Siginet's OEMBIOS addons among others)
hi! i just wanted to report that i was able to do some tests the past couple of days ... tried using it with Dell OEM XP Pro SP2 ... verified that oembios.* files were present in i386 ... but upon getting to the GUI, it asked for activation ... tried likewise previous suggesion to copy winnt.sif from i386 to FIX (although i thought it wouldn't have mattered anyhow since the original file is copied over too during the cmd run ) ... still with the same result ... i know this is an obvious Q but i'd like to ask anyway: would using these OEM CDs be exclusive only for the vendor's machine? you i am trying this in a piece-by-piece assembled system ... i know Dell employs a BIOS-lock mechanism to keep it activation free ...
btw, i've been using HFSLIP for a time now ... & i only got to pay attention to the use of winnt.sif in fix just very recently ... i understand that FIX is used to overwrite compressed file in the source ... so why is FIX (vs HFEXPERT/APPREPLACEMENT) the directory for winnt.sif?
he! he! thanks!
) ... still with the same result ... i know this is an obvious Q but i'd like to ask anyway: would using these OEM CDs be exclusive only for the vendor's machine? you i am trying this in a piece-by-piece assembled system ... i know Dell employs a BIOS-lock mechanism to keep it activation free ... btw, i've been using HFSLIP for a time now ... & i only got to pay attention to the use of winnt.sif in fix just very recently ... i understand that FIX is used to overwrite compressed file in the source ... so why is FIX (vs HFEXPERT/APPREPLACEMENT) the directory for winnt.sif?
he! he! thanks!
Kiki - The files in the hfexpert\appreplacement folder get "pemodified" (if required) and compressed. The FIX folder assumes the files are already compressed and pemodified (if required). Not all files require pemodify, but the ones in appreplacement typically do. I suppose putting your winnt.sif file in appreplacement could work, but I never tried it. Why not test and report back?
Sorry I can't answer your first part of your q.
Sorry I can't answer your first part of your q.
ey TP ... nice to hear from you again! thanks for the reply ... as always i actually intend to experiment on that too (winnt.sif in APPREPLACEMENT) to explore alternate avenues for our cmd ... it's just sad that i couldn't do much testing yet as i'm just using my sister's pc (the reason too for trying OEM pre-activation in a clone machine )... as mine's still busted (mobo is for Athlon XPs but it doesn't work for 2000+, 2200 & 2600 ... yet surprisingly works on Sempron 2200 although shows as Athlon 1200 only ... he! he!)
... it's just sad that i couldn't do much testing yet as i'm just using my sister's pc (the reason too for trying OEM pre-activation in a clone machine )... as mine's still busted (mobo is for Athlon XPs but it doesn't work for 2000+, 2200 & 2600 ... yet surprisingly works on Sempron 2200 although shows as Athlon 1200 only ... he! he!)
QUOTE (Homer_m @ Dec 6 2006, 02:28 PM)
All that has to be done is to look in the I386 folder of the original Dell OEM disk and copy the WINNT.SIF that's in there to the FIX folder hfslip creates. That's it.
hi gentlemen! ... what i discovered in one of my runs today was odd ... i tried Homer_m's suggestion on a clone desktop machine with a Dell OEM XP SP2 issued for a portable ... by simply copying winnt.sif found in i386 of the cd & placing it in FIX ... and it worked --- preactivated OS! install test was done in a VM so i've yet to burn & test it on a real machine ... strange ... i understand that our CMD copies everything from the SOURCE to SOURCESS ... & this includes winnt.sif residing in i386 directory ... however installing the build without prior placement of winnt.sif in FIX requests for activation upon hitting GUI ... now i'm confused ... i will try to do the tests again to duplicate this ...
hi to those interested (if any still?) 
i just wanted to share that putting winnt.sif in FIX seemingly worked as no more prompt down at the lower right portion of the taskbar for activation shows ... however by going through Event viewer, this was what i saw:
Click to view attachment
... o geez! i guess, it's back to the drawing board again ...
i just wanted to share that putting winnt.sif in FIX seemingly worked as no more prompt down at the lower right portion of the taskbar for activation shows ... however by going through Event viewer, this was what i saw: Click to view attachment
... o geez!
i guess, it's back to the drawing board again ...
QUOTE
hi to those interested (if any still?)
Let us know if you find an answer.
hi guys! i'm not sure if this would be of any relevance or help to the issue here but you may want to take a look at this: Download the Windows OEM Installation Kit - NEW ... please do share your experience ...
Hey all.
Man it's been a LOOOONNNNGG time since I've been around, but saw this topic and thought I'd join in (kinda late but...).
I have been using HFSLIP with IBM OEM and Toshiba OEM since I first tripped over this forum, back in 2k5. I have no issues with the actual slipping process. everything is great. My installs of XP are from network share (instead of CD) so I use unattend.txt file instead of winnt.sif. The issues are:
1. cannot share source between OEMs. Results same as #3 below. Need to run HFSLIP on each OEM. I don't have the patience to look for specific files each computer requires as validation (one of the reasons HFSLIP is now labled "PreRequisite tool #1a" on my list of utilities along with BARTs [#1b] ).
2. unattend.txt needs to be modified with proper key. OEM specific (IBM, Toshiba) as well as OS specific (XP, MCE, Tablet)
3. installation into VMWare requires activation. Virtual environment not seen as OEM?
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
Man it's been a LOOOONNNNGG time since I've been around, but saw this topic and thought I'd join in (kinda late but...).
I have been using HFSLIP with IBM OEM and Toshiba OEM since I first tripped over this forum, back in 2k5. I have no issues with the actual slipping process. everything is great. My installs of XP are from network share (instead of CD) so I use unattend.txt file instead of winnt.sif. The issues are:
1. cannot share source between OEMs. Results same as #3 below. Need to run HFSLIP on each OEM. I don't have the patience to look for specific files each computer requires as validation (one of the reasons HFSLIP is now labled "PreRequisite tool #1a" on my list of utilities along with BARTs [#1b]
).2. unattend.txt needs to be modified with proper key. OEM specific (IBM, Toshiba) as well as OS specific (XP, MCE, Tablet)
3. installation into VMWare requires activation. Virtual environment not seen as OEM?
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
hey NtegrA! thanks for sharing your find!
QUOTE (NtegrA @ Feb 23 2007, 12:37 AM)
3. installation into VMWare requires activation. Virtual environment not seen as OEM?
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
Your above two comments may not be valid if you use VLK. With VLK, you do not need to activate AT ALL (applicable to XP, 2000, and 2003). All else....I have no doubts.
I am similar to you:
- use unattend.txt
- use both CD/DVD and NETWORK installation through MSDOS (WIN98SE DOS) and WinPE
- use VMware Workstation, ESX, VPC and VPC Enterprise Server for developing and testing customized OSes
I have never activated any operating systems with VLK before, except the WinXP Tablet PC Edition, which our Enterprise Agreement did not include VLK for Tablet PCs for some reason.
QUOTE (Kiki Burgh @ Feb 10 2007, 05:55 PM)
hi to those interested (if any still?) i just wanted to share that putting winnt.sif in FIX seemingly worked as no more prompt down at the lower right portion of the taskbar for activation shows ... however by going through Event viewer, this was what i saw:
Click to view attachment
... o geez! i guess, it's back to the drawing board again ...
i just wanted to share that putting winnt.sif in FIX seemingly worked as no more prompt down at the lower right portion of the taskbar for activation shows ... however by going through Event viewer, this was what i saw: Click to view attachment
... o geez!
i guess, it's back to the drawing board again ...btw, there is a line in the UNATTEND.TXT (or WINNT.SIF) that tells the system to automatically activate:
CODE
[Unattended]
Unattendmode = FullUnattended
OemPreinstall = YES
TargetPath = WINNT
Filesystem = ConvertNTFS
OemSkipEula = YES
DriverSigningPolicy = Ignore
ExtendOemPartition = 1
AutoActivate = No
UnattendSwitch = Yes
CrashDumpSetting = 0
DisableDynamicUpdates = Yes
WaitForReboot = No
Unattendmode = FullUnattended
OemPreinstall = YES
TargetPath = WINNT
Filesystem = ConvertNTFS
OemSkipEula = YES
DriverSigningPolicy = Ignore
ExtendOemPartition = 1
AutoActivate = No
UnattendSwitch = Yes
CrashDumpSetting = 0
DisableDynamicUpdates = Yes
WaitForReboot = No
I have not tried setting it to "AutoActivate = Yes" before. Like I mentioned in an earlier post, I never need to activate with VLK
Btw, If you are using Winnt.exe to install Windows (install from DOS), make sure that "UnattendSwitch = Yes".
It's worth a try...but I believe you may need to have a direct connection to the Internet. If however you are behind a proxy server, try adding this:
CODE
[Proxy]
Proxy_Enable=1
Use_Same_Proxy=1
HTTP_Proxy_Server = http://proxyserver:80
Proxy_Enable=1
Use_Same_Proxy=1
HTTP_Proxy_Server = http://proxyserver:80
I don't mean make it sound complicated
but if your company uses Automatic Configuration Scripts like we do, add this setting instead of [Proxy]:CODE
[URL]
AutoConfigURL = http://configserver/autoconfig.ins
AutoConfigURL = http://configserver/autoconfig.ins
QUOTE (iTwins @ Feb 23 2007, 12:32 PM)
QUOTE (NtegrA @ Feb 23 2007, 12:37 AM)
3. installation into VMWare requires activation. Virtual environment not seen as OEM?
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
4. (side note) Activation can't be done automatically if you use key from COA sticker. OEMs are required to call MS to activate.
Your above two comments may not be valid if you use VLK. With VLK, you do not need to activate AT ALL (applicable to XP, 2000, and 2003).
VLK activation is not an issue as VLK media is not being used, making 3 and 4 always valid
QUOTE (NtegrA @ Feb 24 2007, 03:51 AM)
VLK activation is not an issue as VLK media is not being used, making 3 and 4 always valid
Heh, in that case, I rest my case.
But then, it would be pointless to say that "installation into VMWare requires activation". If VLK is not used, Installation ANYWHERE, inside or outside of VMware, would require activation.
Anyone try UWin Installer?
This is from the readme:
This is from the readme:
QUOTE
Do You Want To Install Or Upgrade Micosoft Windows Operating System On Your
Computer With Setup Files On Your Hard Disk.
Then UWin Installer (UWI) is what you NEED!
UWI Is A Tool For Quick & Easy Install Or Upgrade Of Microsoft Windows O.S.
By End User From Setup Files On Hard Disk Without End User Attention.
UWI works for Windows 98/ME/2000/XP/2003 Operating System Installation.
What Can UWI do:
- Makes Windows Operating System Installation Quicker By 30%
...
Computer With Setup Files On Your Hard Disk.
Then UWin Installer (UWI) is what you NEED!
UWI Is A Tool For Quick & Easy Install Or Upgrade Of Microsoft Windows O.S.
By End User From Setup Files On Hard Disk Without End User Attention.
UWI works for Windows 98/ME/2000/XP/2003 Operating System Installation.
What Can UWI do:
- Makes Windows Operating System Installation Quicker By 30%
...
some related discussions:
Dell OEM and WPA
DELLXP INSTALL DISK - Trying to perform unattended setup- Noob
Building a Pre-activated CD from an existing installation
and of course, the most extensive:
OEMScan - Automated Multi Manufacture Pre-Activation Utility
btw, thanks iTwins for the feedback
Dell OEM and WPA
DELLXP INSTALL DISK - Trying to perform unattended setup- Noob
Building a Pre-activated CD from an existing installation
and of course, the most extensive:
OEMScan - Automated Multi Manufacture Pre-Activation Utility
btw, thanks iTwins for the feedback
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.