One of my customers is trying to certify our OI 16-bit application on their WinXP desktop. It will still access their current NT server eventually, but they need to QA the app on a local disk. After copying \REVSOFT and \OIDATA (our data files location) directories to the C: drive of a local machine and removing the REVPARAM files in ALL directories, they receive a message to the effect that OENGINE.EXE is not a 32-bit application and the app terminates. My recollection is that they should apply the compatibility features to the shortcut and select WIN98 or WIN2000 as the OS. Is that correct or are there any other solutions?

TIA

Don Miller

C3 Inc.

Don,

Memory is a little faint in this area but I believe there are two possible solutions:

1. Running the client install to make sure all the appropriate DLL's, etc., are in place.

2. Changing a registry setting to permit 16-bit applications to run.

[email protected]

SRP Computer Solutions, Inc.

Would you have a clue what the registry hack might be??

I'll check Microsoft too .. but this might be quicker.

Don M.

Microsoft has introduced a 64-bit version of Windows XP

http://www.microsoft.com/windowsxp/64bit/overview.asp

OI 16 won't run there, nor will AREV nor will a lot of other things. Another fly in the ointment.

Don M

C3 Inc.

Don,

Most Windows-compatible 32-bit applications will run ?as is? in a subsystem of Windows XP 64-Bit Edition.

Great. Just when we get OI into 32-bit we get NTVDMs all over again! ;^)

BTW, is the WinXP problem you are having related to this?

[email protected]

SRP Computer Solutions, Inc.

Don,

Get them to diable visual themes on the shortcut. The problem tends to be with the default XP visual theme (nice rounded corners to the dialog boxes etc) doesn fit well with 16bit apps.

As a bonus they can run in separate memory space (again setting in short cut) and if the app crashes doesnt effect anything else - close the app and re-launch.

I have been running OI16 on XP for ever-since XP and been fine. Do NOT have to set any compatability (other than turn off themes). Some people never notice this issue because the desk top is globally set to the Win2000 classic theme.

BTW… look forwar to meeting you guys later in week.

Richard Bright

BrightIdeas New Zealand

I've run OI16 on XP for some time too but never had any problem with the XP "theme". Except of course the problem with the client area getting smaller so controls at the bottom sit half outside the window. Have I just been lucky?

- Oystein -

PS. I hate the rounded look but have kept it to be compatible with clients who like it.

Probably ..

My customer pretends to be technologically brilliant .. rather like brillo pads. Doesn't give me much of a clue about what they're trying to do and haven't been available for contact for 3 days or so. Basically .. unless they upgrade to OI32 (which for them costs money .. which they are most reluctant to spend), they're up a creek .. I suggest that they keep some ordinary XP / Win2K machines around.

Don M.

Richard, like you, we have been running on XP just fine (didn't know about the themes stuff, but maybe we're just lucky). My suspicion is that some techi-guru is playing with XP-64 .. more than likely. Thanks for the comments, though .. as usual.

Don Miller

C3 Inc.

We've all been running XP, some with themses,some without, and all OI 3.x versions work fine. OI 2.x, on the other hand, crashes and burns faster than…well…it doesn't work.

The Sprezzatura Group

World Leaders in all things RevSoft

]]My customer pretends to be technologically brilliant

I presume your saying this means that you are certain that they would never read the threads on this forum!

David

David .. I really don't care if they do. Consider, for example:

They have a joint research project with a medical school for cataloging and analyzing patient outcome information. To facilitate this, they have a "hot" T1 connection between the hospital and the members of the project. The Computer Science folks at the Med School are busily trying to destroy the hospital's billing information by downloading sniffer viruses that propigate across their network. Rather than spend the dollars for a firewall, they have a staff of 20 drones that go around fixing the damage. They won't even keep their Norton Anti Virus subscription(s) up to date. Since the research project doesn't require live patient information anyway, I suggested that they move the project off to an isolated server that has no connection to any other systems. But .. that would disturb their conferencing and e-mail system. So, rather than spend $10,000 (+/-) to fix the problem, they are spending over $10,000 per DAY!!!

Meanwhile, they are charging ahead with no thought to XP-64 without giving a thought to whatever applications they are currently running .. including some legacy DOS applications which I'm sure will stop.

Go figger!!!

Don

View this thread on the forum...