Jump to content

Flupko

Member
  • Posts

    8
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Netherlands

About Flupko

Flupko's Achievements

0

Reputation

  1. I got it to work in the end. sorry for posting weeks after asking.. but I just didnt get around to it. My commandline looks like this now: I:\win2000.sp3\I386\WINNT32.EXE /S:i:\win2000.sp3\i386 /unattend:c:\unattend.sif /makelocalsource /syspart:c: /tempdrive:c: /noreboot Where I:\win2000.sp3 is the place where I have my install files. This way i dont have to boot after using Diskpart.exe to configure the disk. Thanx for all your help and support guys!
  2. I got it to work guys!! Mats question if I stripped it made me think. I began from scratch again, because I did inject lots of drivers and played with some files of my previous WinPE build. I have now build a new one, and that one is slightly (1MB) bigger then the previous one. Now when I run my scripts they run fine, without strange error messages. I would like to thank all of you for your help and support! Thumbs up guys, much appreciated!
  3. Yes, i used the buildoptionalcomponents.vbs, and in my second try, I installed all components. I started the OC.bat by hand, and that doesnt give me an error. I did not strip it down yet, although i was planning to. I also ran the testwsh.vbs, and that runs fine.
  4. I changed the line to WScript.CreateObject("wscript.shell") I then get the following error message: Could not locate automation class named "wscript.shell" Im new to WinPE, could someone tell me if its even possible in WinPE to use scripts like these? Must be, othwerwise WinPE would be as much as useless, but im not so sure anymore.
  5. Im trying to run VBS scripts in WinPE to automate the installation of W2k and W2k3. When i run a simple script that should start Notepad.exe, i get the following error message: ActiveX can't create object: "wscript.shell" Here's the script im trying to run: ---------------------------------------------------------------------------------- Dim server_shell Dim oExec Dim strExecPath strExecpath= "c:\WINDOWS\system32\notepad.exe" Set server_shell = CreateObject("wscript.shell") Set oExec = Server_shell.exec (strExecpath) While oExec.Status = 0 WScript.Sleep 50 Wend wscript.echo "Done" ------------------------------------------------------------------------------------ The script runs fine on XP, and I used the BuildOptionalComponents.vbs to prepare WinPE, and ran OC.bat after booting WinPE. What am i doing wrong? Thanx in advance for your help and suggestions.
  6. Thanks for your extra info Getwired. Due to other complications at work, I haven't gotten around to test it yet. Ill be sure to post my results here, as soon as i get some time to test it. Again thanks for all the info and support!
  7. Thanx for your reply's guys. @ Mats: I clear the whole disk, and start from scratch. But i guess i will have to use the /syspart option like Getwired says. @Getwired: I havent come around to attach an unattended file yet, will try that next and will post my results here. thanx for your suggestions and support!
  8. Hi, Im trying to install w2k on a server, using WinPE distributed by RIS. Im new to this concept, and just started using WinPE to replace our DOS based unattended server install procedures. I got the distributing of WinPE trough RIS finally running, but encounter some problems when trying to install w2k. Although I allready found lots and lots of information here on the forum, I still got 2 questions: First: I use DiskPart to create partitions using the method I found multiple times here on the forum. This creates a fat32 partition for me, and gives it a driveletter, and makes it primary and active. Then when I run WINNT32.EXE, i get the following message: "No valid system partitions found". Question: Do i really need to reboot after DiskPart has finished? When i Use WINNT32.EXE with the /SysPart option, the install will run, but do i really have to use the /SysPart option to resolve this? Second: When i kick off the WINNT32.EXE, it will tell me the following: "Windows 2000 setup does not support upgrading from Microsoft Windows 2000 Professional to Microsoft Windows 2000 server". I can press OK, and setup will continue with giving me only the Clean Install option, the upgrade option is grayed out. I need the install procedure to be unattended, and i havent found a way to suppress this message. Question: Why do i get this message? The HD is emtpy, so it must be reffering to my WinPE its running. But this is the newest version, so why is it referring to Windows 2000 Professional? And more important: how do i get rid of the message so i can make it completely unattended? Thanx in advance for your reply's guys.
×
×
  • Create New...