Apparently the MSDN one is a different size to the others. Who got it from MSDN and what size was the ISO?
Printable View
Apparently the MSDN one is a different size to the others. Who got it from MSDN and what size was the ISO?
3,387,009,024 bytes. That's directly from Microsoft.com.
I tried installing drivers for my wireless NIC card, but my Windows 7 install already has indexing errors and it won't let me install them. Time to reinstall the entire OS. Dammit. :mad:
By the way, how successful have people been installing x86 software/drivers?
I've been fine with installing. Chipset and graphics drivers are available through Windows Update or built in. The rest, just grab the Vista x__ version of it and install in compatibility mode. I've done that twice now; the first time for my sound drivers and the second time for my LAN drivers.
What's with the Program Files (x86) folder then? That's where it tried installing the XP software for my wireless NIC card. Is that not for 32-bit application compatibility, as the folder would suggest? :shrug:
Yes it's designed for the 32 bit applications, which is the vast majority.
Microsoft wanted to keep the 32 and 64 bit applications in a different folder, for whatever reason. But AFAIK, it makes no difference if you put a 64bit program in the 32bit folder or the reverse. One reason is does exist could be if there are two versions of the same program, one 32 the other 64bit.
as anyone tried this on virtual box yet.
Nope, the driver is x86. I never used Vista, so I'm new to all of this. Looks like an x64 driver is important, though. Unfortunately, Linksys never released an x64 driver for this wireless card. :shakes:
EDIT: So it looks like Linksys did manage to get a rare Vista driver out for my card; however, it is 32-bit. Does that sound right?
yes most companies make 32 bit stuff and never make 64 bit which I find very stupid. You will find out most stuff goes into the 32 bit program mainly because of the companies NOT MICROSOFT who would of guessed. This is why Vista is a good OS and everyone blames it to be crappy because companies are not making stuff to work with it.
X:\Program Files (x86), X:\Windows\SysWOW64, HKLM\Software\WoW6432Node are designed for 32bit components using WoW64
X:\Program Files, X:\Windows\System32, HKLM\Software are designed for 64bit native
not quite.
program files x86 are for 32
program files are for 64
system32 for 32
sysWOW64 are for 64.
yea works good as vmware client.
I have the same problem with a Netgear wireless adapter here, they do have a 32-bit driver but no 64-bit driver and it sure sucks. Windows Update did find a driver for it after a while, but that driver is not directly from Netgear (I think it's from Atheros or something) and is not completely stable. I can't use normal sleep/standby mode (S3 mode) with it and my connection will drop after a couple of hours. So I have no use for that adapter at the moment and just use another one instead. I'm talking about my Vista 64-bit install right now though. I only installed the Windows 7 32-bit beta so far and with that one I have no problems whatsoever (yet :p:).
BTW, I heard reports that the Firefox 3.1 Beta (2) supported the new preview style that Windows 7 has, but for me it doesn't. Is it not enabled by default, or is it still in the works? Also, does anyone know if you can adjust the delay there is between hovering over a taskbar icon with your mouse and the preview window showing up? I think that delay is to long and I'd like to adjust it, maybe I should search through the registry a bit and see what I can find. Although I doubt I'll be able to find something over there.
Dose any one have problem with divx-avi files?
Not quite indeed ;)
WoW64 = Windows On Windows 64bit.
SysWOW64 is redirected to System32 when WindowsOnWindows64 32bit emulation environment is being used, ie 32bit native app. And holds all 32bit native drivers/dlls/apps.
System32 is always 64bit native.
Tell you what if you want to see it for yourself, run x:\windows\system32\cmd.exe, then check task manager process for it and it will be native 64bit, then run x:\windows\syswow64\cmd.exe, check task manager and you will see a "*32" next to process. That means its running under WoW64 32bit emulation
;)
HEres an MSDN article if you are interested in learning.
http://msdn.microsoft.com/en-us/magazine/cc300794.aspx
mikeyakame kewl :) i'll check that later on . 10x
hehe cool no worries ;)
I've become accustomed to the design as when developing / compiling you need to get your head around it so as not try and compile 32bit app in a 64bit dev shell and make it either unusable for 32bit windows or get errors.
Also note that native 32-bit installers ie. NSIS which Firefox/Thunderbird x64 builds use, will install into Program Files (x86) because thats where the environment variable for 32bit app points to. Until NSIS is rewritten for 64bit native that problem will be there.
yea i have the same issues when running 32bit ms.net app on 64bit iis.
That doesn't seem to fully work for me though. I have FF 3.1b2 32-bit installed on my Windows 7 install and the taskbar thumbnail previews don't work in the same fashion as for IE8. I heard they did, but I guess its not yet implemented and is still 'on the drawing board' so to speak.
Does anyone know where I should install my 32-bit Vista driver for my wireless card? The .inf file won't do a right-click install, device manager won't take the .inf file - even though it's asking for a .inf file - and I can't connect to the internet via the standard network port on my mobo to let Windows Update install a driver. Also, none of the pre-installed network drivers work.
Is there any folder I can drop the .sys file into? The package comes with the .inf and .sys file.
Are you using x86 or x64 though?
x64 Windows 7. So there is absolutely zero compatibility for 32-bit Vista drivers and 64-bit Windows 7, but 32-bit applications will work fine?