Wrathchild Posted December 8, 2022 Share Posted December 8, 2022 19 minutes ago, TGB1718 said: if they run another persons attempt before yours, there's no guarantee it will be clear. Why, in the file_id.diz you give instructions on how to run in an emulator? Beyond double clicking an xex there isn't too much too it. Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted December 8, 2022 Share Posted December 8, 2022 1 hour ago, Wrathchild said: Why, in the file_id.diz you give instructions on how to run in an emulator? Beyond double clicking an xex there isn't too much too it. Very true, my mistake was running again and again after changes to the code and obviously I saw corruption, but with a clean start of the emulator, there's no need to clear memory Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 8, 2022 Share Posted December 8, 2022 (edited) 3 hours ago, TGB1718 said: WOW less than 64K 🤣 Did you typo ?? No typo's. lol But if this was a Windows program, anything under 64k would be impressive. Edited December 8, 2022 by reifsnyderb Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted December 8, 2022 Share Posted December 8, 2022 Still working on my Assembler version, so frustrating when you see repeated values but any attempt to reduce duplication costs more processing bytes 🤓 Still I think it's quite tiny now Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted December 8, 2022 Share Posted December 8, 2022 (edited) I think you're looking further into it than they intended... submit both then... Edited December 8, 2022 by _The Doctor__ Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 8, 2022 Share Posted December 8, 2022 12 minutes ago, _The Doctor__ said: I think you're looking further into it than they intended... submit both then... I was thinking about submitting both of mine as well. The larger program I wrote would actually work quite well if there was more on the screen and if there was no mathematical way to derive the picture. Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted December 8, 2022 Share Posted December 8, 2022 23 minutes ago, _The Doctor__ said: I think you're looking further into it than they intended... Yes, but it's fun and good for this old fuzzy brain Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 8, 2022 Share Posted December 8, 2022 5 minutes ago, TGB1718 said: Yes, but it's fun and good for this old fuzzy brain I've been coding in Godot lately and it's interesting to use Atari BASIC again. I had to dig out the book to look a couple things up. 🙂 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 8, 2022 Share Posted December 8, 2022 Working on an Atari BASIC version now... Upper-left corner (cursor showing, no "Ready" prompt): 137 bytes Upper-left corner (no cursor, no "Ready" prompt): 141 bytes Centered (no cursor, no "Ready" prompt): 151 bytes Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 8, 2022 Share Posted December 8, 2022 21 minutes ago, MrFish said: Working on an Atari BASIC version now... Upper-left corner (cursor showing, no "Ready" prompt): 137 bytes Upper-left corner (no cursor, no "Ready" prompt): 141 bytes Centered (no cursor, no "Ready" prompt): 151 bytes Missed something obvious on these... Now, respectively: 130 bytes 134 bytes 141 bytes Quote Link to comment Share on other sites More sharing options...
_The Doctor__ Posted December 8, 2022 Share Posted December 8, 2022 heh tab stops and adjusts Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 2 hours ago, MrFish said: 130 bytes 134 bytes 141 bytes 4 more bytes off each of these Atari BASIC versions. Probably done now... (famous last words) 126 bytes 130 bytes 137 bytes Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 9, 2022 Share Posted December 9, 2022 (edited) 15 minutes ago, MrFish said: 4 more bytes off each of these Atari BASIC versions. Probably done now... (famous last words) 126 bytes 130 bytes 137 bytes ...and it still doesn't fit on a single DOS 2.5 sector. 😜 Edited December 9, 2022 by reifsnyderb 1 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 (edited) 6 hours ago, reifsnyderb said: ...and it still doesn't fit on a single DOS 2.5 sector. 😜 Now two of them do. 6 hours ago, MrFish said: 4 more bytes off each of these Atari BASIC versions. Probably done now... (famous last words) 126 bytes 130 bytes 137 bytes I spoke too soon: 8 more bytes off of each one. 118 bytes 122 bytes 129 bytes Edited December 9, 2022 by MrFish 3 Quote Link to comment Share on other sites More sharing options...
TGB1718 Posted December 9, 2022 Share Posted December 9, 2022 7 hours ago, reifsnyderb said: ...and it still doesn't fit on a single DOS 2.5 sector. 😜 Can't seem to get my BASIC version any smaller, still a lot more bytes than @MrFish But my assembler version easily fits in one sector and that includes the 6 byte header 2 Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 9, 2022 Share Posted December 9, 2022 3 hours ago, TGB1718 said: Can't seem to get my BASIC version any smaller, still a lot more bytes than @MrFish But my assembler version easily fits in one sector and that includes the 6 byte header Admittedly, I can't get my BASIC version any smaller, either. He's got to be using a different algorithm than either of us. Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 18 hours ago, reifsnyderb said: ...and it still doesn't fit on a single DOS 2.5 sector. 😜 OK, now they all fit. 11 hours ago, MrFish said: 118 bytes 122 bytes 129 bytes 108 bytes 112 bytes 118 bytes 1 Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 9, 2022 Share Posted December 9, 2022 11 minutes ago, MrFish said: OK, now they all fit. 108 bytes 112 bytes 118 bytes Are you using assembly language? Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 17 minutes ago, MrFish said: 108 bytes 112 bytes 118 bytes Almost broke the 100 bytes barrier... 101 bytes 105 bytes 112 bytes 1 Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 12 minutes ago, reifsnyderb said: Are you using assembly language? Nope Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 9, 2022 Share Posted December 9, 2022 (edited) 15 minutes ago, MrFish said: Nope Not a string of bytes poked into page 6 then execute with an x=usr() command? Edited December 9, 2022 by reifsnyderb Quote Link to comment Share on other sites More sharing options...
ClausB Posted December 9, 2022 Share Posted December 9, 2022 I got 134 bytes. Bah! Humbug! Quote Link to comment Share on other sites More sharing options...
+MrFish Posted December 9, 2022 Share Posted December 9, 2022 16 minutes ago, ClausB said: I got 134 bytes. Bah! Humbug! What kind of bytes (machine code, BASIC)? Quote Link to comment Share on other sites More sharing options...
ClausB Posted December 10, 2022 Share Posted December 10, 2022 Atari BASIC, text file with abbreviations. Quote Link to comment Share on other sites More sharing options...
reifsnyderb Posted December 10, 2022 Share Posted December 10, 2022 1 hour ago, ClausB said: Atari BASIC, text file with abbreviations. I didn't get my program down to 134 bytes. 😞 It does look like we were both thinking along the same lines. I found out that Atari BASIC doesn't use the abbreviates to save to disk, so I wrote a program to convert a listed filed to an abbreviated listed file. It's a little rough as it doesn't do proper error trapping and it probably has a few bugs. (i.e. I know it won't work right with REM statements without some modifications.) Here it is if anyone is interested... SHRINKER.BAS Quote Link to comment Share on other sites More sharing options...
Like us on Facebook
Follow us on Twitter
AtariAge on Instagram
Watch us on YouTube
Chat on Discord
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.