Jump to content

Recommended Posts

Posted

Well gang I have what I'm sure is a simple question for you seasoned veterans out there. A little history first... Been performing unattended installs since Win2K by the old manual ways before such great programs like nLite came out and what now. So, I have the basic skill sets plus some putting me comfortably at an intermediate skill level I'd say.

Here's what I'm looking to do that I cant seem to solve.

Looking to perform an unattended install of WinXP (created like a million of these before) that does (2) additional things either before the first login or at the first login. I do not care which.

1) Import one registry key that sets XP's SourcePath to the C:\ drive.

Example:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Setup]

"SourcePath"="C:\\"

**********

2) Copy the I386 folder from the CD over to the C:\ drive.

Example:

XCOPY %cdrom%\I386 C:\I386 /E /Q

**********

To me this seems like it should be easy to take care of and I can see where using the $OEM$ with cmdlines.txt would probably accomplish the job except I have one problem there, I'm not using the $OEM$ folders for this particular unattended install because I have to use the F6 option during install and I do not want to integrate the drivers on this disk. I require the

So, I've dug through RunOnceEx.cmd and various INF files and cant find a single way to accomplish these two basic tasks. Let me rephrase, the registry import can be easily accomplished I know. I just have no clue how to perform the batch file command to copy the I386 folder from the CD to the C:\. Hopefully someone has come across a similar scenario and can assist here.

I certainly appreciate any help that you can provide.

User0101


Posted

It may look like a solution, but I doubt that you will be able to copy an entire I386 directory from a batch file ran at cmdlines.txt.

Posted (edited)

There's always ways to get around limitations in the XP install scheme. For example, you can always just add files to txtsetup.sif to be copied during textmode setup rather than using $OEM$ folders. You can also make use of svcpack.inf, which gets executed regardless of whether or not setup is unattended. And you can edit the registry hives with runonce entries which would then be exectuted during windows setup. Or you can create an INF to be executed when sysoc.inf is called during setup to do a lot of work for you.

I use a combination of a little of all of those little tidbits to accomplish a lot of fun stuff without requiring an unattended CD :)

Edited by RyanVM
Posted

There are many ways to skin a rabbit.

For the task you have in mind however, the problem will be finding one willing to hang around long enough for the task to complete.

Hence my first response.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...