A Print to Screen issue on Win98SE client

[logicskr]

We recently upgraded to PSQL 8.5/Macola 7.6.300b. A few glitches in the upgrade, but stable at this point. I do have one issue on a Win98SE client when he prints a Purchase Schedule Report (or any report) to screen. It occurs only on this single computer regardless of the Macola user account used and does not occur with this user account on any other machine. The output is correct, but the report is viewed from a narrow, maybe 1/2 page window that requires scrolling to view the entire document.

I have tried altering the Macola7.ini file, but this makes no difference. I have uninstalled and reinstalled his printer although I wouldn't think it would effect a Print to Screen.

I do believe there are a couple scrXXX.tmp files that I could delete, but again, there are only a few so can't see they would be the problem.

Any suggestions? This is not a show stopper, but is annoying.

Thanks

 

[keain]

Had this one time on a windows XP workstation. I deleted the Macola7.ini, c:\program files\common files\macola shared and Macola registry entries under HKLM\Software and reinstalled the client. That resolved the error that time.

A second time, on a Windows 2000 workstation, I had to update the video drivers to resolve this.

 

[logicskr]

Oh, that's interesting. I could try both suggestions on this Win98SE machine. It'll probably have to wait till Tues. but I will post the results.

Thanks

 

[logicskr]

Only had a chance to update video drivers which changed nothing. I'll give the reinstall of the client a go. There's a Pervasive Client and a Macola Client. Which are you referring to, or is the Macola Client a part of the Pervasive Client?

Thanks

 

[keain]

I mean the Macola client.

 

[logicskr]

Today I uninstalled the client, deleted the Macola7.ini file, the Macola Shared folder, and the Macola key in the registry. Still have the same issue printing to screen. Any other ideas?

 

[kscheeler]

Is it printing the report to screen in the same font as the other computers that work?

Kevin Scheeler

 

[logicskr]

I've tried a variety of different fonts, changing to the same font as a machine that does work correctly, but it doesn't seem to make a difference.

 

[MacolaHelp]

YOu may need to actually copy the font files from a working machine to the non-working machine. Also, you must delete the printer default, report passing & deferred report files, then reselect the printer the next time you initially run the job. Lots of docs with printing problems 7.6.200 & above in infomine.

The geek squad guys were on mpr the other day & they highly recommended a fresh install of xp on a problem machine like yours if it met the xp hardware requirements. Other than that, just spend 2 few hundred on a replacement cpu & be done with it. Win98 was more trouble than it was worth, even when it was the OS of choice, IMHO.

I've also seen print to screen issues if the local user didn't have enough rights to the windows directory, but more so with xp than win98.

 

[logicskr]

I appreciate your input, thank you. I have seen plenty of printing problems in Macola, but this one was not an issue until the upgrade to 7.6.300b and the 8.5 engine. I have yet to see any benefits of the upgrade. The other routine issue we now experience is a message box when attempting to close a module that says it cannot close as there is a window open. Task Manager shows no window open, no indication on the task bar, no trace of an open window. It requires ending the task via Task Manager numerous times before it finally closes. Then Macola has to be restarted. Is this typical of 7.6.300b and is there a remedy for it. It is truly annoying.

Thanks

 

[keain]

Sorry to hear that those two things didn't work, but I haven't seen this issue on a 98 before.

What version did you upgrade from? If it was prior 7.6.200, then there were major printer engine changes, as well as numerous other core changes that prove how obsolete windows 98 is getting.

As for the open windows, look for macexe.exe or vbmacexe.exe in the processes tab. One of those sticking open is what's causing that message. Typically, that's a bug and should be addressed by support. They'll need to know what process it is, and what you're doing when it gets stuck open.