• Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About johnyept

Profile Information

  • OS
    XP Home
  1. Thank you, ChangeOwner.exe works perfectly! I'll use it for now but I'll probably make a batch later to change Name, Organization, Computer Name, and reboot to apply changes. If I don't want to change anything I can always use Ctrl+C to stop it and then run it later
  2. Actually that's what I did! I created a WINNT.SIF with enough instructions to automate the installation except for the partition setup and the "Welcome to Windows XP" (I believe it requires OemPreinstall=No in [unattended] section). At first run, I added the following instructions: [GuiRunOnce]"%systemroot%\System32\control.exe sysdm.cpl,,1""%systemroot%\System32\setowner.exe"The first line opens the "Computer Name" tab in System properties, the second is an utility that I added to the $OEM$ folder to change Name/Organization (unfortunately not keyboard friendly, requires mouse to click Apply). The $OEM$ folder is not copied when using an unnatended install, but $OEM$\cmdlines.txt is ALWAYS executed, so I added this inside it... [COMMANDS]"OemPreinstall.cmd"... and stole $OEM$\OemPreinstall.cmd content from another forum, so here it is: @CMDOW.EXE @ /HID 2>NUL||@ECHO OFFSETLOCAL ENABLEEXTENSIONSFOR %%? IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO ( IF /I "%%?:" NEQ "%SYSTEMDRIVE%" CALL :SUB "%%?:" &&GOTO START)GOTO ENDIT:STARTIF EXIST %MYOEM%\$1 XCOPY %MYOEM%\$1 %SYSTEMDRIVE% /S/I/Q/Y >NULIF EXIST %MYOEM%\$$ XCOPY %MYOEM%\$$ %SYSTEMROOT% /S/I/Q/Y >NULIF EXIST %MYOEM%\$Docs XCOPY %MYOEM%\$Docs "%ALLUSERSPROFILE%\.." /S/I/Q/Y >NULIF EXIST %MYOEM%\$Progs XCOPY %MYOEM%\$Progs %PROGRAMFILES% /S/I/Q/Y >NUL:ENDITENDLOCAL &GOTO :EOF:SUBIF NOT EXIST %~1\$OEM$ EXIT/B 1SET "MYOEM=%~1\$OEM$"EXIT/B 0Basically it does the same as Windows XP does when processing the $OEM$ folder. The resulting CD/ISO contains XP Home/Pro OEM, both install an OEM key and all I have to do is select/create the partitions, let it install, create a user on the "Welcome to Windows XP" menus, change name/organization/computer name on first run and add the correct OEMBIOS files. Done!
  3. I mentioned the recovery partitions as an example, I do not want to create a recovery partition myself. Just wondering if it's possible to make a normal Windows XP installation ask all questions in the end of the installation (oobe section) rather than during installation.
  4. Hi all. I was wondering how to make XP ask all questions (timezone, computer name, workgroup) in OOBE right before first start up, instead of during the installation process. I noticed before that when restoring XP using the recovery partition on some laptops, that XP asks for these questions in OOBE right in the "Welcome to Windows XP" blue screens, along with Account names, etc. The purpose is to create a OEM XP installation disk that only asks for partition creation, installs without stopping, then asks for all info in the end instead of stopping several times. I would prefer this info to be added manually instead of predefined in WINNT.SIF, the only info on the file should be the OEM key and the necessary commands to "push" the questions to the end of the installation, if possible. Can this be done?
  5. Sorry for digging up the topic, I just found it after a google search. Let me try to explain why (in my case) I want to recreate original ISOs down to the SHA1 hash: I decided to combine every 9x Windows on a single All-In-One ISO. To save space, to have it all in one place, just for fun? Take your pick. Since I want to install every Windows from the boot menu (including MS-DOS from the original floppy images, yes it's possible!), this means I can't have all Windows in ISO format as this would require some kind of emulation, plus it would simply not fit on a single DVD. Many files are common between ISOs, so space can be spared by saving common files only once. Just as an example, Windows 2000 SP0/SP4 Pro/server, XP SP0/SP3 Home/Pro, Server 2003 SP0/SP2 Standard/Enterprise plus R2 CDs and several OEM/Retail/Volume versions of them all tottaling around 30GB can all fit in 1 DVD and still be able to recreate all original untouched ISOs with a single batch and the correspondent cdimage versions. When it comes to Windows 9x, any ISO created with cdimage 2.27 or below simply can't be recreated with currently available cdimage versions: you can hexedit the version number, but the header created with newer versions is bigger than the older versions, so even if you find all the right parameters, the ISO size will always be bigger than the original. It might have something to do with how the dates were handled up to v2.27, possibly because of post Y2K dates. It MIGHT be possible to hack a cdimage version, but it will require more knowlegde than simply hexediting a couple of numbers. Solution? Don't have one right now, but one possibility might be to find a cdimage version that can create an ISO identical to the original ISO excluding the header, then use some kind of patch to apply the original header to the newly created ISO.
  6. I have a question about OEMSCAN. Can it handle compressed OEMBIOS.* files? I still haven't used it, I'm just gathering "intel" before starting a multi-oem XP dvd for my own language. If it can't, and if it only scans the bios and then blindly copies the files indicated by PATH, then why not using compressed files in the indicated PATH and then expand them with an external batch or any other method? Or we could just hexedit OEMSCAN, replace the files extensions with BI_, CA_, DA_, SI_ and include a batch for expanding them after they're copied to the hdd. That would save lots of CD/DVD space for MULTI-OEM discs. Just my two cents... EDIT: never mind, just noticed that compressed and uncompressed OEMBIOS.* files are practically the same size
  7. Thanks, I guess that confirms my suspicions. I know support ended long time ago, I just can't figure out why they removed the hotfixes from their page, it's not like they would generate that much monthly traffic. Maybe one day someone leaks them all out... we can only hope Probably someone also had the same idea before, I'll keep searching and maybe one day I'll get lucky
  8. Hi. As the title says, what are the chances of getting all hotfixes/updates in a given language other than English for Windows 95, 98 and/or Me? I wonder why M$ never released such packs after ending support for each Windows version... At first i was searching for USBSUPP.EXE PT-PT for Windows 95 OSR2.0 (i have USBUPD.EXE in PT-PT), but i started to notice there are many updates and fixes to each system, and it would be nice to put them all together in a CD/DVD and share among other people from the same language. Somehow i think this will never be possible...
  9. Hi. I'm thinking about making a theme that mimics a normal program window look with WPI Classic, but before i make a custom theme without a close button on the bottom right, i would like to know if there is a way i can enable the window close button on the window frame. Thanks for reading