Help needed with Bluemsx saving listings

Page 2/2
1 |

By mars2000you

Enlighted (5885)

mars2000you's picture

15-08-2018, 00:35

NYYRIKKI wrote:

and naturally the loadable size is bigger.

And when really too big ... no enough memoy message when trying to loading ... and therefore no compression activated as loading has failed.

Anyway, even when the file is not too big, I don't see where is the 'fun' to have a slow loading! It's the 1st thing that I check on disk images with BASIC programs. If I find ASCII files, I create a new DSK with tokenized files.

By NYYRIKKI

Enlighted (5745)

NYYRIKKI's picture

15-08-2018, 00:46

mars2000you wrote:

And when really too big ... no enough memoy message when trying to loading ... and therefore no compression activated as loading has failed.

So, is it really possible to create a BASIC file on MSX-BASIC environment that can't be loaded on same environment again? Or create a file that you can save on tokenized format, but not on ASCII? I honestly think that this should not be possible... Naturally if you create something ie. without disk support and then you try to run it with disk support, you can get in to this kind of trouble, but other than that I find it quite hard to believe although I have no experience on this.

By mars2000you

Enlighted (5885)

mars2000you's picture

15-08-2018, 00:59

You can have a tokenized file that is just under the maximum available BASIC memory, its ASCII version will be above this maximum and the loading will fail. Of course, the available BASIC memory can differ with or without disk support, but the 'rule' is the same (you just need a bigger program to experiment the problem when there is no disk drive).

And when I say 'just under', it's just a picture. For example, a 16kB ASCII file can correspond to a 12kB tokenized file. Imagine what happens with a 20kB tokenized file when converted in ASCII file.

By sd_snatcher

Prophet (3448)

sd_snatcher's picture

15-08-2018, 01:16

Are you sure it loads the entire text file to the memory before it starts "typing" it? Because that would be useless. It can load one char at a time, or one line at a time, without any trouble.

By mars2000you

Enlighted (5885)

mars2000you's picture

15-08-2018, 01:26

Just try with very big BASIC programs and you will see what happens. The error message would not appear if the entire ASCII file was not loaded.

And if you try saving in ASCII mode of a very big tokenized file, the ASCII file will be incomplete, you will need to create a new tokenized BASIC file with the missing part before saving it in ASCII mode (then merging on PC the two ASCII files).

By NYYRIKKI

Enlighted (5745)

NYYRIKKI's picture

15-08-2018, 01:26

Yes, I still fail to see what might be the problem... @mars2000you, can you please point me to an example BASIC program where this kind problem can be seen? I would like to investigate what is going wrong? (Naturally I can create something, but I would like to see real world case)

By mars2000you

Enlighted (5885)

mars2000you's picture

15-08-2018, 02:46

Ehmm, it seems you are right, I've just checked with an ASCII fike of 28055 bytes (and 23247 byres tokenized), no problem if I desactivate drive B, so it means that the loading/conversion(compression) is made line per line. It's the Hebdogiciel game "Super Chasseur".

However, I had received the mentioned message in the past probably because the memory was not entirely cleared. Sorry for the confusion! Also having to save in 2 parts was probably due to the same problem.

Of course, with too big tokenized files, the only solution is tape and CAS file (example tested: ASCII 33784 - tokenized 26696 - Hebdogiciel game "Intérieurs").

By NYYRIKKI

Enlighted (5745)

NYYRIKKI's picture

15-08-2018, 11:51

mars2000you wrote:

However, I had received the mentioned message in the past probably because the memory was not entirely cleared. Sorry for the confusion! Also having to save in 2 parts was probably due to the same problem.

Yes, this is very easy mistake to make... If BASIC program executes ie. CLEAR or MAXFILES command, the available memory is affected and will not be restored back to boot up defaults even if you execute NEW-command.

sd_snatcher wrote:

It can load one char at a time, or one line at a time, without any trouble.

Yes, this is actually exactly how BASIC internally "thinks" these things. Ok, naturally in real life the actual loading/saving to physical device would not be possible in such a way and this is why the individual characters end up going through file (#0) I/O buffer first. (Even if you do MAXFILES=0, there is still always the buffer #0) If you want to visualize your self, how the file buffers are actually filled & flushed, you can type SAVE"CON",A This will be effectively same as LIST-command, but this time redirected through I/O buffer.

By Uninteresting

Master (184)

Uninteresting's picture

15-08-2018, 21:07

Manuel: If your question was for me -- at least the programs in the later years were released also on mail-order cassettes (the magazine was MikroBitti), but I've also been converting games written in SVI-3x8 BASIC to MSX in the process.

By eimaster

Master (244)

eimaster's picture

24-08-2018, 17:26

Uninteresting wrote:

I've also been converting games written in SVI-3x8 BASIC to MSX in the process.

If you have uploaded the SVI-3x8 BASIC converted programs on the net, then could you please tell me how can I download them?

Page 2/2
1 |