Jump to content

b0r3d

Member
  • Posts

    739
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Everything posted by b0r3d

  1. At some point you'd have to execute the commands from the client. Im sure it wouldnt be that much trouble to copy the batch file from the disk (or even run it from the server) on each client machine. Its alot easier than having to install each update manually.
  2. just use windows search engine to search for all .cab files on your Office cd. If its not there, thats your problem
  3. Just adding the Autopartitian = 0 to the winnt.sif file will prompt you when you boot off the CD which drive you want to install windows to. When you select it, it'll format it for you aswell.
  4. Make sure you have the most recent drivers for all your hardware.
  5. Yes. Put it on a floppy disk, and walk it around to each of the 10 pcs. Put the patches on the server, and in your batch file, use the net use command to map a drive to the server, and run the patches from there.
  6. Is the .cab file on the CD? If it is, is it currupt? If not, are you able to browse for it, and tell the installer where it is?
  7. Suburb is Balgowlah. Very close to Manly
  8. Looks very spiffy Well done
  9. Greetings and Salutations! I'm a 20 y/o sex godess from Sydney Australia. Qualifications: CERT III - Network Administration CERT IV - Network Management CERT IV - Database Administration CCNA - Stages 1 & 2 Currently Studying: CCNA - Stages 3 & 4 Looking forward to seeing your input on the boards!
  10. Okay, after a little research, ive done all the work for you Throw this in your batch file: To defrag: START /WAIT DEFRAG C: <-- replace C: with any drive letter you choose To ScanDisk: START /WAIT CHKDSK
  11. Consider it done.
  12. The first thing you need before you do anything, is a program that can open up, and examine the innards of the WINNTBBU.DLL. The program i use is Resource Tuner. Most people use Resource Hacker (cause its freeware), but i find this one alot more user friendly. Whilst that is downloading, you may wish to extract the WINNTBBU.DLL from your I386 Directory on your WindowsXP CD, and chuck it in a folder someplace. I recommend making a brand spanking new folder where you can store all your new setup screen goodies, so you have them all in the one spot when you need them. Download is done? Excellent. Give Resource Tuner the good ol' install treatment, and when you're done, execute the application. From there, you'd want to select File --> Open and then select your WINNTBBU.DLL file you extracted earlier. Since Resource Tuner is a 30 day trial program, it'll ask you to register blah blah, just smash continue. Your screen should look like this: If you expand the bitmap subfolder, you'll see lots of little enteries that start with 100, and go up to 192. Now all of them arent there, so dont be alarmed. It goes from 100 to 109, then skips straight to 150. This is normal. You're not missing any enteries, so take thoes fingernails out of your mouth. If you have a little browse through the enteries in the bitmap subcategory by clicking on a few, you'll notice that each one holds a different bitmap image. These are what you will be editing, and replacing, in order to make your install screens look spiffy. You will notice that there are several versions of each bitmap image. One set are for 1024 x 768 (high resolution) and the other set are for 640 x 480 (Low resolution). We will be editing the high resolution images. Here is a brief explanation of where the bitmap files you will need are located: 100 - Windows Logo in the top left hand corner. 101 - Windows Logo in the top left hand corner. 102 - Windows Logo in the top left hand corner. 103 - The main background image. 104 - Image shown next to the task when it has been completed. 105 - Image shown next to the task which has not been completed. 109 - Image shown next to the task when it is being performed. 181 - 192 - Little animating images in the bottom right hand corner of the setup screen. Okay. From then on, all you need to do is Right click on the image you wish to edit, and select Save Resource As... and choose a location to save the image. Once you've extracted an image, its time to edit it. Any graphics editing program will suffice. Change it how you wish. The only limits are, that the backdrop must be 1024 x 768, and all images must be in 256 colours. I find it easier to make the image, then convert it to 256 colours at the end. So now you have your new image that you want to throw back into the WINNTBBU.DLL. This is how you do it. Back in your resource tuner, select the key that you extracted the image from, right click --> edit resource. On the next screen, you need to press the Open Resource button, illustrated below. From there, select your edited bitmap. Next, select Ok. Select Yes from the next dialog box. Follow thoes last few steps to editing your bitmap files, for all the other bitmaps you wish to change, save your new WINNTBBU.DLL (File --> Save File As...) and bobs your monkey! But don't relax yet ... we're not done. By this point, you should have all your bitmaps replaced in the WINNTBBU.DLL file. You're almost done! Open up a command prompt (windows key + R, then type in cmd) and navigate to the directory where you saved your WINNTBBU.DLL. (If you dont know how to navigate directorys through dos, i suggest you find out) Next, at the command prompt, type in this command. makecab winntbbu.dll This will create a file called winntbbu.dl_ in the same directory. All you need to do now is throw that file you just created (winntbbu.dl_) into your i386 folder on your XP CD, and thats it! Congratulations, you've just changed your XP Setup Screens! Give yourself a pat on the back and a chocolate eclair. You've earnt it. Note: You do NOT need to put the new WINNTBBU.DLL file into your i386 directory. Only the winntbbu.dl_
  13. Greetings and Salutations!
  14. Are you guys using an administrator account that you've serparatly created, or the admin account that comes installed with windows by default?
  15. I assume so. All you'll have to do is find out the dos name and switches for each program. To test it out, go to start --> run --> and type what you find in there. If it starts defragging/scan disking, then thats the command you're looking for
  16. Doesnt WindowBlinds suck up a huge chunk of RAM ?
  17. I have no idea what you're talking about
  18. Nice little guide there. Im sure alot of the MSFN members (and even alot who arent) will appreciate it!
  19. My main point is that you need to be able to installed it unattended.
  20. In order to use that program with an unattended XP CD, you'd first need to install AutoIt without attention, and then be able to call different point and click macros at will, all without a reboot.
  21. Angelfire does not support img linking Moo!
  22. I see. That's rather handy. With that you can automate literally any program you want.
  23. What refresh fix are you referring to ?
  24. How does simulating mouse clicks or keyboard strokes help with automating Unattended XP Install CDs ?
  25. %SYSTEMDRIVE% is a variable used by windows. Variables are indicated by the % symbol. The %SYSTEMDRIVE% variable will take you to the drive that windows is installed on, no matter the drive letter. (Because some funny people like to install Windows on drives other than C:) Windows has many other variables for reasons such as this.
×
×
  • Create New...