Jump to content

Tripredacus

Supervisor
  • Posts

    13,112
  • Joined

  • Last visited

  • Days Won

    24
  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by Tripredacus

  1. Make sure your functions are cleared too! Some del keys are remapped if a certain function set is loaded.
  2. If only there was such thing as a "legally downloaded XP". Just wait for when Steam starts selling Windows.... won't that be scary?
  3. So your normal.dot file is getting corrupted everytime you use word. http://wordprocessing.about.com/od/trouble...ordregentry.htm
  4. Are your wireless hubs powered through the computer or connect to their own power source?
  5. Its not hard at all. Vista drivers work pretty much the same as XP drivers. I haven't had to do anything more than adding the Vista (Windows 6.0) support line and copy the DEV IDs into that section. Really??!! It's that easy? If that's the case I can throw a tool together... but only if someone pm's me detailed info and examples of how it is done. Does this method work for just about any drivers? Or just creative sound drivers? No you have to research the drivers. Some of them just put in registry entries, while other install programs and DLLs and other files. The number one problem you will run into with the latter type is whether those files will work in Vista or not. Here is an example of an INF that I changed to allow install into Vista. Taken from this original version, because Intel's drivers for the IME on certain boards didn't support Vista. ; File Name: HECI.inf ; Install information file for HECI Driver ; ; Generated by C DriverWizard 3.1.0 (Build 1722) ; Requires DDK Only ; File created on 6/20/2005 And I added these lines: [Intel.NTx86.6.0] ; DisplayName Section DeviceId %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_2974 %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_2984 %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_2994 %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_29A4 %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_29B4 %HECI_DeviceDesc%=HECI_DDI, PCI\VEN_8086&DEV_29C4
  6. You should try using OfficeReady to be in your Vista install. It is designed for that purpose. It gives you 60 days to use it or you can type in your key and your version will be set up.
  7. You set the default email client in Internet Options as well?
  8. Actually 195MB isn't that big at all.
  9. Its not hard at all. Vista drivers work pretty much the same as XP drivers. I haven't had to do anything more than adding the Vista (Windows 6.0) support line and copy the DEV IDs into that section.
  10. Are you using wireless internet? Specifically 802.11b? They use the same freq as your keyboard and mouse. That is my first idea.
  11. I don't get it... You can already do this with the PE Command Prompt...
  12. There are a bunch of errors when you try to validate it. I don't know how picky MS is about that. http://www.stg.brown.edu/service/xmlvalid/
  13. Yea the WAIK and the OPK are basically the same thing. The WAIK is for when you need to install Windows in a corporate environment, and the OPK is for when you need to install Windows on a computer that you are selling. The difference is all a licensing thing really. I was using the WAIK until VMux told me I should be using the OPK. Migrating to the OPK was seamless.
  14. http://www.msfn.org/board/Internet-Explorer-8-t113661.html
  15. Are you trying to installing through the website or with the exe? Also do you get an error?
  16. My original question was going to be "how big is your profile" but wasn't sure how roaming profiles work with RDP.
  17. No. You should only compress files that are not used often. The compression only gives you more available disk space. Compressing EXEs and DLLs (especially the Windows, Program Files or Documents and Settings folders) are not recommended and may lead to an unstable system.
  18. I noticed that on some boards, if you disable the AC97 in the BIOS it still sometimes show up in Windows but won't let you install it. I hate integrated sound!
  19. For your desktop's private NIC (the one to connect to your notebook) put the DNS info in there that is on the other NIC. You would probably have less problems if you just bought a router to use.
  20. My friend has a problem with his sidebar also. He runs a widescreen resolution (not sure which one but not 1280x1024 or 1600x1200) and if he loads up a game (typically running 1024x768 or 800x600) when he exits and can see the Desktop again, the Sidebar takes up half the screen! It was quite funny to see it do that.
  21. Wow am I glad I never told Intel I was writing Vista drivers for the IME on their boards that only have XP drivers...
  22. New Diskpart script (revised) select disk 0 clean create part pri size=62220 select part 1 active assign letter=c: format fs=ntfs quick create part ext size=14096 select part 0 create part log size=14096 select part 2 assign letter=d: format fs=fat32 quick exit Revised Cleanup script select disk 0 select part 1 attributes vol set hidden attributes vol set nodefaultdriveletter set id=12 I Was about to attempt a second time imaging but I somehow broke my WIM... looks like I am SOL for the moment. I will get to do more work on it next week when I can do a recapture again. Anyways, I found my ID changing cmd in another thread I made someplace on this forum: http://www.msfn.org/board/Imagex-question-t103807.html
  23. Alright I am manually testing this script and there appear to be some issues with it. 1. It won't let me assign the ID byte when creating the partition. I will instead set the partition ID during the cleanup phase by using 'attributes set id=0x12' instead. 2. When you create an extended partition, the default numbering for it is 0 (zero). 3. I cannot make part 0 active because it says it is not a data volume. HELP: I need to insert the following after creating the extended partition? create partition extended [offset=n] [noerr] I will try it out, or is it recommended to create the logical partition instead of the extended one? Also, obviously my cleanup script needs to be changed from selecting part 2 to part 0.
  24. Because we cannot use RE for XP recovery options, we use another method. This changes the drive ID to x12 instead of x07 so if we are to expect it to match previous computers we shipped out, we need to duplicate it as best as possible. We can already see the current ID with Ghost which shows the C drive to be 7 and the recovery partition to be 12.
×
×
  • Create New...