Jump to content

Alanoll

Patron
  • Posts

    5,494
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Alanoll

  1. the hotfixes, distrobution.... that's been done with XPCreate. Though not GUI, but you just put the hotfixes in the RIGHT folder, and everything goes smoothly.
  2. Alanoll

    XPlode 1.0.3

    and here we thought there wasn't much left besides cosmetics....
  3. the OemPnPDriversPath is not necessarily for Textsetup, but for GUISetup and afterwards... the driver copied as you said is just typically the dll, but the other files are neccesary for normal operation in Windows. When you add the card in windows, and then do the add new hardware wizard, it copies more then just the dll for the card to work right. The OemPnPDriversPath does this automatically.
  4. just out of curiousity... after the IE6 install has entered the entries in RunOnceEX, has anyone tried while still in setup (i dunno if possible, haven't touched 2k in a while) to try and open regedit and export the entries, then move them to another number so you can continue to use RunOnceEX with other values after it? Just out of curiousity.
  5. did someone forget what forum their in? thanks though, always interested in new deployment stuff
  6. most of it is the same. if you used a svcpack.inf, i believe the top portion is different (the Version tag) and that's just been recently answered. You could most likely use the same Winnt.sif but change the ProductKey and everything accordingly. You may also want to have a look at the deploy documentation for Win2k and that might answer alot of your questions
  7. that's a very good question, and just for curiousity, I want to know too. my guess would be multiple unattend.txt files.
  8. i don't think it's neccesary, if you look in like Txtsetup.sif, it's not listed under [sourceDisksName] and such. Just those tag files. but if it is neccesary, you could maybe just create a dummy HTML and then rename the original 2.
  9. i suggest you look at a different thread. This one is quite old. Look for the one about How to Make the Winntbbu.dll files. Its in teh "Threads of Interest" sticky in the forum.
  10. wierd...my guess would be that your XP doesn't have the file. Do you have HOME? attached is my bootcfg.exe bootcfg.exe
  11. use the makecab command example: makecab ntoskrnl.exe and it will come out like this ntoskrnl.ex_ just drop it in the i386 folder to replace the original one i renamed my custom boot kernel to oemkrnl.exe and copied it to system32 forlder the bootcfg command doesnt work for me so i did this to my boot.ini added the /kernel=oemkrnl.exe and it looks like this [boot loader] timeout=0 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional Custom Boot Logo" /fastdetect /kernel=oemkrnl.exe multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows XP Professional" /fastdetect i made a duplicate entry in my ini to test my kernal and it works ok oiy, thanks anyway.....but uh..... yeah. ever notice how old that was??? I have a batch file that does it all for me, regardless of Multi or single processor
  12. the short answer is yes, but the progress bar on the boot screen can only be moved up and down, not side to side. If you download the program i linked to a few posts up, its called BootEditor, it should do you. Its really easy to figure out
  13. already on there
  14. you can't change the color in the winntbbu.dll file. You have to hex edit it. THere is another thread by flyakite about that. as for teh fonts.....to use any font that is not installed by Windows by default.... remember those threads awhile back about isntalling fonts and such (search for it, you'll find it) and how it had registry settings. Just make the settings into inf compatiable, and then search through the hive files for the one containing the fonts (I'm writing this from memory) and copy that there. Then put the actual file in $$\Fonts and you're good to use a custom font.
  15. did you check MS knowledge base for that error and stop code?
  16. what can StyleXP do, that a hacked UXTheme.dll can't?
  17. http://www.softpedia.com/public/cat/13/9/13-9-1.shtml that seems to work fine for me. the page looks like my attachment. just in case, I believe this would give you a direct link to the download. Click the second option...."Download Metropolitan " as thef irst one didn't work for me. http://www.softpedia.com/public/scripts/downloadhero/13-9-1/
  18. its because the colors in the kernel don't match those of your picture. first off, Colors in the picture should be 16bit, and not 256. second, you need to either use the SAME colors as the original XP logo image, or replace the current ones that match yours. use a program called boot editor. this may save you some trouble. this can replace the palette as well as give you a good idea what it will look like. Quite easy to use. You may wish to use this before going to 16bit colors, just incase it comes out satisfactory. (Link to Boot Editor) http://www.softpedia.com/public/cat/13/9/13-9-1.shtml (Homepage for Boot Editor) http://www.belchfire.net/~userxp/indexbe.htm
  19. oops
  20. well....thats what i'm trying to AVOID. those would get copied onto the hdd. is there anyway to reference them without copying to the harddrive?
  21. say you had everything install from a CD. how would you get it to be referenced in the winnt.sif?
  22. yes, but don't know which strings, and i can't look at the file right now. and judging by steve02a post, it doesn't appear that obvious
  23. its defined by one of the strings judging by this post
  24. I too am also interested
×
×
  • Create New...