Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Clipper running on Windows XP Professional
- Thread starter alsacto
- Start date
A thread on the foxpro forum has a solution which also applies to clipper:
Rob.
Here is the text of the thread:
Windows 98, 98se and Me all run real DOS windows and have native support for LPT1, LPT2, etc. Windows NT, 2000, XP and 2003 are the "better and newer" systems but the big drawback is that they emulate DOS imperfectly in many ways. There are a number of issues when changing from one system to the other, probably the most notable being printing. In short, DOS programs are difficult to run without issues and it will likely only get worse in the future. Until you can rewrite them or have them rewritten you'll have to find workarounds.
Search here for a description of a program PrintFile. What you do is have your printout sent to a file in a specific directory. Once the file is there the program pick it up and sends it on to the printer. Perhaps it will work in your Novell environment.
Also make various keyword searches for NET USE and other likely words. Some of the following posts do mention Novell issues, so check these out too:
Thread182-718345 (has my post with NET USE workaround code)
Thread182-787526
Thread182-502586
Thread182-547112
Thread182-65500
Rob.
Here is the text of the thread:
Windows 98, 98se and Me all run real DOS windows and have native support for LPT1, LPT2, etc. Windows NT, 2000, XP and 2003 are the "better and newer" systems but the big drawback is that they emulate DOS imperfectly in many ways. There are a number of issues when changing from one system to the other, probably the most notable being printing. In short, DOS programs are difficult to run without issues and it will likely only get worse in the future. Until you can rewrite them or have them rewritten you'll have to find workarounds.
Search here for a description of a program PrintFile. What you do is have your printout sent to a file in a specific directory. Once the file is there the program pick it up and sends it on to the printer. Perhaps it will work in your Novell environment.
Also make various keyword searches for NET USE and other likely words. Some of the following posts do mention Novell issues, so check these out too:
Thread182-718345 (has my post with NET USE workaround code)
Thread182-787526
Thread182-502586
Thread182-547112
Thread182-65500
What type of printer, parallel or USB? If it's a USB printer, share it and do a:
NET USE LPT1 \\PCNAME\PRINTERNAME /PERSISTENT:YES
If it's a parallel printer then generally there's not usually a problem. Maybe a little more specific hardware info might help.
Ian Boys
DTE Systems Ltd
NET USE LPT1 \\PCNAME\PRINTERNAME /PERSISTENT:YES
If it's a parallel printer then generally there's not usually a problem. Maybe a little more specific hardware info might help.
Ian Boys
DTE Systems Ltd
- Thread starter
- #4
The problem is not with a USB port or specifically with a printer. The program locks up in various places and at different times on the compter running Windows XP PRO. I tried using the debugger to trace through the program and was unsuccessful. I'm assuming the problem is related to XP professional as I have no problem with XP Home. So I thought someone might have experienced a similar situation.
Al Nystrom
Al Nystrom
Hello,
This doesn't sound like the printer thing, it smacks of the keyboard interrupt problem.
Clipper thinks it has 100% of the processors attention when it gets to scanning the keyboard during 'reads' and 'inkeys'.
You can check this by looking at your machine while it seems to be hung and doing the Ctrl-Alt-Del thing. Look at the processor utilisation and you will probably see it's at 100%
There are, however, ways to get around the problem!
If you have a look at the following you should find a solution:
here on thread288-942760
Good luck
Regards
Griff
Keep [Smile]ing
This doesn't sound like the printer thing, it smacks of the keyboard interrupt problem.
Clipper thinks it has 100% of the processors attention when it gets to scanning the keyboard during 'reads' and 'inkeys'.
You can check this by looking at your machine while it seems to be hung and doing the Ctrl-Alt-Del thing. Look at the processor utilisation and you will probably see it's at 100%
There are, however, ways to get around the problem!
If you have a look at the following you should find a solution:
here on thread288-942760
Good luck
Regards
Griff
Keep [Smile]ing
- Thread starter
- #6
Thank you all for your responses. Apparently I have not been clear in explaining the difficulty I am having. The program runs great under Windows XP Home but not under Windows XP Professional where it will "lock up". So, I was questioning if anyone else had exerienced a simliar situation.
Al Nystrom
Al Nystrom
- Thread starter
- #8
Hi Al,
To be honest, XP Home IS XP Pro, with a few things disabled, in fact there is even a rumour that someone has written a little utility that switches it from home to pro and on to server... but that may or may not be true.
Why it should behave differently, I have no idea!
Regards
Griff
Keep [Smile]ing
To be honest, XP Home IS XP Pro, with a few things disabled, in fact there is even a rumour that someone has written a little utility that switches it from home to pro and on to server... but that may or may not be true.
Why it should behave differently, I have no idea!
Regards
Griff
Keep [Smile]ing
- Thread starter
- #10
- Status
Similar threads
- Locked
- Question
- Locked
- Helpful tip
- Locked
- Question
