For some reason, when you use LPRINT ATTACH to connect to a UNC printer share, an error 68 is generated. This only occurs when the machine sharing the printer is running Vista.
Tests Completed Thus Far:
1. I have tested Vista with UAC turned OFF (see TweakUAC & msconfig/tools/disable UAC)
2. I have used the command line to enable the Vista administrator account and then logged in as the administrator (NET USE Administrator /active:yes ) and then tested the LPRINT ATTACH
3. I've run the PowerBASIC code "as administrator"
4. I've tested this issue on Vista Home Basic, Home Premium and Business editions.
On all versions of Windows LPRINT ATTACH works perfectly provided that the machine hosting/sharing the printer is not a Vista machine.
Please do not post back "you should use XPRINT". We need to send a complex series of binary escape codes to control industry specific equipment. It is not possible to use XPRINT to accomplish this. Because LPRINT creates a downlevel print job, it is the only solution I've found in PowerBASIC.
If anyone has ANY IDEAS (calling DLLs, Assembly code, etc etc) please post your thoughts.
If you are a super guru and have any ideas what Vista is doing differently from XP, please feel free to share your thoughts. My best guess is that the compiled code produced by PowerBASIC is not running under the proper escalation level. This may be a bug in Windows Vista or it may be an issue that a M$ patch is available for. Perhaps some inline assembly code could make the Vista O/S accept an LPRINT ATTACH?
Thank you so much in advance for any help.
Best,
Todd
Tests Completed Thus Far:
1. I have tested Vista with UAC turned OFF (see TweakUAC & msconfig/tools/disable UAC)
2. I have used the command line to enable the Vista administrator account and then logged in as the administrator (NET USE Administrator /active:yes ) and then tested the LPRINT ATTACH
3. I've run the PowerBASIC code "as administrator"
4. I've tested this issue on Vista Home Basic, Home Premium and Business editions.
On all versions of Windows LPRINT ATTACH works perfectly provided that the machine hosting/sharing the printer is not a Vista machine.
Please do not post back "you should use XPRINT". We need to send a complex series of binary escape codes to control industry specific equipment. It is not possible to use XPRINT to accomplish this. Because LPRINT creates a downlevel print job, it is the only solution I've found in PowerBASIC.
If anyone has ANY IDEAS (calling DLLs, Assembly code, etc etc) please post your thoughts.
If you are a super guru and have any ideas what Vista is doing differently from XP, please feel free to share your thoughts. My best guess is that the compiled code produced by PowerBASIC is not running under the proper escalation level. This may be a bug in Windows Vista or it may be an issue that a M$ patch is available for. Perhaps some inline assembly code could make the Vista O/S accept an LPRINT ATTACH?
Thank you so much in advance for any help.
Best,
Todd
Comment