Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by johnyept

  1. Lucky you, you resurrected this topic 1.5 years after the last post, I'm resurrecting it 11 years later I could create a new topic, but the answers in this one were very helpful and my questions continue where LoneCrusader left off, but he never solved his last problem, just worked around it. The subject is basically the same as the original poster, I'm making an All In One ISO with one O.S. of each flavour, and I want Windows 95 OSR2, Windows 98 SE OEM and Windows Millennium OEM to have unattended installations. For Windows 98 SE and Windows Me, I have a working menu in the boot floppies with 5 installation options: manual (same as original), manual with no key required (MSBATCHK.INF), unattended/typical (MSBATCHT.INF), unattended/portable (MSBATCHP.INF), unattended/compact (MSBATCHC.INF), unattended/minimal (MSBATCHM.INF) and unattended/full (MSBATCHKF.INF). I'm using VirtualBox as the test bench. Windows 95 OSR2 unattended, on the other hand, is a pain in the butt to get it right... 1st problem (solved): when setup reboots from 1st stage to 2nd stage, Windows 95 no longer sees the CD/ISO, probably because it uses (if at all) outdated CD-ROM drivers, so the solution was to add a section in MSBATCH.INF that copies the (Windows 98) drivers from the floppy to the HDD and adds the correspondent lines to AUTOEXEC.BAT and CONFIG.SYS, so setup sees the CD/ISO and continues the installation. 2nd problem (solved): Since I have all MSBATCH*.INF in the boot floppy, it MUST have a MSBATCH.INF with at least [SETUP] ProductType=1 in the WIN95 CD folder to skip the CD-KEY which I want to do in unattended mode, this line won't work from any INF file in any other location. 3rd problem (solved): Since Windows 95 won't run on CPUs faster than 2.1Ghz, I'm using FIX95CPU and MSBATCH.INF to install an AMD patch that solves this issue, but 2nd stage setup was stopping due to an older NDIS.VXD being copied over a newer version, so all I needed was to copy this new file from FIX95CPU to the WIN95 CD folder so setup copies this file instead of the one in the CABs. I'll probably move FIX95CPU to the boot floppy at a later stage and install it from there. 4th problem (unsolved but not important): 2nd stage setup stops and aks me to configure Microsoft Exchange's Incoming folder when this component is installed. The FULL installation option includes this component, so I wonder if there is a way to skip the configuration by adding something to MSBATCH.INF. Even if there isn't, I might just disable it in the FULL installation, since it's not selected in the 3 default configurations (Tipical/Portable/Compact). 5th problem (unsolved for now): 1st stage setup can't find LEIA-ME.TXT (aka README.TXT in English versions), if I skip it everything else copies OK, but the file is there, and it copies fine when using the original CD/ISO, so it's probably just a question of using the correct cdimage parameters, I'll figure that one out eventually. 6th problem (unsolved): some components aren't installed when the soundcard isn't detected, specifically "Audio Compression", "Sample Sounds", "Volume Control" and "Sound Recorder". It's the same problem LoneCrusader was having, and the problem is described in this article, but adding "/p c-" to disable safe class detection will make install crash on Virtualbox, and possibly some real computers too. If I do a manual installation I can select a check box for sound cards and network cards, which will find the Soundblaster 16 and install the 4 missing components. Is there an equivalent option to this checkbox for MSBATCH.INF? I don't mind posting my MSBATCH*.INF files, CONFIG.SYS and AUTOEXEC.BAT when they're 100% working and fully translated to English, if anyone is interested.
  2. A text file with a brief description of what each update is for would be nice, but I commend you for giving us tugas such a nice treat If you would like to add untouched ISOs from the older operating systems to the collection (win95/98/98SE/Me/2K) just let me know, I have the original CDs.
  3. Thanks for the reply, but I should have explained myself better. I meant some sort of unattended file I could add to the ISO to do it automatically during install..
  4. Hello. Is there a way to add/change a registry value in HKLM\System during Windows 8 install, right after partitioning/applying the image to disk but before the first reboot?
  5. Yes I know about copying files to HDD, I'm from that time too But in this case I'm trying to find a method that uses the original CD and a floppy, where the only thing the user has to do is answer the usual questions and the floppy just runs OEMSETUP.EXE with an INF files for the cd drivers, leaving the rest with Windows itself. EDIT: it's funny how the world is round and we always come back to the place we started... I was trying to find an "untouched" Windows 95 boot floppy and I discovered 2 things: upgrade CDs counted on ms-dos or Windows 3.x already having cd drivers installed so they didn't have a boot floppy; OEM CDs included a boot floppy that was based on a prototype floppy included in the Windows 95 "OEM Adaption Kit" (OAK), where they would add their own CD drivers and modify a file named DRVCOPY.INF which does exactly what I want! And you (jaclaz) posted links to it in another topic! Ain't life funny? I'll post the modified DRVCOPY.INF as soon as I get time to take a look at it EDIT2: Here's the working INF! ; DRVCOPY.INF ; ; This is the Driver Copy information file for ; real-mode CD-ROM drivers. ; ; These driver(s) are copied to the root of the hard disk ; during setup, and are installed in config.sys and autoexec.bat ; ; This file MUST be modified by the OEM prior to shipping ; to end users. ; ; OEMs will need to modify this to add the proper name(s) ; for their real-mode CD ROM drivers. ; Lines that must be modified are marked OEM_Modify ; You can also copy additional drivers and add lines to autoexec.bat ; and config.sys using this file. [version] ; Do not change this section signature=$chicago$ [DestinationDirs] ; Do not change this section RM.driver.dest.copy = 30 ; root directory [install] ; Do not change this section copyfiles=RM.driver.dest.copy updatecfgsys=RM.Sys.upd updateautobat=RM.Auto.upd [RM.driver.dest.copy] ; OEM_Modify - Change the name from SAMPLE.SYS to your CD ROM drivers. ; - You can insert additional filenames for your real ; mode driver(s). ; This file name will be copied to the hard disk. OAKCDROM.SYS BTDOSM.SYS FLASHPT.SYS BTCDROM.SYS ASPI2DOS.SYS ASPI8DOS.SYS ASPI4DOS.SYS ASPI8U2.SYS ASPICD.SYS [RM.Sys.upd] ; OEM_Modify - Change the name from SAMPLE.SYS to your CD ROM drivers. : - You can also change the driver name here and below. ; This line will be added to the user's CONFIG.SYS. DevAddDev=OAKCDROM.SYS,device,,"/D:MSCD001" DevAddDev=BTDOSM.SYS,device DevAddDev=FLASHPT.SYS,device DevAddDev=BTCDROM.SYS,device,,"/D:MSCD001" DevAddDev=ASPI2DOS.SYS,device DevAddDev=ASPI8DOS.SYS,device DevAddDev=ASPI4DOS.SYS,device DevAddDev=ASPI8U2.SYS,device DevAddDev=ASPICD.SYS,device,,"/D:MSCD001" [RM.Auto.upd] ; OEM_Modify - Change the "D" in L:D to represent the default drive ; letter for your CD ROM. ; - The OEMCD001 parameter should agree with the ; config.sys parameter above. ; This line will be added to the user's AUTOEXEC.BAT CmdAdd=MSCDEX.EXE,"/D:MSCD001 /L:D" [SourceDisksNames] ; Do not change this section 100="%oem.boot.desc%",,5,A:\ [SourceDisksFiles] ; OEM_Modify - Change the name from SAMPLE.SYS to your CD ROM drivers. ; Do not change the 100,,2000 ; This file will be copied to the hard disk root directory. OAKCDROM.SYS=100,,2000 BTDOSM.SYS=100,,2000 FLASHPT.SYS=100,,2000 BTCDROM.SYS=100,,2000 ASPI2DOS.SYS=100,,2000 ASPI8DOS.SYS=100,,2000 ASPI4DOS.SYS=100,,2000 ASPI8U2.SYS=100,,2000 ASPICD.SYS=100,,2000 [Strings] ; This string is displayed to the user. It can be localized as ; necessary. oem.boot.desc="Setup Boot Disk"
  6. Tried this modification, install ran up to 99% then it asked me where "Windows 95 Boot Floppy" files where located, I typed "A:\" followed by ENTER and installation continued without any more hiccups. Almost there... no idea how to fix it. [version] signature="$CHICAGO$" [DestinationDirs] files.cdrom=10 [Install] CopyFiles=Files.floppy UpdateCfgSys=Update_config.sys UpdateAutoBat=Update_autoexec.bat [Files.floppy] ASPI2DOS.SYS ASPI4DOS.SYS ASPI8DOS.SYS ASPI8U2.SYS ASPICD.SYS BTCDROM.SYS BTDOSM.SYS FLASHPT.SYS OAKCDROM.SYS [SourceDisksNames] 99 = %DiskName%,BOOT95,0 [SourceDisksFiles] ASPI2DOS.SYS = 1 ASPI4DOS.SYS = 1 ASPI8DOS.SYS = 1 ASPI8U2.SYS = 1 ASPICD.SYS = 1 BTCDROM.SYS = 1 BTDOSM.SYS = 1 FLASHPT.SYS = 1 OAKCDROM.SYS = 1 [Strings] DiskName = "Windows 95 Boot Floppy" [Update_config.sys] DevAddDev=OAKCDROM.SYS,device,,"/D:MSCD001" DevAddDev=BTDOSM.SYS,device DevAddDev=FLASHPT.SYS,device DevAddDev=BTCDROM.SYS,device,,"/D:MSCD001" DevAddDev=ASPI2DOS.SYS,device DevAddDev=ASPI8DOS.SYS,device DevAddDev=ASPI4DOS.SYS,device DevAddDev=ASPI8U2.SYS,device DevAddDev=ASPICD.SYS,device,,"/D:MSCD001" [Update_autoexec.bat] CmdAdd=MSCDEX.EXE,"/D:MSCD001 /L:D"
  7. I'm trying to install Windows 95 on VirtualBox with a homemade floppy and an original CD. I know that the emulated chipset is not supported by Windows 95, so the first part of the installation "sees" the CD drive because of the drivers loaded by the floppy, but the second part of the installation doesn't see the cd drive because it's no longer booting from the floppy, and fails to copy files. Some years ago I used this workaround with VirtualPC, which also works with VirtualBox. It basically copies the cd drivers to the Windows folder during Windows installation, and adds the required lines to config.sys and autoexec.bat: - copy cd drivers to \WIN95 folder (aspi*.sys, bt*.sys, flashpt.sys and oakcdrom.sys) - create \WIN95\CD.INF with the following content: [version] signature="$CHICAGO$" SetupClass=BASE LayoutFile=layout.inf [Setup] EBD=0 [Printers] [Install] CopyFiles=Files.cdrom UpdateCfgSys=Update_config.sys UpdateAutoBat=Update_autoexec.bat [Files.cdrom] OAKCDROM.SYS BTDOSM.SYS FLASHPT.SYS BTCDROM.SYS ASPI2DOS.SYS ASPI8DOS.SYS ASPI4DOS.SYS ASPI8U2.SYS ASPICD.SYS [DestinationDirs] ;10=WINDOWS ;11=SYSTEM ;13=COMMAND ;17=INF files.cdrom=10 [Update_config.sys] DevAddDev=OAKCDROM.SYS,device,,"/D:MSCD001" DevAddDev=BTDOSM.SYS,device DevAddDev=FLASHPT.SYS,device DevAddDev=BTCDROM.SYS,device,,"/D:MSCD001" DevAddDev=ASPI2DOS.SYS,device DevAddDev=ASPI8DOS.SYS,device DevAddDev=ASPI4DOS.SYS,device DevAddDev=ASPI8U2.SYS,device DevAddDev=ASPICD.SYS,device,,"/D:MSCD001" [Update_autoexec.bat] CmdAdd=MSCDEX.EXE,"/D:MSCD001 /L:D" - recreate ISO with thie new files - boot from floppy - start installation with SETUP.EXE CD.INF. But now I want to use CD.INF from the floppy, ie SETUP.EXE A:\CD.INF because the cd drivers are already in the floppy and so I don't have to use a modified ISO. Can CD.INF be modified so it searches for the files in the floppy? I tried it as is, and at 23% the installation stopped and asked me where the *.sys files were, pointing to D:\WIN95, which is where they obviously are not.
  8. 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
  9. 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!
  10. 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.
  11. 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?
  12. 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.
  13. 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
  14. 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
  15. 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...
  16. 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

  • Create New...