Jump to content

SKARDAVNELNATE

Member
  • Posts

    6
  • Joined

  • Last visited

  • Donations

    $0.00 

About SKARDAVNELNATE

Profile Information

  • OS
    98SE

SKARDAVNELNATE's Achievements

0

Reputation

  1. Trying to get back on track with what I know to work. Started over with Windows Update and checked each KB# against the files I had. Removed 6 of them that start with "IE8-" which didn't install until after Internet Explorer was configured. Also wrote some batch files that edit the names of the remaining files down to just their KB# and append them to a text file to keep the SVCPACK folder and INF neat. Plan to do a batch that will start Internet Explorer, allow me to configure it, then when it closes install the 6 remaining updates. With that in mind I'm now focusing on the $OEM$ section of the guide. I also want to add some custom folders to the start menu. There are now 2 others issues. 1) During Windows Setup a dialog box opens and I have to press Next > to continue. 2)These 2 folders in the ISO $OEM$\$1\Documents and Settings\All Users\Start Menu $OEM$\$1\Documents and Settings\Default User\Start Menu They are copied to C:\ as expected but instead of using these, Windows has created new folders C:\Documents and Settings\All Users.WINDOWS C:\Documents and Settings\Default User.WINDOWS Edit: Just found another issue. In my WINNT.SIF I added [setupData] OSLoadOptionsVar="/noexecute=alwaysoff" This was one of the additions I noticed from trying nLite earlier. But this doesn't appear to be handled correctly because I find conflicting settings in Boot.ini multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Home Edition" /noexecute=optin /fastdetect /noexecute=alwaysoff
  2. I think I'm just getting further off track now. UDC - Identified 22 files as obsolete And another 7 files that are not from the list. IE8-WindowsXP-KB2598845-x86-ENU.exe IE8-WindowsXP-KB2632503-x86-ENU.exe WindowsXP-KB942288-v3-x86.exe WindowsXP-KB961118-x86-ENU.exe WindowsXP-KB968930-x86-ENG.exe WindowsXP-KB2492386-x86-ENU.exe WindowsXP-KB2808679-x86-ENU.exe nLite kept giving me errors so I started over with everything. Copy CD contents to C:\XPCD Integrate SP3 Run UDC from an otherwise empty folder. Comparing the 2 folders I find that UDC had ignored qchain.exe rootsupd.exe Windows-KB909520-v1.000-x86-ENU.exe WindowsSearch-KB940157-XP-x86-enu.exe WindowsXP-WindowsMedia-KB2834904-v2-x86-ENU.exe And anything pertaining to DotNet nLite still had a message for me. KB2686509 hotfix is known to cause issues if: - Windows key is disabled the in Tweaks (advanced), Explorer, Disable Windows Key - keyboard components removed I think the is a typo. Also I got this message a few times. H-Could not find part of the path 'C:\XPCD\hottemp\update' When I tested the new setup I ran into a new problem. Fatal Error An error has been encountered that prevents Setup from continuing. One of the components that Windows needs to continue setup could not be installed. A components file does not match the verification information present in the component manifest. SXS.DLL: Syntax error in the manifest or policy file "D:\I386\asm\60\MSFT\Windows\COMMON\CONTROLS\CONTROLS.MAN" on line 5. At least when doing this manually I knew I could fix something if I did it wrong. I don't think I can fix something nLite did wrong. In terms of reference material for understanding how an unattended setup works nLite isn't that useful. I did find a few lined in WINNT.SIF to try out on my own. I was having the most success with the SVCPACK.INF method. With the /integrate switch, that too would add entries into SVCPACK.INF. nLite doesn't appear to have created that file and I don't understand what it's doing with the SVCPACK folder.
  3. I already downloaded all the updates I needed. I want to set it up manually so that I understand how it works. The only problems I'm having is that... 1) the integrate switch doesn't work as described here: http://unattended.msfn.org/unattended.xp/view/web/23/ 2) Some updates seem to be skipped when added as described here: http://unattended.msfn.org/unattended.xp/view/web/24/ When I study the batch scripting section of the guide more I may wind up fixing the problem that way instead. I see nothing wrong with Window Media Player 11 in my test setup. Including it in SVCPACK appears to have been sufficient. I went to http://www.microsoft.com/en-us/download/default.aspx and searched for "KB968930 XP x86" For some reason that was the file it pointed me to at the time. Also it installed and removed the Widows Update item when I tested it. I'll update my notes with the correct version. That appears to be a thread about experiencing errors when using a program which I'm not using. Could you elaborate on which part I'm suppose to find relevant? I don't understand.
  4. I am using Virtual PC 2007 to test an updated ISO of the Windows XP CD. I've been following the instructions at http://unattended.msfn.org/unattended.xp/ Completed so far: Copy CD contents to C:\XPCD Integrate SP3 Created WINNT.SIF Created SVCPACK.INI Added Internet Explorer 8, Windows Media Player 11, Windows Update Agent 3.0, Windows Installer 4.5, and qchain to SVCPACK Updated ISO and tested. Everything works as expected so far. Run Windows Update and downloaded remaining updates separately. Now I've reached the point where I can use the /INTEGRATE switch or SVCPACK.INF Methods. I thought I would use the /INTEGRATE switch as I did with SP3. First I determined which files utilize the switch using a batch file with FOR %%f IN (*.exe) DO "%%f" /? After moving those that didn't I used FOR %%f IN (*.exe) DO "%%f" /Integrate:C:\XPCD However 17 of the files produced an error when I tried this. IE8-WindowsXP-KB2909210-x86-ENU.exe WindowsXP-KB2849470-x86-ENU.exe WindowsXP-KB2859537-x86-ENU.exe WindowsXP-KB2862152-x86-ENU.exe WindowsXP-KB2868626-x86-ENU.exe WindowsXP-KB2876217-x86-ENU.exe WindowsXP-KB2876331-x86-ENU.exe WindowsXP-KB2883150-x86-ENU.exe WindowsXP-KB2892075-x86-ENU.exe WindowsXP-KB2893294-x86-ENU.exe WindowsXP-KB2898715-x86-ENU.exe WindowsXP-KB2914368-x86-ENU.exe WindowsXP-KB2916036-x86-ENU.exe WindowsXP-KB2922229-x86-ENU.exe WindowsXP-KB2930275-x86-ENU.exe WindowsXP-KB2808679-x86-ENU.exe WindowsServer2003-KB968930-x86-ENG.exe An error occurred while attempting to integrate this software update package. Verify that the architecture, language, and service pack level of this software update are valid for the target distribution folder. I have tested these 17 files separately to see if they install and didn't encounter any problems aside from integrate. Updated ISO and tested. After formatting Windows setup encounters a problem and gets stuck in a loop of continually rebooting. lsass.exe - Not Enough Quota Not enough virtual memory or paging file quota is available to complete the specified operation. So even when the files integrate smoothly something else still goes wrong. I started over and went with the SVCPACK.INF Method. Again I encountered a few problems. Windows-KB890830-V5.11.exe Neither "/Q /O /N /Z" nor "/Q:A /R:N" appear to be correct for this file. Some updates that were included in SVCPACK still appear in Windows Update. IE8-WindowsXP-KB2510531-x86-ENU.exe IE8-WindowsXP-KB2909210-x86-ENU.exe IE8-WindowsXP-KB2632503-x86-ENU.exe IE8-WindowsXP-KB2598845-x86-ENU.exe IE8-WindowsXP-KB2936068-x86-ENU.exe IE8-WindowsXP-KB2964358-x86-custom-ENU.exe
  5. I tried that one as well. it did remove the question marks on the two devices, however it also went through 2 dozen or so other New Hardware Found boxes and froze on the Windows is shutting down screen. Is there a way to install the drivers seperately for just the two devices?
  6. Hello, according to http://www.intel.com/support/motherboards/desktop/sb/CS-008326.htm The D875PBZ board is suppose to fully support Windows 98. However the wrong chipset driver is provided. INF_AllOS_8.3.1.1009_PV_Intel.exe claims to be for Windows 98 SE and Intel® Desktop Board D875PBZ. But attempting to run the file in Windows 98 SE results in this. The INF_AllOS_8.3.1.1009_PV_Intel.exe file is linked to missing export SHELL32.DLL:SHCreateDirectoryExA. Some searching revealed that there was an -A flag to extract the files it would install. Including a readme.txt which says: Also "* Target Chipset#: X38 & 3200/3210 Chipset" but according to a manual PDF the Intel D875PBZ uses 875P Chipset. In device manager there are 2 items that have question marks. PCI System Management Bus Unknown Device


×
×
  • Create New...