pmgraphics Posted November 9, 2018 Share Posted November 9, 2018 I read that turbo basic xl can run atari basic programs at about 3 times the speed. I have some atari basic programs that I made ages ago that are slow. I tried to load them with turbo basic xl but I keep getting an error 170 ?FILE. The progams load fine in atari basic. is it not possible to load atari basic programs in turbo basic xl? I am using Altirra 2.7 as 600XL/800XL. thanks Quote Link to comment Share on other sites More sharing options...
gozar Posted November 10, 2018 Share Posted November 10, 2018 I read that turbo basic xl can run atari basic programs at about 3 times the speed. I have some atari basic programs that I made ages ago that are slow. I tried to load them with turbo basic xl but I keep getting an error 170 ?FILE. The progams load fine in atari basic. is it not possible to load atari basic programs in turbo basic xl? I am using Altirra 2.7 as 600XL/800XL. thanks Error 170 is "File not found". In TBXL type DIR to get a drive listing. Double-check the filename. 1 Quote Link to comment Share on other sites More sharing options...
Kyle22 Posted November 10, 2018 Share Posted November 10, 2018 LOAD "D:FILENAME.EXT" or, if they are saved as text files, ENTER "D:FILENAME.EXT" Quote Link to comment Share on other sites More sharing options...
pmgraphics Posted November 10, 2018 Author Share Posted November 10, 2018 (edited) The file name is correct, it's QUEST.SAV. whether I use load "D:QUEST.SAV" or load "D:QUEST.EXT" they both have the same error- 170 ?file. Using load "D:QUEST.SAV" in atari basic the program loads and runs. In altirra I attach disk one to: Turbo_Basic_XL.atr disk two to: my_programs.atr Edited November 10, 2018 by pmgraphics 1 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted November 10, 2018 Share Posted November 10, 2018 (edited) The file name is correct, it's QUEST.SAV. whether I use load "D:QUEST.SAV" or load "D:QUEST.EXT" they both have the same error- 170 ?file. Using load "D:QUEST.SAV" in atari basic the program loads and runs. In altirra I attach disk one to: Turbo_Basic_XL.atr disk two to: my_programs.atr Well, there's your problem... If your programs are in D2, then your load command should be LOAD "D2:QUEST.SAV"... not "D:QUEST.SAV". Edited November 10, 2018 by MrFish 2 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted November 10, 2018 Share Posted November 10, 2018 face palm... 1 Quote Link to comment Share on other sites More sharing options...
pmgraphics Posted November 10, 2018 Author Share Posted November 10, 2018 Actually I did use LOAD "D2:QUEST.SAV". the D was just a typo in this post. Quote Link to comment Share on other sites More sharing options...
+slx Posted November 10, 2018 Share Posted November 10, 2018 (edited) Actually I did use LOAD "D2:QUEST.SAV". the D was just a typo in this post. Do you see your file if you do DIR "D2:*.* ? If you don't load Turbo BASIC, does it load normally from Disk 2? Depending on the DOS you use, is the DOS set up for dual drives? I have attached a more or less "blank" Turbo BASIC XL with XDOS which is capable of dual drives. You can boot with that version and try if it loads from Disk 2. AFAIK Turbo BASIC XL will not work correctly with DOSes that use memory below the OS (as TBXL uses that area for itself). It didn't work with DOS XL for me but I have not tried a lot of others. Depending on the DOS you use you might have to remove the RAMDISK. TurboBasicXL_XDOS.atr Edited November 10, 2018 by slx Quote Link to comment Share on other sites More sharing options...
pmgraphics Posted November 11, 2018 Author Share Posted November 11, 2018 The command DIR "D2:*.* produces the message: 999+free sectors. If I use the disk (the atr file) with QUEST on it by itself, the game does load and play. >is the DOS set up for dual drives I can use this atr in drive2 and a second atr in drive1, load a program from drive1 and save it to drive2. The atr file is DOS3 if that matters. I tried your turbobasicxl_dos.atr and it produced the same load error and DIR "D2:*.*" created a similar message: ??? free sectors. If I need to transfer my programs from dos3 atr files to a different dos atr file, how can I do that? Thanks Quote Link to comment Share on other sites More sharing options...
Sikor Posted November 11, 2018 Share Posted November 11, 2018 (edited) @pmgraphics: extension *.sav? I think, you dont use any DOS and save savestate of altirra, yes? So, simplyu copy your listing as text in altirra, next - load Turbo Basic XL with any DOS, paste text from clipboard and save as "D:name.ext". Run it now. Edit: ohh, you attach Load from D2. You load Turbo Basic first? Step by step: - Attach disk 1 with Turbo Basic XL and DOS - attach disk 2 with your programs - boot without Basic - load Turbo Basic XL - DIR "D2:*.*" - list of your games - now LOAD "D2:name.ext" good luck. Edited November 11, 2018 by Sikor 3 Quote Link to comment Share on other sites More sharing options...
phaeron Posted November 11, 2018 Share Posted November 11, 2018 Your disk being DOS 3 formatted is the problem. Those disks typically can't be read from any other DOS, including the one that Turbo-Basic XL is booting from. To resolve this, upgrade to Altirra 3.10 and use its option to convert the disk from DOS 3 to DOS 2 format. This option is on the triangle button for the drive in the Disk Drives dialog, under Convert Filesystem > DOS 2.0S/2.5. Do this on a copy of the disk image. You can also use Disk Explorer to copy the files out to the PC and back into a DOS 2 disk image. 4 Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted November 11, 2018 Share Posted November 11, 2018 (edited) or copy the turbo basic disk to a dos 3 disk if it's not going to be a memory conflict.... all of these DOS disk came with conversion utils to copy from one format to another... 2-3 3-2.5 (and that would cover 2 if sd) etc. etc. but seriously, who would think to try to use incompatible formats together like this, it is akin to using dos 2 and trying to read a dos 2.5 extended file or even just using a MyDos disk to read SDFS or something... we don't have his specific disks so we can't know what DOS he is using on his turbo basic disk... even though folks tried to get him to copy his files to other dos disks to be certain about this.. so again. Palm - Face on the other hand it's probably solved so thumbs up. Edited November 11, 2018 by _The Doctor__ Quote Link to comment Share on other sites More sharing options...
pmgraphics Posted November 12, 2018 Author Share Posted November 12, 2018 the basic turbo xl atr, according to disk explorer, is DOS 2.x. So I need to get my programs from the DOS3 atr onto a DOS 2 atr. How exactly do I, "...use Disk Explorer to copy the files out to the PC and back into a DOS 2 disk image," as phaeron mentioned. In disc explorer I don't see the option to copy files out to the Pc and back then back into altirra. Also the DOS3 menu system seems to only have an option to convert DOS2 to DOS3, if I understood it correctly, as below, the source is DOS2 and destination DOS3. Access DOS 2 utility Copyright 1983, Atari Source drive number? 2 DOS 2 filename? Q.SAV Destination drive number? 3 DOS 3 filename? Quote Link to comment Share on other sites More sharing options...
Wrathchild Posted November 12, 2018 Share Posted November 12, 2018 You can drag drop files between the disk explorer window and a file explorer window and vice-versa 2 Quote Link to comment Share on other sites More sharing options...
pmgraphics Posted November 12, 2018 Author Share Posted November 12, 2018 (edited) Thanks Wrathchild that was simple. My program now loads in turbo basic xl, and it is fast, crazy fast. (thanks phaeron, I now see what you meant) Edited November 12, 2018 by pmgraphics 2 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.