Jump to content

BeeryMiller

Members
  • Content Count

    1,810
  • Joined

  • Last visited

Community Reputation

1,281 Excellent

About BeeryMiller

  • Rank
    Stargunner
  • Birthday 01/04/1964

Contact / Social Media

Profile Information

  • Gender
    Male
  • Location
    Campbellsburg, KY
  • Interests
    Powered Paragliding and scuba diving.

Recent Profile Visitors

6,365 profile views
  1. I think @InsaneMultitasker identified some kind of issue with 6.7 RC2, so I would say 6.50 would be the recommended version. I don't think MDOS when it boots calls itself GeneveOS. I suspect the directory name just makes it easier to find the operating system, MDOS Vx.xx Beery
  2. I used the 7.2a version of TIDIR and had no problem with any of the files. Here is a zip file with the individual files in v9t9 format. MDOS-FORTH.zip
  3. Does it slow it down below Geneve normal speed if you have a quad core, 16 GB PC? I would think if you barely had the horsepower for a lower end PC it would, but have not seen what looks to be anything slowed down on my PC. Beery
  4. That geneve.bat file is likely something that originated from me. I had several bat files, one that started up the debug, and another that established RS232 serial support. For the most part, when I use MAME/Geneve, it is trying to debug and figure out what is not working the way it should. The debug function is really nice as you can open multiple debug windows to look at memory all over the place. Beery
  5. Everything from McCann as far as Forth for the Geneve is already on whtech including all the documentation as well as his package. It is three very large archives at: http://ftp.whtech.com/Geneve/mdos/forth/ It's also likely on the MAME image under the bootdisk1.hd image under the FORTH directory. The DIS/VAR 80 files aren't there, but they are up on whtech to be grabbed. Beery
  6. If someone would drop those PDF's on whtech in the Geneve area someplace, that would be great so they aren't lost. Beery
  7. I'm pretty sure Mike had all the work completed for Forth for the Geneve/MDOS with the XOP's. I am not 100% sure I have those disks. If I get some free time, I will investigate. I do not remember a hard-copy manual for that software, so I am hoping the docs were on the disks(s). Beery
  8. It is serial number 1 if nobody caught that.
  9. I still have some of the original Jerry Coffey Jumpboot disks I think in 3.5" disk format. About the only thing I did not add to my note that could be used to speed of the boot process by a fraction of a second would be the actual placement of SYSTEM/SYS on the disk and maybe the an alternative skew on the first track to minimize the time to locate the File Descriptor Record and then advance to begin reading the first sectors of SYSTEM/SYS. We are talking less than 0.25 seconds here so what I described above in an earlier post is something very easy for someone to create without much effort. Beery
  10. There was only one fair I did a MDOS programming session, and somewhere it was taped as I recall seeing it sometime in the past 4 years while watching some video. Not sure if it was a Chicago or Lima Faire. I think the biggest part of that session was the handouts that gave examples for setting up memory, passing command line arguments, and details on the XOP's which are part of the file attachments above but in greater detail. Beery
  11. OK, here are the documentation files for GenPROG and for MDOS mode. The Bootmame.zip file should have the actual files on the MAME image in the MDOS folder is where I typically place those utilities such as the assembler, linker, and maker programs Beery GenREFDsr.pdf GenREFVideo.pdf GenREFUtility.pdf GenREFMemory.pdf GenREFKey.pdf GenMAKE.pdf GenLINK.pdf GenLIB.pdf GenASM.pdf GenREFMath.pdf BootMame.zip
  12. The actual filename itself is limited to 10 characters, but you are placing the full path to the file into that FLNM, so something like TIPI.EDITOR.CODE.PART1.SOURCE1-S is a valid filename with a length of 32 characters. Now, on a TI, CD, or Myarc FDC you are limited to a length of DSK1.FILENAME12 for maximum length of 15 characters. The Myarc HFDC allows a Subdirectory on floppies that can have a SUBDIRECTORY length of another 10 characters plus the period to bring it to 26 characters. On the Myarc HFDC with a hard drive, that pathname length is either 40 or 80 characters maximum, not sure which though. Beery
  13. Me personally, I would have made FILENAME or FLNM in the above example, longer at either 40 or 80 characters, whatever is the maximum length for a filename the Myarc HFDC and/or the TIPI can handle. Then, the LI R2,20 would have been much longer to move the full PAB into VDP. Whether that overlaps >07D0 from >079E, you would have to count. Myself, unless VDP memory space / PAB buffers are tight, I would have established things at easier to see boundaries like >0800 and >0870'ish. That is me though. Remember, you are in assembly so you do not have the constraints of extended basic, mini memory, etc. Beery
  14. In the example above, the filename length above is fixed by design for the program to access specific directories on the TIPI, in this case, for a BBS. So, I do not need to adjust the filename length each time I call the routines. There is nothing wrong with writing a 60 byte PAB even when the filename because it may be very short is something as simple as DSK1.A with a filename length of >06h. The extra characters will not be used in the DSR. So, what I am saying is you do not need to count the full length of your PAB each time someone enters a different length filename for the VMBW write. Just stick with something that is the maximum one would/could encounter, and stick with it. Not sure if Matt is following this thread, but I do not know what the maximum filename length would be for the TIPI, and do not have the notes to know if the maximum filename length for the Myarc HFDC is either 40 characters (>28h) or 80 characters (>50h). Anyone know??? Beery
  15. I pulled this individual file, FILESEARCH, from the AfterHours BBS source code I referenced earlier in one of our exchanges. It reads in text from a DIS/VAR 80 file and looks for a string, and then goes onto another read. What you do not know about the text file that it reads is there is one line of characters I believe every 4th line I do not evaluate as it is either "=====================", or some such individual breaks. Either way, it shows open, reading, and all the VSBR and VMBW reads/writes that are necessary. The entry into this program is at the label FILESEARCH. The routine for the BLWP @ONECHR retrieves either a key from the keyboard or a keypress received from a TIPI socket. I also indicated earlier you should really plan on a filename with a length of at least 40 characters as either the TIPI or Myarc HFDC support longer filenames and it is better to support that now, than modify things later. FILESEARCH
×
×
  • Create New...