9640News

Have you connected to your router and are you then able to see the attached PI? That will give you the ip-address:port where it is located. If it is not displaying on the router, and if you are using WIFI, then you likely are not using proper credentials on your PI configuration.

I'll be looking for one, maybe more, as well.

Thanks. It wasn't that hard to do with the original extended basic program having data statements and values instead of unprintable characters. This is probably the first time I have used the MATH XOP's in a program in 30 years. I did see something if there is room in the XOP, an additional opcode I would like to add. I was pointing to a wrong buffer converting the last math command back to an integer and the sounds were playing at the wrong speed. I had to add some debug code to see why the notes were playing too long.

In an earlier post in another topic, I took the Extended basic example code for the AXELF theme song and converted it to MDOS. Source code is provided for anyone wanting to see the MDOS code. To be noted, extended basic uses duration in milliseconds while the MDOS XOP's use 1/60th's of a seconds for duration. Thus, I used the MDOS Math XOP's to convert the duration to floating point, divided by 1000 to get the decimal portion of time, then multipled by 60 to get the number of 60th second intervals all in floating point. Then, converted that back to an integer to call the sound routine. Another sound routine checked to see when the current sound was completed before playing the next array. Enjoy, and feel free to use the code base to convert any other music/sound files to MDOS. Beery AXELF-MDOS.zip

I still have my X10 serial unit around here somewhere. I actually switched pins 2 and 3 on it and connected it up to the PC at one time.

Can you check to see if the email portion of the website is actually sending and receiving email? I had issues in the past with the Geneve MDOS conversion of Stuart's browser.

Yeah, I think a couple of those pages are within a handful of bytes. Do you have the LINK script with the extra EVAL statements at the end that shows where the page? You can use this link to get the updated LINKer command file at ABasic/!ABLINK.txt at main · BeeryMiller/ABasic (github.com) or the info you need is shown below. EVAL P7ENDB From file 166\CALL2-SRC EVAL P7ENDA From file 167\SYMBOL-SRC EVAL P6END From file 165\CALL1-SRC EVAL P8END From file 168\NUD2-SRC EVAL P2END From file 162\NUD1-SRC EVAL P4END From file 164\CMD-SRC

@InsaneMultitasker Hmm. I am wondering if it may have something to do with having two or more files open simultaneously and either getting an error, out of diskspace, or closing one file but not the other????

@InsaneMultitasker Let me know with file updates when you are confident you have everything worked out. I wonder if you format a disk as DS/SD then format SS/DD, then update sector 0 so the disk thinks it is DS/DD whether that will be sufficient to create a "bad" disk when it tries to write a file beyond sector 720. Beery

I thought that was what Dan was referencing as far as the "disk" that was sold. JumpBoot was just a specially formatted disk with interlace/skew that could be created with HyperCopy.

All Jerry did was have a disk with a modified skew and an interlace of one where system/SYS was written. I wrote about that in 9640 News at the time. You could create your own disk with HyperCopy.

Mayhem was quoted in the comments as saying it did nothing.

Reading the comments from the posted video on youtube, that extra bit does nothing.

Yeah, CYA can mask the AUTOEXEC loading as you can specify the device name and redefining the SCSMAP configuration can impact device number as well.

I believe back 2+ years ago, I posted the wrong source files and the wrong LOAD-xxx files for SCSI and IDE. Check these updates out: LOAD-IDE LOAD-SCS

OK, this appears to confirm the IDE and SCS loader files need to be updated.

OK, right after MDOS has been loaded by the LOAD-xxx file off the device, and right before operation is transferred to MDOS, there are two bytes written to onboard RAM at >F04E STUPST SBO 0 9640 mode LI R0,'TI' MOV R0,@>F04E CLR @>F110 *ADD LABEL BLWP @0 The file CLI\HCLIS then looks at those two bytes, then to determine SCSI, IDE, MFM, TIPI and updates the location PAB for xxx1.AUTOEXEC I just looked at the source code for SCSI and IDE and I am not seeing the necessary two bytes written, instead just a CLR @>F04E. I am not sure if I uploaded the wrong source files, or something I overlooked as I never heard anyone report back about not picking up AUTOEXEC on a SCSI or IDE device. The TIPI source for the LOADER does have the code. This is the code in CLI\HCLIS which loads starting at >0400. It is down about 190 lines in the source code file. MOVB @>F114,@SCRPAG MOV @PWRFLG,R1 JEQ HDPWR9 this is a ctl-alt-del reboot MOV @>F04E,R1 test horizons boot flag JEQ HDPWR9 CI R1,'TI' 1.13.2021, test for tipi boot flag JEQ HDPWRT CI R1,'SC' 2.27.2021, test for SCSI boot flag JEQ SCSWRT CI R1,'ID' 2.27.2021, test for IDE boot flag JEQ IDEWRT * CI R1,'BM' 3.06.2021, HDS2.AUTOEXEC boot * JEQ BWMWRT CI R1,'HD' was this a load/sys boot? JNE HDPWR8 nope, must be a horizons boot MOV R1,@OLDNAM LI R1,'SX' MOVB R1,@OLDNAM+2 JMP HDPWR9

I think this is the file you need.Myarc512K.BIN

I've got the ZuluSCSI. Backups are easy as it is just a matter of copying the individual hard drive images (250 MB or whatever size you format) to another device. I have not encountered any issues using on a Geneve.

I have updated everything to be included for any potential future release.

I must be missing something, as I go to the website (need to add www prefix to the URL by the way), and I see photos of the two newsletters, but no way to click on them to read them.

Boot Eproms 0.97 0.98 1.0 2.0 Boots from HFDC, TIPI, IDE, SCS, DSK and some(all?) versions of the HRD. LOAD Programs LOAD-IDE, v2.6i Loader for SYSTEM-SYS for 2.0 eprom LOAD-MFM, no version # for SYSTEM-SYS for 2.0 eprom LOAD-SCS, v2.6s Loader for SYSTEM-SYS for 2.0 eprom LOAD-TIP, no version # for SYSTEM-SYS for 2.0 eprom

MyWord, not sure if version 1.21 or 1.22 BROWSER, V9.4g - Web browser MDOS version, not sure if it is "important" as not widely used. Maybe only me. ASM V1.03, MDOS Assembler LINK V1.03, MDOS Linker FZAP or FILEZAP, V1.6 MDOS File Editor MEMTEST, V2.60, Memory tester These are programs I use frequently.

Everything is running fine on my PI5 Mame 262 version. Loaded CENTIPEDE and EA cartridges. Can you post your cartridge(s) you are tyring to load? Make sure they have TIFILES headers and not V9T9.

@InsaneMultitasker, @arcadeshopper, @mizapf I took a look at the issue, and I believe it may not be a MAME nor TIPI issue. I think this issue may be specific to ROM only cartridges and using the MENU version of GPL versus the MYGPL set of files. Using MYGPL where you get the TI Title Bar screen, the ROM cartridges show up. With the MENU program, this does not.