Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


  • Content count

  • Donations

  • Joined

  • Last visited

Community Reputation

0 Neutral

About WadeV1589

  1. Program Files Directory Problems

    Well I think that fixed it. For some reason the keys there were CommonFilesDir(x86) and ProgramFilesDir(x86)...see the tiny difference? Added 2 more keys with spaces in and so far all installations seem to be using the right directories. So thanks for that, one of those things I would've never ever noticed, a missing space!...The question is, how on earth did it happen on a fresh install? o.o
  2. I just cannot work out what on earth is going on but after a fresh install when I try and install things like Visual Studio, Adobe Acrobat or MSN Messenger they default to "C:\Windows\Program Files (x86)". What I don't get is a search in the registry for "Program Files (x86)" comes up blank, so does "C:\Windows\Program Files", as well as "%\Prog" (incase it's using a short name). The ProgramFiles and ProgramFiles(x86) set variables are both correct (pointing to D:\Prog...) and the registry values at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion are both correct. Of course other installation programs work fine and detect the correct folder but a lot are not and I am totally stumped where they're getting this Windows\Program Files (x86) directory from. Anyone got any idea's at all what could be causing this?
  3. event 4226 tcpip.sys

    Yeah I'm in need of this too now Luckily the uxtheme.dll patch was easy to find but I can't find this one anywhere yet!
  4. SATA Boot Order

    It doesn't seem to allow you to choose which is the first device...or the first device Windows XP setup see's.
  5. SATA Boot Order

    In the end I had to go into the BIOS and disable it...wasn't really happy about having to do that, there really needs to be an option to control the true boot order and drive order on this motherboard - Abit NF7-S 2.0 for those of you wondering which motherboard doesn't seem to let you.
  6. SATA Boot Order

    I have 2 hard drives, a 120g partitioned so the first partition is 4gb and is where I currently have XP installed, this is the SATA connected drive. The second drive is 40gb and is connected via the IDE cable. Last time I installed XP it wrote the boot record to the first partition on the 40gb drive and installed Windows onto the first partition of the SATA connected drive. I don't want this because I want to be able to remove the 40gb drive and my PC not fail to boot up because none of the boot information is on the C:...Windows is on the C: BTW but during setup it's detected as F:.
  7. I don't think this is for the drivers forum seen as it's more to do with XP setup and how it reads the drives but... Anyway so I've got it accepting my SI3112 fine and XP setup asks me to choose which drive to install to (hoorah!) however...my PC also has one hard drive that is connected via the older IDE cable. What I want to know is how can I get my PC to say "SATA is first"...right now I get my older drive being recognised first and as a result in setup it says C: is on that instead of being on the SATA connected drive.
  8. Well I got home today, ran Office Shrink and...it worked! Nothing had changed, I was even using exactly the same files that I had left on my hard drive from the time before. Go figure!
  9. I tried the original CD and the result was the same. I'll have to get you the logs when I get home and re-run it - Terminal Services + VMware is painful even on DSL!
  10. It keeps telling me shrinkage is already complete. I've followed the admin install point guide and created an mst file and this is being run in a clean xp install (on VMware). This is Office 2003 and all I want is Outlook. office.log
  11. I gave Aston a go and got nowhere, tried a manual install by copying over the aston directory and the registry files...it just loaded up borked.
  12. ZoneAlarm 4.5 Error

    I'm installing at the T-13 stage using a command line start /wait %CDROM%\SOFTWARE\Zonealarm\ZAPSETUP_45_594_000.EXE /s /noreboot That's it.
  13. ZoneAlarm 4.5 Error

    So just to clear this up I searched for Zonealarm, read every thread it was mentioned in and tried the command line options and sure enough it's silent but it refuses to install at T-13 saying "Could not find C:\Documents." or "Cannot find C:\Documents".
  14. I'm not insane right? This code could not possibly cause this problem could it? As you can see it sets up a non Windows piece of software and MSN Messenger and I'm getting the problem! Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\Software\Pathfinder] "AutoClose"=dword:00000000 "ExcludeBots"=dword:00000001 "IncludeEmptyServers"=dword:00000000 "Speed"=dword:00000004 [HKEY_CURRENT_USER\Software\Microsoft\MSNMessenger] "AppSettings"=hex:02,02,01,00 "DisableTabs"=hex:01,00,00,00 "InstalledMSNCertificate"=dword:00000000 "RTCTuned"=dword:00000001 "ShowCustomEmoticons"=hex:01,00,00,00 "TaskListState"=hex:03,00,00,00 "AlwaysOnTop"=hex:00,00,00,00 "CrossPromoRefreshLogon"=hex:01,00,00,00 "DSBkgndMode"=hex:01,00,00,00 "MobileFilter"=hex:01,00,00,00 "SharePassportCredentials"=hex:00,00,00,00 "ShowCustomEmoticons"=hex:01,00,00,00 "ShowEmoticons"=hex:01,00,00,00 It seems that the second I modify the HKCU stuff at T-13 it breaks something! I've had HKLM stuff going in before but added that in post-install and it failed then so I instantly got rid of that as a potential problem. I am totally lost now!
  15. Well I just did an install with the minimal HKCU changes and it still made it fail...so right now I'm going to apply totally inactive settings to HKCU and see if it causes it to fail, if it does I have a serious problem going on here!