Jump to content


  • Content Count

  • Joined

  • Last visited

1 Follower

Contact Methods

  • Website URL

Profile Information

  • Gender
  • Location
    San Diego, CA

Recent Profile Visitors

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

  1. epooch

    JetPack for SE/30

    Hmm. You just said which made me think we were on very different pages. Anyway, good luck!
  2. epooch

    JetPack for SE/30

    NuBus Runs on a 10MHz clock, even on the II. The discussion was about a IIsi NuBus adapter. The Mac II has 4 state machines to keep the system synced up with Nubus. Maybe they are all incorporated into the IIsi NuBus adapter, but I don't see why they would be.
  3. epooch

    Info needed

    It's open! http://www.retrochallenge.org/
  4. epooch

    JetPack for SE/30

    The SE/30's 16MHz bus speed is not right for running 10MHz NuBus. That's why the 20 MHz IIsi can do NuBus with so little hardware. You would probably need to accelerate the SE/30 to 20 MHz, and lose all of its onboard capabilities (including video and SCSI), or have a whole lot of hardware doing timing and caching. Basically another whole computer running NuBus. Maybe some card that are not timing dependent would work, but I can't think of one that wouldn't at least need a crystal change. Then your fast accelerator is running 25% slower, at best.
  5. epooch

    DNS issues while using serial for internet

    What system is crashing? The Raspberry Pi or the Mac? What Mac/System/Browser are you using? When you are saying that outside domains are not resolving, I assume that no packets are getting through, not just that DNS isn't working (like it is a symptom, not the actual problem). Some ping tests to ip addresses would narrow down the issues. Assuming it is a routing problem, for linux PPPd, you usually need to add the options: # Enables IP forwarding on linux ktune # Add an entry for the peer to this system's ARP table. proxyarp to get everything working. This will allow Raspian to do NAT, forward the packets to your network, and will update the arp tables so packets intended for your Mac will go to your Raspberry Pi. You are sort of doing this manually in your script, but it is built into PPPd, and it does work. see https://ppp.samba.org/pppd.html for details about these settings.
  6. epooch

    512k Floppy Drive won't eject

    Or spray some WD-40 on the contact points (making sure to not get overspray on the drive head). Work it around, wipe down, and put on some new lithium grease. It saves the effort of having to disassemble.
  7. epooch

    Source for IWM Chips?

    Sorry, that was vague. I was referring to modifying the I/O to the logic and drive controller in the 800k Drive. So the Sony's 800k drive controller would just work. Hmm, I thought the SmartPort firmware in conjunction with the IWM was used to control the Apple 3.5" drives and the 'Intelligent" 3.5 UniDisk drive. But if the Liron ROM is a sub-set of the standard Smartport firmware (which makes sense), then I agree that IIc+ or IIgs ROM code would be needed. Now I definitely think it would be easier to have a microcontroller sitting in between, translating SmartPort to 3.5" drive control and buffering data from the 3.5" drive. At that point, it is probably easiest to emulate a 65C02 and run the actual Rom from the Unidisk or Apple SuperDrive controller. Anyway, thanks for the help. This is all a lot clearer to me now.
  8. epooch

    Source for IWM Chips?

    My thought was to half the PWM frequency and double the TACH frequency so that the 800k controller would just work. But I am sure there will be problems with jitter, etc, running it so far out of the specifications. I think I am better off just looking into a modern buffering FIFO (or even a microcontroller) that can take the place of the 65C02/RAM combination.
  9. epooch

    Source for IWM Chips?

    I bought an old corroded Mac Classic Logic board to harvest the SWIM off of it. I was going to try to make my own Liron card for the Apple II, but I don't think that makes a lot of sense based on the drives it is limited to. I have a question though: It is apparent that the Apple IIe needs the Liron and 3.5" Unidisk, or the Apple II SuperDrive controller card, to read an 800K drive. Each of those solutions has its own 65C02 and RAM to be able to cache data from the drive. I though I might just be able to slow the drive down... I know the 400K drives from the Mac use PWM to control the drives speed, and the early Mac 800K drives do not, which causes a crash on the 64K Mac ROMs. However, the later Apple 3.5" Drive, (Apple p/n A9M0106) is compatible with a 64K ROM Mac. Anybody know how they did this? Is the Mac really controlling the speed of the drive, or is it just sending the drive speed back, and still self-regulating? If the Mac is really controlling the drive speed, it seems like this would be a good drive to slow down to be readable by an Apple II with just an IWM chip.
  10. epooch

    Apple IIe Craigslist find

    Yes, he has one for the IIe.: http://a2heaven.com/webshop/index.php?rt=product%2Fproduct&product_id=142 out of stock though.
  11. Yes. you will probably need to install ppp on the raspberry pi though: sudo apt-get install ppp
  12. epooch

    030 PDS -> LCIII PDS Adapter?

    I will test it out with a bunch of short jumper wires first, then look at designing it. Regarding the jumper block - yes, I was thinking a dip switch could work well for that.
  13. I missed it! So glad someone is using ElWhip, even if it is only one person! That was a serious challenge to get the TCP/IP stack and PPP stack running in 128K. Maybe it is time to build a web browser for the Mac 128K now...
  14. epooch

    030 PDS -> LCIII PDS Adapter?

    Oh, if everything is in 24 bit mode, you would invert A22 instead, I think. I need to check my LC PDS NIC to see what address lines are decoded.
  15. epooch

    030 PDS -> LCIII PDS Adapter?

    Software: I think most of the big manufacturer's drivers are the same for Nubus / LC PDS. That would imply that the drivers can look for their ethernet card in any slot, not just LC PDS pseudo slot $E. Designing cards and Drivers for the Macintosh Family states pretty clearly that using pseudo slots would allow manufacturers to use the same driver for NuBus and PDS slots. So, I think the drivers will find the card regardless of what slot it is in and will not need to be modified. That is, if the driver would run on an SE/30 at all. Hardware: Assuming that the LC PDS card is hard-wired to decode addresses on pseudo slot $E, I think that by modifying the address signal from the 030 slot to the LC card, you could move the addressing of the card from pseudo slot $E to another slot. In 32 bit address mode, you could just invert A26 between the slot and the card to enable the card when the computer is addressing pseudo slot $A. This would avoid the conflict with SE/30 video RAM/ROM. You would then connect /IRQ2 with /SLOTIRQ.E so that a interrupt from the LC card would correspond with pseudo slot $A interrupt. I am not sure what addressing mode (24 or 32 bit) an LC PDS Ethernet card uses, or how it would affect all of this though. The modifications to the addresses probably would be more complicated then. I just don't know how that works. It is a nice coincidence that the LC bus is 16Mhz, like the SE/30 which should make timing a non-issue.