Jump to content

xxl

Members
  • Content Count

    1,142
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by xxl

  1. lda #255 ;Check for 255 255 cmp BLSEGHEAD bne GS_ENDA cmp BLSEGHEAD+1 bne GS_ENDA ;If 255 255 not found, continue sta BL_HDR_FOUND ;Indicate header was found --- lda BLSEGHEAD and BLSEGHEAD+1 cmp #$ff bne GS_ENDA ?
  2. > But is that really useful when you can just exomize your xex ? no. > I still don't understand how to set high speed mode there are several types of turbo for disk drives, xB supports US. xHSPEED. If there is a different value than $ff, this means that the flop drive supports US and if you used xBIOS_SET_DEFAULT_IOMODULE (or .cfg) you can request communication at that particular speed. lda xHSPEED bmi no_US sta xSPEED no_US If you use AtariOS for communication, the HSPEED variable does not matter because xBIOS to read data refers to the OS and not to the hardware - it can be any device working at any speed. > Does this mean my own IRQ handler will run if set to 1 ? I have no idea what it's used for... no, if you use xBIOS_SET_DEFAULT_IOMODULE, you can use IRQ when communicating with the device. This is for advanced users - look at $D20E > xAUDCTL for advanced users, communication can affect music playback. > I wish I could remove the write to disk code with a setting in the CFG file to save some space. it does not take much space > As? for a custom I?O module, I wo?uldn't know wher?e to start for users who want to create xB for a specific device, for example, cartridges, ramdisks, etc. It seems to me that you should not change the I/O module, use that one xBIOS has after launch - you will not have to worry about turbo systems or various devices like HDD or cartridges, they will all be supported - however, the price of such a solution - you must have enabled OS ROM during communication. If you write under the 80's standards, then you have a simple .atr (Atari - peripheral) .car (Atari - cartridge) if you write under the user's "standards" from 2019 then do the .xex version for 256KB ram: D
  3. @rensoup 0EAB: A9 20 LDA #$20 0EAD: 2C A9 00 BIT $00A9 means: lda #$20 .byte { BIT $ffff } lda $00 yes, xBIOS is optimized in terms of code length and not speed of code, thanks to this it takes only 1KB with so many functions. All operations (also binary load) are buffered, it has its consequences but also advantages - let's be a binary loader with LZ4 decompressor?: stream decompresor (part of binary loader not loaded file) starts working when in binary load semgment stop adres = 0: source binary file (21 KB): 0. 2000-2005 1. Init 2000 2. 2010-459F 3. 4800-4AD2 4. 5400-8303 5. Run 5800 compreset segments (12 KB): 0. 2000-2005 1. Init 2000 2. 2010-0000 (LZ4) 3. 4800-4AD2 4. 5400-0000 (LZ4) 5. Run 5800 http://www.atari.org.pl/forum/viewtopic.php?pid=245899#p245899 if you want other I/O than SIO try your own and use: xBIOS_SET_IOMODULE (e.g. like I did with RAMCART) but you must know that this will allow you to communicate with any imaginary device but there must be AtariDOS filesystem - not Sparta, nor FAT - if you want use eg.FAT use devices that perform translation on the fly to the AtariDOS family file system (eg SIOCart , WiFiPrime
  4. Yes, we have access to the SIO device to which we transmit which song is to be played from the SD card and in what way. The sound is mixed through the AUDIO IN in the SIO slot - just like the left channel in the tape recorder. We have control over the volume balance, stop, pause etc. The SIOCarta part is a jukebox which we control using the SIO commands and the Motor Control line 🙂
  5. sio2sd + IRQ generator + SD Music player with 6bit volume control
  6. works fine: First, I want to publish the SIOCart project and then WiFiPrime
  7. xxl

    xxl

  8. I draw using the OS_PLOT function in any graphics mode (OS_GRAPHICS; x40, x80, x160, x320). the scene is drawn with vertical stripes in three steps (sky, walls, floor). The worst are the walls lying close (blocky) but it is the fault of a simpled distance calculation. 280 (x80/x48)
  9. no, there is no correction and that is why there is a fish eye effect. it's not the only simplifications ... and there will be more ...
  10. no. compressed data: 15kb decompresed: 35147 bytes so: 35147 / 55 = 639 bytes
  11. LZ4 is very fast gpl3.txt - 35147 bytes exomizer - 12382 bytes + depacker 1 page =~ 12.3 KB, decompress 128 frames (2.6 sec) deflate - 11559 bytes + depacker 2 pages =~ 11.8 KB, decompress 179 frames (3.6 sec) LZ4 - 15622 bytes + depacker <150 bytes =~ 15.3 KB, decompress 55 frames (1,1 sec) there is also a bootloader with lz4 streaming decompression test-lz4.atr test-normal.atr
  12. after loading xB, the code is relocated and modified to the appropriate disk format (sector size, which filesystem). After this step, you can change everything with files and directories - size of files, write / delete, sort, create catalogs, etc. you can even add directories that store more than 64 files - (catalog entry longer than 8 sectors)
  13. I don't think you even tried :-) I succeeded brethe.atr
  14. rename game to AUTORUN and: http://xxl.atari.pl/download/xboot.obx https://www.horus.com/~hias/atari/atarisio/tools-win32-190220.zip dir2atr -md -B xboot.obx bootablegame.atr sourcedirectory done
  15. does not change perocesor flags nor registers delay6 .byte $80 delay5 .byte $80 delay4 .byte $80 delay3 .byte $04 delay2 .byte $1a
  16. you hold the OPTION key for a long time - as you hear that the FDD reads do not hold OPTION - OPTION in xBOOT is used to bypass the the AUTORUN file ...
  17. 6502c is the official processor in 8bit atari... 65816 is an unofficial modification so if you have problems with atari software on your moded hardware, run them on the atari emulator.
  18. "one button" game. currently such a popular type for mobile :-)
  19. "Aztec challenge" was one of my favorite games. What's more ... I like today no less :-)
  20. Atari Lynx ready in 1987 sniffed the whole "Super XE Console" project drawn on a handkerchief. Suzy (16-bit custom CMOS chip running at 16 MHz) Unlimited number of blitter "sprites" with collision detection Hardware sprite scaling, distortion, and tilting effects Hardware decoding of compressed sprite data Hardware clipping and multi-directional scrolling Math engine Hardware 16-bit × 16-bit › 32-bit multiply with optional accumulation; 32-bit ÷ 16-bit › 16-bit divide Parallel processing of CPU All this "new atari" with vbxe, rapidus and so, where atari is used as a power supply board, there is no sentimental value - and only sentiment holds people at 8 bit atari. if someone wants more efficient equipment with a soul of 8 bit atari, then he should be interested in the amiga. for some programmers, 8bit constraints are a challenge and motivation for more efficient and creative work - thanks to them we have programs that could be dreamed about in the 80's on a real 8-bit atari
  21. xBoot - 384 bytes (at start, reusing it 256 maybe) xBios - 1024 bytes (1K) 2. you can boot DOS, load xB from DOS - xB loads xautorun file (your program) -- xB supports many varieties of DOS filesystem, you need to run xB to configure&relocate itself according to the preferences of the coder.
×
×
  • Create New...