Eprivilege error on Win 2000

[RZillmer]

I am using Borland Builder 3 on a Win95 system to develop some applications. I can compile and make the project just fine. When I move the exe to the network and try running it from a Win2000 machine, I simply get an error message that says eprivilege. I checked the help files and it talks about some processor access violation, but doesn't say much more on it. Does anyone know how I can solve this problem? Thanks in advance.

 

[RZillmer]

Here is some more information I have uncovered about the error.

I have figured out that my outportb and inportb statements are causing the error. What is odd is that I have another app much like this one (made about six months earlier) that uses the exact same functions on the exact same Win2000 system with no problems. The only thing I can think of is that I'm compiling with some settings different than the older apps.

 

[2ffat]

The inport and outport won't work with NT based OS's. See

http://www.bcbdev.com/faqs/faq30.htm

for more info. James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that I am now qualified
to do anything with nothing.

 

[RZillmer]

Thank you for linking me to that faq. I had already figured out what I had to do (use a driver), but knowing WHY I have to do it will work wonders towards recovering my sanity.

I have one more question now. The project I am working on is upgrading numerous small programs from DOS to a windows environment...and also making them Win2000 compatible. Anyway, some had already been completed before I inherited the project. These programs DID use inportb and outportb and DO work on Win2000. Is it possible to change the bitmap field contained in a program to allow port access to the needed addresses? For example, I have an exe from one of these programs that works on Win2000, but when I compile a new exe from the source code, it does not work. The FAQ mentions that Win95 will just change the bitmap field if an exception occurs. Would running the exe on Win95 before taking it to Win2000 be a quick and dirty way around the problem?

Sorry if my questions are dumb; this is my first time dealing with programming for NT-based OSes.

 

[2ffat]

Would running the exe on Win95 before taking it to Win2000 be a quick and dirty way around the problem?

To be honest, I don't know if that would work or not. I also don't know if compiling it on Win95 then taking it over to NT will work or not either. It wouldn't hurt to try, though. James P. Cottingham

I am the Unknown lead by the Unknowing.
I have done so much with so little
for so long that I am now qualified
to do anything with nothing.