scp

Now you can download the updated command line version above, which also works with SP2 and other versions (like LH4074 bbu). Below I also provide a easier GUI version. bbudlg_nvc.zip

@toreach If you cant delete a file or folder or file with bad characters just open a command prompt (Eingabeaufforderung :-)) and change to the parent folder, i.e.: C: cd "Programme" Then enter "dir /x" to see the short DOS filename (in your case it may be Comman~1), then enter "rd Comman~1" or "del Comman~1" to delete the folder/file.

If you only want to test a bootable CD/DVD, you DONT need a OS installed. VPC works like a real PC. So, do you install MS-DOS or something before you install XP from a bootable CD on your real PC?

Maybe you or a use of cmd/tool has modified the SYSOC.INF file. Look, if these two entries are found in [Components] msmsgs=msgrocm.dll,OcEntry,msmsgs.inf,,7WMAccess=ocgen.dll,OcEntry,wmaccess.inf,,7In I386 folder SYSOC.INF is stored as SYS.IN_, extract it and look in it. (May be a ,hide,7 is in the msmsgs line, this is also OK)

WindowsShell.exe dont uses the registry for the start menu entries. The default entries are hardcoded into the .EXE. But it seems to be that new entries can also be added to the start menu via DT.CFG. I tried following: shortcutname My Computerposition 10, 10 shortcutname Network Neighborhoodposition 90, 10 menuprogram %SYSTEMROOT%\system32\RegMon.exeicon %SYSTEMROOT%\system32\RegMon.exe,0name RegMonI get a submenu named "Programs" in the Start menu and the correct icon and name for RegMon is shown in ta submenu entry. BUT - If I click on it , regmon don't starts, the "System Compare Wizard" starts. Any additional idea on this?

What about renaming regedit.exe to one of the ERD .exe's and then recreate the ISO and run it?

i think it doesn't really work. The .inf files should be always uncompressed. If you want to compress the other files (.dll, .sys etc.) you must modify the [sourceDisksNames] section in the .inf files. Or you can compress each file seperatly without any other modification (like the files with _ in I386 folder).

I don't no about the law in danmark. In germany it is prohibited to bundle software with hardware. So, if someone sells a OEM Windows seperatly its legal.

No, I think that is stored in another file, it would be difficult to find.

Here is a screenshot of a test bbu:

It is possible to change the text color / progress bar color in WINNTBBU.DLL: 1. Open a Hex Editor 2. Search for the hex word "83 F8 08 B8" 3. You will see something like this: 00001d30h: 59 83 F8 08 B8 FF FF FF 00 A3 48 0A 00 5A A3 44 00001d40h: 0A 00 5A A3 3C 0A 00 5A A3 38 0A 00 5A A3 34 0A 00001d50h: 00 5A A3 20 0A 00 5A A3 18 0A 00 5A 76 45 B9 00 00001d60h: 25 6D 00 89 0D 1C 0A 00 5A 89 0D 24 0A 00 5A C7 00001d70h: 05 40 0A 00 5A FF 80 00 00 C7 05 4C 0A 00 5A 07 00001d80h: 9E 05 00 C7 05 5C 0A 00 5A 00 32 96 00 C7 05 58 Original value = description FF FF FF 00 = text color / progress bar background color 00 25 6D 00 = title text shadow color FF 80 00 00 = text color (current step) 07 9E 05 00 = progress bar color You can replace these values by using HTML hex values, most picture software will display it in there color picker. You can also use my little commandline tool: - Unpack it - Fill the bbucolor.ini with your values - Run bbucolor.exe C:\path\to\winntbbu.dll Note: If you don't use the tool and make it with a hex editor you have to set the Last Modified time/date stamp manually back to its original value, otherwise setup will display a error. bbucolor.zip

@flyakite: No, I want that the user will be asked for a product key after the first boot up, not during the setup. @OcTroN No, it must not be the same key again, I think it must be the reseal thing. If I set "OemPreinstall = Yes" in WINNT.SIF and create a sysprep.inf with the right parameters in $OEM$\$1\Sysprep it will be automatically copied to harddisk and sealed, is this right? Or is it more difficult to do? My intention is to make an unattended CD-ROM, which installs Windows and seals it automatic after setup has done.

I agree to Mavericks. You find the required reg keys and file in \plugin\keyboard\keyboard.inf (bundled with PE Builder).

I tried it but something is wrong. After the first bootup, sysprep runs, but it displays a window with some options i can choose, but no additional prompt for user info and product key will be shown. Here is my winnt.sif: ;SetupMgrTag [Data] AutoPartition=0 MsDosInitiated="0" UnattendedInstall="Yes" [Unattended] Unattendmode = FullUnattended OemPreinstall = Yes TargetPath = * Filesystem = LeaveAlone OemSkipEula = Yes FactoryMode = Yes EMSSkipUnattendProcessing=1 [UserData] FullName = "Preinstall" OrgName = "Preinstall" ComputerName = * ProductId = "12345-67890-ABCDE-FGHIJ-KLMNO" [GuiUnattended] TimeZone = "004" AdminPassword = "*" EMSBlankPassword = Yes AutoLogon = Yes AutoLogonCount = 1 OEMSKIPREGIONAL = 1 OEMSKIPWELCOME = 1 [LicenseFilePrintData] AutoMode = "PerServer" AutoUsers = "5" [Display] BitsPerPel = 4 XResolution = 800 YResolution = 600 VRefresh = 70 [GuiRunOnce] Command0="start /w %SYSTEMDRIVE%\Sysprep\sysprep.exe -oobe" [Identification] JoinWorkgroup = Workgroup [Networking] InstallDefaultComponents=Yes Must I create a sysprep.inf or winbom.ini in sysprep folder?

Thanks, very interesting, now I'll try it out.

Thanks. Yes, that was the entry I focused but not really believed that its the right one. Can I let Setup run "sysprep.exe -oobe" automatically? I know there are many ways to run something custom (cmdlines.txt, GUIRunOnce...), but which is the right one in this case?

How can I make an unattended installation where no user info and product key will be set and the user will be asked for it after the first boot up (like it works on these funny PCs you can buy in the super market)? I've looked in ref.chm but not found something like these.

Hi ZoRoNaX, I know its not part oft this topic, but... Are you working on your WIM Dumper for the 405x versions or do you have already a new version? Thx, SCP PS: I found a bug (?) in v1.02: If I wan't to extract a .cab from a WIM I only get the first bytes of it, not the whole one.

Remove failed VPC Additions Have you ever tried installing the VPC Additions of the 5.x Version on Longhorn? I have. After I run setup.exe in XP Compatibly mode and I restarted, Longhorn hanged in an endless loop. I don't wanted to reinstall it, so I decided to getting it back with some registry tweaks. First, it is also not possible to run in safe mode, because the VPC keyboard and mouse driver doesn't work. You need to boot from a WinPE or a second working NT5 (XP/2003/Longhorn). 1. Type Start -> Run... -> regedit 2. Click on HKEY_LOCAL_MACHINE, then File -> Load hive..., select the file "system" found in system32\config of your broken Longhorn. Press OK and enter a name for the hive tree (WinLH or something). 3. Look in ControlSet001\Services\i8042prt an replace "vpc-8042.sys" with "i8042prt.sys". Look also in other available ControlSets (ControlSet002, ControlSet003 etc.) 4. Now you should be able to boot in safe mode. 5. Back in Longhorn safe mode, open the Device Manager and delete the networking card, keyboard, mouse and display adapter. 6. Now it should be done. If you can't boot Longhorn with this modifications: 7. You should go back to the second NT5 and repeat steps 1 and 2. 8. Delete this registry entries: ControlSet001\Enum\Root\LEGACY_MRXVPC ControlSet001\Enum\Root\LEGACY_VPCMAP ControlSet001\Services\1-driver-vpcsrvc ControlSet001\Services\1-vpcsrvc ControlSet001\Services\MRxVPC ControlSet001\Services\VPCMap Look also in other available ControlSets (ControlSet002, ControlSet003 etc.) 9. Delete these files: CNTX\VPCSRVC.SYS CNTX\VPCSRVC.EXE system32\MRxVPCNP.dll system32\VPCMap.exe system32\drivers\mrxvpc.sys system32\drivers\vpc-8042.sys Get sound and graphics card driver Just take add this files from WinXP to a virtual or real floppy disk: From WINDOWS\INF or I386: display.inf s3nb.inf s3sav3d.inf s3sav4.inf s3savmx.inf s3trio3d.inf sbp2.inf wave.inf wdma_csc.inf wdma_ctl.inf wdma10k1.inf From drivers.cab: ctlsb16.sys s3legacy.dll s3legacy.sys Then use these during the driver installation with "Have disk..."

Now updated the .inf file with some registry classes. and now you can use it as a real plugin. You don't need the whole $WINDOWS.~BT anymore. Only the WinSxS folder, some files from system32 and the 2 well known network INFs (See PluginHelp for Details). 28.03.2004: Now tested with Build 4053. Works too, but if you wonder that Cryptographic Service not works, just add these 2 dlls: sensapi.dll=2 senscfg.dll=2 Also PE Builder may display some missing files (some DLLs, MFLs, MOFs and MUIs), they are not required, just run PE Builder a second time and select "ISO Build".

This error message means that the dll is not a self registering DLL, so it don't works with regsvr32. One chance is, that it is a self installing DLL, try: regsvr32 /i /n noinput.dll You can find out, if a DLL is self registering or not if you use a tool like EXESCOPE and watch at the Exports. A self registering DLL has a exported function named DLLRegisterServer A self installing DLL has a exported function named DLLInstall Its possible that one DLL has both entries.

Here is the final .inf file for a basic Longhorn PE (needs XPE plugin for Explorer). 26.03.2004: Updated the plugin ZIP. zzz_lhpe.zip

I forgot something essential: 1. if you use plugins which take files from the Windows CD-ROM/source dir you should look for each file if there is also a .mui or a .mu_ file. This file must be copied to i386\mui\fallback\0409. Her is an .inf example: [WinntDirectories] f="mui\fallback\0409",1 [SourceDisksFiles] bootcfg.exe.mui=f charmap.exe.mui=f cic.dll.mui=f clbcatex.dll.mui=f 2. There is a special case if you use XPE or the Shutdown Enabler plugin: msgina.dll.mui must be copied to ginaorg.dll.mui to enable shutdown in longhorn. In a .inf it is a line like this: msgina.dll.mui=f,ginaorg.dll.mui 3. Longhorn EXPLORER.EXE needs csmagnet.dll and csmagnet.dll.mui to work.

There is a way getting 4051 PE work with BartsPE: - Get a copy of the "windir"\I386 directory of an installed Longhorn. Use it as source dir. - Get a copy of $WINDOWS.~BT or BOOT. Use it as Additional Source directory. - You may also need hive*.inf and ASMS01.CAB from Windows 2003 or XP CD-ROM But currently this is just for fun, because only the Desktop works, but the start menu isn't visible, it needs the Themes Service which currently not runs under PE (as I know). Additional notes: In $WINDOWS.~BT you must delete following files: biosinfo.inf bootfix.bin BOOTSECT.DAT ntdetect.com setupldr.bin spcmdcon.sys txtsetup.sif winbom.ini system32\biosinfo.inf system32\config system32\config\default system32\config\sam system32\config\sam.log system32\config\security system32\config\software system32\config\software.log system32\setupreg.hiv Rename $WINDOWS.~BT to i386 and define the parent folder as source. To get START MENU snd TASKBAR create an INF file named siderbar.inf with following contents in a plugin directory of your choice: ; sidebar.inf ; PE Builder v3 plug-in INF file for disabling Longhorn Sidebar ; Created by SCP [Version] Signature= "$Windows NT$" [PEBuilder] Name="Longhorn PE: Registry - Disable Sidebar" Enable=1 [Default.AddReg] 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "Initialized", 0x00000001 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "Width", 0x00000096 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "Minimized", 0x00000001 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "Height", 0x00000096 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "AutoHide", 0x00000000 0x4, "Software\Microsoft\Windows\CurrentVersion\Explorer\StartBar\Sidebar", "Enabled", 0x00000000