Rich_Weiss

Member
  • Content count

    18
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rich_Weiss

  1. The Office Genuine Advantage Notifications (KB949810) published: 8/25/2009 is showing up on the Microsoft Update site. I updated my copy of the MSDownloads.ulz, and recreated my msdownloads.exe by using the MSBuild.cmd. However, after I ran the msdownloads.exe, the Microsoft Update site still showed that I needed the update. I installed the update using the Microsoft Update site, and then checked the install log file located at C:\Windows\WindowsUpdate.log and discovered that it had downloaded a file from http://download.windowsupdate.com/msdownlo...2e3c11d03d0.cab. The updater then renamed the file to OGANotifier.cab, and extracted OGANotifier.msi from it. Then it ran the OGANotifier.msi using the following command and switches: OGANotifier.msi REBOOT=ReallySuppress ALLUSERS=1 REBOOT=REALLYSUPPRESS. I copied the file to another computer (that also required the update) and using the same command and switches installed it manually. I then checked the Microsoft Update site, and the update was no longer required, having been successfully installed. The version of the OGANotifier.msi is 2.0.0048.0 I am going to add it temporarily to my install script, pending further direction from Darkshadow or others. I also noticed the message on the Microsoft Office Update site that, as of August 1, 2009, Microsoft discontinued support for Office Update. To continue getting the latest updates for Microsoft Office products, use Microsoft Update. Are there files that were required for the Office Update site, that are no longer necessary, and can be removed from the msdownloads.exe, such as the Office Update icon?
  2. As you can all see, and thanks to everyones help, I've got this working exactly like I wanted it to from the local HD's, However, after spending a considerable amount of time, I've been unsuccessful in getting this Vista PE ISO to boot from a USB Flash Drive. I copied the files from the working HD to the flash drive, however when grub finds the ISO and begins to load it, the led on the flash drive indicates activity, but the image never finishes loading. In fact there is no indication that it even started to load (ie the progress bar across the bottom never shows up) I can load other ISO's, off of the flash drive, by using the exact same grub menu.lst, and syntax, but not the ISO that I created from the Vista PE WAIK I've tried different flash drives, reformatted the Flash Drive. I've defragged the ISO, tried loading grub from DOS instead of from the ntldr/ boot.ini. I tried to use the --mem option to load the ISO to RAM first, and yet I can't figure out what I'm missing. If I remove the ISO from the Flash Drive, and copy it to the local HD the "find --set-root" in the menu.lst on the Flash Drive, locates it on the HD, and it runs perfectly. I am assuming its either the ISO itself (since other ISO's load from the flash drive) or the syntax / emulation of how I'm calling it from the menu.lst (but again it works fine when located on the HD). Could it be that Vista is resetting the USB ports before the ISO can finish loading, like the XP install does? But then why didn't the --mem option work? I'm at my wits end.
  3. Wow, What a good idea. I renamed the grldr to WinPEx86, and changed the boot.ini to match. Thanks again. I now have it successfully booting from a hidden recovery partition as well, and will be using imagex to restore images to the primary drive. PS The next project is going to be getting it to boot from a USB Flash Drive as a system support environment.
  4. First let me say say thanks to WreX for your info, I'll integrate it into the Vista installs. And to jaclaz, I used your info to tweak the xp version. So here's the latest procedure that I've used for booting a PE 2.x .iso (created from the Vista WAIK) from a XP PC using the Grub4DOS CDROM emulation. Note: This also worked with other bootable ISO images, I simply changed the name of the ISO in the menu to match. I suspect I could even have a list of several ISO's in the menu to choose from, all of which could be in an ISO directory, located on a hidden support/recovery partition, but I will have to look into that idea at another time. Download the Grub4DOS from Grub4DOS Project Download GrubInst from Grub4Dos Utils Project Create a temporary directory Extract the grldr file, from the Grub4Dos download, to the temporary directory Extract the grubmenu.exe, from the GrubInst download, to the temporary directory Create a new menu.lst in the temporary directory which contains the following code - default 0 timeout 0 title WinPEx86 find --set-root --ignore-floppies --ignore-cd /WinPEx86.iso map /WinPEx86.iso (hd32) map --hook chainloader (hd32) Import the new menu.lst into the grldr using grubmenu.exe by executing the following command from the temporary directory - grubmenu.exe import grldr menu.lst Copy the grldr from the temporary directory to the root of the C: Drive Appended the C:\BOOT.INI with this line: C:\GRLDR="WinPEx86" And finally copy the WinPEx86.iso to the root of the C: Drive - Note: This file must be in one contiguous disk area for drive emulation to work, so defrag it if neccessary, or if you have enough RAM add a --mem option to the menu.lst before importing it by changing the "map /WinPEx86.iso (hd32)" to "map --mem /WinPEx86.iso (hd32)"
  5. I still may tweak this a little, or even find another solution, such as suggested by WreX, but so far I've got it working by using Grub4DOS. I discovered that GRUB for NTLDR, can be used to boot into GRUB from the boot.ini menu of Windows XP. Nothing needs to be installed either, which is perfect, since all I have to do is drop my files into the root, and I'm good to go. I simply copied my WinPEx86.iso, and the GRLDR, (which I extraced from Grub4Dos), to the root directory of the C: drive, appended the C:\BOOT.INI with this line: C:\GRLDR="WinPEx86", and then created a menu.lst, that I also put in the root of the C: drive with the following code. timeout 0 default 0 title WinPEx86 find --set-root --ignore-floppies /WinPEx86.iso map /WinPEx86.iso (hd32) map --hook chainloader (hd32) boot Thanks everyone. This Board is awesome
  6. Thanks for the quick response. Its a PE 2.x .iso (Vista/Server2008/7 based ISO. So I'll check out the 2nd link. Hopefully I can pass control to grub4dos from the ntldr/boot.ini since I need to keep the MS XP boot process intact.
  7. I have a WinPE.iso that contains a few support tools. It was created from Vista WAIK on an XP PC. The ISO, when burned, and booted from a CD works perfectly. What I would like to do is create a boot.ini menu item called WinPE that would load the ISO from the C: Drive into RAM, and then run it from there so I don't need to carry the CD around with me. I've been able to successfully use Win Builder to create a BootSDI.img, that I've added to the boot.ini and it works perfectly. But I need to stick to MS products if at all possible, and therefore I would like to be able to do the same with the WinPE.iso or any bootable ISO that would fit in RAM. I've been searching on and off for a solution to this for some time, but I can't seem to find any clear directions. I'm hoping someone here can point me in the right direction.
  8. Is there a way to tweak this so it will map the disk type groupings to a certain range of drive letters rather than one drive letter after the other? I would like to have the first CD/DVD drive map to drive R: and the next to S: etc. and the removable drives to end at drive Z:. For Example C: Local System Drive D: Local Data Drive N: Network Drive R: CD ROM S: DVD ROM X: Removable Drive Y: Removable Drive Z: Removable Drive
  9. This looks great and very helpful. Thanks for sharing your efforts with us. However, I have a question regarding the Build_All.cmd, which calls the install_msd.cmd and install_network.cmd files. I do not seem to have the install_msd.cmd and install_network.cmd files, and I did not see where to get them, or how to create them from your WIM Imaging Tutorial 1.5. I must be missing something somewhere, and would be grateful if you would enlighten me. The best I can tell is that I should rename and use the Install_Drivers.cmd, copying one into the drivers/network folder and another into the drivers/msd folder.
  10. Without looking at your file it is hard to tell what is wrong, but one thing that I have discovered is that Manufacturer is a required field, and without it nothing else will display. [General] Manufacturer=Some text must be here Model= [Support Information] Line1= Line2= Line3= Line4=
  11. Are you using a Dell XP recovery CD? If so the SLP Product Key is located in the I386 folder in the WINNT.SIF file under [userData] -> Product Key= If not, here's a link with SLP's for most major royalty manufactures. http://forums.mydigitallife.info/showthread.php?t=2602 And here is some information from Microsoft that you might find helpful called "Preserving OEM Pre-Activation when Re-installing Windows XP" http://technet.microsoft.com/en-us/library/bb457078.aspx
  12. Perhaps a different method that achieves the same result will work. Here's what I do, I use ComputerName=* to set a random name, and then at T-12 I run this small program (40KB) that prompts for a new name, converts the name to caps automatically, and then changes the random name to the typed name. You can find more information about its other features here. http://www.engl.co.uk/products/zcnclite/index.html
  13. Set this registry key [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment] "SEE_MASK_NOZONECHECKS"="1" See http://support.microsoft.com/kb/889815 and http://vlaurie.com/computers2/Articles/environment.htm for more info.
  14. This is the relevant part of my RunOnceEx.cmd File ECHO. ECHO Installing MS Windows XP .Net Framework 1.1 REM .NET Framework Version 1.1 Redistributable Package dotnetfx.exe /Q:A /C:"Install /Q" REM .NET Framework 1.1 Service Pack 1 NDP1.1sp1-KB867460-x86.exe /Q REM .NET Framework 1.1 Service Pack 1 SYSTEM.WEB.DLL and MSCOREE.DLL Security Update for Windows XP NDP1.1sp1-KB928366-x86.exe /Q ECHO. ECHO Installing MS Windows XP .Net Framework 3.5 with SP1, and 3.0 with SP 2 REM .NET Framework Version 3.5 Redistributable Package (KB951847) dotnetfx35.exe /Passive /NoRestart /OverWriteOEM /NoBackup REM .NET Framework 3.5 Family Update for Windows XP REM http://www.microsoft.com/downloads/details...54-6450b0212565 NDP20SP2-KB958481-x86.exe /Passive /NoRestart REM .NET Framework 3.5 Family Update for Windows XP REM http://download.microsoft.com/download/C/6...B958483-x86.exe NDP30SP2-KB958483-x86.exe /Passive /NoRestart REM .NET Framework 3.5 Family Update for Windows XP REM http://www.microsoft.com/downloads/details...66-a31b83931953 NDP35SP1-KB958484-x86.exe /Passive /NoRestart REM Update for Windows XP (KB961118) Printer driver may be unsigned after you install the Microsoft .NET Framework 3.5 SP1 WindowsXP-KB961118-x86-ENU.exe /Passive /NoRestart /OverWriteOEM /NoBackup
  15. If it is just one workstation that is shared by several people, each with their own profile, and they are not logging in through a server, then I would think that a batch file that runs the first time each user logs in might be one possible solution. It would need to identify the currently logged in user, then run the appropriate user.cmd file which would import their personal email settings into the HKCU. For Example - add this key at T-12 to integrate it into the default user profile. "HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce" /ve /d "UserRunOnce.cmd" Then create individual cmd files for each user named after their login name ie TSmith.cmd, JDoe.cmd, etc Then create a UserRunOnce.cmd batch file similar to this one UserRunOnce.cmd Call %UserName%.cmd Exit When a new user logs in, the UserRunOnce batch file will run once, and call their personal cmd file, and then remove itself from their registry profile. Just a 4am suggestion that might point you in the right direction.