Jump to content

cathrynm

Members
  • Content Count

    73
  • Joined

  • Last visited

Everything posted by cathrynm

  1. I have an old-ish Samsung TV, and if I plugin to the video connector without XEPVHOLD the screen chops off the bottom two lines and the right two characters, and XEPVHold fixes the bottom two lines, but the right two characters are still chopped. I have a retroTink to HDMI and the same monitor, and that is the same vertically, but I get most of the 80 characters on screen with the same TV only losing a few pixels on the 80th column, and this for me is mostly useable. I do have a cheap USB video/Svideo recording dongle and I'm unable to get it to work at all with XEP80. I tried Pal Mode and NTSC mode, and nothing works with that. This thing has zero documentation at all, so I don't even know if it's supposed to work with PAL. I might try the settings above, but not optimistic. I was hoping there'd be some kind of PAL to HDMI dongle out there on Amazon that might work and show all the lines, but so far my experience has been that this signal is too weird for the one I have. How did it ever ship like this? I suspect engineering at Atari was getting sloppy in the Tramiel era.
  2. "WARNING: There is a bug in SIO that causes incorrect actions when the last byte of a buffer is in a memory address ending in $FF, such as 13FF, 42FF, etc." I saw this in the Atari OS manual (which I have my original printed copy of). It says 'íncorrect actions' but I have no idea what that is. Is irritating to avoid this.
  3. Oops, well, that's sillier than I thought. There's not a lot out there on SIO. I google this, and most of the results are you, asking questions about it.
  4. Trying to understand, why is there both ddevice 0x71-0x78 and a unit # 1-8? If ddevice= 0x71 unit= 3 -- is that N3? But what about ddevic 0x73 and dunit=1? Does unit take precedence? The examples I looked at all use 0x71. OS.dcb.ddevic=0x71; OS.dcb.dunit=unit;
  5. Did you modify the relocator code in the driver to relocate all the jmp/jsr to be lower? I speculate, maybe if you set memtop to be the top of the place you wanted it to be, loaded the driver, then put memtop back, it would relocate itself lower in memory? (This would be massive hacky though.) Best to build from the source instead.
  6. Wouldn't be that much code change. It looks like it needs MADS and some atcompiler thing, which it looks like it builds itself. Probably more work to get the build env setup, than actually write the code. And I see why XIO 24/25 aren't doing anything in xep80handler.s. That'd require 'figuring out' looks like. cmd18: cmd19: rts
  7. I give the altxep8*.sys drivers credit for opening my eyes about this hardware. It has potential to be 'actually okay' for tinkering with fujinet commands from SPARTADOS, fussing with files and disks Would an updated Spartados Driver allow that EDX editor to work on XEP80?
  8. Thanks for this, I understand now much better what's going on with SDX. I suppose loading to memtop, not an actual bug with altx80*.sys because the original driver does this, but I get now why SDX has its own XEP80.SYS.
  9. Oh I see. You're right, if I boot from Altirra disk it resets fine. All this reset trap handling I've never really understood about Atari 8bit. Not sure what's going on with SDX. On mode changing, I was just looking that up. This stuff is in an XEP80.DOC file that's on the original disk that comes with XEP80. I'm not sure, but maybe this is a driver bug? For me these are working on the original XEP80 disk but not from the Altirra additions disk. For 80 to 40 XIO 25,#1,12,0,"E:" 40 to 80 clear XIO 24,#1,12,0,"E:" 40 to 80 no clear. XIO 24,#1,44,0,"E:"
  10. Oops, sounds like those guys have "Poke 766,1" set. Someone will have to update their code.
  11. I have another one. This is with the altxep8u.sys driver though it's not related. On a real XEP80 a DEL or DELCHR will cause the logical lines to be shortened if there are only spaces to the end of the line. This code on a real XEP80 shows a row of 0's on the right side as it prints spaces over the subsequent characters, and then prints a delete on the top line. What happens then is the logical lines is only the top line now, and the chr$(156) on the next line deletes only the empty line, not both lines. On Altira it shows nothing because the logical line is still two lines high. 5 POKE 82,2:POKE 83,79:PRINT CHR$(125); 20 FOR N=0 TO 3 30 POKE 85,70:POKE 84,N 40 PRINT "012345678 0123456789"; 50 POKE 85,71:POKE 84,N 60 PRINT " ";CHR$(31);CHR$(29);" "; 70 POKE 85,72:POKE 84,N 80 IF N<2 THEN PRINT CHR$(126); 81 IF N>=2 THEN PRINT CHR$(254); 90 POKE 84,1+N:PRINT CHR$(156); 110 NEXT N And one last thing, far as I know of. System reset on altxep8u.sys returns the atari to 40 column mode. with xep80.sys that comes with spartados, the Atari stays in 80 columns. Not sure if this is intentional or not. LATER NOTE: And I see, the original atari autorun.sys does reset to 40 columns on system reset. Maybe this is arguably more correct?
  12. Mostly I'm distracted these days by regular paid employment. I'm getting interested in Atari/C64 again these days, I think maybe mostly due to Incognito + Fujinet, but I only have time for tinkering really.
  13. Thanks, this isn't specific to altirra or the emulator, but the altxep8u.sys version I have doesn't seem to be obeying the poke 766,1 flag on either. When I do a listing in basic with an up arrow character in a string, it does this. I thought I got the most recent version of this, but posting these file lengths I'm using to check.
  14. I've been playing with an XEP80 I got from Best. This looks to me like a difference between Altirra's xep80 emulation and the real thing. Both cases, I'm running the altxep8u.sys driver from the additions.atr disk. That the real XEP80 inserts a line break only when drawing into the far right column on the last line of a logical line block. 10 POKE 82,0:POKE 83,79 20 PRINT CHR$(125); 30 FOR N=1 TO 8 40 PRINT "NOGAPSBETWEENLINESONREALXEP80"; 50 NEXT N 60 FOR N=0 TO 5 70 POKE 85,79 75 POKE 84,N 80 PRINT "U"; 90 NEXT N
  15. Should it ever run config if a cart is present? Wouldn't the natural flow with a cart be, that you'd load a DOS or maybe your 'micro-config' with no UI, and then you'd launch proper config when you type 'DOS' from Basic, like it does for dup.sys? config is closer to a dup.sys than it is to dos. If the cart doesn't have a way to load dup.sys, then it just has to deal with what your micro-config offers as far as drives.
  16. For server-side Atari 8bit, R: and its 'concurrent mode' is kind of screwy, limited by its original design back in the 1980's. I don't know, is there a way to fix R: so it'd just ignore the concurrent mode calls and work normally? I think so, but as Thom often says, someone will have to do that work.
  17. So something like this would work then? Maybe in the future, we don't need D1: anymore? SET PATH=N:/SD/;N2: NCD N2:TNFS://RASPBERRYPI/Games/ BURIEDBU On my Incognito, I'm kind of getting settled in with SpartaDos, which has pretty good memlo. Except right now I'm at my father's house, where I only have a 48K 400, so maybe, though this keyboard is such a pain I'm not doing a lot of Atari command line.
  18. Running config from SpartaDosX worked for me. I was trying to go all command line, but what went weird for me is that although FLS was working fine from DOS2.5, it was acting weird from SpartDosX. I can list a directory of the root of a, err, host, but some extra garbage character was getting into the command line that caused it to break if I tried adding a path. DOS2.5 it's fine though. I think it's something on the 6502 side, but I looked at the source, but didn't see anything obvious.
  19. I was running APE to load files from my laptop, and just noticed it never gets to Ape's R:, whatever I seem to do. I don't actually have a real dialup modem hooked up these days of any kind, so I don't actually need that. I was just going back and forth to see how Fujinet/Ape compare with R: really.
  20. Is there a way to get to Ape's R: driver with a Fujinet? I have Ape 3.0.15. Well, actually, if I turn Fujinet off with the switch, I can get to R: on Ape, but then I lose the rest of Fujinet.
  21. You should be able to simulate the Atari cassette recorder's both tracks (audio and digital data) with a CD-player by recording the audio on one of the channels (say left channel) and the digital data on the other channel (say right channel). Then you just need to feed the audio out left channel into the SIO audio in line and the audio out right channel needs to be converted (and amplified) from 0.. 1Vpp to 0..5V DC and fed into the SIO Data In line. You could record the CD in such a way so that the audio playback rate (150kb/second) produces a 600bps equivalent data output in the conversion circuit for the data and audio normally (on the left channel). Then you could use the MOTOR control line to set CD to start playing current track and DATA OUT line to seek next track in a loop through all tracks on the CD. Some programs may need to be modified to use MOTOR/DATA OUT properly. For new custom programs, they can use the SYNC marks put on the CD (via location 53775) and take advantage of the CD features for audio w/o loading any programs from it. The hardware should work with any CD player with stereo audio outputs. I guess if you play the mono CDs on a stereo speaker system, the right channel would just cause some clicks at end of audio tracks or phrases. Yeah, this would be a fun little project. I suppose it's also be possible to play wave files off of an SD card or something like this, but I kind of see the retro-factor in having a physical CD version of some of those old Atari tapes. It provides a straightforwards way to backup -- audio to audio. Me, I never actually owned any of the educational System tapes. I assume when they reach the end, they prompt you to rewind? I guess there's no way to detect this, and the player just has to push a button to restart the thing. Or when the Atari goes 'Bleep, bleep -- motor on' then it knows to rewind? And just 'motor on' means continue on the current tape?
  22. Yeah, this was a cool feature. I've never seen Ape or any of the emulators can simulate audio from the tape. You just have to buy a tape drive and play these with real hardware.
  23. What about... 1. On the SIO bus. No-solder install. 2. XEP-80 like driver. 3. Pass through for Atari video output. 4. Overlay 80 over 40. 5. SVGA output.
×
×
  • Create New...