PDox 10 vs 11, 12, x3 Printing

Is there something that went horribly wrong with printing to printers with multiple paper trays between these versions?  Expecially in the Ricoh/Savin line of business printers?

Scott:

I haven't found or heard of a good solution yet, but I'm curioius, are you saying that you do not get the expt-error when exiting Paradox 10?

I linked my Can you install Paradox 10/11 on vista article to the top of this thread. That's where I'm documenting my ideas and experiments and eventually a complete solution.

Hi Scott:

I corrected a minor issue in your code above, you forgot the "[]" in your DynArray declaration.

I'm not sure why it didn't work for you with Vista, but the kill Task Scheduler has worked very consistently for me on Vista but I still don't like killing a critical process. Also, the problem with killing Task Scheduler is that multiple copies are launched. Some say that Task Scheduler restarts automatically and immediately so it's not an issue. I'm not sure, but I don't think that's correct because when I kill Task Scheduler, I can start and exit Paradox many times and I never see this error again until I reboot. I do see taskmgr.exe in the Task Manager so it is running but I think for other Task Scheduler events.

Several developers have contacted me and said they are having luck killing the Paradox process itself. I like this better but it's still an incomplete and odd work-around but it is something I can get behind so I did add it to my Can I Install Paradox 10/11 on Vista article. One problem I have with it is that it kills all instances of pdxwin32.exe and not just the current one. I frequently develop in multiple instances of Paradox and The Exit features of my Workbench for Paradox product helps with this issue. I just have to remember to use it to exit Paradox applications I'm working on!

The only thing you need to change in your code above is the process you're killing. Change it to pdxwin32.exe.

Here's a complete example.

method pushButton(var eventInfo Event)
Var
 dynSysInfo  dynarray[] String
 sWinVer   string
Endvar

sysinfo(dynSysInfo)   
;dynSysInfo.view()

sWinVer=dynSysInfo["WindowsVersion"]
sWinVer=sWinVer.substr(1,1)      
;sWinVer.view()

if sWinVer="6" then  ;Vista
  Execute("TaskKill.exe /F /IM pdxwin32.exe", No, ExeHidden)
endif
endMethod

Quote:

Originally Posted by tekmisia

As far as it not working, I need to look at it further. I was probably working with it after lunch and suffering from food coma.  heh

Hey, we all suffer from that! Seriously, I always have to test things several times. Even when I do, I sometimes get it wrong!  So, no biggie.

I see alot of "miss-information" out there so I tend to double check everything. We are all just trying to get good quality information out and "truth" is often very allusive. Watch out for half-truths! And, if you see anything incorrect on here, let me know! I'll be happy to double check and/or clarify.

Version 11 is the only version above 10. 

And even it is merely a service pack that Corel (WiPro?) messed up and threw the switch when compiling, winding up with a new version #. 

What are you seeing, and what do you think you should be seeing? 

Well,  our application has been around for 14 years.  It has travelled from ver 8 to current.  All of our clients with Printers that have accessory paper trays (more then standard) have trouble when choosing print trays. Version 10  and previous did not have this problem. I am rolling one client back this week to resolve this problem.

I gave up on Paradox 11+.  I now roll out all new clients with Pdox 10.  Cant go wrong with that.  On the Vista front, I have been toying around with the script I found from Tony McGuire. (which i have included below).  It seems to make the problem go away in Server 2008 but I still get in on Vista. I'll keep working on it.

Var
dy dynarray[] string
s string
Endvar

sysinfo(dy)   ;dy.view()
s=dy["WindowsVersion"]
s=s.substr(1,1)      ;s.view()
if s="6" then  ;Vista
  Execute("TaskKill.exe /F /IM TaskEng.exe", No, ExeHidden)
endif

 ***Just Added***

I just read your article about Taskeng.exe.  I will keep that in mind before implementing.

Scott

This of course will work fine if my app is the only paradox app running.  I have had a few places running some homemade labeling systems using paradox. 

Thanks for correcting my code. I have it correct in my working files. I must've copied from an old snippet.

As far as it not working, I need to look at it further. I was probably working with it after lunch and suffering from food coma.  heh

Thanks