Talk:BSAVE (graphics image format)
From Wikipedia, the free encyclopedia
I am still in the process of adding info and references to this page. I wrote it from scratch and from memory so I need to clean-it up some more and add other platforms and some format variation info.
I'll try to keep the references up to date. Time constraints will undoubtedly prevent me from finishing this today or tomorrow, but seems pretty complete so far.
--Bill Buckels 19:13, 23 May 2007 (UTC)
I need to add information on the BLD and PLT variations of the Bsaved image format used by VGACAD. It's hard to say how many people actually used VGACAD. But the BLD file extension is referenced all over the web, including WikiPedia.
--Bill Buckels 17:04, 24 May 2007 (UTC)
I will need to split this page into several topics before I am finished. I am not at that point yet, and need to complete the Apple II information. I work on this a little every day and leave this page in a more or less finished manner each edit.
--Bill Buckels 09:50, 2 June 2007 (UTC)
I will be finishing this over June.
--Bill Buckels 07:46, 14 June 2007 (UTC)
I have added the first part of the Commodore 128 specifications. I am currently working on this as time permits. and I will bring this to a completion point in the next few weeks.
--Bill Buckels 10:51, 22 August 2007 (UTC)
"C64's BASIC did provide a LOAD command which was intended to LOAD both binary program images and BASIC programs but this command when used in a C64 BASIC program could not be used to load binary data files like BSAVE images. This was because C64 BASIC would clear the current program from memory and automatically attempt to run (chain to) the newly loaded binary data assuming that it was program code. While this was desired behaviour for programs, using the LOAD command in a BASIC program to load binary data files like BSAVE images would cause the C64 to execute invalid instructions and probably to hang."
Not true. A non-relocating load could be specified, which did not overwrite the BASIC program in memory. The non-relocating load would reset the text pointers at CHRGET, which would restart the BASIC program. However, a flag variable could be used to detect that effect and compensate for it. —Preceding unsigned comment added by 70.228.163.254 (talk) 13:47, 18 April 2008 (UTC)

