I am just wondering why I can't run the Windows version at all. "pcbasic -h" will work, but not when start with the default graphical mode either by executing "pcbasic.exe" from command line or from start menu. A windows will pop up but soon closed, then nothing. Thanks for the help!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just tested a fresh download on Windows 7 and 10 and it runs without problems for me, so I'll need some more information about your specific install to find out what's wrong.
Can you please post the output of pcbasic --debug -v
Also please let me know if there are any warnings or messages when running from the command line.
Finally can you try pcbasic -b which should run a non-graphical session of BASIC (use SYSTEM or Ctrl+Z to exit).
Thanks!
Rob
Last edit: Rob Hagemans 2015-08-24
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, thanks for the output; that is all as expected. Curses is not the problem, it is not available for Windows anyway. It's only needed for the text interface on Unix systems.
I don't really knwo what the problem could be, I've installed that precise version on a Windows 10 VM earlier today and it ran without issues.
Are there any messages on the console at all when the window pops up and disappears? Could you try running pcbasic --debug
and see if anthing shows up?
Also let me know what happens with pcbasic -b
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have tried to install it on a different Windows 10 system, and it seems to work there, so I think it must be related to some configuations on this system. However, some earlier versions such as 14.10.1 do run on this system. Running "pcbasic --debug" is same as running "pcbasic" directly, which causes a window to pop up and disappear immediately, and no message left in the console. Furthermore, "pcbasic -b" will run on both machines, but on both of them I am not able to run any commands properly, but this is probably another (i.e. unrelated) problem or bug.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It's very strange... I fear that unless I can somehow reproduce the issue so I can have some hands-on time with it it'll be very ifficcult for me to find out what the problem is there. Are there any obvious differences between the two Windows machines (e.g. 32 bit vs 64 bit or something)?
I'm also interested in the issue that you can't run commands properly, could you elaborate on that? What commands do you type, what would you expect to happen, what does actually happen?
Thanks
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Both Windows 10 machines are 64-bit, and were installed from the exactly same ISO. One was upgraded from Windows 7, and the other was upgraded from Windows 8.1. It is the latter which has this problem, but it generally run other programs fine, so I think it is strange too.
As for "pcbasic -b", it shows the following when I run it:
PC-BASIC 3.23
(C) Copyright 2013--2015 Rob Hagemans.
60300 Bytes free
Ok
However, when I type any letter then, e.g "a", it shows two of them (e.g. "aa"). If I type Enter, then it changed to a new line, but nothing else happens (no result from thhe command or error message etc), and I am not even able to exit by typing the "SYSTEM" command. I am currently using ConEmu for command prompt, but it does not work correctly in plain "Command Prompt" shipped with Windows 10 either.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Curious. Let's do one more try, I just realised that it may be that warning messages simply disappear on the Windows console. Could you run pcbasic --debug --logfile=log.txt
and post the contents of log.txt? Hopefully it is not empty and we'll get some information on what is happening.
As to the second issue: Oh dear, I see what you mean. It's a total mess. (You can still get out of the program by typing Ctrl-Z, by the way).
It looks like the problem is in ansipipe, which is a subproject I set up to handle the Windows console. This issue only shows up in Win10, it seems - XP and 7 are OK though I haven't tried Win8. There must have been changes to the console API or maybe something changed with regards to the named pipes ansipipe uses to communicate with pcbasic. Looking forward to some quality time with Microsoft documentation :/
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good news! By trying with the PC-BASIC source, I see why it does not run on one of the Windows 10 machines for the first problem. It is because of the "list index out of range" in line 1657 of backend.py when I attach a Logitech Dual Action Gamepad to a USB port of the system. When I unplug the Gamepad from the system, PC-BASIC will run properly. Hope it will be fixed.
P.S. The "--logfile=log.txt" method won't work as the file is indeed empty.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Could you post the whole stack trace of that error? Usually python prints a few lines of code and messages before the final error message, which are very useful for finding the root cause of the issue.
Rob
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
ERROR: Unhandled exception
Traceback (most recent call last):
File "D:\d\pcbasic-code-3b75e185b8f67632b1abe13ad043174111cdca39\pcbasic__main.py", line 137, in start_basic
backend, console = prepare_console()
File "D:\d\pcbasic-code-3b75e185b8f67632b1abe13ad043174111cdca39\pcbasic__main.py", line 254, in prepare_console
if backend.init_video(video):
File "pcbasic\backend.py", line 837, in init_video
if not video or not video.init():
File "pcbasic\video_pygame.py", line 319, in init
backend.stick_moved(joy, axis, 128)
File "pcbasic\backend.py", line 1691, in stick_moved
state.console_state.stick.moved(joy, axis, value)
File "pcbasic\backend.py", line 1657, in moved
stick_axis[joy][axis] = value
IndexError: list index out of range
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all, I've uploaded release 15.03.5.
This is a bugfix release. Fixes include, among other things:
Enjoy,
Rob
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Dear Rob,
what version release of your PC Basic application do you recommend overall? I'd like to download a copy of your BASIC software.
I'd recommend the most recent release - currently that's 15.08.8.
Cheers,
Rob
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I am just wondering why I can't run the Windows version at all. "pcbasic -h" will work, but not when start with the default graphical mode either by executing "pcbasic.exe" from command line or from start menu. A windows will pop up but soon closed, then nothing. Thanks for the help!
Hi, what version of Windows are you using?
I just tested a fresh download on Windows 7 and 10 and it runs without problems for me, so I'll need some more information about your specific install to find out what's wrong.
Can you please post the output of
pcbasic --debug -vAlso please let me know if there are any warnings or messages when running from the command line.
Finally can you try
pcbasic -bwhich should run a non-graphical session of BASIC (use SYSTEM or Ctrl+Z to exit).Thanks!
Rob
Last edit: Rob Hagemans 2015-08-24
Also quick note - from the command line you should run
pcbasic.com, notpcbasic.exe. Or just typepcbasic.View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I am running Windows 10. The output of pcbasic --debug -v is:
15.03.5
numpy: available
pygame: available
curses: not available
pexpect: available
serial: available
So is it because of problem with curses? Isn't it installed automatically by the PC-BASIC installer when necessary? Thanks!
Hi, thanks for the output; that is all as expected. Curses is not the problem, it is not available for Windows anyway. It's only needed for the text interface on Unix systems.
I don't really knwo what the problem could be, I've installed that precise version on a Windows 10 VM earlier today and it ran without issues.
Are there any messages on the console at all when the window pops up and disappears? Could you try running
pcbasic --debugand see if anthing shows up?
Also let me know what happens with
pcbasic -bThanks!
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have tried to install it on a different Windows 10 system, and it seems to work there, so I think it must be related to some configuations on this system. However, some earlier versions such as 14.10.1 do run on this system. Running "pcbasic --debug" is same as running "pcbasic" directly, which causes a window to pop up and disappear immediately, and no message left in the console. Furthermore, "pcbasic -b" will run on both machines, but on both of them I am not able to run any commands properly, but this is probably another (i.e. unrelated) problem or bug.
It's very strange... I fear that unless I can somehow reproduce the issue so I can have some hands-on time with it it'll be very ifficcult for me to find out what the problem is there. Are there any obvious differences between the two Windows machines (e.g. 32 bit vs 64 bit or something)?
I'm also interested in the issue that you can't run commands properly, could you elaborate on that? What commands do you type, what would you expect to happen, what does actually happen?
Thanks
Rob
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Both Windows 10 machines are 64-bit, and were installed from the exactly same ISO. One was upgraded from Windows 7, and the other was upgraded from Windows 8.1. It is the latter which has this problem, but it generally run other programs fine, so I think it is strange too.
As for "pcbasic -b", it shows the following when I run it:
PC-BASIC 3.23
(C) Copyright 2013--2015 Rob Hagemans.
60300 Bytes free
Ok
However, when I type any letter then, e.g "a", it shows two of them (e.g. "aa"). If I type Enter, then it changed to a new line, but nothing else happens (no result from thhe command or error message etc), and I am not even able to exit by typing the "SYSTEM" command. I am currently using ConEmu for command prompt, but it does not work correctly in plain "Command Prompt" shipped with Windows 10 either.
Curious. Let's do one more try, I just realised that it may be that warning messages simply disappear on the Windows console. Could you run
pcbasic --debug --logfile=log.txtand post the contents of log.txt? Hopefully it is not empty and we'll get some information on what is happening.
As to the second issue: Oh dear, I see what you mean. It's a total mess. (You can still get out of the program by typing Ctrl-Z, by the way).
It looks like the problem is in ansipipe, which is a subproject I set up to handle the Windows console. This issue only shows up in Win10, it seems - XP and 7 are OK though I haven't tried Win8. There must have been changes to the console API or maybe something changed with regards to the named pipes ansipipe uses to communicate with pcbasic. Looking forward to some quality time with Microsoft documentation :/
Rob
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Good news! By trying with the PC-BASIC source, I see why it does not run on one of the Windows 10 machines for the first problem. It is because of the "list index out of range" in line 1657 of backend.py when I attach a Logitech Dual Action Gamepad to a USB port of the system. When I unplug the Gamepad from the system, PC-BASIC will run properly. Hope it will be fixed.
P.S. The "--logfile=log.txt" method won't work as the file is indeed empty.
Excellent! Thanks very much for digging this out.
Could you post the whole stack trace of that error? Usually python prints a few lines of code and messages before the final error message, which are very useful for finding the root cause of the issue.
Rob
View and moderate all "[CLOSED] General Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
The whole stack trace is like this:
ERROR: Unhandled exception
Traceback (most recent call last):
File "D:\d\pcbasic-code-3b75e185b8f67632b1abe13ad043174111cdca39\pcbasic__main.py", line 137, in start_basic
backend, console = prepare_console()
File "D:\d\pcbasic-code-3b75e185b8f67632b1abe13ad043174111cdca39\pcbasic__main.py", line 254, in prepare_console
if backend.init_video(video):
File "pcbasic\backend.py", line 837, in init_video
if not video or not video.init():
File "pcbasic\video_pygame.py", line 319, in init
backend.stick_moved(joy, axis, 128)
File "pcbasic\backend.py", line 1691, in stick_moved
state.console_state.stick.moved(joy, axis, value)
File "pcbasic\backend.py", line 1657, in moved
stick_axis[joy][axis] = value
IndexError: list index out of range
Got it, thanks!
Fix is already checked into git :)
I've also fixed the issue with ansipipe, so the console interface should be workable on Windows 10. Will include with next release.