Jump to content

b0r3d

Member
  • Posts

    739
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Australia

Everything posted by b0r3d

  1. if you want to test its durability, give it to me. Ill throw it on a derby track
  2. The interface is a huge difference from what it was before. More pleasing to the eyes, and alot easier to navigate. and NO FRAMES! Eventhough im sure its not completed, it seems to lack a little content, and i feel the interface could still be improved. (Thats what you get for opening a poll on an uncompleted website lol ) Looks like your heading in the right direction though! Keep up the good work mate. Vote: 3 - Ok
  3. If Microsoft says it, then it must be a load of bollocks
  4. If your not using a domain, then the batch file is easy. @Echo Off Echo =================================== Echo = This batch file will install = Echo = Windows XP Hotfixes and updates = Echo = ================================= Echo. Echo If you wish to exit, press Ctrl+C now. Echo. PAUSE net use v: \\server\hotfixes V: Echo. Installing Q123456 Hotfix Echo. Please Wait... start /wait q123456.exe /switches C: net use v: /delete Explanation: The first few lines are straightforward. Just telling the user whats going to happen. PAUSE This command makes the Press any key to continue... prompt appear. Simply a precaution incase you accadently double click the batch, or dont wish to continue for whatever reason. net use v: \\server\hotfixes this line maps a drive (in this case v:) to a shared folder on the server. (ie hotfixes directory, on the server named, funny enough "server") This mapped drive now acts like any normal drive on the local computer. you can make directorys, remove files etc on the servers directory, from your local computer if you wish (and if server permissions allow) v: switches to the V: From then on, its just a matter of executing each hotfix with the correct switches. Exactly the same as the batch file made for the CD. At the end you switch back to the C: and remove the mapped v: Just make the batch, whack it on a floppy, take it around to each of your computers and your away. If you are using a domain, let me know, ill explain how to login to the domain etc. Hope it helps!
  5. *shrugs* Strange
  6. According to my knowledge the $OEM$ directory must not be created inside the i386 directory, but along side it. ie. CDROM:\$OEM$\$1 ... etc. CDROM:\i386\ Not CDROM:\i386\$OEM$ but i could be wrong
  7. Don't listen to this man. He's nuts. :excited:
  8. Youd have to place the hotfixes in a directory on the server. Use the net use command to logon to the server then either copy all the batches to the local hard drive and delete them later, or run them directly from the server. Ill do a little research, and write out the commands more specifically. Just one question. Are you using a Domain ?
  9. *bump*
  10. why not just remove the root hotfix directory afterwards ?
  11. Thank AaronXP for this one. 23.
  12. Make more skins that we can choose from
  13. Your win2k3 CD should be bootable. Failing that, try and bootable XP CD. Once the initial setup loads, you should have your partitioning options.
  14. Its nothing you couldnt find on the installation guide
  15. Where is your $OEM$ folder placed on your CD?
  16. Does anyone out there in cyberspace have any good websites that contain good and useful tutorials on Flash or Photoshop?
  17. I dont think it does matter which order they are installed. Just as long as when you apply hotfixes certain programs (ie WMP9 for example) that WMP9 is installed first.
  18. Can i call you Mac-Daddy?
  19. Im not going to do all your researching for you, but i can point you in the right direction. This website will most probably contain all the tweaks your looking for. Click me All you need to do is locate the registry tweaks your looking for, throw them in a text file, save it as a .reg file, and silently merge it to the registry.
  20. You are getting an error because you are trying to run it off the CD. If you have the batch file in the GUIRUNONCE section of your winnt.sif file, make sure that the files in the $OEM$\$1 directory are being copied to the \install directory on %sytemdrive%. For example. If you have placed your batch file in $OEM$\$1\Install on your CD, they will automatically be copied to your %systemdrive%. Check that the paths in your winnt.sif file are consistant to that of your actual directory structure.
  21. Yes it is. Its located in \Windows\System32\wbem directory. How are you testing your CD? Perhaps something went wrong when encoding the ISO?
  22. Sounds to me like either your downloads of WMP9 and DX9.0b are incomplete, or you've got a dud (or incomplete ie. Beta) version of Windows.
  23. A more simple solution would be to place the patches on a server, and create a batch file to run on each of the client computers that installs the patches from the sever over the network. Thats the way i'd do it. If you need help with the batch file just ask.
  24. %systemdrive% = <drive where you installed windows> The batch files arent supposed to run until windows itself has been fully installed. If the error you are getting tells you that it cant find the file, it means there must be a typo there somewhere. Have you tried double clicking the batch file, and seeing if it runs correctly ?
×
×
  • Create New...