Jump to content

Ray Gillman

New Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

13 Good

About Ray Gillman

  • Rank
    Space Invader

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Here is the pdf of this found here might be easier to read http://www.atarimania.com/atari-magazine-analog_18.html The source should be Aug 86? http://www.atarimania.com/mags/pdf/analog_no_45.pdf
  2. So I found an old box of atari 8 bit floppies and wondered what is the simplest way to browse those with a PC?
  3. I noted what a lot of programs on the 8-bit started to do through the later years was to utilize disk space and stuff like page 6 memory to keep a transferable image of some "core variables" and then they would be better able to workaround the severe memory limit and variables limits by having these programs pass the baton to the next program. So you'd have a set of variables be loaded or understood to be in certain PEEK locations and they could then have each program in the application collection of programs load the next module and it would fire up by grabbing some core variables and so on it would go. This is reflected in many later programs as well such that the "World Builder" or "Character Editors" were always separate programs but dealt with the same core variables and data. Many would often even have the Flashy music and graphics of the first start screen be in a temporary Startup program which would go away after the intro was done wowing the user with flashing colors and sounds
  4. Yes I know I have seen one before and the downside was, it uses generic variables like X Y Z A B C rather than meaningful variables. Thanks!
  5. I have some newb-ish questions if you can offer any much appreciated help thank you in advance. Where is this PAGER variable? Environment variables? How do I access the files on the CAR: volume? Every time I try to do anything like edit or read or copy the files on CAR: to D1: it always errors with 161 too many channels open? Weird. It seems to want you to not touch the files on the CAR just run them? Interesting that changing default current path to CAR: results in DCAR1: odd device name. Final question which version of SDX448 should I work with, there are three in the package maxflash8, maxflash1 and sdx128? I am using an emulated 8 bit so my preference is the 576K or 1088K biggest ram space (why not right). I think I found a thread which answers part of this the CONFIG.SYS must be on a Sparta volume. My guess is this is where the environment vars must be stored and partly why it's not easy to work with. The Cartridge SDX seems unfriendly with random disks in D1: ?? reference to matching 2011 thread
  6. I have some newb-ish questions if you can offer any much appreciated help thank you in advance. Where is this PAGER variable? Environment variables? How do I access the files on the CAR: volume? Every time I try to do anything like edit or read or copy the files on CAR: to D1: it always errors with 161 too many channels open? Weird. It seems to want you to not touch the files on the CAR just run them? Interesting that changing default current path to CAR: results in DCAR1: odd device name. Final question which version of SDX448 should I work with, there are three in the package maxflash8, maxflash1 and sdx128? I am using an emulated 8 bit so my preference is the 576K or 1088K biggest ram space (why not right).
  7. AHH the X.COM on the CAR - just learned I can also ED the manuals MAN files like ED CAR:X.MAN fun stuff. Thank you again
  8. First I heard of this CAR: volume - wonders what all the MAN files are but AHA it makes sense now. Volume is in the "cartridge ramdisk" effectively. Brilliant. 448sdx does read MyDos disks just fine looks like but can't find any version of Ostrowski's TurboBasic that will run with it. Which basic is best for use with this SDX ideally one with a compiler? Thanks for sharing your expertise flashjazzcat!
  9. So if I wanted to run a "Universal Menu" to access all the disk formats and retrieve and copy files from one format to another would SpartaDos X be the way to go here or is there a better way to approach this? I am primarily concerned with MyDos 4.53 format ATR files (with foldered subdirectories with the : colon) and SpartaDos ATR files (also with foldered subdirectories with the > greater than) To give more info, I find subtle differences like I have to rename MENU.COM to MYMENU.COM to be able to run it under SpartaDosX because it has a built in MENU when you type MENU it doesn't load the MENU.COM from disk. It looks like it can read most MyDos disks so I am optimistic this is the best one to use so far. Your opinions? Photo just for effect
  10. https://download.virtualbox.org/virtualbox/6.0.14/VirtualBox-6.0.14-133895-Win.exe If you haven't tried these they are great for testing environments - best of all it's 100% free and getting regular updates - updating mine from 6.0.12 right now Not suggesting you ever install some malware just to test but we run so much random EXE files from the internet - you never know - cheers Snapshot so you know it's real. I setup small disk space emulated PC's to run various Linux tests and for when I have something wont work in Win10 64 bit I have a handy emulated Win10 32 bit to try it on. Most 32 bit stuff runs on 64 but not all and certainly not any 16 bit old stuff really.
  11. I've had good results working with Windows Total Commander freeware using the foreign language plugin for ATR files - had to use the 32 bit version of the Total Commander to link the plugin as the plugin is 32 bit but it works on 64 bit windows 10 pretty well for both pulling and pushing things in and out of ATR images. It navigates and shows the ATR files as little yellow compressed folders - sometimes the simplest is the best solution - sometimes DIR2ATR is simpler because you just want all the files in an ATR - but other times I just want to add or update one file and commander gets it done for me
  12. The 2.11 version would give a mini-dos as pictured and you could exit and do some limited things and then Quit back to basic and your code would still be there None of the other versions including 2.0 have this I don't believe. Seemed like a poor trade off for over 2.5K of program space in my view. I can't even tell you what Load Save and Verify do even. Dos goes to the real Dos and Quit just jumps back into the interpreter
  13. Thanks for that info - mini dos seems hardly worth nearly 3K of program space in my way of thinking. I think I figured out another part of the puzzle. From the above Turbo_Basic_XL_2.0.atr.zip package if you get into Turbo 21 and exit to dos you can Quit back into Turbo 21 and your source code is still in memory untouched. If you Dos out of Turbo 2.0 the code in the interpreter gets flushed when 2.0 loads lacking the Quit back to Basic option.
  14. version 2.0 leaves just over 34K fre(0) where version 2.1 leaves under 31.5K fre(0) big diff still trying to figure out what the difference is
  15. Anyone have experience working with TurboBasic 1.5 and 2.11? The Ostrowski gem? Is the upgrade to 2.11 worth giving up like 2,548 bytes of workspace? (34,021 - 31,473) ---- update ---- I found this write up in German and translated it Hello, everybody, have been asked to explain the different versions of Turbo-BASIC XL. We can find them on the Atriki from our polish friends: http://atariki.krap.pl/index.php/Turbo_BASIC_XL used in: http://www.DeepL.com following declaration: " A variant of the BASIC language for small Atari, which was developed in 1985 by the German programmer Frank Ostrowski and distributed by the magazine Happy Computer as a public domain program. There are two official versions: Turbo-BASIC 1.4 - for 400/800 computers with min. 32 KB RAM. This version has a built-in DOS 2.0 - the interpreter is "glued" in the DOS.SYS file. Turbo-BASIC XL 1.5 - for XL/XE computers. This version partially loads into the RAM under the ROM of the operating system, which gives the user program more memory (slightly more than 33k - manually ?). FRE(0) returns the result of 34021 bytes). In addition, several unofficial changes have been made: Turbo-BASIC XL 1.6 by Thomas Richter Turbo-BASIC XL .... by Torsten Karwoth Turbo-BASIC XL 2.0 - Hack Version 1.5 with modified title text, with "(c) 1990 LASER Software". Other differences unknown. Turbo-BASIC XL 2.0 & Turbo 2000 System (also known as TT-Basic XL 2.11) - Change of version 1.5 by Jiří Richter, the Czech author of Turbo 2000, 1988. It contains an integrated Mini-DOS for the Turbo system and a handler for the T:. Turbo BASIC 3.2q - Version 1.4 adapted for cooperation with SpartaDOS 3.2, by Tom Hunt from 1992. BPUT and BGET commands are missing, but can be replaced by corresponding XIO calls. The interpreter package contains a handler for operating P:R: Connection together with a program for loading this handler from the BASIC level. Turbo BASIC is loaded from a hard disk or tape into the RAM of the computer. Interpreter has more instructions than the original Atari BASIC, there is also a Turbo BASIC XL compiler. The main advantage of Turbo BASIC XL is its speed, the programs are executed three to five times faster than in the Atari BASIC interpreter, which is mainly due to the fact that Turbo BASIC has its own very fast floating point procedure package, which works well in most applications. Another important advantage of the interpreter is the backward compatibility with Atari BASIC, so that almost all programs written in this package run under Turbo BASIC XL (with few exceptions). It would be nice if the knowledge carriers among you could make additions if necessary. Especially for the version 1.6 by Thomas Richter and for the version by Torsten Karwoth, for which unfortunately all documents have been destroyed by water damage. Translated with www.DeepL.com/Translator
×
×
  • Create New...