jda-au

With regards to Auto-patcher Win98.UBCD, I have killed/deleted "Windows Update Manager". Having a connection to http://windowsupdate.microsoft.com/ is a waste of space and effort, as it is dead in the water. If you access Windows Update, this is how far the process will get: Windows Update is looking for available updates... 0% complete If you open "C:\Windows\Windows Update.log" 2008-09-06 09:36:34 23:36:34 Success IUCTL Starting 2008-09-06 09:36:43 23:36:43 Success IUCTL Downloaded iuident.cab from http://windowsupdate.microsoft.com/v4/ to C:\Program Files\WindowsUpdate\V4 2008-09-06 09:36:44 23:36:44 Success IUCTL Checking to see if new version of Windows Update software available 2008-09-06 09:36:44 23:36:44 Success IUCTL Current iuctl.dll version: 5.3.3790.13 2008-09-06 09:36:44 23:36:44 Success IUCTL Current iuengine.dll version: 5.3.3790.13 2008-09-06 09:36:44 23:36:44 Success IUENGINE Starting 2008-09-06 09:36:45 23:36:45 Success IUENGINE Determining machine configuration 2008-09-06 09:36:46 23:36:46 Success IUENGINE Determining machine configuration Once "Windows Update" has identified System is Win98 and confirmed result, no further action will occur. So you have a few extra kb's of useless Registry Data to assist in slowing OS speed, plus some files on your HDD that serve no purpose! I have tested it, one step at a time, and if placed into the respective places of Win98.UBCD, or any other Win98SE Installation, 'tis hands off and gone forever. My OS is Win98SE (Full Version, not that there is any difference between any identical version of Full/Upgrade/OEM except in price). The only enhancements, spit 'n polish is by way of Win98.UBCD.4.0.8.001, as supplied. The files are all commented, but a quick abbreviated explanation is in order: Filename: kill_WU.bat Comment: Looking at a link in the registry, I am now having second thoughts on deleting "WUPDMGR.EXE", as it appears to be used during Active Setup. If in doubt, REM it out! But I did not REM it out, as the only visible work "WUPDMGR.EXE" appears to do is access WindowsUpdate. deleted WUPDMGR.EXE deleted OWINDO~1.XML deleted Windows Update.log deleted Start Menu\Windows Update.lnk Filename: kill_WU.reg kills WindowsUpdate enables/disables NoDevMgrUpdate enables/disables NoWindowsUpdate Comment: NoDevMgrUpdate controls: Start -> Settings -> System -> Device Manager -> Driver -> Update Driver -> Update Device Driver Wizard -> Microsoft Windows Update Comment: NoWindowsUpdate controls: (visble/hidden) IEXPLORE.EXE -> Tools -> Windows Update link (and) Start -> Settings -> Windows Update link (and) Start -> Windows Update link The titles are self explanatory: (with a .txt tag added). 8th Sept. 2008 No changes made anywhere, removed "kill_WU.bat", restored, no change. kill_WU.reg.txt kill_WU.bat.txt

Thanking you for your help, been a very long time since I played around with a DOS (Dirty Operating System). Oh!, how the GUI makes children out of us, if we can't click it we can't do it, begging pardon to the children whom may take offense. Thanks heaps, Slightly off subject, but still regards Win98.UBCD, I have killed/deleted "Windows Update Manager". I have tested it, one step at a time, and if placed into the respective places of Win98.UBCD, or any other Win98SE Installation, 'tis hands off and gone forever. My OS is Win98SE (Full Version, not that there is any difference between any identical version except in price). The only enhancements, spit 'n polish is by way of Win98.UBCD.4.0.8.001, as supplied. For an expanded explanation, and download the two files, which are only a total of 5.98K, Auto-patcher Win98.UBCD, (delete/hide) "Windows Update" links

Hi Soporific, I was unsure as to where to post this, as I know you are in the process of moving Win98.UBCD.#.# I am using a Bootable CDROM, on a eleven year old system Gigabyte GA-586HX Motherboard, Intel 430HX Chipset, Pentium MMX 200MHz CPU, 120MB RAM; which requires CDROM Drivers to be loaded to access the Optical Drive. System BIOS does not auto-boot from Optical Drive. Version in question, 4.8.0.001 I soon realized I needed to be accessing/calling "UNATTEND.BAT", instead of setup.exe When I do access/call setup.exe, normal Installation occurs, no extras, no copyover occurs, and no Desktop#.bat's Even so, it is one very fine piece of work, I am impressed, very. I receive the following message: There was a problem with the options as defined in CONFIG.SYS This is a programming error, please report it to www.msfn.org Please press any key to exit... Now starting 98Lite... Bad command or filename A:\> I have not altered/deleted any files, other than edit msbatch.inf My CONFIG.SYS DEVICE=HIMEM.SYS DOS=HIGH,UMB DEVICE=EMM386.EXE FILES=40 DEVICEHIGH=VIDE-CDD.SYS /D:MSCD001 LASTDRIVE=Z My Autoexec.bat @ECHO OFF REM Load CDROM Driver LOADHIGH MSCDEX.EXE /D:MSCD001 REM Search for CDROM Disc, set parameters if 'correct disc' exists. FOR %%i 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 EXIST %%i:\LocateCD.386 SET BTCDROM=%%i:\ REM Only if "LocateCD.386" exists, else skipped. IF EXIST %BTCDROM%LocateCD.386 ECHO "Commencing Installation of "Soporific's" Updated 'Windows 98SE UBCD V4.8' REM Only if "UNATTEND.BAT" exists, else skipped. IF EXIST %BTCDROM%SETUP\UNATTEND.BAT CALL %BTCDROM%SETUP\UNATTEND.BAT EXIT Probably not required/needed, but... Modules using memory below 1 MB: Name Total Conventional Upper Memory -------- ---------------- ---------------- ---------------- MSDOS 18,848 (18K) 18,848 (18K) 0 (0K) HIMEM 1,168 (1K) 1,168 (1K) 0 (0K) EMM386 9,856 (10K) 9,856 (10K) 0 (0K) VIDE-CDD 5,024 (5K) 5,024 (5K) 0 (0K) COMMAND 7,296 (7K) 7,296 (7K) 0 (0K) MSCDEX 21,648 (21K) 21,648 (21K) 0 (0K) Free 591,296 (577K) 591,296 (577K) 0 (0K) Memory Summary: Type of Memory Total Used Free ---------------- ----------- ----------- ----------- Conventional 655,360 64,064 591,296 Upper 0 0 0 Reserved 393,216 393,216 0 Extended (XMS)* 133,169,152 638,976 132,530,176 ---------------- ----------- ----------- ----------- Total memory 134,217,728 1,096,256 133,121,472 Total under 1 MB 655,360 64,064 591,296 Total Expanded (EMS) 33,947,648 (32M) Free Expanded (EMS)* 33,554,432 (32M) * EMM386 is using XMS memory to simulate EMS memory as needed. Free EMS memory may change as free XMS memory changes. Largest executable program size 591,168 (577K) Largest free upper memory block 0 (0K) MS-DOS is resident in the high memory area. Do I need to be doing something different, like a different bootable floppy? (which is a Bootable Windows 98 1.44MB). (Thinking out loud, (not always sensible!), "98_boot.ima" on 2 x 1.44MB Floppies, as my FDD only accepts 1.44MB). Should have no bearing, the CDROM has your "98_boot.ima", set as a 2.88MB Floppy. Regards and best wishes, UPDATE: How absolutely simply dumb of me!, (been a long time since I played with this Computer, BIOS). Checked out the BIOS, and set the Boot sequence to CDROM, HDD. (Got a bit throwed off course, as this BIOS does not list CD/DVD drives as visible, unlike my current System). My current problem is fixed, but it would be nice to install to a System that does not have Bootable Optical BIOS, and still have the ease! Thanks again Soporific A further problem, this time with the Optical Drive/HDD "clashing", causing temporary "freeze". Setup/System was locking up while installing: System Updates (2 of 4)... It began at: START /WAIT "D:\installs\1\hotfixes\ie938127.exe", problem could be cured by opening the Optical Drive, and closing again. There were no error messages, until I opened the Optical Drive, then the operation would continue successfully, until the next "freeze", which may be immediate, or a few seconds later. I must have opened and closed the Optical Drive one hundred times, I persisted with it (after a few unnecessary Resets), problem disappeared after Setup finished with Step 2 of 4 and reset. The Optical Drive is a DIAMONDDATA 52X CDROM I put the Optical Disc in the VMware, start to finish without a problem, so it must be some problem with my Computer. (I did have an Adaptec AHA-150X SCSI minicard Adapter installed, with a Jumper installed on a different IRQ than Win98SE was (obstinately) selecting, Jumper was on IRQ11 instead of IRQ9 as Win98SE set the Resources). Needless to say, the adapter would not work until I changed the Jumper Setting. Now that all the hardware is working correctly, I think I should perform the complete Win98SE install process, else I am thinking of copying the complete Optical Disc contents to the HDD.

Not really ever had problems using nLite, until now. (Other than HFSLIP & nLite don't really like each other, but that is off subject). Have been successfully Slipstreaming XP SP3 with nLite V1.4.5 (on NT5 System), until I added the July Hotfixes/Updates released 3rd & 7th July '08. (Seemed to be getting a variety of errors, all occurring before the initial/first API appeared, causing reboot). Have since upgraded to nLite V1.4.7; now appears I am only getting a single error, still occurring before the initial Setup API appears. The Error: lsass.exe - Not Enough Quota (X) Not enough virtual memory or paging file quota is available to complete the specified operation. [ OK ] I do not know which Hotfix/Update may be causing the problem, or what I could do to fix, other than removing one Update at a time until the problem disappears. This error appears whether I use the destination (Dell Inspiron 1150), or Virtual PC, so it may be more to do with environment than hardware. I have checked the integrity of all the files I am using, and am using fresh Source. The Hotfixes/Updates (all July '08 releases) (added and error appeared): WindowsXP-KB951376-v2-x86-ENU.exe IE7-WindowsXP-KB950759-x86-ENU.exe WindowsXP-KB951698-x86-ENU.exe WindowsXP-KB950762-x86-ENU.exe WindowsXP-KB950760-x86-ENU.exe WindowsXP-KB951748-x86-ENU.exe Am only using nLite V1.4.7 and using fresh source, nLite completes without error or complaint. Additional: I have removed the above six (6) Hotfixes/Updates from nLite V1.4.7 installation, (fresh Source), Setup API displays AOK, Setup proceeds. I will add one (1) Hotfix/Update at a time, until error returns, then remove that particular Hotfix/Update, and continue adding other Hotfixes/Updates one at a time. That should definitely pinpoint the problem Hotfix/Update. Will post result(s), so stay tuned. (AM not laying blame on nLite, problem may well be with the Hotfix(es)/Update(es)). Addendum: Added the above Hotfixes/Updates one at a time (testing after each addition) beginning lowest, KB950759, to highest, KB951748; adding to the same nLite'd Source. No errors. Perhaps I need to alter the sequence the Hotfixes/Updates are stacked/queued in nLite list, I thought nLite took care of processing sequence. I'll create a fresh source, and do the full nLite routine, but I don't know what else to do. This is the sequence the Hotfixes/Updates (originally) appeared in "Hotfixes, Add-ons and Update Packs": WMP11-WINDOWSXP-X86-ENU KB950759 - (03/07/2008) Cum. Sec. Update IE7 IE7-WINDOWSXP-X86-ENU KB941833 ROOTSUPD KB929399 KB936782 KB939683 WindowsUpdateAgent30-x86 KB941569 KB942763 KB950760 - (03/07/2008) KB950762 - (03/07/2008) KB951376 - (03/07/2008) KB951698 - (03/07/2008) KB951748 - (07/07/2008) KB947864 Maybe someone can come up with an answer, nuhi ? Answer: The nLite software and good hearted nuhi tends to make the lazy lazier! There is a Help Button provided which gives instructions about using/adding "Hotfixes, Add-ons and Update Packs". nuhi recommends/advises sorting Hotfixes/Updates by Date. Problem was User-induced , I had forgotten to sort the Hotfixes/Updates in "Hotfixes, Add-ons and Update Packs" Dialog (Window). (Columns are sortable, Heading(s) are clickable, plus Sort-arrows are also available). Note: nLite applies the FIFO (First In First Out) principle, i.e. works from top down. Sort earliest (Date) to latest (Date). Also, as nLite seems to process WMP first, I put it first, then IE7, then KB######'s sorted by date. (Sorted) "Hotfixes, Add-ons and Update Packs": WMP11-WINDOWSXP-X86-ENU IE7-WINDOWSXP-X86-ENU ROOTSUPD WindowsUpdateAgent30-x86 KB929399 -------------- 03/22/2007 KB936782 -------------- 06/12/2007 KB939683 -------------- 07/17/2007 KB941833 -------------- 2007/08/24 KB941569 -------------- 10/31/2007 KB942763 -------------- 2007/11/14 KB947864 -------------- 2008/03/01 KB950760 -------------- 2008/04/24 KB951698 -------------- 2008/05/07 KB950762 -------------- 2008/05/09 KB950759 -------------- 2008/05/20 KB951376 -------------- 2008/06/16 KB951748 -------------- 2008/06/20 Problem fixed.

Post deleted - Subject of no consequence/importance - by "jda-au" Jun. 9th, 2008

Subject: Alternative RunOnceEx I have been looking at all this Programming to inject everything into RunOnceEx, 'tis a pain I think, but there is more than one way to "skin a cat". All that is required is one command/routine (whichever!) to originate from RunOnceEx e.g... @ECHO OFF IF EXIST %SYSTEMROOT%\SYSTEM32\CMDOW.EXE CMDOW @ /HID SET KEY=HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx REG ADD %KEY% /V TITLE /D "Installing Applications" /f REG ADD %KEY% /V Flags /T REG_DWORD /D 128 /F REG ADD %KEY%\010 /VE /D "Applications Installation Batch File" /f REG ADD %KEY%\010 /V 1 /D "%systemdrive%\Software\install.cmd" /f @ECHO OFF // Filename: install.cmd" IF EXIST %SYSTEMROOT%\SYSTEM32\CMDOW.EXE CMDOW @ /HID // If you don't know where %temp% will take you, enter it as a command. MKDIR %temp%\myprogram1 MKDIR %temp%\myprogram2 COPY /V /Y /B %SYSTEMDRIVE%\Software\myprogram1.exe %temp%\myprogram1 COPY /V /Y /B %SYSTEMDRIVE%\Software\myprogram2.exe %temp%\myprogram2 START/WAIT %TEMP%\myprogram1\myprogram1.exe START/WAIT %TEMP%\myprogram2\myprogram2.exe RD /S /Q %SYSTEMDRIVE%\Software EXIT I know the above looks very abbreviated, but that's all you need. Of course one (anyone) would have more than two pieces of Software to install, but still very simple, and it works a treat. I used to install my Programs from "%SYSTEMDRIVE%\Software", and delete on finish, but some Programs require access to it's source to uninstall, or repair or re-install. Which just causes a hassle. I also tried installing direct from the CD-DVD, some Software was okay with it, and others were not. (Trial and error). It is no big deal or loss of time to copy them over to "%temp%\Folder", and makes everything very neat and orderly. I know which way I will be doing it...

I believe this will also work for Microsoft Vista, the Activation principles and Code has been toughn'd up.

Subject: MS Windows Install Unattended Setup, Matrox Parhelia & Millennium P650/P750 ... I am mystified by the following, in particular, why is Setup (MS Windows XP Pro Setup) rejecting Device: "Matrox Millennium P650"; Driver: "Matrox Millennium P650"; Provider: "Matrox Graphics Inc."; Mfg: "Matrox Graphics Inc." ? Reason:#I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001. // * Filename: "setupapi.log" extracted "Matrox" from setupapi.log // * "Matrox Millenium, Parhelia P650/750" Driver Installation routine: #-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup // * Comment: This is newer Driver downloaded from Matrox Graphics Inc. Date Released: Jan 17, 2006 #I022 Found "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B" in C:\WINDOWS\NLDRV\003\mtxparh.inf; Device: "Matrox Millennium P650"; Driver: "Matrox Millennium P650"; Provider: "Matrox Graphics Inc."; Mfg: "Matrox Graphics Inc."; Section name: "IN00". #I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001. #I023 Actual install section: [iN00]. Rank: 0x0000c001. Effective driver date: 12/22/2005. // * Original as provided to MS by Matrox for inclusion in DRIVER.CAB #I022 Found "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B" in C:\WINDOWS\inf\parhmse.inf; Device: "Matrox Millennium P650 (Microsoft Corporation)"; Driver: "Matrox Millennium P650 (Microsoft Corporation)"; Provider: "Matrox Graphics Inc."; Mfg: "Matrox Graphics Inc."; Section name: "IN00.ENG". #I023 Actual install section: [iN00.ENG]. Rank: 0x00000001. Effective driver date: 06/06/2003. #I022 Found "PCI\VEN_102B&DEV_2537" in C:\WINDOWS\inf\parhmse.inf; Device: "Matrox Parhelia LX (Microsoft Corporation)"; Driver: "Matrox Parhelia LX (Microsoft Corporation)"; Provider: "Matrox Graphics Inc."; Mfg: "Matrox Graphics Inc."; Section name: "IN00.ENG". #I023 Actual install section: [iN00.ENG]. Rank: 0x00002001. Effective driver date: 06/06/2003. // * Comment: I also added the above rejected Driver Package to "DRIVER.CAB", using TommyP's HFSLIP \HFSLIP\HFEXPERT\DRIVERCAB and extracted all files directly into \DRIVERCAB\ #I022 Found "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B" in C:\WINDOWS\inf\mtxparh.inf; Device: "Matrox Millennium P650"; Driver: "Matrox Millennium P650"; Provider: "Matrox Graphics Inc."; Mfg: "Matrox Graphics Inc."; Section name: "IN00". #I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001. #I023 Actual install section: [iN00]. Rank: 0x0000c001. Effective driver date: 12/22/2005. #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #I063 Selected driver installs from section [iN00.ENG] in "c:\windows\inf\parhmse.inf". #I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}. #I060 Set selected driver. #I058 Selected best compatible driver. #-124 Doing copy-only install of "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B&REV_02\4&630BA98&0&2808". #-166 Device install function: DIF_INSTALLDEVICEFILES. #W383 "layout.PNF" migrate: PNF Language = 0409, Thread = 0c09. #-011 Installing section [iN00.ENG] from "c:\windows\inf\parhmse.inf". #W383 "layout.PNF" migrate: PNF Language = 0409, Thread = 0c09. #-340 Extracted file "MTXPARHD.dll" from cabinet "C:\WINDOWS\Driver Cache\i386\driver.cab" to "C:\WINDOWS\system32\SET1D8.tmp" (target is "C:\WINDOWS\system32\MTXPARHD.dll"). #-024 Copying file "C:\WINDOWS\system32\SET1D8.tmp" to "C:\WINDOWS\system32\MTXPARHD.dll". #E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\SET1D8.tmp" for driver "Matrox Millennium P650 (Microsoft Corporation)" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject. #-340 Extracted file "MTXPARHM.sys" from cabinet "C:\WINDOWS\Driver Cache\i386\driver.cab" to "C:\WINDOWS\system32\DRIVERS\SET1DA.tmp" (target is "C:\WINDOWS\system32\DRIVERS\MTXPARHM.sys"). #-336 Copying file "C:\WINDOWS\system32\DRIVERS\SET1DA.tmp" to "C:\WINDOWS\system32\DRIVERS\MTXPARHM.sys" via temporary file "C:\WINDOWS\system32\DRIVERS\SET1DB.tmp". #E360 An unsigned or incorrectly signed file "C:\WINDOWS\system32\DRIVERS\SET1DA.tmp" for driver "Matrox Millennium P650 (Microsoft Corporation)" will be installed (Policy=Ignore). Error 0x800b0100: No signature was present in the subject. #-166 Device install function: DIF_REGISTER_COINSTALLERS. #I056 Coinstallers registered. #-166 Device install function: DIF_INSTALLINTERFACES. #-011 Installing section [iN00.ENG.Interfaces] from "c:\windows\inf\parhmse.inf". #I054 Interfaces installed. #-166 Device install function: DIF_INSTALLDEVICE. #I123 Doing full install of "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B&REV_02\4&630BA98&0&2808". #I121 Device install of "PCI\VEN_102B&DEV_2537&SUBSYS_1830102B&REV_02\4&630BA98&0&2808" finished successfully. I wonder (may take a bit of work to avoid errors) if I remove the supplied Matrox Driver from DRIVER.CAB, including all references to the package (wherever that may be), if then MS Setup would install the rejected Driver-package.! (I do have better things to do, so must be enjoying myself!). If anyone can tell me why (Setup decides "Driver node not trusted,) this is happening?, I would be pleased, I don't like mysteries, except for Stephen King's kind. (Self) Answer: to above question, (well actually more of a remedy than an answer). Use nLite to remove all Display Drivers. I used to always do this, but got out of the habit when I started testing new Slipstreamed Source on VMWare Workstation. 22nd July, 2008 The true/correct answer is to use "WHQL" Drivers, and Setup will choose the latest Driver.

Subject: MS Windows Install Unattended Setup, Matrox Parhelia & Millennium P650/P750 To automate P650/P750 Driver installation, and dispense with the following dialog: ['Do you want Independent Mode on this Matrox Graphics Package?' YES/NO] Note: Dialog default is "YES" .. add NoIndependentPrompt = true to "MtxSetup.ini" [sETUP] PromptForIndependentDisplays = false to "MtxSetup.ini" [sETUP] // * Filename: "MtxSetup.ini" // * Matrox Driver Filename: Parhelia & Millennium P650/P750 "xp2k_111_00_114_hf_whql.exe" Release Date: Jan 17, 2006 [SETUP] NoIndependentPrompt = true PromptForIndependentDisplays = false To avoid the only other dialog that (may) appear(s) during installation, a possible .NET Framework warning if installing PowerDesk, change .NETRequired = TRUE to .NETRequired = FALSE NOTE: PowerDesk requires .NET Framework, but does not require .NET Framework to be present/installed for "Matrox PowerDesk" to install. Please note .NET Framework is not required for the AGP P650/P750 Driver. // * Filename: "MtxSetup.ini" [.NET] .NETRequired = false The only other change to the default (as supplied) "MtxSetup.ini" was a change to the default Bootup XResolution = 800 YResolution = 600 Monitor Size. // * Filename: "MtxSetup.ini" /*Default boot-up resolution HKR::DefaultSettings.XResolution:DWORD:1280 HKR::DefaultSettings.YResolution:DWORD:1024 To put it all together: // * Filename: "MtxSetup.ini" // * Matrox Driver Filename: Parhelia & Millennium P650/P750 "xp2k_111_00_114_hf_whql.exe" // * [SETUP] PackageName = Matrox Parhelia & Millennium P650/P750 // * The following were added ResetAllSettings = false ResetAllSettingsVisible = false NoIndependentPrompt = true PromptForIndependentDisplays = false EnableIndependentDisplays = false SilentInstall = true ForceNoReboot = true // * End of additional Settings InstallPowerDeskVisible = false InstallPowerDesk = false LOGFILE = MtxSetup.log IniFormatVersion=2.0 [.NET] .NETRequired = false [AddReg.0528.1571102B] ... ... /*Default boot-up resolution HKR::DefaultSettings.XResolution:DWORD:1280 HKR::DefaultSettings.YResolution:DWORD:1024 ... If you change the Default Bootup Resolution, you may also wish to change the "mtxparh.inf" to the same X/Y Resolution, e.g. // * Filename: "mtxparh.inf" // * Matrox Driver Filename: Parhelia & Millennium P650/P750 "xp2k_111_00_114_hf_whql.exe" // * ... ... [AddReg.DefModes] HKR,,DefaultSettings.BitsPerPel,0x00010001,32 HKR,,DefaultSettings.XResolution,0x00010001,1280 HKR,,DefaultSettings.YResolution,0x00010001,1024 ... Success? (You bet!) For other possibly helpful "MtxSetup.ini" settings, see: peachy's Help Click here! Final comment: "Why Matrox Inc. could not have answered my very short and to the point query, instead of a much longer negative directive/reply and an explanation/excuse about Corporate ...,"; "Is beyond my understanding (maybe I just don't want to understand)!" -- It just proves how much they (don't) value the ordinary customer -- PS. IMPORTANT: Apart from extracting the files from the downloaded Driver-file, you must (also) extract the files in "Mtxparh.cab" All files to be in the one Directory/Folder. Helpful hint: You can later (after OS installed) change "MtxSetup.ini" "mtxparh.inf" settings, (unless you delete driver-files after install). Goto "%systemroot%\?????\?????" (Where ????? = the related Driver Folder/Directory). Note that unless you add "Setup.exe" to Driver-list of Driver-files to be copied, (I am bit lazy, so I add Driver-files using NLite, and NLite does not include "Setup.exe" in copy-list), unsure - you may not be able to run the Driver-file at a later time - unsure. I copy "Setup.exe" at later stage of my own copy routine. PPS. A very helpful hint: I opened "Setup.exe" in Notepad and with some scrolling, plus some use of Find, it was in a reasonable time and I had the correct "Unattended Settings" for inclusion on "Unattended XP Pro SP2 Installation"; (no thank's are due to Matrox Inc.! ). I tried peachy's Settings, (see above link), did not work for my Driver Version. Hope this is of assistance. Additional (Feb 8, 2008): Above "mtxSetup.ini" settings will (should) also work with Matrox Parhelia & Millennium P650/P750 Driver-files up to and including: "vxp2k_113_00_158_hf.exe" released on May 08, 2007 The only difference concerns: // * "mtxsetup.ini" [.NET] .NETRequired = false At some stage in the past, this setting was changed to: // * "mtxsetup.ini" [.NET] .NetVersionRequired=2.0 Which only relates to PowerDesk, could be commented out. Finally, a bit of fun at the expense of Matrox Inc. // * Matrox Program Error: (Software Programmer Error); (as supplied): // * Driver Filename: "vxp2k_113_00_158_hf.exe" Release date: May 08, 2007 // * Filename: "MtxUpgradeTasks.ini" [Backup.File] %ALLUSERSPROFILE%\Application Data\Matrox\PowerDesk\8.0x = *.* %SERSPROFILE%\Local Settings\Application Data\Matrox\PowerDesk\8.0x = *.*// * Let's play spot the Programming Error! Comment: It has been in their System for a very long time! 22nd July, 2008. Unattended/Silent (Matrox) Driver Install. I was creating a new unattended "XP Pro SP 3" installation CDRW, and using "vxp2k_113_00_158_hf.exe" released on May 08, 2007; will not install on XP Sevice Pack 3. Updated to "vxp_206_02_004_se_u_whql.exe" released on Jun. 25, 2008. Installed with no problems/errors. Attention: (24th July, 2008) Something strange going on with Driver "vxp_206_02_004_se_u_whql.exe". Firstly, I removed the INF & CAB files which did not apply to my Millenium/Parhelia, unattended Setup failed, during locating Display Device/Driver. So I restored the removed files, Setup succeeded (to successfully strip this Driver Version, at a guess, need to remove all references to Display Device from kept INI/INF files that do not apply to your Device); anyhow, (Unattended) Setup loaded my Parhelia, but used a default VGA driver, and informed me that the Driver was for a previous version of MS Windows. Perhaps Matrox have changed/altered some of the switches I have provided below. Please Note: Running (Matrox) Setup using the switches provided below, the Driver is installed silently, but is disabled by Windows System (System loads the default VGA driver). I will need to check which switch(es) are invalid, and check for new switches. Update: I have checked the switches, they do exist. (I don't know what the problem is!). Please Note: "mtxpar.inf" is missing that final necessary blank line (empty return). Adding/changing "mtxsetup.ini" settings as below is causing BOINC (seti_advanced) repeated "Windows 0xc0000005 error (Access Violation)" errors; so use below settings with caution. (I will see if I can find a Driver written only for "Parhelia & Millennium P650/P750", instead of this generic Driver). I first inserted the following lines into "mtxsetup.ini"; which allows for a (completely) Silent Install. Insert after "PackageName = Matrox PowerDesk-SE". NOTE: InstallPowerDeskVisible = false (already exists). NOTE: InstallPowerDesk = false (already exists, is set to true by Matrox). The switches are self explanatory. ; Filename: "mtxsetup.ini", Matrox Driver Version (for XP) "vxp_206_02_004_se_u_whql.exe" [SETUP] PackageName = Matrox PowerDesk-SE SilentInstall = true ForceNoReboot = true InstallPowerDeskVisible = false InstallPowerDesk = false [FAMILY] ; ; NOTE: "Comment out all EXCEPT your particular Graphics Card, and you can delete the corresponding *.INF, *.CAT, *.CAB ; NOTE: For unattended Windows Setup, YOU MUST extract files from your particular *.CAB. "MS XP Setup" WILL NOT extract ; during Setup ; ; MSerX.inf = Matrox M-Series version 2.06.02.004 mtxpar.inf = Matrox Parhelia & Millennium P650/P750, version 2.06.00.002 ; G550.inf = Matrox G550 Series, version 5.96.004 ; G450.inf = Matrox G450 Series, version 5.96.004 ; G450MMS.inf = Matrox G450MMS, version 5.96.004 ; G400.inf = Matrox G400 Series, version 5.96.004 ; G200.inf = Matrox G200 Series, version 5.96.004 ; G200MMS.inf = Matrox G200MMS, version 5.96.004 ... I also changed the Default Bootup Mode in "mtxpar.inf" from the default 32 x 800 x 600, e.g., ... [AddReg.DefModes] HKR,,DefaultSettings.BitsPerPel,0x00010001,32 HKR,,DefaultSettings.XResolution,0x00010001,1280 HKR,,DefaultSettings.YResolution,0x00010001,1024 ... 27th July, 2008 Filename: "vxp_206_02_004_se_u_whql.exe" released on Jun. 25, 2008. In reference to: Matrox Parhelia & Millennium P650/P750 I have re-enabled the settings in "mtxsetup.ini", seems cannot remove references to other Graphics Cards, not without rewriting. I have also restored/kept all files in package, but only extracting all files from "MtxPar.cab" which is for my particular Graphics Driver. ; Filename: "mtxsetup.ini", Matrox Driver Version (for XP) "vxp_206_02_004_se_u_whql.exe" [SETUP] PackageName = Matrox PowerDesk-SE ResetAllSettings = true ResetAllSettingsVisible = true NoIndependentPrompt = false \* No effect PromptForIndependentDisplays = true \* No effect EnableIndependentDisplays = true \* No effect SilentInstall = true ForceNoReboot = true InstallPowerDeskVisible = false InstallPowerDesk = false IniFormatVersion=2.0 [FAMILY] MSerX.inf = Matrox M-Series version 2.06.02.004 mtxpar.inf = Matrox Parhelia & Millennium P650/P750, version 2.06.00.002 G550.inf = Matrox G550 Series, version 5.96.004 G450.inf = Matrox G450 Series, version 5.96.004 G450MMS.inf = Matrox G450MMS, version 5.96.004 G400.inf = Matrox G400 Series, version 5.96.004 G200.inf = Matrox G200 Series, version 5.96.004 G200MMS.inf = Matrox G200MMS, version 5.96.004 ... Important: (No final empty line). Must add a final (empty, as in blank line) to end of "mtxpar.inf" ; Filename: "mtxpar.inf" ... \* "mtxpar.inf" [Strings.0A];Spanish MtxUninstallDisplayName = "Matrox controlador" MtxUninstallHelpLink = "http://www.matrox.com/graphics/es/support" MtxUninstalUrlInfoAbout = "http://www.matrox.com/graphics/es/ \* This is added (empty) return. IMPORTANT NOTE: Whichever type of Graphics Card/Driver you have/are using, (the above Driver supports several), you must extract files from your particular version of *.cab when you are adding files to your Installation Disc. The *.cab files do not need to be included.

Need more!Something like: [SETUP] INDEPENDENT_MODE = NO I resisted the urge to click the dialog: 'Do you want Independent Mode on this Matrox Graphics Package?' YES/NO Though the Driver did install, nothing else in Package did, as Setup was waiting for input, and will only wait for a determinable time. NOTE: I contacted Matrox at http://www.matrox.com/graphics/en/corpo/su.../requestdoc.php They told me to run SETUP.EXE for each installation (I have three Systems with Matrox Graphics). (Their interest is Corporate with hundreds/thousands, not faithful small Purchasers). So I replied that I will not be purchasing Matrox in future. I will solve the problem with the single Driver Install dialog (given time) and post the answer/result.

I changed to: .NETRequired = FALSE Although .NET is required (for the PowerDesk), stops Setup from failing install of PowerDesk (if .NET is currently absent); PowerDesk will still install. PowerDesk will only be enabled, on first reboot, after install of .NET Comment: .NET is not required for the Graphics Driver.

By your supplied STOP: (error), If it was me, I would be checking PnP (Plug and Play) settings in MBoard BIOS. There is usually a "Load Fail-Safe Defaults" option in BIOS Menu. Problem does not relate to your XP Installation, but your PnP settings/configuration.

June 8th, 2009 Activating Windows XP SP3 Oh what was I thinking!, restoring SP2 files to a clean up-to-date SP3 installation, then doing an in-place "upgrade". It does not matter if you have only SP2 backups and do a (clean) SP3 install (files change, not system-state), not that I can notice. Quick and easy... Step 1). Perform a clean (formatted hard-drive) install. Step 2). Rename "wpa.dbl" retrieve/restore from backup "wpa.dbl" "wpa.bak". Step 3). Restore registry-system-state and reboot, job's done. Though I have software in/on my xp-setup, instead of installing at first login, I manually activate RunOnceEx, after I perform a backup. This allows me less to backup, I know I have an uncluttered error-free, and less error-prone OS. Further, I can refresh the installation at any time, and later restore my other 'stuff'. (Restoring "wpa.bak" averts System from a moment of (noticeable) hesitation while it checks data, and creates a new backup). (Also, as I have reduced to minimum hardware for installing-windows, less risk the better; see Error occurs during the installation of Windows XP, scroll down, 'tis 3rd last item). ******************************* September 11th, 2008 Activating Windows by any means, other than from Backup or through Microsoft, is just not possible. Backup programs such as EMC® Retrospect® for Windows stay in total control, providing all/any resources, dialogs etc to complete restore. M$ Windows may be running, but is not in control. The instant that Windows is booted, Windows-System is in total control, and opened (locked, cannot write to an open key) "HKLM\SYSTEM\WPA", where the activated-state data is located. ******************************* Please note: This "quick activate installation" I have had success with. Quickest/simplest way to get an "activated" installation (without calling Microsoft), do a clean-install, start your backup program, do a "Registry-System-state" only restore, before you restart computer, you must, rename existing "wpa.dbl" and retrieve "wpa.dbl" from backup. On restart, no activate key-icon will appear in system-tray, your registry may/will have entries belonging to software not installed. For a detailed clean-install, restore (files ?) an activated registry and valid activated copy of "wpa.dbl" see below... September 3rd, 2008 Activate Windows XP Activate Windows XP Activate Windows XP Activate Windows XP I have managed to "activate" a clean-install, without contacting Microsoft, using a valid previous copy of "wpa.dbl". Please note that I do have System Backups. Using EMC® Retrospect® for Windows I first do a clean-install of WinXP SP3. IMPORTANT: Windows System would not successfully reboot for me when I restored missing files. No problems restoring registry only plus (activated) copy of wpa.dbl. I believe the problem is to do with the version of "Graphics driver" Windows begins using. Alternative: Especially if you have "WinXP SP3" setup disc, and "WinXP SP2" backup, (1) clean-install, (2)restore files and registry (everything) to a previous date, (3)reboot, (4)"Optical Drive\i386\SETUP.EXE" /UNATTEND 'tis worth trying restore missing files, if problems encountered, remedy by (1) clean-install, (2)skip file restore, (3)restore registry, (4)rename "\Windows\system32\wpa.dbl" to "wpa.dbl.old", (5)restart computer, ... I then install and start Retrospect for Windows restoring missing files. Retrospect will ask me do I really want to restore WinXP SP2 files to a WinXP SP3 file system? *** Yes ***. When missing files restore is finished, rename "\Windows\System32\wpa.dbl" to "wpa.dbl.old" and copy my backup of "wpa.dbl" to "\Windows\System32". ***** Important: You must do this file rename and copy, because Retrospect is restoring missing files, and is unaware the existing "wpa.dbl" is incorrect. ***** Next, restore registry (from backup) and when registry restore only is completed reboot. Congratulations are in order, as WinXP is now (or should be) in the activated state. If not you have missed a step, or done something wrong. WinXP is operating, but extreme caution is required. Though WinXP is stable enough to show the "Desktop", remember I executed a clean-install of WinXP SP3 and restored missing WinXP SP2 files and registry. So *** stop! *** Insert copy of WinXP SP3 in optical drive, click "Start -> Run" and type "(OpticalDrive)\WINNT32.EXE /UNATTEND". Note: I have noticed that "WINNT32.EXE" can be case sensitive, I remember a "Help Window" opened when I typed in lower-case, you only have lower-case or upper-case (which is good odds!). "WINNT32.EXE" will now do an inplace upgrade using all required settings from the registry. You may notice that the Install_dialog that opens looks different/strange, I know I did, a darker color. There should be no problems encountered during this stage, as WinXP Setup only copies required files to disk, and then restarts the PC. When WinXP Setup finishes, you will have a clean-installation, and is (still) activated. Though this may seem a strange example, it was! Microsoft releasing SP3 was a milestone (of sorts), and this example was the only way I could get a clean-installation of WinXP SP3 without activating by telephoning Microsoft. On a previous occasion I was very nicely informed by the Telephonist that they were only too happy to assist with Activation anytime, I found it a real pain in the "a#$%", as you always have to key in a stack of numbers, knowing that it would fail activation because you have exceeded the allowable number of installations, and you would be transferred to a human being. ********************************************************************************************** ********************************************************************************************** I have just now, read in my latest edition (October 2008) of PC User p78 (Australian Edition), required steps to reactivate Windows XP. Comment: The procedure below DOES NOT WORK, though I understand it use to, ( "minus the stupid "oobeinfo.ini" step, a statement from "Nameless BOOTI" (see further below)) before security regarding activation was strengthened. OS checks if Activated_State_Value exists (which is lost with clean-install), so there is one more step to complete. "Nameless BOOTI" writes: Before you reinstall either the retail or OEM version of XP, backup "C:\Windows\System32\wpa.dbl" and "C:\Windows\System32\oobe\oobeinfo.ini" to a floppy disk. (Or retrieve from a previously activated backup). Note: It is reported that applying Service Pack 3 (SP3) will also cause the operating system to deactivate. It is also reported that OEM XP users are limited to phone options for activation, as Microsoft has disabled internet activation for preactivated operating systems. Boot into Safe Mode, Click Start -> 'My Computer', browse to "C:\Windows\System32\wpa.dbl" and rename to "wpa.dbl.old". Then, browse to "C:\Windows\System32\oobe\oobeinfo.ini" and rename to "oobeinfo.ini.old". Finally, copy the version of "wpa.dbl" you saved on floppy to "C:\Windows\System32" and "oobeinfo.ini" to "C:\Windows\System32\oobe\"; then restart your PC. When Windows restarts in normal mode, click Start -> 'All Programs' -> Accessories -> 'System Tools' -> 'Activate Windows' to confirm that your reactivation effort was successful. Comment:The above procedure DOES NOT WORK, though I understand it use to, ( "minus the stupid "oobeinfo.ini" step, a statement from "Nameless BOOTI" (see below)) before security regarding activation was strengthened. OS searches for registry Activated_State_Value (which is lost with clean-install), so there is one more step to complete. I did the above, plus I had the pertinent registry data, however, System has one or more registry keys open that need to be written to. Which means, to successfully reactivate Windows, you must restore from backup or call Microsoft. Maelstorm has listed the Registry keys that relate to Windows being in an Activated state. Please note:Below is my response/reply (which I hope PC User will have the courage to publish in next (November 2008) issue. I have expanded on the activation details to make it obvious to the most dense, where in short, the activation process has a value in "HKLM\SYSTEM\WPA" which Windows System checks, if missing, Windows "knows" activation has not been completed. My reply to the PC User (Australian) article, "Reactivating Windows XP, p78 October 2008. I was hopefully excited and (wrongly) trusting when I read the "Reactivate Windows XP" article, by "Nameless BOOTI", PC User p78, October 2008. I followed the instructions, and failure followed. I understand reactivation was achievable by renaming "\Windows\System32\wpa.dbl" to "wpa.dbl.old" and copying a backup copy of "wpa.dbl" to "\Windows\System\" when the activation process was first introduced. Security regarding activation was strengthened by Microsoft ages ago, though I am unable to state the date. Windows will only be in a activated state if the total value of "HKLM\SYSTEM\WPA\Key-Machine_Specific_Value" and "HKLM\SYSTEM\WPA\SigningHash-Machine_Specific_Value" plus "HKLM\SYSTEM\WPA\Activated_State_Value" are of equal value to "\Windows\System\wpa.dbl" With a clean-installation, "HKLM\SYSTEM\WPA\Activated_State_Value" value is lost, therefore value of "HKLM\SYSTEM\WPA" will be less than your backup copy of "\Windows\System\wpa.dbl" "Nameless BOOTI" used ancient information, adding totally incorrect information stating, "Even worse for OEM users, it's not just a clean installation that will deactivate the operating system; applying Service Pack 3 (SP3) also does this, because it overwrites the file C:\Windows\System32\oobe\oobeinfo.ini, where the preactivation product key is installed and oobe stands for 'Out of Box Experience'." On completing Windows XP Setup, the Out of Box Experience (OOBE) runs activation-process, registration, mouse tutorial and user creation. OEM's activate Windows XP prior to the end-user receiving the PC, an end-user applying Service Pack 3 (SP3) will have no effect on the state of activation, except if a reinstall is initiated. Doing so will cause a value imbalance between above named registry keys and "wpa.dbl". "Nameless BOOTI's" statement that ""Microsoft has disabled internet activation for preactivated operating systems."" is pure double-dutch. Preactivated PC's do not require activation, it is already activated. "Preactivation" simply means that activation has been done prior to delivery (to end-user). "Nameless BOOTI" is in desperate need of a dictionary, to refer to "prior", "pre" and "activate". I am a very long time annual subscriber to PC User, and will continue to do so. However, I really believed that PC User was more scrupulous in the article reporting department. Shame "Nameless BOOTI", this is the standard of hack reporters and television "news hounds". ********************************************************************************************** ********************************************************************************************** Comment: I had forgotten, but I have seen previously "simply stupid" articles by "Nameless BOOTI", fortunately the particular person in question does not submit a lot of articles for publication. This particular individual is a contributor, and I hope the remuneration is as lousy as the article writing.

This really should not be in the nLite subject forum, but anyway... As per "Windows XP Activation" - before you destroy your OS: Grab/save a copy of "wpa.dbl" from %SystemRoot%\System32\ (size can vary from 3kb to +14kb each) Some information removed/deleted, as was incorrect, my sincerest apologies. Please note: This subject continues here... Please click me...

Your info re SP2 is incorrect. I have used the "wpa.dbl" "wpa.bak" twice in last 4 days (on same system, unfortunately). (I use "Recovery Console" (have it as boot option) to copy/replace the files just to be sure of nothing untoward, and certainly quicker than Safe Mode). You may be onto something with those Registry entries, my "wpa.dbl" is only 3kb, I do however, have one on backup that is 14kb so don't worry about the size. If you do not have a backup program such as Retrospect, you'll need to do a trial and error. Further info: Click here Or here

I did a "Registry and System State" restore (using Retrospect V7.5) and on reboot, started "Recovery Console", replaced "wpa.dbl" "wpa.bak" with the correct versions (from my last Backup). Exited "Recovery Console" and on next login, Windows was (already) re-Activated. Please note that this will only work if you are doing a re-install to the same System, and you have not made drastic changes to your System since your last Backup, (else Windows XP will spit the dummy and demand re-Activation). Comment: I did not want to replace any other files as my previous Installation (which I did have a Backup of, and used for above steps) was not perfect. This would also be a fantastic way to freshen your installation (after using HFSLIP and/or nLite). As the "wpa.*" idea helped me, I hope that this will help others. (... and now I don't need to do the phone thingy).

I tried the "wpa.dbl" "wpa.bak" workaround, 'tis nothing but a exercise in wasting time. No doubt the above files do play a part in the Activation/Activated process, but there must also be a required Registry Setting. I did a System-state restore (Retrospect), no file copy, XP remained un-Activated. Copied the above two files, from Recovery Console, XP remained un-Activated. I say this as I have had to Activate via Phone, as my allocated/permitted number of Activations is now -2. (About to do the phone thingy again). Microsoft Staff have no problems (I was informed) regarding Activation, no matter how many times. I did mention that Symantec will simply reset their database, allowing auto-activation again for the allowed number of Activations. Phone Activation can be done without talking to a human, as long as you do not enter any incorrect (phone) key-presses. Why the sequence has to be over +35 digits is beyond me. I must/will try a "wpa.*" + System-state restore (Retrospect) and see if that works. The comment elsewhere in this subject that Activation process does not contact Microsoft Servers is incorrect.

Thanking all who have replied, have helped me no end with observations, answers. I didn't bother to check what the version was, just compared the file dates. Once Explorer loaded, I didn't even think to check on version. Thank you for identifying ngen. This much I do know, .NET most definitely does not touch any System Files. I will be carefully following all info/help provided. This project is not as simple as doing a 2K/XP slipstream, but I implicitly state that 98SE was/is best version ever. (Cannot compare with newer versions, that is totally unfair (on 98SE).

Using "Soporifics" "Win98_UBCD_4.5.20.zip" Unattended Boot CD, complete with the Software/Programs courteously provided, and USP2.1a, System gets all the way to completion of Installation Routines. However, after final (auto) Reboot, I am greeted with; Error loading Explorer.exe You MUST reinstall Windows. OK - I know that one of the Software Programs (provided in zip file) installs a copy of explorer.exe, but I do not know which one. May need to go through a process of elimination, removing/adding one Program at a time, until Fatal Error goes away/returns. Q1). Any ideas on which routines/software installs/replaces explorer.exe. (Comment): Apart from a slight problem with some of the batch-files, seemed @UPDATE1.BAT was in a continual loop, ( I have now copied your "fresh" code thanks "Soporifics"; I am really impressed and most grateful for all the work you have done. Yay! Q1). Any ideas on which routines/software installs/replaces explorer.exe. Regards and best wishes, Jim (Addition): August 05, 2007 12.00HRS GMT To make use of this posting, it is ALL MY FAULT (not yelling!), Do NOT add .NET_V2.0 to installation, (I was too lazy to check compatability at MS). .NET_1.1_SP1 is fine, even the switchless compilation available with two Updates integrated at RyanVM. Edit: (13/08/2007) How simply Dumb of me!. Do not use the above .NET_1.1 in "Windows 98/98SE/ME". It has been patched with XP updates. Excellent! (as says Mr. Monty Burns). Jobs' fine, except an installation named "ngen" did not install, hung during install. I am thrilled with the end result, and to get things back onto 1CD, I removed Tour and those silly Try-me games included. Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Excellent! Regards and best wishes, Jim (Addition) August 05, 14.00HRS GMT I found/solved the fatal Windows Error (see above): Pressed F8 prior to seeing "Starting Windows 98", and selected Command Prompt Only. Something? renamed "EXPLORER.EXE" "EXPLORER.XXX", in %windir%, so I renamed to "EXPLORER.EXE", (Excellent, says Monty B.) What is renaming this critical file? Is it "ngen"? (I believe so!) "ngen" was the only Installation not to complete. But, I don't know to which piece of Software to relate "ngen" to! (I believe "ngen" is renaming "Explorer.exe" so it can do it's Setup without interference). An answer would make my (very early here, 1.00hrs) morning! Jim Info: Explorer.exe %windir% Size: 168KB Modified: 20/08/99 12:58AM Explorer.exe %windir%\OPTIONS\CABS Size: 176KB Modified: 12/05/07 8:48PM (Note: Date Format is dd/mm/yy). So I replaced (from DOS (Safe Mode) Command Prompt Only) %windir%\Explorer.exe with %windir%\OPTIONS\CABS Jim