Jump to content

carlsson

Members
  • Posts

    18,976
  • Joined

  • Last visited

  • Days Won

    53

carlsson last won the day on January 7

carlsson had the most liked content!

About carlsson

  • Birthday 04/08/1975

Profile Information

  • Gender
    Male
  • Location
    Västerås, Sweden

Recent Profile Visitors

85,875 profile views

carlsson's Achievements

Quadrunner

Quadrunner (9/9)

26.3k

Reputation

  1. There also was Austro Comp. I think the different compilers supported different subsets of instructions and variable types, so the choice of compiler might depend on your program as well.
  2. My comment was regarding Blitz BASIC, not the JavaScript version of MOSpeed. Both of us posted the very same minute.
  3. Last year, I learned that Sega had ongoing plans to make a home computer, the SC-3000 when they found out that Nintendo was about to release a video game console, and reworked the SC-3000 hardware (which indeed origins from the same reference platform as the ColecoVision, Sord M5 etc) into a console of their own, to be launched at the exact same day as the Famicom. Actually the SC-3000 was launched at the same time.
  4. Perhaps it comes with a hefty runtime environment, and it compiles down code to calls into the runtime?
  5. It sounds like you had a keyboard issue, as I can't imagine the emulation of C64 BASIC to be that poor that it mixes up less than and greater than.
  6. P-Code is a kind of bytecode, an intermediate format that is interpreted, rather than directly to assembly code. I have never used Blitz so I can't tell how effective it is, compared with other C64 BASIC compilers. If you like to spend some money, you can buy a license of Vision BASIC. If you like to tinker with free stuff, you can try MOSpeed. You might also try another programming language like Turbo Rascal Syntax Error or perhaps some C compiler, e.g. cc65 or which other compilers are out there today. Now, I know that it is quite a far step from BASIC but if you are slightly handy in programming and want a good deal of speed, those are some of your options.
  7. Also, the Atari 2600 has 128 colors in NTSC, 104 in PAL (and 8 in SECAM), compared to the Intellivision and ColecoVision which both have 16 colors, though slightly different palettes. That means even if those had the ability to change color per scan line, you could not get quite as smooth color fades as the 2600 can. Technically, I believe one of the differences between the TMS VDP in the ColecoVision and the STIC in the Intellivision is that you can address the VDP at any time (at least when interrupts are disabled), but changes will take place at next vertical blank, while the STIC can only be addressed at vertical blank.
  8. The command line tool "tmscolor" takes a BMP as input and generates ColecoVision graphics as far as it can. Regarding your question on colour resolution, I believe for character mode it is 1 fg + 1 bg per cell just like ZX (but weird grouping of 8 characters at a time sharing both) but in bitmap mode you get higher colour resolution.
  9. Atari 8-bit: Diamond Mine - 2 min. Apparently the graphics for this game were designed with NTSC artifacting in mind, and thus it looks less pleasant on PAL. Combined with other factors, I didn't play more than that, and instead concentrated on sleeping and programming.
  10. If I understand the instructions correctly, you should create a file called AUTOSWAP.LST inside the folder with your VIC-20 software. That file should in its turn contain the names of the D64 images you want to swap between - in this case MICROSPEC-VIC-DATA-MANAGER.D64 and BLANK.D64. However you might want to move those files to a folder of their own so you still can access all the other D64 images in the same folder. DATA-VIC is the name of the loadable program on the disk image, and has no relevance when it comes to the swap list, since the list operates on disk images, not individual files. Most use cases of the autoswap list and the prev/next buttons would be multi disk games which prompt you to insert the next disk, but it could be used with data disks too. What I wonder about is if the autoswap feature is enabled if you mount and load a program from the FB20/FB64 browser, or if you have to do it manually using the buttons for the feature to work. As I mentioned, I have never tested out this functionality. The D64 image I posted above should already be setup for a register, so you don't need a blank disk. Rather you could treat this D64 as a semi-blank register disk, which you could duplicate if you need more than one register, instead of using the built-in function to format a new disk and install itself. As noted, B-P should work but unsure about B-A, which is the older syntax for the U1 command to allocate single blocks on the floppy disk. Again you might want to create a setup containing the SD2IEC (temporarily set to device 9) and a real 1541 which you transfer the program onto, in case the SD2IEC isn't compatible enough.
  11. Anyway, I made a quick and dirty conversion of intybasic-mode.el into cvbasic-mode.el, and for testing compiled one of Oscar's sample programs and verified in emulation that it runs. It seems CvBASIC + gasm80 have quite a few less arguments that can applied than what IntyBASIC + as1600 have, so a few of the settings in this mode are bogus for the moment being. Yes, you need to have Emacs 22.x or newer installed in order to use it. cvbasic-mode.zip
  12. Which is the recommended extension for CvBASIC programs? I tend to use .BAS for IntyBASIC though I know that is a very generic extension. Perhaps one can use .BAS here as well, and just set up the environment to handle those as required. Also, are there any command line settings for verbosity of the compiler and list file of the assembler? I didn't find neither.
  13. 685 pts. I managed to rescue three diamonds at best, then my body told me this is not a game I should play. Maybe I'll try again later.
  14. I had a look into VIC Data Manager. The original disk image has some kind of marker on every block that is not used by the program or the SEQ file. I tried to create a blank D64 image and copy the two visible files to it. Still it wouldn't let me store any records on the program disk. After going through the program, it seems to use Block-Allocate (B-A) for individual blocks, that don't show up in the directory and which won't affect the number of blocks free. Actually if the validate command worked (which we by now know does not work on SD2IEC type devices), it likely would wipe all records allocated in such way. What is more interesting is that if you create a new disk, which could be done on the SD2IEC by setting up a disk swap list (*), the program formats the disk, allocates blocks and saves itself to the new disk, so you can load back the program from the data disk. The SEQ file seems to be generated as you go along with adding records, as a side file to the register. The program also uses B-P for setting the buffer pointer. A few days ago, I thought that the SD2IEC firmware emulates nearly all of the logical level 1541 commands, and it was just CPU and RAM/ROM emulation that it doesn't do, but the fact that validate fails, makes me worried that commands like B-A and B-P inside a D64 image may screw up as well. Someone would have to verify if those actually work, otherwise it is a course in futility trying to make it run from a D64 mounted on a SD2IEC. What I did was to load the program in emulation, swapped to a blank D64 and let the program format it and install itself. I used the maximum 9 fields, which you obviously have to define before you can format the disk. (*) I've never done this, so someone else would have to explain how to create a such list for the buttons to work. Rob already has a blank D64 image which he can duplicate into multiple of course, but I understand it needs to be in the swap list. vic-data-manager2.d64
×
×
  • Create New...