Jump to content

sunder

6502
  • Content Count

    105
  • Joined

  • Last visited

Contact Methods

  • AIM
    rayarachelian
  • Website URL
    http://lisaem.sunder.net
  • Yahoo
    ray.arachelian
  • Jabber
    ray.arachelian@gmail.com

Profile Information

  • Location
    Somewhere in time...
  • Interests
    68k, PPC macs, emulators

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. sunder

    TAM cable to speaker stuck

    Thanks, I'll give it a shot.
  2. So I've had this issue for a while now, the cable between my 20th anniversary Mac speaker and the main computer seems to be a large twist lock kind of cable that has many pins. After I got the TAM, I hooked it up and haven't separated the speaker base from the main computer since. When we moved house a few years back, I tried to disconnect the cable but wasn't able to, so revisiting this. Do these get stuck? Is there a specific motion to disconnect them without damaging them?
  3. sunder

    GEMDOS on the Lisa can be built again!

    Might be interesting to replace that FAT12 with something that supports more than 8.3, not just larger volumes - but yeah, that's going to be insanely hard and you'll have to change a lot of the underlying CP/M code, etc. as well as the GEMDOS side and certainly the apps too. FAT32 is likely going to be an insane effort because it's a hack where a file takes up as many 8.3 file entries on top of the original as it would take to store the name. Oh well. But yeah, you'll likely want to create a for-loop that passes VIA addresses one by one for each of the 7 possible locations, trap on segfaults, and if you successfully read block 0xffffff and get proper block sizes from the drive instead of an error, you can make use of that drive. This probably can happen during the boot loader if you can grow it by a bit, or possibly as part of the BIOS when it is initialized.
  4. sunder

    GEMDOS on the Lisa can be built again!

    I don't know of any, but in general, check each slot for a dual parallel port card, if installed check each card for the OCD bit - Open Cable Detect, if the cable is connected, there might be a drive there. If there is a drive there, you can try to probe reading of block 0x00ffffff - this will give you the name and size of the drive, and whether it is a ProFile like or a Widget like drive, but don't depend on the text name, look at the protocol version. Take a look at the Widget ERS for this. If you don't want to deal with the crazy multi-block read/write commands, stick to ProFile-y commands only - the Widgety drives are backwards compatible with this protocol, though it's slightly slower. Note that SunRem and Corvus made compatible drives that may have different sizes, but that -1 block will give you the size of the drive. Please don't do what Lisa Office System and Xenix did - they hard coded the expected drive size inside the driver :facepalm: - as a result, if you attach a 30MB or 40MB SunRem MFM drive you could only use the first 10MB. The ROM routine for the ProFile only contains a read block routine only for ProFile style disks, but you can pass the address of the VIA and thus test both the motherboard parallel port for an attached hard drive - whether Widget or ProFile (or X/ProFile), and any/all of the 6 possible attached external drives. You'll need to hook the bus error vector to prevent crashes as accesses to non-existant ports won't properly signal DTACK and so will generate a bus error. You can setup the ISV (Interrupt Service Routine) ahead of time to write a flag saying that port isn't there before you call the ROM profile read routine and maybe maintain an array of info about what's connected where and what size it is. From what I recall, if you have 2 port serial card, the 2K ROM onboard does a quick check of the port, and then if clicked for boot, would set the right variables to the address of the port and pass them to the Boot ROM ProFile routine to read the block and boot that way, I don't think they contain actual ProFile read routines.
  5. I'm not sure about the serial numbers, but the Lisa 1 mice had a very narrow button vs the newer ones that were shared with the Mac and Lisa 2's, and also a different DB9 connector hood (no screws). see the photos here: https://www.worthpoint.com/worthopedia/apple-lisa-mouse-a9m0050-early-013519-1863798648 There's a few of these on ebay that are super expensive as well. There is a formula for the serial number of Lisas that tell you the manufacture date and plant in a document called "Good Things To Know About The Lisa.pdf" from SunRem, but not sure that a similar scheme applies to the mice. It does appear that the newer mice that came with the Mac 128 to the plus had a different serial number scheme than what's on the Lisa 1 mice. And to add more confusion, they all have the same model number. I wouldn't go by the serial number as much as the shape.
  6. sunder

    GEMDOS on the Lisa can be built again!

    To quote Zoidberg, "I'll take 8!"
  7. sunder

    GEMDOS on the Lisa can be built again!

    On the Mac (and even LOS), the A-Line traps are almost fully used. You could cheat and use some of the F-Line traps that aren't used by the FPU or PMMU, or perhaps use some other mechanism if GEMDOS allows for it.
  8. sunder

    GEMDOS on the Lisa can be built again!

    Pity, they missed an opportunity here to call that error something a lot more fun: Major Havoc
  9. sunder

    GEMDOS on the Lisa can be built again!

    Can you modify the boot loader such that it zeros RAM before it loads the BIOS/BDOS? You should be able to get max ram from the Lisa BIOS low memory globals at 0294: 0000| 0000 0294 MAXMEM .EQU $0294 ;MAX MEMORY ADDRESS + 1 Generally the Lisa's BOOT ROM will load the boot block around address 2000 depending on which device is selected/options ROMs are loaded, but you should be able to know from the boot loader where the boot loader ends, so use that as your start address and zero RAM all the way to MAXMEM-1 using a DBRA loop.
  10. sunder

    ADTPro Lisa Profile Transfer

    Thank you @fri0701 taking a look now
  11. yeah, I vaguely remember that HD disks will not work fine because of the coercivity or whatever it's called in low density drives back from the commodore days. I used to order floppies from a bulk maker and for a while the DS/HD were cheaper than DS/DD, but they didn't work well at all in C1541s for example. Perhaps other brands of DS/HD will also work if the disk is degaussed first. This is kinda like punching the R/W hole on the other side of the disk so it can be used as a flippy, but taken to the next level of complexity.
  12. So did DS/HD floppies work well to hold data or did you need to switch to DS/DD?
  13. sunder

    GEMDOS on the Lisa can be built again!

    Love that command's name! And yes, fond memories of BBEdit back when I was still on an actual mac.
  14. sunder

    GEMDOS on the Lisa can be built again!

    So this is a bug with the SMF I have or possibly postgres setup with SMF, there's some visible or invisible unicode char it complains about. It only seems to happen from macos x or iOS. The only fix I've found for this, and it's lame, is to paste the text of the code into a pure text only editor such as vi in terminal and then copy it back and paste it into SMF to strip things out. It might be something like smart quotes or emdashes or hard spaces, not sure exactly, there's a description here (must be logged in to see it): https://lisalist2.com/index.php/topic,64.0.html
  15. sunder

    GEMDOS on the Lisa can be built again!

    Very nice! Are there many CP/M68k apps out there? I know there were a ton for the 8080/z80.
×