ChipMaster's bwBASIC This also includes history going back to v2.10. *WARN* some binary files might have been corrupted by CRLF.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 

120 lines
3.5 KiB

  1. 4-16-2020 Updated 8-8-2020 3.20d
  2. Bwbasic has been around since the early 1990's
  3. in one form or another and actually quite powerfull.
  4. This should work under most any Linux and Linux under
  5. WSL (Ubuntu, Debian) for windows at the command prompt.
  6. If running this under Linux you will need 'gcc' compiler.
  7. To see if it's installed type in gcc --version if OK
  8. then simply do the following:
  9. tar -xf bwbasic-3.20d.tar
  10. cd <here>
  11. To make 'cls' work as it does in DOS perform once
  12. sudo ln /usr/bin/clear /usr/bin/cls
  13. Tip: Now linking to clear within a bwbasic program you
  14. can clear the screen using command SHELL "cls"
  15. This can be embedded in you program. You can also
  16. use OPTION TERMINAL ANSI then use command CLS
  17. Now lets build bwbasic and renum
  18. (1) make
  19. To test before installing (2) make runlocal
  20. Then to install (3) sudo make install
  21. To remove installed programs (4) sudo make remove
  22. To remove compiled programs and recompile (5) make clean
  23. That's it.
  24. bwbasic and renum will be in /usr/bin
  25. If you want bwbasic to work from a GUI cd GUI
  26. (1) copy bwbasic.sh to a suitable location
  27. and make sure to chmod 755 bwbasic.sh
  28. so it's executable.
  29. (2) copy bwbasic.png to a suitable location
  30. (3) edit bwbasic.desktop and change references
  31. for File Location and png location then
  32. cp bwbasic.desktop to ~/Desktop/.
  33. and it should work from the desktop.
  34. Doing the above should allow you to click on the icon
  35. on your desktop and start bwbasic.
  36. If running under Windows 10 you will need 'gcc' compiler.
  37. To see if it's installed type in gcc --version if you
  38. think you have gcc installed verify your 'PATH' by entering
  39. at the command prompt echo %PATH% to see if it's there.
  40. If OK then at the command prompt
  41. cd <here>
  42. compile.bat
  43. Read prompts
  44. That's it.
  45. Move bwbasic.exe and renum.exe to locations in your PATH.
  46. There are many, many examples in BAS-EXAMPLES and
  47. available information in INFO.
  48. All should work fine. But as usual no guarentee is implied.
  49. Any references below to relays pertain to the BeagleBone Black.
  50. I have included some runtime files and sample input files.
  51. Place profile.bas in your current working directory and
  52. relays.pro and allon.inp and alloff.inp. The file examples
  53. will let you to by example turn off all relays alloff.inp.
  54. To do this you would enter at the command line:
  55. bwbasic --profile relays.pro --tape alloff.inp relays.bas
  56. To turn all relays on:
  57. bwbasic --profile relays.pro --tape allon.inp relays.bas
  58. To work interactive you would:
  59. bwbasic relays.bas
  60. Once you get a handle on relays.bas commands you can
  61. create you own .inp files and reference them by
  62. bwbasic --profile relays.pro --tape <your file.inp> relays.bas
  63. All the above can placed into a simple script file.
  64. The purpose of relays.pro is to redirect standard and error
  65. outputs to files relays-stdout.txt and relays-error.txt and
  66. to turn off ANSI so the output is easily readable without
  67. escape codes. Using relays.pro then gives you a quiet display
  68. suitable when scripts via .inp is executed.
  69. The purpose of profile.bas which is used by default is to
  70. enable ANSI control sequences so the command 'cls' works
  71. and to set the normal editor to nano which if desired can
  72. bet set to vi. The editor comes into play when creating
  73. or changing a .bas file. To use while running bwbasic you
  74. would issue the command edit.
  75. As a simple example try the guessing game with
  76. bwbasic guess.bas
  77. If you come up with some ideas or enhancements or have a
  78. problem drop me a message keeping in mind my main goal
  79. is to do maintenance updates where necessary.
  80. ken.at.github@gmail.com