64bit compatility issues

[bX510]

I have a windows vista ultimate 64bit, and I need to use some software that is not 64bit compatible. Is there anyway to by pass this:? can I install xp as 32 bit or something?

 

[snor]

There's a couple things you can do. You reintall your OS as windows xp 32-bit/ dual boot it.
or you can run a virtual machine with windows xp as a guest. Since you are using 64 bit, I assume you have plenty of memory for VM use.

 

[Zstream]

If the application is not 64bit compatible it will run in 32bit mode.

 

[cdnbum88]

I have had issues with a couple of 32 bit programs like my Pareto RegCure and Xsoft. They did not work and don't have a 64 bit version, so I am out of luck.

So, I think in some cases the 32 bit programs don't run in 64 bit mode.

 

[BonzaiDuck]

Originally posted by: cdnbum88
I have had issues with a couple of 32 bit programs like my Pareto RegCure and Xsoft. They did not work and don't have a 64 bit version, so I am out of luck.

So, I think in some cases the 32 bit programs don't run in 64 bit mode.

I'm jumping into the VISTA 64 pool cautiously, just getting my feet wet. I installed it on a different machine -- because I had the parts. I've used dual-boot approaches before, without serious trouble actually, but I didn't want to complicate things on a system I use daily. And since we are going through a constant upgrade in this house, it's all "part of the plan."

So far, I've had trouble with insignificant things, like PrimoPDF freeware version. That's really OK, because I expect MS Office Pro to run perfectly on the VISTA system, and MS offers a plug-in for that feature.

So far, a couple of games seem to work fine. I know I will encounter more troubles as I seek to install older software. And I can defer buying newer software, because I have other machines networked here.

 

[Zstream]

Hmm, you ran them in compatibility mode as well?

 

[Avalon]

BX510...if your 32bit programs won't run under Vista64, try enabling compatibility mode for XP 32bit on them. If that doesn't work, I'm not sure. I haven't come across a 32bit program that didn't run.

16bit on the other hand...not supported. I installed Windows 2000 in VMware to run the couple 16bit apps I had. Works nicely.

Bonzaiduck...most games that I know of work in Vista64. I've even been playing Lords of the Realm 2 (when did that come out, 1996?) without having to change a thing. You shouldn't have much trouble, unless the game has a 16bit installer like HOMM2 and the original C&C + Red Alert.

 

[bX510]

I am trying to run Dragon Naturally speaking.

 

[BonzaiDuck]

Originally posted by: Zstream
Hmm, you ran them in compatibility mode as well?

If you mean the games, etc. from my post -- no -- I just installed them.

Originally posted by: Avalon
BX510...if your 32bit programs won't run under Vista64, try enabling compatibility mode for XP 32bit on them. If that doesn't work, I'm not sure. I haven't come across a 32bit program that didn't run.

16bit on the other hand...not supported. I installed Windows 2000 in VMware to run the couple 16bit apps I had. Works nicely.

Bonzaiduck...most games that I know of work in Vista64. I've even been playing Lords of the Realm 2 (when did that come out, 1996?) without having to change a thing. You shouldn't have much trouble, unless the game has a 16bit installer like HOMM2 and the original C&C + Red Alert.

I really don't expect a lot of trouble. I've had this up and running for about 4 weeks now -- just discovered "Flip 3D." It's a pretty zippy OS, if you ask me. Chances are, if I have trouble with some piece of software, it will most likely be an older license and I will make decisions about upgrading. Anyway, this isn't my "only computer" -- I've got three downstairs on a (10-year-old, no less!) Belkin 4-port KVM switch, and "my old moms" has two upstairs. I access her systems through Remote Desktop. I distribute my software between a Win2KPro, an XP-Pro and this here VISTA-64.

If you jumped on the technology in 1982, there's no effective methadone treatment for it. So far, I can even manage the utilities bill . . . .

 

[Dadofamunky]

I've had some trouble overall, but most well-written 32-bit software (like Adobe and Microsoft suites) works fine. What's most important is to make sure your basic utilities (AV, backup, etc) are 64-bit. Avast! has an excellent 64-bit AV program. I don't think Symantec does, but I won't put Symantec anything on my computers anyway.

 

[aka1nas]

Originally posted by: cdnbum88
I have had issues with a couple of 32 bit programs like my Pareto RegCure and Xsoft. They did not work and don't have a 64 bit version, so I am out of luck.

So, I think in some cases the 32 bit programs don't run in 64 bit mode.

That doesn't have anything to do with running the app in "64-bit mode", you're trying to run a 32-bit registry cleaner program on an OS that doesn't have a 32-bit registry to clean.

 

[bharatwaja]

Originally posted by: Dadofamunky
I've had some trouble overall, but most well-written 32-bit software (like Adobe and Microsoft suites) works fine. What's most important is to make sure your basic utilities (AV, backup, etc) are 64-bit. Avast! has an excellent 64-bit AV program. I don't think Symantec does, but I won't put Symantec anything on my computers anyway.

I am using BitDefender 2008.... there wasn't a 64-bit version of it while I started using Vista Ultimate x64, so I used the x86 version of bitDefender itself.... Had no problems with it whatsoever.... So far I am yet to encounter a 32-bit app that won't run on vista x64...

95% of my system crashes (BSODs) are due to nVidiot's drivers... I wanna shoot myself for getting NVidia.... the remaining BSODs are due to intel's "iastor.sys" or the Matrix storage manager.... and only once courtesy my OC:beer:....... been using Vista x64 for more than a year now.... no problems with 32-bit compatibility to date.....

Now, if everyone started programming for 64 bit n dump 32 bit, it wud be great.... (32-bit OSes n apps, don't have much of a life left do they?)

 

[Idontcare]

Originally posted by: bharatwaja
.... the remaining BSODs are due to intel's "iastor.sys" or the Matrix storage manager.... and only once courtesy my OC

bharatwaja I recently started dealing with this issue, ony in my case I'm in 32bit XP Pro.

I am not overclocking the system that this issue (and wasn't overclocking it prior to the issue becoming an issue either).

It's been driving me nuts lately. Do you know any more about this? I would love to resolve the problem, whether it is to replace my hard-drive or mobo or replace some corrupted driver, etc. Right now I am operating in the dark while I try to debug my problem but the only feedback (naturally) is BSOD which means lost files and corrupt files over time.

 

[bharatwaja]

@ Idontcare:
Well... I think it has something to do with Intel's Matrix Storage manager which is required if you are using the Hard drives in AHCI or SATA mode on ICH9R...

What is your mobo?

My situation is like this....
I was using my Hard drives in IDE mode till august... Then I had to reformat my OS drive, so I decided to go with AHCI mode in BIOS.... Till August I never had any problems... For AHCI mode to work, i need the Intel Matrix Storage manager application which installs the required drivers.... Now for the past 45 days I've been getting this problem.... I've got it only 2 to 3 times so far and it happens usually when my hard disk is having constant but minimal activity, mainly when downloading... I start downloads at night, and twice I woke up to check up on them, and found windows rebooted... On logging in, the faithful vista error diagnostics informed me of the error code and reported it as a problem with IaStor.sys file....

Here's another thing to consider, Vista has its own AHCI drivers... You just have to enable it from the registry.... Around mid-July I first switched to AHCI mode, by using vista's own AHCI drivers... just enabled it in the registry and rebooted, changed the BIOS to AHCI for HDD and it was all just fine.... I reformatted my HDD for some partition purposes and it isnt like VISTA crashed on me or something....

So AFAIK, this seems to be a problem with Intel's drivers.... And then recently MS released an error report or something which detailed the major causes of vista crashes, I suppose you'd have heard... That also indicated that Intel's drivers were a cause of 17% of crashes, although I cant say whether it referred to intel's IGP drivers or this or any other drivers....

Some questions for you,
How long have you been having this issue?
did you recently switch to AHCI or SATA mode?
If you had been on IDE mode previously, was it causing any troubles?
Another thing to consider, if you have always been using the HDD in AHCI or SATA mode, did u recently update your Intel Drivers? May be this issue had been introduced in the recent version Matrix storage manager.....could it be so?
Are you using a Western Digital drive? If so which drive? I suspect there could also be an issue with the controller perhaps Specific to Western Digital? Cause some of my friends too have this issue....

 

[Acanthus]

Originally posted by: cdnbum88
I have had issues with a couple of 32 bit programs like my Pareto RegCure and Xsoft. They did not work and don't have a 64 bit version, so I am out of luck.

So, I think in some cases the 32 bit programs don't run in 64 bit mode.

Regcure wont work because 64 bit vistas registry is fundamentally different.

Thats actually not because of application problems, it simply cant alter the 64 bit versions registry because its not updated to do so.

 

[Acanthus]

Originally posted by: Idontcare

Originally posted by: bharatwaja
.... the remaining BSODs are due to intel's "iastor.sys" or the Matrix storage manager.... and only once courtesy my OC

bharatwaja I recently started dealing with this issue, ony in my case I'm in 32bit XP Pro.

I am not overclocking the system that this issue (and wasn't overclocking it prior to the issue becoming an issue either).

It's been driving me nuts lately. Do you know any more about this? I would love to resolve the problem, whether it is to replace my hard-drive or mobo or replace some corrupted driver, etc. Right now I am operating in the dark while I try to debug my problem but the only feedback (naturally) is BSOD which means lost files and corrupt files over time.

This issue seems very odd to me as i know people that have it, but i dont personally.

Are you using software raid? Which ICH version does your mobo sport?

Im having a hell of a time finding a pattern in the issues as it seems to cross platforms and operating systems.

 

[bharatwaja]

Originally posted by: Acanthus
Im having a hell of a time finding a pattern in the issues as it seems to cross platforms and operating systems.

Exactly.... its is very hard to source this problem.... Almost certainly seems to be a problem with Intel's drivers.... but in a more fundamental level, with the controller perhaps?

 

[Idontcare]

My situation is one of those cases where I haven't touched the hardware or software end things since Jan of this year. I've got raptors in raid, all setup thru F6 proper-like on the XP install. Worked beautifully until about a month ago (roughly, can't recall when it specifically started).

Only thing I updated until then was just Windows updates, SP3, etc, whatever the updates took care of.

I first realized the source of the problem after I forced a reboot (hardlock, had to use the physical reset button) and after reboot XP popped up a window and said my iastore device was the culprit and took me to the Intel download site for new drivers. (which did not help the problem)

I did some more research this morning and there are tons of google links regarding this issue. There was one link that discussed the LPM (power savings mode) as the culprit and recommended a registry edit hack to get around it in XP. I just tried the hack and so far no issues. Oddly enough my system is acting like it is 2x as snappy as before I did the hack too. Keeping my fingers crossed.

 

[Acanthus]

Originally posted by: Idontcare
My situation is one of those cases where I haven't touched the hardware or software end things since Jan of this year. I've got raptors in raid, all setup thru F6 proper-like on the XP install. Worked beautifully until about a month ago (roughly, can't recall when it specifically started).

Only thing I updated until then was just Windows updates, SP3, etc, whatever the updates took care of.

I first realized the source of the problem after I forced a reboot (hardlock, had to use the physical reset button) and after reboot XP popped up a window and said my iastore device was the culprit and took me to the Intel download site for new drivers. (which did not help the problem)

I did some more research this morning and there are tons of google links regarding this issue. There was one link that discussed the LPM (power savings mode) as the culprit and recommended a registry edit hack to get around it in XP. I just tried the hack and so far no issues. Oddly enough my system is acting like it is 2x as snappy as before I did the hack too. Keeping my fingers crossed.

That certianly would be an odd solution.

The north and south bridge dont change voltages while idle do they?

I dont use any power saving features, cpu or mobo... that may be the difference in our setups. No EIST or Speedstep-like features enabled. I also use the "performance" setting in vistas power saving settings.

 

[VirtualLarry]

Originally posted by: Idontcare
There was one link that discussed the LPM (power savings mode) as the culprit and recommended a registry edit hack to get around it in XP. I just tried the hack and so far no issues. Oddly enough my system is acting like it is 2x as snappy as before I did the hack too. Keeping my fingers crossed.

Have that link handy?

 

[bharatwaja]

Originally posted by: Idontcare
There was one link that discussed the LPM (power savings mode) as the culprit and recommended a registry edit hack to get around it in XP. I just tried the hack and so far no issues. Oddly enough my system is acting like it is 2x as snappy as before I did the hack too. Keeping my fingers crossed.

This hack you mention, is there some solution for Vista x64 too? I link to that hack would be great....

But the thing is, I dont have power savings feature enabled on my system either, I dont see how they could affect this, like Acanthus asked, do the north and south bridge voltages changes when idling? But, even then, how it cause such a problem?

 

[Idontcare]

So my specific error logged in event viewer is this:

The device, \Device\Ide\iaStor0, did not respond within the timeout period.

Doing a google search for this entire text string resulted a couple hundred hits, no idea if they are all relevant.

The first link contains a link that leads to this Intel website documenting the issue:

A change was made by Microsoft* in the Windows Vista setup process. The result of this change is that the Intel® Matrix Storage Manager Link Power Management (LPM) registry settings that were intended for mobile installations are added for desktop installations as well. These LPM registry settings are added for both the Intel® Matrix Storage Manager RAID driver on the Windows Vista installation disk, as well as for any drivers added during the installation process.

Various desktop Serial ATA devices such as hard drives and CD/DVD drives have been reported that do not comply with the Serial ATA LPM device specification and display erratic behavior when LPM is enabled.

Because the setup change means that LPM is enabled by default for all Windows Vista platforms, using a device that does not completely follow the specification may result in one of the listed issues.

http://www.intel.com/support/c.../imsm/sb/cs-025783.htm

The Intel solution is to update your Matrix software.

Now this says it is only a Vista issue, and I am not using Vista but I updated my software (XP version of course) just in case. Still had the problem afterwards.

So I dug thru more links, and one of them had a link that led to a link that suggested you force your registry to ignore the LPM situation altogether: (and this deals with XP2 SP2, so while possibly same issue as Vista, was more relevant to my situation)

I installed the latest drivers from Intel in an attempt to resolve this issue with no luck. I am pretty sure that I solved the issue on my two computers by renaming this registry key:

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters]

to

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\iaStor\Parameters.Bad]

Then reboot and see if that fixes your problem. Good Luck!

http://www.paulscomputerservic...os/intelSataError9.php

This is the "hack" I implemented. Only I did a global search for all iaStor\Parameters and renamed them (after review on case-by-case basis) to iaStor\Parameters.Bad.

I have not had my system hardlock since, and it seems quite a bit zippier.

Sadly I just opened event viewer and noticed I have in fact had another timeout event. So the hack did not appear to fix the problem. The good news though is that my system did not lock from the timeout, it did recover and kept going which it never did before. So the registry edit must be worth something.

I must say this whole affair has decreased my perception of Intel chipset stability...what worked 8 months ago should not be broken now unless hardware is dying and all the hardware level diagnostics I am running are not flagging anything. (nor did it for the vast number of people I am reading on the web who tangled with this situation in the past 2 years)

 

[bharatwaja]

But using the Vista AHCI drivers instead of the Intel Drivers seems just fine to me, as This problem does not recur when I switch to AHCI drivers in Vista itself.... Been using that for a fortnight now, no errors to date......

Doesn't this imply that there is something wrong with the Intel Matrix storage manager drivers specifically?

**EDIT**
I am using the Latest updated version Matrix storage manager like intel suggests....

 

[Idontcare]

Originally posted by: bharatwaja
Doesn't this imply that there is something wrong with the Intel Matrix storage manager drivers specifically?

It would appear so. I had hoped the integrated graphics team wasn't allowed to co-mingle with the ICH team but I guess you can't keep them from fraternizing after hours.

 

[Denithor]

Originally posted by: Idontcare

Originally posted by: bharatwaja
Doesn't this imply that there is something wrong with the Intel Matrix storage manager drivers specifically?

It would appear so. I had hoped the integrated graphics team wasn't allowed to co-mingle with the ICH team but I guess you can't keep them from fraternizing after hours.

:laugh: