Hello,
Just wondering if the ISO image can be used with PXE BOOTP install via a local LAN? I am using Unattended http://unattended.sourceforge.net/index.php (http://unattended.sourceforge.net/index.php). I was thinking to copy the \I386 folder only to my PXE server! Would the above approach work? Thanks for sharing your CD. :)
I think no specialist included me will be able to answer such a gobbledygook.
Hello, Greetings scarface,
Thank you for your reply and please do let me try to explain:
1. I have a Local area network (LAN);
2. Within this LAN, I also have a Trivial File Transfer Protocol (TFTP) server;
3. With that I can install software using the Preboot eXecution Environment (PXE) protocol;
4. Normally, I would just copy the I386 directory to my TFTP server say /srv/wxpp32/i386;
5. I also have an unattend.txt file on the TFTP server which would copy over;
6. Once I initiate the install, PXE will copy files to the C:\ drive; and
7. Once complete, then PC reboots and install from C:\ drive.
I did copy the CD to my TFTP server, however, Windows XP text mode setup cannot copy the following files consistently:
1. ie4uinit.mui;
2. iedkcs32.mui;
3. ieframe.mui;
4. mshta.mui;
5. msrating.mui; and
6. msvbvm50.dll.
After a couple of reboots WinXpP reports at T=13 minutes that:
QuoteC:\WINDOWS\system32\regsvr32.exe.
Windows cannot access the specified device, path, or file. You may not have the appropriate permissions to access the item.
I then press OK a few times and continue my setup and in GUI mode, Windows reports that:
QuoteYour current security settings do not allow this file to be downloaded.
Install fails. Anyone have any idea would be much appreciated.
check that there are no duplicated entries about these files
1. ie4uinit.mui;
2. iedkcs32.mui;
3. ieframe.mui;
4. mshta.mui;
5. msrating.mui; and
6. msvbvm50.dll.
in txtsetup.sif like:
ie4uinit.mui = 1,,,,,,,2,0,0,ie4uinit.exe.mui
ie4uinit.mui = 1,,,,,,,1005,0,0,ie4uinit.exe.mui
ie4uinit.mui should be copied to \windows\system32 and renamed to ie4uinit.exe.mui, and to \windows\system32\en-US\ and then deleted from temporary dir but problems might happen-thats why it sparks a 'file not found'.
also try to switch msdosinitiated=0 to 1 as msdosinitiated=0 tells the setup its initiated from a CD.
Thank you! I am working with the latest June 2013 .iso files, I had found the following lines in TXTSETUP.SIF:
Quoteie4uinit.mui = 100,,,,,,,2,0,0,ie4uinit.exe.mui
ie4uinit.mui = 100,,,,,,_x,270,0,0,ie4uinit.exe.mui
iedkcs32.mui = 100,,,,,,,2,0,0,iedkcs32.dll.mui
iedkcs32.mui = 100,,,,,,_x,270,0,0,iedkcs32.dll.mui
ieframe.mui = 100,,,,,,,2,0,0,ieframe.dll.mui
ieframe.mui = 100,,,,,,_x,270,0,0,ieframe.dll.mui
mshta.mui = 100,,,,,,,2,0,0,mshta.exe.mui
mshta.mui = 100,,,,,,_x,270,0,0,mshta.exe.mui
msrating.mui = 100,,,,,,,2,0,0,msrating.dll.mui
msrating.mui = 100,,,,,,_x,270,0,0,msrating.dll.mui
msvbvm50.dll = 1,,,,,,,2,0,0 (line 5902)
msvbvm50.dll = 100,,,,,,,2,0,0
I removed the line 5902 (see above) and after that file=msvbvm50.dll copied successfully.
As the other *.mui files need to be placed in two different directories (ie, directories 2 and 270), I left the lines alone but that didn't work! However, if I commented out all lines contained "100,,,,,,_x,270,0,0,", then all files can be copied successfully. My plan is to manually add the five files using $oem$\$1\system32\en-US\ later.
I also use msdosinitiated=1 but I am still getting the same error at T=13 minutes. Only one small steps closer. After the failure, I went in and inspected the drive and determined that the directory %SystemDrive%\systems32 is "read only"? Anyone has a solution please post.
Check cmd takeown /f path /r /d y
According this link: http://technet.microsoft.com/en-us/library/cc753024%28v=ws.10%29.aspx (http://technet.microsoft.com/en-us/library/cc753024%28v=ws.10%29.aspx)
QuoteApplies To: Windows 7, Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2, Windows Server 2008, Windows Server 2008 R2, Windows Vista
Q1. Is there a Windows XPP command I can use?
Q2. If so, where would I place this command? eg. in *.INF, *.CMD, etc.
Many thanks!
could you first check the file is not missing or altered?
Not sure what you are asking? However the file=takeown.* cannot be found in the last three released .iso with release dates May 2012, November 2012 and June 2013.
regsvr32. I suspect your iso is not original and can include errors.
no one still cares about xp and a fortiori to install it from a ftp. You are probably a very devious person.
"Windows XP: Download & Support" is the most visited/replied to topic on this forum a fortiori some one (eg 40% of US Businesses) still cares about XP.
Hopefully they will be off line by April
to topdog:
You are right, this is the most visited forums. But its like TV: the emissions with the best audience are not the best, they are usually the worst and the most daft. But xp was a very good os, however its outdated and most users still using it are not installing it as a brand-new os. I didnt criticize it, just the fact that other alternatives are possible.
on the contrary the specialist aa1234779 asked me in days of old if a section for open source (linux) would be of any use. I told him no-one would answer him, but it doesnt demean linux of course.
Gentlemen,
Thank you for all your comments and all your help; much appreciated. Let me explain further. Indeed XP is old and MS will discontinue their support in about a year. However, a few of my clients whom run small businesses (10 and up to 50 workstations). At this very moment all my clients are still running XP with their desktop. Some of the notebooks are now on Win7, etc. The problem is that a few of them are still using "DOS" programs written in the 90s. Why? Costs! I am not alone, Banks, Airlines, lots of big companies are still running XP.
Anyway, the install method I chose: http://unattended.sourceforge.net/index.php (http://unattended.sourceforge.net/index.php) works for me for years with the original CD + SP3 on a network share\i386. I was hoping I can use the ISO image created by Maher so that I can take advantage of all the latest security fixes. My thinking is that if someone had already invented the wheel, why try to reinvent the same wheel? More later!
So its working with an original xp but not with maher's?
I dont know how maher creates his isos, he seems he want to keep the secret, but most probably he uses an integrator such as nlite. its known to give inconsistancies with winnt.sif dosnet.inf, txtsetup.sif or other things.
The only way to have a perfect updated iso is using...sysprep. For xp the procedure is different from 7 and 8 I think but if you really want something perfect perhaps you should do it yourself. I say that without consideration about what is uploaded here. Download the tutorial of harkaz to see what Im talking about.
Maher is indeed using nLite, as in the last line of many of the *.INF files say so:
Quote; Customized by nLite - www.nliteos.com
I have used nLite in the past as well and nLite works well. As you have suggested, I may just have to bite the bullet.... Again, why reinvent the wheel? :( So, someone has a solution? Please post!
it seems your wheel is not adapted for your use. Then use sysprep, as I said before.
Ive looked how to run sysprep for xp. Its a little different from vista and 7. its located in support/tools on the cd. Now you have the elements to do what you want. I already gave a few elements about sysprep and winpe on the forum for a few users but they didnt give signs of life. Obviously they were too weak to do something. With your knowledge about setting a ftp you are even able to do it via vmware. In fact the only question now is: are you a wimp or not? and its a binary question. You can only answer yes or no.
If you decide to sysprep xp i can be available for questions.
It has been so long ago since my colleagues and I test-drove System Preparation Tool (Sysprep); circa Windows 2000 P & Server and Sysprep v1.1 (I think?). It didn't really worked for us! From memory, I recalled that we had lots of issues with Security Identifier (SID). Sysprep is not the answer. The answers are the following two LAMP/PXE/TFPT/Samba server based "Open Source" tools:
1. http://unattended.sourceforge.net/index.php (http://unattended.sourceforge.net/index.php)
2. http://www.opsi.org/en (http://www.opsi.org/en)
I never tested with xp but never had problems with 7. sysprep is now v3.14. Contact the sysprep specialist harkaz for further information: http://www.nomaher.com/forum/index.php?action=pm;sa=send;u=60846
It seems sysprep for xp was indeed complicated:
(https://i.ibb.co/Tg451rM/IC96752.gif)
"Audit boot and factory" probably stands for "audit mode and oobe" in 7. As for the flags, I don't know their meaning. But you will likely not follow this way.
Sysprep 1.0 and 2.0 for Windows XP have serious flaws compared to the sysprep v 3.14 found in Windows Vista and later.
-To use sysprep in XP, you have to log in as system Administrator immediately after installing Windows. (Trick: to do this in oobe after XP Setup completes, enter "System" as a user name at the "Who will use this computer?" screen.) After that, create a folder named "Sysprep" in C: drive. (C: must be the drive where you have installed windows xp).
-Copy sysprep executable files in C:\Sysprep folder. Run sysprep.exe and click the "Audit" button. Optionally, create a winbom.ini file with configuration details about entering the audit mode.
-System will restart in audit mode. Audit mode in XP is similar to the Windows 7 audit mode. In audit mode you can install software and updates for your image. Avoid installing antivirus software.
-Perform all necessary system reboots. Your system will continue in audit mode until you decide to reseal your system. The "Factory" button is used when you have changed the winbom.ini file and you want to apply those changes.
-Create an appropriate sysprep.inf file, include mass storage (SCSI/RAID) driver files for the first boot, unattended settings, HAL-related tricks, specify OS installation files (use Windows XP CD files or merge them with the updated DLLCache files) and more. sysprep - bmsd command from the command line to prepare sysprep.inf with all native Windows XP SCSI/RAID Drivers
-Prepare your system for the end-user= Use mini-setup, Scan for PnP, generate SIDs (do not check the NoSIDGen box) and refresh the original 30-day grace period (do not check Preactivated) + finally click reseal.
-Capture image.
You should use the sysprep executable found in the CD-ROM for the Windows XP Service Pack you are using. For example, if you want to sysprep windows xp SP3 you have to use sysprep from the official Windows xp sp3 disk (not a manually slipstreamed one). (The image you posted is from sysprep 1.0).
Second, sysprep is actually a frontend for Mini-Setup or Windows Welcome. Windows Welcome is another name for the out-of-the-box experience while Mini-setup is a compact mode of Windows Setup. Windows Welcome is ludicrous and cannot be used to deploy Windows XP on different Hardware. Mini-Setup is the best option. Mini-setup generates a new security identfier (SID) for your system, uninstalls all previously installed devices, detects the new computer hardware and optionally updates the HAL, configures basic system settings (computer name, product key, date and time, locale, networking, etc.) and prepares the user environment for first time use. Problem: it is available only under Windows XP Professional. Moreover, you have to use the same HAL with the reference computer (the system you have created the image from).
I will be back later with more info about XP's sysprep.
Probably I will also make the switch to ubuntu rather soon. Windows 8.1 has no significant improvements over Windows 8. Linux is a very powerful and free platform. By the way, do you know backtrack?
I dont but it seems complete. For windows 8 lets see, I have a windows 8 phone and it is rather convenient.
For linux the plus is an antivirus is not needed and the firewall is very good (can manage both incoming and outgoing connection contrary to windows, technically I think you can connect in passive mode with linux like behind a router, thats not the case with windows which dont block incoming connection, so its not secure at all...even if in pratic the passive mode is not recommended), anyway the command "sudo apt-get install gufw" is needed to install the firewall gui.
Also the mingw compiler is interesting, its used to compile...some windows apps: I wanted to recompile handbrake, which is compiled under ubuntu lts with mingw for my own needs. It will be probably done next year, I'm going to be busy this year.
Beware with your wep software, airplay, airdump are not really legal, now most keys are wpa by the way.
I have used backtrack to retrieve WEP passwords. Backtrack is much more powerful than that, It can be used to penetrate in Windows systems, for example, but I don't know at all how to do that. It's not so familiar an interface.