Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Sign in to follow this  
clivebuckwheat

Nlite cd to a network share

Recommended Posts

Hi

I have my nlite cd working perfectly, with the os and many apps installed like a charm. Now I would like to transfer my Nlite cd to a network share, and start the install from the network share.

Is this possible?, how would a go about this?.

Share this post


Link to post
Share on other sites

Ive put my packages on a network share and the cd calls a batch file on a server that installs the packages, bashrats packs take care on the drivers part:-)

I think you are referring to a distribution share instead of installing via the cd,

Edited by mike1210

Share this post


Link to post
Share on other sites

no windows is installed from the cd its only the packages which come from a network. The batch file is called from the answer file

mine looks like this on the answer file

which is stored in the xp cd in \$OEM$\$1\D

$OEM$ is made for the drivers

$1 is the system drive

and D is the driver folder made by the bashrat drives

answer file extract:

[GuiRunOnce]

%systemdrive%\D\batch_file.cmd

the batch file calls another batch file stored on the server, reason i did it this way was i can make changes to the file without having to reburn the cd

check out http://unattended.msfn.org/unattended.xp for all guides on how to do it

Edited by mike1210

Share this post


Link to post
Share on other sites

I set up the source with the $OEM$ production folders on a network share, then start the computer with Bart's PE, map a network drive to the share, and start winnt32.exe from there. Try searching the forums for winnt32 or winnt32.exe; there's a bunch of info.

Share this post


Link to post
Share on other sites

Do I have to use the bartpe boot disk?

I was hoping to make a network boot cd that loads the nic driver, maps to a network share using the net use command, and then fire off the windows xp install using the winnt32.exe command.

Obviously this network share will contain the contents of my unattended nlite xp cd.

Edited by clivebuckwheat

Share this post


Link to post
Share on other sites

Yep, that's the way to go.

BartPE, Net use command and winnt32.exe command.

Search for the right winnt32 command line on the forums.

You will be making a local source that way.

After reboot, the normal stuff will go on... without CD!

No more CD burning, just Bart.

Don't forget to put the $OEM$ inside I386.

Edited by Djé

Share this post


Link to post
Share on other sites

:}

can you explain me why it is better to use the bartpe disk as opposed to a "normal" boot cd that loads the nic driver and maps to the network share?

I really don't understand the upside of using bartpe disc.

Share this post


Link to post
Share on other sites

What do you mean by a "normal" boot CD? Are you loading DOS, or some variant (e.g. FreeDOS)? If so, winnt32.exe won't run, but winnt.exe will, and you can use the same basic idea.

You've got the concept...load some OS from the CD, connect to the network, start the Windows install via winnt.exe or winnt32.exe (depending on your OS), reboot. Easy!

On a side note, if you specify "..\$OEM$" for the OEMFilesPath in your unattend file, you do not have to embed $OEM$ inside I386; you can keep it parallel. This is useful if you decide to use junctions to create network installation sources on-the-fly (I made a PHP app for our technicians to customize the $OEM$ folder for their particular install needs).

Edited by tridgely

Share this post


Link to post
Share on other sites

Thanks for the reply. Yes something like freedos on a boot cd that will load the nic driver and then map to a network share using the tried and true net use.

I read what you wrote about the OEM, but excuse my ignorance here, I don't quite understand what you mean?. This will be the first time I try an unattended install from a network share.

if you could elaborate a bit more on the OEM portion of your post i would greatly appreciate it.

Share this post


Link to post
Share on other sites

The advantage of using BartPE is those windows tools in it.

Plus, when installing from a network share, you are AUTOMATICALLY making a local source.

And I don't know about write access to a ntfs partition from dos to do this, if ever you don't have any fat partition arround. But maybe winnt.exe can deal with that. Don't know.

For the $OEM$ thing: this is an additionnal folder that may be on your CD (next to I386) with some extra stuff to install (applications, drivers, etc.). If you don't have it then don't worry about it, you don't need it, otherwise nLite would have made it.

Now, your turn: experiment and tell us about it. ;)

@tridgely: thanks for the OEMFilesPath trick. I'll make good use of it. :)

Share this post


Link to post
Share on other sites

I used to use a DOS-based installation method, running winnt.exe, as clivebuckwheat has explained above. This method has some limitations to it that caused me to switch over to Bart's PE for winnt32.

Using winnt.exe in DOS, your filenames must match an 8.3 filename restriction, which many of my installers in $OEM$ did not. Because of this, I used to 7zip them all up and unpack them after the install, but it was tedious to maintain.

Also, you have a restriction on the amount of data that you can copy over. I believe it's 2 gigs, but that could be wrong.

I've been very happy since I switched to Bart's PE. The learning curve was fairly steep, so I was up and running pretty quick.

@clivebuckwheat, if you have a $OEM$ distribution folder, basically used to copy extra files over during setup, it would normally need to be placed inside the i386 folder for a network-based installation via winnt.exe. However, if you make an entry in your unattend answer file, you can specify the location of the $OEM$ folder. By placing a line with:

OEMFilesPath="..\$OEM$"

In your unattend file, then you can keep $OEM$ parallel to (alongside) the i386 folder.

After this is all said and done, will create a batch file in DOS to map the drive via net use, and then run winnt.exe from the i386 folder, with the switches that you want.

I'm not 100% sure what you're having trouble with, but I'm more than happy to explain further if it helps you.

Share this post


Link to post
Share on other sites

I made a network boot cd(win98), that loads the nic drivers and then I used the command. net use u: \\ComputerName\sharefolder

I wanted to put the contents of my nlite cd in the share folder and start the installing from the share using winnt.exe

But my boot cd bombs out net use command and i get cannot locate registry.

HELP ME :no:

Share this post


Link to post
Share on other sites

Make sure that your path is set as

net use u: \\computername\sharename

and not

net use u: \\computer name\share name

I have had a few times when I made a share on the remote with a shared folder with a space in the name. Check your shared system name and folder.

jd

Edited by 03GrandAmGT

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...