barnold

Hi, Is there a way to hard-code an IPv6 address from the command line on a server 2K3 or XP system? In Server 2k8 and Vista you can do it via the GUI but in 2K3 and XP the properties button for TCP IPv6 is grayed out, so I think I have to do it from the command line. I'm working in an enterprise network. Both the IPv4 and IPv6 addresses are set to DHCP Here are the IPv6 addresses on my system: IP Address. . . . . . . . . . . . : 2002:c023:9c17:51a:bc51:a6:a34b:a8df IP Address. . . . . . . . . . . . : 2002:c023:9c17:51a:609e:1621:65cc:d20d IP Address. . . . . . . . . . . . : 2002:c023:9c17:51a:216:35ff:feaf:16b0 IP Address. . . . . . . . . . . . : fe80::216:35ff:feaf:16b0%7 I ran the command: netsh interface ipv6 set address "Local Area Connection" 2002:c023:9c17:51a:bc51:a6:a3 4b:a8df and the message, "OK" is returned which leads me to believe that something worked, but did this command set that IP static? How can I confirm that? When I run that same command on the other two IP addresses (ending in d202 and 16b0) I get the message: "A device attached to the system is not functioning" Side question: Why do I have so many IPv6 addresses? I know the fe80 one is the link local address, but why the three 2002.. addresses? Thanks! brian

Everyone, Wanted to let you know that I'm not getting the error anymore. I took John's advice (Thanks John!!) regarding always using fresh source files and looked into RyanVM. I decided to use RyanVM to integrate the hotfixes as well as the driverpacks, then used Nlite only for the unattended stuff and .iso creation. That worked like a charm. I suspect that the problem had something to do with the hotfix or driver integration stages in Nlite. I had extracted the driverpack's drivers to a folder and pointed Nlite to it instead of directly slipstreaming the drivers into the source files using the DPs_Base application. I also had manually downloaded the security updates and was integrating them with Nlite. I think using RyansVM to slipstream that drivers and hotfixes directly into the source files was a lot cleaner and is probably what fixed the problem. Thanks to all for your help!!! brian

Everyone - thanks so much for your help. I will need to continue this on Monday, ok.? I will post results then. Thanks again brian

Thanks for the tips John. I attached the lastsession.ini file (had to remove the BSOD screenshot due to 200k size limitation). I'll start from scratch with a fresh set of source files and keep you posted. Appreciate everyone's support/advice! Regards, Brian

Thanks for the response. This Nlite build WAS working fine before I integrated the updates and I am using the same computer and haven't changed the RAM. I can try to find different hardware to test on to rule that possibility out, but could this have anything to do with the updates? thanks!

Hi, I created an XP with SP3 unattended install disk with Nlite that is bluescreening during setup. This disk was working perfectly BEFORE I integrated any hotfixes. The stop error is: A problem seems to be caused by the following file: setupdd.sys PAGE_FAULT_IN_NONPAGED_AREA Background: In Nlite: Base OS: XP (SP2) Slipstreamed XP SP3 Added Windows Hotfixes Slipstreamed storage, nic and chipset drivers (previously extracted using DriverPacks BASE 8.12.4) The stop error occurs during Setup while the system files are being copied to the hard drive. The file copy process lasts probably 2 or 3 times longer than during a functional setup and I may be wrong, but it appears that it is looping (the same files being copied over multiple times). I'd estimate that the stop error occurs about 15-20 minutes into the copy process. I created the disks in stages and always tested on physical hardware before the next stage. First just the OS with SP3 slipstreamed. Then the OS with the drivers slipstreamed. Those disks worked great, but when I add the updates it fails. The first time this occured I had added all the hotfixes I downloaded (29 in total). Then I rebuilt the disk (using the same lastsession.ini without integrating any hotfixes and it actually failed again, which really surprised me. At that point i suspected that maybe there was something wrong with the system files, so I recopied over the original XP source files to my build folder. Using those files I built a working disk again with drivers and sp3 slipstreamed but without integrating any windows hotfixes. Now I was pleased to be back to square one so I could start from scratch knowing that the OS source files were working. I decided to only integrate 10 hotfixes into the next build but again, it failed with the exact same PAGE FAULT IN NON-PAGED AREA error and referenced setupdd.sys as the possible culprit. Could one of the hotfixes cause this error? Is there a proper method to add the hotfixes to nlite (i.e. should I add them in numerical order by release date, or by KB number)? See attached pic and thanks for your help. brian LAST_SESSION.INI

Hi, I'm unable to get the PENETCFG plugin to automatically load network support. When Barts loads I'd like network support to be automatically enabled, the nic detected and an IP address automatically assigned by DHCP. If I manually load netowork support the nic is detected and an address assigned without a problem. I currently do not have the BARTPE: Network Support plugin enabled. Can anyone provide some advice? Thanks! brian Here's the code of the PENETFCG files: PENETCFG.INF ; PE Builder v3 plug-in INF file [Version] Signature= "$Windows NT$" [PEBuilder] Name="PENETCFG: PE Network configurator (theTruth)" Enable=1 Help="penetcfg.htm" [sourceDisksFiles] penetcfg.exe=2,,1 penetcfg.ini=2,,1 penetcfg-*.ini=2,,1 readme.txt=2,penetcfg.txt,1 license.txt=2,penetcfg.lic,1 srvsvc.dll=2 [Append] nu2menu.xml, penetcfg_nu2menu.xml PENETCFG.INI [General] AutoStartNet=Yes PromptForProfile=No ShowGUI=Yes [NetProfiles] Dynamic IP Address (DHCP)= penetcfg-dhcp.ini Static IP Address (Manual)= penetcfg-static.ini Custom from A:\= a:\penetcfg.ini Custom from C:\= c:\penetcfg.ini ; You will get the settings below if you hit ; escape/cancel on the profile dialog [NetAdapter1] EnableDHCP=Yes UseStaticGateway=No UseStaticDNS=No UseStaticWINS=No IPAddress= SubnetMask= DefaultGateway= DNSServer= [NetDrive1] Drive= NetworkPath= UserName= Password=

Thanks for the response. I initially tried the driverpacks and they slowed down the installation time dramatically. I'm 90% done with this disk and removing all my manually-added drivers (which are working great) and trying out the driverpacks again is unnecessary. Can you or anyone else comment on my question(s)? I'm very curious about the order in which Nlite integrates drivers. Thanks! brian

Hi, I'm using Nlite to create an unattended install of XP with SP3 on multiple hardware models. My question pertains to the driver installation order that Nlite uses. In the "official guide" ( http://unattended.msfn.org/unattended.xp/view/web/34/) it says when you are installing drivers via winnt.sif to name the driver folders starting with numbers to assure that they are installed numerically in the correct order like this: 000_chipset 001_network 002_graphics 003_tv_out 004_sound 005_monitor 006_keyboard 007_mouse 008_and_so_on As I said I am using Nlite for this disk (not winnt.sif) and want to know if I still need to name the folders in this order. Currently my disk is working well on multiple hardware models and I did not put much thought into the folder order because Nlite doesn't appear to care what order I put them in. In the i386\NLDRV folder nlite has a bunch of folders: 001, 002, and so on.. but the order is completely random (i.e. 001 is a storage driver, 002 - 004 are audio drivers, 005 is a network driver, then there is a storage driver a few folders later, etc) My folder structure is in alphabetical order because thats how Windows likes them Audio Network Storage USB Video I purposely have not included any chipset or cpu drivers because i don't want to take a chance and hose my disk (which is working well so far) by accidentally implementing them in the wrong order. From what I have read it is important that the chipset driver be installed first. If I change to a numerical folder structure and add a chipset folder I might change it to look something like this: 000_chipset 001_storage 002_network 003_graphics 004_sound 005_usb I guess my questions are: 1) Do I need to use the numerical folder structure if I'm using Nlite? 2) Does Nlite even care about the folder structure? 3) If Nlite doesn't care about the folder structure, is it smart enough to install the chipset drivers first? 4) Does the above folder order look good? Thanks! brian

Hi, I'm using Nlite to create an unattended install of XP with SP3 on multiple hardware models. My question pertains to the driver installation order that Nlite uses. In the "official guide" ( http://unattended.msfn.org/unattended.xp/view/web/34/) it says when you are installing drivers via winnt.sif to name the driver folders starting with numbers to assure that they are installed numerically in the correct order like this: 000_chipset 001_network 002_graphics 003_tv_out 004_sound 005_monitor 006_keyboard 007_mouse 008_and_so_on As I said I am using Nlite for this disk (not winnt.sif) and want to know if I still need to name the folders in this order. Currently my disk is working well on multiple hardware models and I did not put much thought into the folder order because Nlite doesn't appear to care what order I put them in. In the i386\NLDRV folder nlite has a bunch of folders: 001, 002, and so on.. but the order is completely random (i.e. 001 is a storage driver, 002 - 004 are audio drivers, 005 is a network driver, then there is a storage driver a few folders later, etc) My folder structure is in alphabetical order because thats how Windows likes them Audio Network Storage USB Video I purposely have not included any chipset or cpu drivers because i don't want to take a chance and hose my disk (which is working well so far) by accidentally implementing them in the wrong order. From what I have read it is important that the chipset driver be installed first. If I change to a numerical folder structure and add a chipset folder I might change it to look something like this: 000_chipset 001_storage 002_network 003_graphics 004_sound 005_usb I guess my questions are: 1) Do I need to use the numerical folder structure if I'm using Nlite? 2) Does Nlite even care about the folder structure? 3) If Nlite doesn't care about the folder structure, is it smart enough to install the chipset drivers first? 4) Does the above folder order look good? Thanks! brian

Hi, I'm using Nlite to create an unattended install of XP with SP3 on multiple hardware models. My question pertains to the driver installation order that Nlite uses. In the "official guide" ( http://unattended.msfn.org/unattended.xp/view/web/34/) it says when you are installing drivers via winnt.sif to name the driver folders starting with numbers to assure that they are installed numerically in the correct order like this: 000_chipset 001_network 002_graphics 003_tv_out 004_sound 005_monitor 006_keyboard 007_mouse 008_and_so_on As I said I am using Nlite for this disk (not winnt.sif) and want to know if I still need to name the folders in this order. Currently my disk is working well on multiple hardware models and I did not put much thought into the folder order because Nlite doesn't appear to care what order I put them in. In the i386\NLDRV folder nlite has a bunch of folders: 001, 002, and so on.. but the order is completely random (i.e. 001 is a storage driver, 002 - 004 are audio drivers, 005 is a network driver, then there is a storage driver a few folders later, etc) My folder structure is in alphabetical order because thats how Windows likes them Audio Network Storage USB Video I purposely have not included any chipset or cpu drivers because i don't want to take a chance and hose my disk (which is working well so far) by accidentally implementing them in the wrong order. From what I have read it is important that the chipset driver be installed first. If I change to a numerical folder structure and add a chipset folder I might change it to look something like this: 000_chipset 001_storage 002_network 003_graphics 004_sound 005_usb I guess my questions are: 1) Do I need to use the numerical folder structure if I'm using Nlite? 2) Does Nlite even care about the folder structure? 3) If Nlite doesn't care about the folder structure, is it smart enough to install the chipset drivers first? 4) Does the above folder order look good? Thanks! brian

Hi, I want to print out all pages of the beginner, intermediate and advanced unattended Windows guides on this page: http://unattended.msfn.org/unattended.xp/view/web/1/ I don't see a way to print all 3 guides at once and it looks like I have to print out the individual topics and subtopics which could take a while. Is there a .pdf or something that combines all 3 guides that I can printout? Thanks brian

So sorry for the delayed response - I have been away from an Internet connection for almost a week now. There is not a "NoRun" entry in the path you specified. Any other ideas? Thanks! brian

Hi, The Run command is missing from my XP unattended install. I chose Classic Start Menu and do not have "Hide Run Button" selected in the Tweaks option. Ideas? Thanks! brian

Hi, I would like to clean install XP and have the system or boot partition of the computer to be F: (not C:), however, I don't see that as an option during XP Setup (clean install). Is it possible to have the boot or system drive letter to be anything other than C:? Thanks! brian