OI v9.4 - ARev32 - Win10 Pro

Any idea why DIRECT_PRINT to file from AREV32 would stop working? The file gets created but is zero bytes.

If I login to a different user on the same workstation it works. Both users are in Admin.

I haven't checked it yet but probably OSBWRITE/OSWRITE is failing as well.

Hi Warren,

I'm strickly an AREV32 user (expert!), so not used "DIRECT_PRINT". I always open a "DOS" file using the PDISK command followed by the path and filename. Then do printing process. When completed, must close the print file by issuing another PDISK command, reassigning to PRN (printer) device, as:

PDISK PRN

Before you issue the "close" PDISK command, the file in DOS will show as zero bytes.

Hope this helps.

Robert.

Hi Robert

The application has been working for years with no problem. I've run across this print to file problem on Windows 10 workstation at home.

None of the print to file options work for this user (windows) login.

PDISK, DIRECT_PRINT, or OSWRITE/OSBWRITE.

Yet if I login as another user on the workstation and run any of process that uses any of the above it works.

Application also works fine on Windows 7 workstations.

Another symptom of when this stops working on an Windows 10 workstation is the ARev32 window doesn't save the any resizing and always starts in the default size.

Windows Server 2019, UD 4.7.2, OI 9.4

Hi Warren,

Oh, sounds like a Windows User "rights" issue. Are you able to see and compare the settings of the User Profiles (the working one vs the non-working one)? I think this would be your best lead.

Robert.

Where is the settings for the ARev32 window size, and OI debugger windows saved? In earlier versions of OI they were saved in an INI file as I recall in the Windows directory. Making sure the user had the proper permissions to the INI file used to solve problems like this.

Basically if I know which folders to look at I can compare permissions.

I just wonder why it stopped working a week or so ago. The only Windows or software updates I can see were applied 12/17/22 and I should think these would affect all users on the same workstation.

For now I'll have the user login on my user name and hide all the developer shortcuts to run the reports and exports.

FYI:

Login as USER

TCL:

pdisk c:\temp\test.txt (so

list 10 voc (p

pdisk prn (so

test.txt 0 bytes

Login as Warren

repeat above

test.txt 1 byte

edit test.txt shows the typical output.

I need to get a handle on this in case it happens on other Win10 workstations. The client generates numerous text exports throughout the day which get uploaded to some of their financial institutions.

Hi Warren,

Sorry, but using a "work" laptop, I do not have any "Administrator" access to hunt around.

Use the adage: "What's changed?"

If it was working before, something has changed. Who has Admin rights on those laptops/networks? New laptop? Windows upgrade?

What's the same? What's different?

Microsoft have a nasty habit of making changes that appear to be minor but can have big effects.

Hopefully you can find the issue, or someone can jump in here to lend you a hand.

Robert.

Hi Warren,

I am running into a similar problem and I was wondering if you were able to resolve this issue, and if so, how?

Post removed by author

View this thread on the forum...