Heaven/TQA Posted March 8, 2014 Share Posted March 8, 2014 Just tried to follow the instructions on XXLs site regarding autobook. I was under the impression that with Xbios I can boot files with lomem starting $800. But how? Does I simply copy the file on an ATR which contains Xbios & xboot? and rename the file AUTORUN? but this does not work even starting Xbios or starting xboot? Can someone help me here? Quote Link to comment Share on other sites More sharing options...
Roydea6 Posted March 8, 2014 Share Posted March 8, 2014 isn't xboot only 3 sector long. and should occupy the first 3 sectors of the atr.. And then add xbioos as the first file of the ATR. Quote Link to comment Share on other sites More sharing options...
xxl Posted March 8, 2014 Share Posted March 8, 2014 (edited) xboot allows to load program with lomem $800 (xbios - $c00, or even $0000 if you know how). just rename your program to "autorun" without extension and thats it - with xboot. no need to copy xbios to disk. here is tool to make .atr with xboot: (take proper xboot for 128/256 disk sector size) dir2atr: http://www.horus.com/~hias/atari/#tools-win32 > And then add xbioos as the first file of the ATR xbios does not need to be first file... may be even the last in root catalog (128 file in catalog on BiboDOS/TopDOS supported) Edited March 8, 2014 by xxl 1 Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted March 8, 2014 Author Share Posted March 8, 2014 thx XXL... so actually doing this: Usage: dir2atr [options] file.atr directory If you don't specify the size (in sectors), dir2atr will automatically calculate it so that all files in the directory will fit into the image. If you set the image size to 720 sectors (either SD or DD) or to 1040 SD sectors (the 1050 "enhanced" density format), the disk image will be created using standard DOS 2.x format, otherwise dir2atr creates an image in MyDOS format. Note: in MyDOS format dir2atr also descends into subdirectories. Options: -a enable MyPicoDos 4.04/4.05 autorun mode Note: only a single file may be present on disk (in addition to PICODOS.SYS and, optionally, PICONAME.TXT) which will then be automatically loaded on boot. -d create a double density (256 bytes per sector) image (default is single density, 128 byte per sector). -m create a MyDOS image (use this option to create a 720 or 1040 sectors image with subdirectories). -p create a 'PICONAME.TXT' (long filenames for MyPicoDos) in each (sub-) directory of the image. -P like '-p', but the extension of is stripped from the long names in PICONAME.TXT. So, for example a file 'Boulder Dash.com' on your PC will show up as 'Boulder Dash' in MyPicoDos. -b <dostype> create a bootable image. -B <filename> load boot sector data (384 bytes) from file. (-B option?) Quote Link to comment Share on other sites More sharing options...
HiassofT Posted March 8, 2014 Share Posted March 8, 2014 (-B option?)Yes. And: RTFM, it contains an xbios example :-) so long, Hias Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted March 8, 2014 Author Share Posted March 8, 2014 Hias.... I tried but it hangs reading sector 361... Quote Link to comment Share on other sites More sharing options...
xxl Posted March 8, 2014 Share Posted March 8, 2014 attach a atr file or send it to me via pm Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted March 8, 2014 Author Share Posted March 8, 2014 ok...works... forgot that I need to rename the file AUTORUN Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted March 8, 2014 Author Share Posted March 8, 2014 Just to be sure... XXL... When appending many parts of a demo... All parts are started with INI segment while the last part with RUN. Is there anything we have to know when exit one part with RTS... Will xboot continue? Quote Link to comment Share on other sites More sharing options...
xxl Posted March 8, 2014 Share Posted March 8, 2014 yes, but there's better way. you can save demo parts as files and: xBOOT_LOAD_FILE equ $5f1 ldy < fname ldx > fname jmp xBOOT_LOAD_FILE fname .byte c'NEXTPARTCOM' ; 11 chars ATASCII 1 Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted March 9, 2014 Author Share Posted March 9, 2014 Cool. Thx. Quote Link to comment Share on other sites More sharing options...
Creature XL Posted March 19, 2014 Share Posted March 19, 2014 AS I fiddled with XBIOS the last days... When I name my program "AUTORUN" it gets laoded, but "xBIOS" is not there. When I copy xbios to the ATR and name my program "XAUTORUN" it works as (I) expected it. I'll check at home if I rember that correctly. Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 23, 2014 Author Share Posted April 23, 2014 Arsantica uses xBOOT and it works flawless. most issues I had were trashing stack and NMI conflicsts with the SIO OS routine. Next production will use xBIOS plus loading music... is RMT stable? and does RMT need to run in immediate VBL? (546,547)? or when OS gone standard NMI? does anyone has experience with RMT and xBIOS? Quote Link to comment Share on other sites More sharing options...
xxl Posted April 23, 2014 Share Posted April 23, 2014 for now RMT player for xB is not stable, much better solution is using DeltaMusicComposer, especially with player that uses "xAUDCTL" xB variable for additional sound effects and not to interfere with the I/O. 1 Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 24, 2014 Author Share Posted April 24, 2014 for what I hear the youtube video it is enough at the moment... better than silence ;=) thx, XXL. just thinking of switching from xBoot to xBios for the final version of Arsantica Demo. Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 24, 2014 Author Share Posted April 24, 2014 XXL... which sound channels did you used? Quote Link to comment Share on other sites More sharing options...
xxl Posted April 25, 2014 Share Posted April 25, 2014 1&2 use DeltaMusicComposer Player... tested Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 28, 2014 Author Share Posted April 28, 2014 got everything working with my own simple player (Delta to be tested this week). It is really cool to have sound channels 1+2 free. btw. on a stereo machine in theory I could use 2nd pokey for complete 4 channel track? e.g. patching RMT player to play only on the $d21x pokey? Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 28, 2014 Author Share Posted April 28, 2014 ah. one thing... good help is exporting simple format in RMT in ASM format. I was ticking the export feature "taking notes from freq. table". with that options I could directly paste that values into POKEY. Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 28, 2014 Author Share Posted April 28, 2014 XXL. one further question... where can I grab the event of "next sector" was loaded? is there any counter I can compare? need that for Arsantica loader. the demo now runs completly with xBIOS instead of xBOOT so it could run from hard disc. 1 Quote Link to comment Share on other sites More sharing options...
xxl Posted April 28, 2014 Share Posted April 28, 2014 xDAUX1 equ xBIOS+$3fe xDAUX2 equ xBIOS+$3fd sector counter with files ? ... better take current file offset by: jsr xBIOS_GET_FILE_OFFSET reg Y/X/A - current offset Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 28, 2014 Author Share Posted April 28, 2014 want to replace the sector counter with something "loading action". offset would work better as it is not depending on sector size etc. how would you indicate device independend how long it takes to load? Esp. Arsantica would need info for part1. Part2 and part3 I can wait until the scrollers are run to their end. Quote Link to comment Share on other sites More sharing options...
Heaven/TQA Posted April 28, 2014 Author Share Posted April 28, 2014 thx XXL.... xdaux1,xdaux2 helped here... I am just checking if they changed to previous checks and if so I am decrementing the sector counter... Quote Link to comment Share on other sites More sharing options...
8bit-Dude Posted October 12, 2020 Share Posted October 12, 2020 Hey Guyz! I have decided to replace DOS with XBIOS in 8bit-Unity. I was able to produce a disk that runs my CC65 executable, and access the XBIOS functions for file loading. But I noticed something very strange with my code, which previously used SHADOW registers for most functions: PEEKING the joystick registers $0278 / $0284 does not work. PEEKING the associated HW registers $d300 / $d010 also does not work. POKING colors into the color registers $02c4 - $02c8 works, but after about 5 seconds delay. POKING the associated HW registers $d016- $d01a does not work. I guess that XBIOS disables the normal Shadow/HW registers associations... Could someone tell me how to get Joystick/Colors (and more I am sure) working again? Thanks in advance! Quote Link to comment Share on other sites More sharing options...
rensoup Posted October 12, 2020 Share Posted October 12, 2020 perhaps you disabled the OS in the xbios config file (PORTB value) ? .byte $43 ; config for v4.3 version .byte c'LAUNCHEROBX' ; autorun file fname .byte >xBIOS_BASE ; xB adress for relocator .byte >(xBIOS_BASE-$100) ; xB buffer adress for relocator .word $02e2 ; INITAD .word $02e0 ; RUNAD .word $0000 ; custom I/O module - $0000 means use internal xB SIO .word $0000 ; relocator for custom I/O module .byte $ff ; PORTB - you can't swith off BASIC this way .byte $40 ; NMIEN - config at start .byte $80 ; IRQEN - config at start 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.