jda11560

Member
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About jda11560

  1. The RunOnceEx example listed at: RunOnceEx does not work for/in Windows 2000; however, if you convert your RunOnceEx.cmd file to a Registry file you will have success. I created/copied a suitable RunOnceEx.cmd file, ran (doubleclick) the file and then saved the RunOnceEx (Registry) branch as RunOnceEx.reg; this I did in Windows XP. (simply because I did not know how to create a Registry script). RunOnceEx runs exactly as it should, when it should (just after first logon). If any of your installation programs need to reboot immediately after install, RunOnceEx will, on next startup, continue on from previously installed program; RunOnceEx keys do not get deleted until after the program/file runs or is cancelled. The only problem with using a *.reg file is the path(s) must be absolute, e.g. %systemdrive% wil not work. Here is a short sample, you will be able to create your own *.reg file from this if you wish. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx] "TITLE"="Installing Applications" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\010] @=".NET Framework V1.1 SP1" "1"="C:\\install\\dotnet11sp1.exe" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\018] @="Windows MediaPlayer V9" "1"="C:\\install\\MPSetup9.exe" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\019] @="Tweakui V1.33.0.0" "1"="rundll32.exe setupapi,InstallHinfSection DefaultInstall 132 C:\\install\\tweakui.inf" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\020] @="Java Runtime Environment V1.5.0.90" "1"="C:\\install\\jre509.exe" [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\095] @="Cleaning up, delete temp files" "1"="C:\\install\\cleanup.cmd" Where ther are quotes, " , these must remain, and where there are double \\ , these too must remain. The numbers after \RunOnceEx\ are simply to provide order/sequence, lowest numeric/alphanumeric will run first. If you read the RunOnceEx example, this is exactly the same except for being a *.reg file. To integrate/merge quietly into the registry, use (in cmdlines.txt): regedit /s Example: [Commands] "some command 1" "regedit.exe /s RunOnceEx.reg" "some command x"
  2. I open a DOS PROMPT in Windows 98SE, and type; d:\i386\winnt32 /dudisable /u:winnt.sif Setup dialog does open, but then I get the error: The specified Setup script file (d:\i386\winnt.sif) is inaccessable or invalid. I know what is happening; WINNT32.exe (and required files) is being copied to: C:\Windows\WINNT32\ (This is a temporary Folder, and gets deleted by WINNT32), on close I guess. WINNT32 won't read the setup script from d:\i386\ nor from c:\Windows\WINNT32\ (if I manage to get a copy of my Setup Script into c:\Windows\WINNT32 So I guess my question is: Is it possible to do an inplace upgrade to Windows XP using a Setup Script?
  3. My apologies and I am not finding fault, but the I386 Folder in graphic should be separated by an extra couple of folders. When you are working on the $OEM$ (Applications Folder(s)) the I386 Folder is not even visible on branch. There is actually (if you are also installing PnP Drivers to be installed during Installation) two (2) $OEM$ Folders, one (1) in the I386 Folder, which creates a branch when you add your Drivers. A second $OEM$ Folder is situated (on my Folder Tree) two (2) Folders above the I386 Folder. When you add Application(s) Folders to this $OEM$ Folder, a second branch will be created. The I386 Folder should should be separated, $OEM$ Distribution Folders The rest of the information is correct, but, "a picture paints a 1,000 words" and the graphic will lead you down the garden path, (did me). |-I386- $OEM$- $1- pnpdrivers Above: Directory Structure: FOR "OEM" (Adding your own PnP Drivers, e.g., Motherboard, RAID, SCSI, VIDEO, NET, what you want or require). Place in pnpdrivers, you can split the different PnP drivers into respective Folders, but, they must all be in pnpdrivers. The above applies when you are using Software such as: nLite Adding "OEM" (Your extra Software on Operating System CDROM) Software during Setup Installation. There seems to be some confusion as to adding Software during Setup Installation. I think some people (me included) have their brain centred/fixed on the I386, $OEM$ Folders. For an "OEM" (and Unattended) Installation, a second $OEM$ Folder is added to the Folder tree of your Installation. This will often be situated at the very top of main branch. |-I386 |-DISCOVER |-BOOTDISK |-$OEM$- $1-| $$-| $Progs-| Note: The above applies when you are adding Software/Applications, extra PnP drivers, (or empty Folders which will be already in Search Path when you add (at present unknown) PnP drivers at a later stage. $1 resolves to %systemdrive%, $$ resolves to your Windows Folder, %windir%, e.g., "Windows", "Windows XP", "WINNT" $Progs resolves to "Program Files", or whatever you or Setup decides. Note: Which Drive this happens on does not come into the discussion.
  4. If I have an $oem$ directory structure set up, and put a directory under the $1 directory, the directory should be copied over to the system drive during install and be there after the OS is installed correct? i.e. D:\RemoteInstall\Setup\English\Images\WINDOWS\i386\$oem$\$1\TestDir\, there should be a directory named c:\TestDir\ on the machine once the install is complete. Am I understanding this correctly? $OEM$ should be parallel to i386, not within it. =============== |-i386 |-$OEM$ |-$1 |-pnpdrivers =============== Directory Structure: FOR "OEM" (Adding your own PnP Drivers, e.g., Motherboard, RAID, SCSI, VIDEO, NET, what you want or require). Place in pnpdrivers, you can split the different PnP drivers into respective Folders, but, they must all be in pnpdrivers. Adding "OEM" (Your extra Software on Operating System CDROM) Software during Setup Installation: ======================================================================== There seems to be some confusion as to adding Software during Setup Installation. I think some people (me included) have their brain centred/fixed on the I386, $OEM$ Folders. For an "OEM" (and Unattended) Installation, a second $OEM$ Folder is added to the Folder tree of your Installation. This will often be situated at the very top of main branch. =========== |-I386 |-DISCOVER |-BOOTDISK |-$OEM$ |-$1 |-$$ |-$Progs =========== $1 resolves to %systemdrive%, $$ resolves to your Windows Folder, e.g., "Windows", "Windows XP", "WINNT" $Progs resolves to "Program Files", or whatever you or Setup decides. Note: Which Drive this happens on does not come into the discussion.
  5. Hi Gurgelmeyer, What a fluke! I only joined this Forum an hour ago, did a search for - Break IE5 in WIN2K and integrate IE6 SP1 - and I came across your name within seconds. Subject: WIN2K Pro. SP4 Mshta.exe Error Message Appears When You Start the Add/Remove Programs Tool in Control Panel. SYMPTOMS: When you start the Add/Remove Programs tool in Control Panel on a computer running Microsoft Windows 2000 Professional, the following error message may be displayed: Mshta.exe has generated errors and will be closed by Windows RESOLUTION: To resolve the behavior, type the following commands in the Run dialog box: • sfc /purgecache • sfc /scannow NOTE: Windows 2000 prompts you to insert the Windows 2000 Professional CD-ROM to complete these commands. If you run these commands and the behavior is not resolved, perform an in-place upgrade of Windows 2000 Professional. APPLIES TO: • Microsoft Windows 2000 Professional Edition These errors may not have occurred prior to "Windows 2000 SP4", but attempting to do an upgrade using "Windows Update" on "Windows 2000 SP4" simply does not integrate into the system correctly, (although it is supposed to). As you probably know, IE6SP1 is integrated directly into the Operating System by "Windows Update" and you are given no choice of downloading and installing at a later date. To get around that problem, I downloaded IE6SP1 using WINME, (I also have XPSP2Pro, running VMware WS 5.5; In download options, can select different Operating System versions, at least M$ gave us that choice. After installation (of IE6SP1), the Operating System thinks it is IE6SP1, but the "Windows Update website" knows it is actually IE5. I did after a long attempt, manage to access "Windows Update", but I realised that I would always be stuck with the problem with Internet Explorer. So I am thinking, There must be some way of stripping Internet Explorer 5 out of Windows 2000, and it would have to be done before integrating "Service Pack 4 (SP4)" into "Windows 2000 /Windows 2000 Professional", using nLite:http://www.nliteos.com/ Possibly not so much stripping "Internet Explorer V5" out of "Windows 2000", as breaking the installation so it is not installed as V5, which is the default, but as V6. When "Windows Update" completes installation of "Internet Explorer 6 SP1", "Windows Update" still recognises the version as Version 5 (Five). Well Gurgelmeyer, I think that is my story well and truly told, (maybe not well), I will have to follow up on this usp51.zip file. Regards and best wishes, Jim