TGB1718

Remember some games were written for the original 800 so won't run on a 130XE/800XL, there's a program (the name eludes me at the moment, but I'm sure someone will tell you), that installs the 800 ROM into RAM under the OS and allows the older games to run.

Where did you get that photo of the wife

Location ?

Just to update, copied files off the FAT32 partition, re-formatted to FAT, copied files back, all working now thanks @flashjazzcat

Thanks for the info, I'll build another card and make sure it's FAT16 and see what happens

That did cross my mind afterwards I have one issue now, SIDE3 seems to be fine, the loader now see's the card and file, CART's load .XEX load and it shows the APT and FAT partitions, however when I boot normally into U1M SDX all the partitions seem fine except the FAT partition, I can see FATFS.SYS is loading on the boot screen. U1MB SIDE PBI BIOS v.3.10, dev. 0 Ultimate clock installed FATFS v.0.87L DOSKEY: loaded 9 aliases SpartaDOS X 4.49 8-04-2020 Copyright (C) 2020 by FTe & DLT "DRIVES D5: D6: D7: D8: D9: AND DO:" D5: but when I dir DO: it says 148 Unknown File System I then installed SIDE3.SYS as per you instructions just in case it would help, but it's still the same Can't access the FAT Partition

Sorry to ask, but should I now put SIDE3.SYS on my boot drive and add add DEVICE SIDE3.SYS to CONFIG.SYS. Just thought I would add, when I tried to update using the S3loader.xex, no matter what I did all I got was "Waiting for Media" (U1M settings as advised). I have a second unmodded 130XE, I put the SIDE3 into this and it loaded just fine and updated . Since doing both updates it seems to be working, currently copying all my files to the Partitions from backups so may take a while.

Thanks @BillC I knew I forgot to mention something, pretty important that

At least my "FAT" code will work regardless of the OS installed and for the topic starter I think it's much more informative as he's obviously new to assembler, without knowing how those routines in the OS work it will still be a bit of a mystery as to how it's working.

Beat me to it, this is a better solution if CIOV is not wanted, however please remember If you use CIOV what you put in the message bytes is what will appear on the screen, writing directly to the screen will not produce what is in the string, have a look at the attached screen shot, you would have to decode the screen characters into what you want to see. 0100 CONSOL = $D01F 0110 *= $2000 0120 SOURCE = $CB 0130 DEST = $CE 0140 SCREEN = $58 0150 START LDA SCREEN 0160 STA DEST 0170 LDA SCREEN+1 0180 STA DEST+1 0190 LDA #MESSAGE&255 0200 STA SOURCE 0210 LDA #MESSAGE/256 0220 STA SOURCE+1 0230 LDX #3 0240 LOOP LDY #39 0250 L1 LDA (SOURCE),Y 0260 STA (DEST),Y 0270 DEY 0280 BPL L1 0290 JSR ADD40 0300 DEX 0310 BPL LOOP 0320 WAIT LDA #$FF 0330 STA CONSOL 0340 LOOPW LDA CONSOL 0350 CMP #6 0360 BNE LOOPW 0370 RTS 0380 ADD40 CLC 0390 LDA SOURCE 0400 ADC #40 0410 STA SOURCE 0420 LDA #0 0430 ADC SOURCE+1 0440 STA SOURCE+1 0450 CLC 0460 LDA DEST 0470 ADC #40 0480 STA DEST 0490 LDA #0 0500 ADC DEST+1 0510 STA DEST+1 0520 RTS 0530 MESSAGE .BYTE "A!!!A##########FFFF################A!!!A" 0540 .BYTE "#+ ++++++++++++++++++++++++++++++++++ +#" 0550 .BYTE "++++++++++++++++++++++++++++++++++++++++" 0560 .BYTE "++++++++++++++++++++++++++++++++++++++++"

Worst coding practice ever, one of the first things I was taught "Thou Shalt Never, NEVER, Make Direct Calls Into The OS !!!!" Always use the supplied vectors, they are safe.

Don't be so sure

If all you want to do is write to the screen, this is a more simple solution using CIOV calls and does not need a call into the OS which would not work on all versions of the OS. Ignore the line numbers, it's a partial listing using MAC/65. Should be easy to convert into whatever assembler you are using. Hopefully this will give you an idea how to Open and Close channels and send data to a device, in this case the screen. 0100 CIOV = $E456 0130 JSR CHAN2 ; CLOSE CH2 0140 JSR CHANNEL ; OPEN SCREEN 0150 LDA #MESS1&255 0160 LDY #MESS1/256 0170 JSR MESSAGE 0180 LDA #MESS2&255 0190 LDY #MESS2/256 0200 JSR MESSAGE 0201 LDA #MESS3&255 0202 LDY #MESS3/256 0203 JSR MESSAGE 0304 LDA #MESS4&255 0205 LDY #MESS4/256 0206 JSR MESSAGE 0207 JSR CHAN2 0210 RTS 1520 CHAN2 LDA #CLOSE ; CLOSE CH 2 1530 LDX #$20 1540 STA $0342,X 1550 JSR CIOV 1560 RTS 1570 CHANNEL LDX #$20 ; OPEN CH 2 1580 LDA #OPEN ; TO SCREEN 1590 STA $0342,X ; FOR MESSAGES 1600 LDA #NAME&255 1610 STA $0344,X 1620 LDA #NAME/256 1630 STA $0345,X 1640 LDA #3 1650 STA $0348,X 1660 LDA #0 1670 STA $0349,X 1680 LDA #12 ;R/W 1690 STA $034A,X 1700 LDA #0 1710 STA $034B,X 1720 JSR CIOV 1730 RTS 1740 NAME .BYTE "E:",$9B 1750 MESSAGE LDX #$20 ; WRITE 1760 STA $0344,X ; MESSAGES 1770 TYA ; TO SCREEN 1780 STA $0345,X 1790 LDA #PUTREC 1800 STA $0342,X 1810 LDA #120 1820 STA $0348,X 1830 LDA #0 1840 STA $0349,X 1850 JSR CIOV 1860 JSR DELAY 1870 RTS 1930 MESS1 .BYTE "A!!!a##########FFFF################a!!!A",$9B 1940 MESS2 .BYTE "#+ ++++++++++++++++++++++++++++++++++ +#",$9B 1940 MESS3 .BYTE "++++++++++++++++++++++++++++++++++++++++",$9B 1940 MESS4 .BYTE "++++++++++++++++++++++++++++++++++++++++",$9B

Cheap Raspberry Pi does these sort of things really well, added advantage the Pi runs Respqt too if you need it. Just power it up, log on using Putty in Windows, piece of cake no keyboard/mouse/monitor needed on the Pi. And for the Pi GUI, VNC when using running Respqt

Yes you will need some circuitry if you are using 9 pin RS232, SIO2PC which was I think the original way to connect a PC to your Atari via SIO. Attached is a circuit, you also need some software which runs from the command prompt. Also the FAQ and the SIO2PC software for the PC side The components are cheap. I have an old laptop that runs MSDOS which is the ideal environment, don't use it much these days as I have USB2SIO and SDrive-Max SIO2PC.COM SIO2PC FAQ.htm