a8isa1

I found an image of Monkey Wrench II for 800. I composed an Atarimax 8mbit with MW2 in banks 0 and 127. Works. Both MW1 and MW2 work in my 800 with the same caveat. Since my last post I've learned the pin on the card edge that I've been covering corresponds to RASTIME on 800's cartridge port. Can someone explain why covering this pin allows the cartridge to work? It's easier to cover both RASTIME and CCTRL with a single piece of tape. CCTRL isn't needed in this case. No bank changes occur. -SteveS [EDIT] My bad memory (or electronics dyslexia) has kicked in again. I disassembled an Atari cartridge to determine the pins I've actually been covering. They are pin A - R/W Late 1 and pin 1 - Phi2, as described by the "Official FAQ".

if you get a dance mat working with track 'n field please post a video of yourself playing it. I need a laugh! -SteveS

Survey choices don't fit my situation. I have osteoarthritis in my left thumb and can't hold or stabilize an Atari style joystick. Right thumb is currently not nearly as bad off. I think I could use a gamepad if the D-pad was on the right-hand side. Would be useful if I could use whichever button for trigger. Finger fatigue is also a problem but not painful like my thumbs. I can't simply switch hands using a two button joystick. -SteveS

Awesome! I don't know how the original looks but I love the way the lighting came out in your conversion. There's an expression, "can't see the forest for the trees". I'd almost swear I can see individual trees in your image. -SteveS

I thought I had done this some years ago but it was Monkey Wrench 1 that I managed to get working. I don't recommend trying this but this is what I did. First I built a 1 mbit image with Monkey Wrench in bank 0 and also bank 127. Both banks because I can never remember whether I have the new or old version of Atarimax's flash cartridge. After flashing the cartridge I gave it a try. It didn't work. At some point I came to the solution of covering two *fingers* of the card edge. I think these would be B-Phi2 (right most finger, forward edge, as the cart sits in the 800) and the opposing finger (CCTL, cartridge control) of the other side of the PCB. I cannot remember why this works. I tried it again just last night. Brown BASIC cartridge (Rev A) in left slot. Atarimax 8mbit cart in right slot. That procedure did not work with MW II. I'm wondering if I have an image meant only for XL/XE When I first did this I had only the 800. Had to use the hot swap method to reprogram the Atarimax cartridge. This takes many, many attempts usually. Now the Maxflash USB programmer exists, though I don't own one . I do have an 800XL with QMEG 4.04 in it. I can boot to the selector screen and get to the monitor where I can disable the cartridge (command - D580;1). From there I can reboot and run the ATR based flashing program. If someone has a confirmed Monkey Wrench II (for 800) image I'd like to give this one more try. I'd just want to see it on real hardware (for nostalgia purposes). -SteveS

You have reminded me I had started another attempt at this rendering. I think this one is better. -SteveS a8isa1_gort2.xex

Which test do I need to install to examine high speed SIO? Do I need to enable something in the sketch? -SteveS

Classic SDrive only worked with divisor 3 and lower if Hias Reichl's firmware is installed. That firmware had been available as early as 2009 IIRC. Paired with Hias' MyPicoDOS S0 the two items together work great. No OS mod or patch needed to load games at 128kbits even on good old 800. With MyPicoDOSS0 you don't need to use the SDrive configuration program to set the speed. MyPicoDOS does the setting for you to run with divisor 0. (There's also MyPicoDOS S1 which uses divisor 1). Come to think of it. Hias' XL/XE OS HISIO ROM patch works at divisor 0 as well (and not just with SDrive). so it's WIN WIN WIN! Three wins! Thanks Hias!

Thanks, CharlieChaplin! The green line I believe is an old blunder in my shell script that I forgot to remove. In the same script I noticed the saturation (mencoder filter hue=0:1.75) is too high, a change from a test that I forgot to restore. I generally use 0:1.5 for NTSC and 0:1 for PAL. I still don't know if people with real NTSC Ataris and original output can see the colors of the video conversions. They didn't work on my only two remaining CRT TVs. Works great on my scan converter. I don't have any video upgrades or other monitor combinations. [EDIT] I corrected the script but no difference so I don't know what is causing the green line.

Somewhere in the 60 Fps for SIDE 2 thread (I forget the exact name) are instructions on how to do conversions in Windows. The last three utilities that you listed above were written by Phaeron. The Source codes are available somewhere in that same thread. -SteveS

I usually run the following commands as a shell script. #NTSC mencoder -nosound -of rawvideo -ovc raw -vf hue=0:1.5,scale=77:192,expand=160:192,format=yv12,harddup,swapuv -sws 6 -ofps 59.9227 'my_video.mp4' -o my_video.raw ffmpeg -i my_video.mp4 my_video.wav sox my_video.wav -C 0.5 -c 1 -b 8 -r 15700 my_video.u8 gain -l 10 ./encvideo60n <my_video.raw my_video.mov ./encaudio60n <my_video.u8 my_video.aud ./mux60n my_video.mov my_video.aud my_video.dd #PAL #mencoder -nosound -of rawvideo -ovc raw -vf hue=0:1,scale=77:192,expand=160:192,format=yv12,harddup,swapuv -sws 6 -ofps 49.86 my_video.mp4 -o my_video-pal.raw #WAV file is the same for PAL conversion #ffmpeg -i my_video.mp4 my_video.wav sox my_video.wav -C 0.5 -c 1 -b 8 -r 15558 my_video-pal.u8 gain -l 10 ./encvideo50n <my_video-pal.raw my_video-pal.mov ./encaudio60n <my_video-pal.u8 my_video-pal.aud ./mux50n my_video-pal.mov my_video-pal.aud my_video-pal.dd I never tried to automate the process. I always need to play with scale, crop, and expand filters of mencoder. I re-run sox manually to see how much clipping occurred. I can lower the gain but this also reduces the average volume level. If the audio is too dynamic I pull the WAV file into audacity and use compression. I don't know if this is ideal but usually it's once and done. Reencode. -SteveS

Your comment puzzled me for a bit. I guess I need to pad the end with zeros so the player stops (on an error). -SteveS

Awesome! How does the conversion look with PAL? I don't have any PAL gear. -SteveS

Data is raw sectors for a CF card. No MBR. No partition table. The ".dd" extension just reminds me it's a raw image and to use linux utility dd (to write to removable media) in raw mode. Sorry, I probably should have used ".img" instead. In linux the command to fill the CF card is something like this: dd bs=512 conv=notrunc if=twerking_blocks.dd of=/dev/sdb ; my media reader This will essentially wipe what's on the CF card. Best to commit one just for movies. I no longer remember how to write to a CF card from in raw mode using Windows. Sorry. I know there are players for internal/external MyIDE and SIDE. Can't remember if there's one for MyIDE II, Incognito or KMK IDE+ 2.0. -SteveS

Not sure I got the aspect ratio right. Don't expect much. Canvas is 70x192 I think. twerking_blocks

I forgot to mention that I don't have a proper driver for SDX. For this reason JIFFY.SYS is a prerequisite and should be installed in your CONFIG.SYS (or in CONFGI.CFG or in CONFIG.CFG for ebiguy's Atarimax 8mbit cartridge build). -SteveS

Some years ago I took Hias Reichl's I2C driver (for PIA pins), patched it to pass pin data, pin mask, and buffer information and appended it to some utilities which I wrote in the Action! language. This allowed me to connect an Arduino add-on DS1307 RTC module to my Atari and use it with SpartaDOS, SpartaDOS X and Bewedos. Perhaps some will find the utilities of use. Notes: SETDS7.COM takes the time and date from the DOS system clock and sets the RTC. Only DS1307 or DS3231 RTCs are supported. DS7TIME3.COM performs the reverse function. Sets the system time from the RTC. CLOCK2.COM is a digital clock display. It reads data directly from the RTC . CLOCK3.COM is the same but adds a temperature reading. This is a feature of the DS3231 only. I2CSCAN.COM is a general purpose utility. It looks for I2C slaves connected to Port A I/O pins. Any pin can be SDA and any other pin can be SCL. Only 7-bit I2C slave addresses are supported. Hopefully I'll re-find the sources soon. Here's a quick demonstration. Sorry for the poor quality of the video. I was holding the phone with one hand and typing with the other. Files SETDS7.COM CLOCK2.COM CLOCK3.COM I2CSCAN.COM DS7TIME3.COM

A bit late to respond because I was confirming the version of BBSB that remowilliams posted here and also the one in Kheffington's disk set (files may be one in the same) both run on my 800XL with Rambo XL loading from SDrive-MAX. I'll extract the files from the ATR (if I am able to do so) and see if they are the same. -SteveS

I came up with a workaround. It's a bit laggy but it does what I want. Example: File ACT.BAT ACT ECHO RESTORING COPY F:ACT.SAV O: SET CAR=O:ACT.SAV CAR ECHO ARCHIVING COPY O:ACT.SAV F: -SteveS

Sounds workable, though I know nothing of the inner functioning of SDX or any of the languages. I hope you can make it work. The ability to pop to the SDX CLI and back would be quite convenient. -SteveS

I believe the answer is probably NO but is it possible make what is commonly called the *MEM.SAV* feature work between multiple language cartridges and across cycling power OFF/ON? I tried to do the following: In CONFGI.CFG SET BASIC=F:BASIC.SAV ; for Atari BASIC then I created batch files like the following: ; for Action! cartridge SET CAR=F:ACT.SAV ACT CAR and ; for OSS Integer BASIC cartridge SET CAR=F:INT.SAV INT CAR However each time I invoke a batch file the language boots with a clean session instead of restoring an old one. This ability isn't terribly important. It only occurred to me to try it some minutes ago. Something fun to do (if it worked). -SteveS [EDIT] Oh! The ACT.BAT file does work! The INT.BAT doesn't. I wonder why.

Thanks, Atari friends! -SteveS

sorry, I meant SPIFFS was empty during my test. I have an appointment with the cardiologist so further testing will have to wait. I find out today whether I have a problem that needs immediate attention or if it's just something that needs watching. I don't have a USB to serial adapter so no direct means to see your debugging output. Perhaps I can rig something with a Raspbery Pi later. -SteveS

During the video scan Wi-Fi was in spiffs. moving the program externally allowed me to run the test and detect my routers. -SteveS

- I left spiffs empty - loaded scan Wi-Fi externally (sdrive-max) - disconnected sdrive-Max - connected #FujiNet which is was powered - press the key to rescan -SteveS