• Content count

  • Joined

  • Last visited

Community Reputation

-1 Poor

About ChiDragon

  1. I edited the first post with an updated script to allow for CD-only installs as well. It can easily be changed to remove the need to search for a file on the disc if you only have one CD drive, or if you know that the CD drive it's in will always be first in letter order. Let me know if you want that...
  2. I made this simple "RunOnceEx" script in AutoIt the other day and I figured I'd share it. It's basically just two functions that auto-increment the keys/values they add to the registry. Usage is easy, just use ROE1() to add the name of the program to be installed, followed by however many ROE2() commands are necessary to install the program. For fully CD-based installs, use GetCD() with a filename to search for the right CD drive, then use CD: wherever required in your paths. Advantages to using a RunOnceEx.cmd file: - Easier syntax... - No need to fix things like quotes (in a CMD you need to change " to \") - No need to use CMDOW to get it to run silently, it already does - No need to add numbers to get everything to run in the order you want, just script it in the proper order - Adding additional programs later on is easier due to the above A few example installations are included. Enjoy. RunOnceEx_withCD.au3
  3. I think any changes would count as additions to the next time "RunOnceEx" is checked and ran (the next reboot). What happens if you use your RunOnceEx entry to check the existence of the server, add the new entries accordingly, then set an auto-reboot?
  4. Even if it was a quick fix to get it to use your "SP0" files under SP1 and SP2, you wouldn't want to. There are reasons that the files were updated to begin with, after all...
  5. Yeah, that's how it was for me until I fixed it up as mentioned there.
  7. I thought logonui.exe could be 16 or 24 bit or something, since by the time that's loaded up the full video drivers are loaded.
  8. There are no hotfixes out for SP2.
  9. System file protection? You've gotta boot into safe mode to replace it.
  10. No problem. I agree that it doesn't look right somehow. Though the actual #10 bitmap is removed from the SP2 kernel (and whichever number the Home graphic is... #7?), so probably the only way to get it back would be to add the Professional text straight onto the #1 bitmap instead of using overlay.
  11. If you go to and scroll down to "XP - bootscreen", you can find info on how to edit the XP boot screen. However, some of the info is out of date... All of the strings are the same as mentioned on that site, but the addresses are different. After doing a little hacking and checking, I found the proper addresses to manually edit the kernel in order to apply the right palette and to move the status bar's position for the XP SP2 final kernel. Hex addresses 75688 to 756C6 contain the screen's palette. Hex addresses 37344 to 37347, 3912D to 39130, and 391B9 to 391BC contain the first progress bar string (62 01 00 00). Hex addresses 373C2 to 373C5 and 391AF to 391B2 contain the second progress bar string (6A 01 00 00). Also, Photoshop was a b***h about changing the 4-bit boot screen's palette to all-black (which makes it so there isn't a flash of color before the boot screen fades in). I hex edited my bitmaps' palettes, which were located at hex addresses 36 to 74. Everything from address 36 to 74 should be changed to "00". Not sure if that applies to every indexed 4-bit bitmap or just mine, though. Hope this helps someone else wanting to edit the newest kernel for their boot screen.
  12. No one replied but I managed to figure out my errors.. hopefully someone else can learn from them. I somehow ignore the part about Office Shrink needing to be used on a clean install.. so I did a clean one in VMWare, used Office Shrink on the Office setup files, and moved them to my real computer with the shared folders option. I encountered a second problem with Office, where RunOnceEx was not waiting for Office to install before going on with the other programs, which was fixed by making a batch file just for Office and opening it from RunOnceEx instead of the installer. The XCOPY problem was in my switches.. I had chosen to copy directory structures where I shouldn't have. Cleaned up my switches and now I've got none of those extra folders floating around.
  13. It needs to be the same version number as the OS you're using (and some hotfixes change the version number of ntoskrnl apparently).
  14. Mine. I removed all the MS propaganda text from the DLL.. just be aware.... Pic WINNTBBU.DL_
  15. Their isn't any. You'll have to use %systemdrive%\Document and Settings and hope its there... Erm... %allusersprofile% for all users and %userprofile% for current user.