Installed 6.40d on a P4 PC running XP Pro Service Pack 2.
Everything works well when the program is run in a window... BUT
as soon as it is run in full screen the program(POS.exe, posconfig.exe, purchase.exe etc.) opens up the first screen but does nothing further.
In other words:- "press any key" does... well, nothing and the program must be closed with Windows Task Manager.
The keyboard(and others) works fine in Windows
Funny thing cause I have a test copy of DHPOS on another P4 PC with XP Pro and it works very well.
After searching this forum I tried various combinations of settings and solutions but nothing works.
Any ideas anybody?
May Your Christmas be Blessed and Happy!!
ToPS
Weird World
Moderators:daleadmin, Dale Harris, Alan, Andrew
-
brucef2112
- Forum Regular
- Posts:336
- Joined:Mon Mar 06, 2006 11:19 pm
- Location:Broward County, Floriduhh
- Contact:
The way to XP and DHPOS husbandry
Those who are looking for the way to XP & DHPOS husbandry, read on!
Here is some marginal computer advise.
The command.com is the original command interpreter (Windows DOS).
The cmd.exe is the MS Windows NT command line shell. A 32 bit application.
(also applies to Windows NT, Windows 2000, Windows XP and beyond)
Command.com is included for backwards compatibility and should be used with old MS-DOS programs (16 bit applications) that burp with the NT shell.
1) This should work
Try opening a DOS window using COMMAND.COM
START > RUN > COMMAND.COM
Start DHPOS in the DOS window and see if Command.com plays nice with DHPOS.
You may find some of the command line switches (like /E:nnnnn to set up an environment size) may make things work better.
For full screen, create a batch file and short-cut and fiddle with the properties and see if this helps.
2) Your mileage may vary but just for yucks;
Try opening a DOS window using CMD.EXE
START > RUN > CMD.EXE
Start DHPOS in this window and see if cmd.exe plays nice with DHPOS.
For full screen, create a batch file and short-cut and fiddle with the properties for each and see if this helps.
If #1 works, you have reached the nirvana of XP & DHPOS husbandry.
If #2 works, you are one of the chosen ones to have peace in the NT shell.
If neither one works, then at least you've confirm Microsoft sucks BUT at least they're consistent...
B
Here is some marginal computer advise.
The command.com is the original command interpreter (Windows DOS).
The cmd.exe is the MS Windows NT command line shell. A 32 bit application.
(also applies to Windows NT, Windows 2000, Windows XP and beyond)
Command.com is included for backwards compatibility and should be used with old MS-DOS programs (16 bit applications) that burp with the NT shell.
1) This should work
Try opening a DOS window using COMMAND.COM
START > RUN > COMMAND.COM
Start DHPOS in the DOS window and see if Command.com plays nice with DHPOS.
You may find some of the command line switches (like /E:nnnnn to set up an environment size) may make things work better.
For full screen, create a batch file and short-cut and fiddle with the properties and see if this helps.
2) Your mileage may vary but just for yucks;
Try opening a DOS window using CMD.EXE
START > RUN > CMD.EXE
Start DHPOS in this window and see if cmd.exe plays nice with DHPOS.
For full screen, create a batch file and short-cut and fiddle with the properties for each and see if this helps.
If #1 works, you have reached the nirvana of XP & DHPOS husbandry.
If #2 works, you are one of the chosen ones to have peace in the NT shell.
If neither one works, then at least you've confirm Microsoft sucks BUT at least they're consistent...
B
Ok, I tried it again by starting in a window and loading DHPOS and the program loaded a ran. I then had the window open into full screen and DHPOS continued to run. However DHPOS is actually several program files linked together and when one of the other program files is loaded the entire thing dies.
Dale
Dale
-
ToPS
Who is online
Users browsing this forum: No registered users and 144 guests