Jump to content


  • Content Count

  • Joined

  • Last visited

Contact Methods

  • AIM
  • Website URL
  • Yahoo
  • Jabber

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. If anyone's interested I released the beta code that includes the BLU changes. I'll need more BLU images to compare to. While lisafsh is now able to get a directory, it's not right somehow. So the metadata for the directories is right, but when I try to extract the files they don't match known good extracted files from a profile image from LisaEm. It's possible this has to do with interleaving or the offset to the start of the file system. https://github.com/rayarachelian/lisaem.git git repo https://lisaem.sunder.net/downloads/lisaem-1.2.7-20200314-msw.zip windows binaries https://lisaem.sunder.net/downloads/lisaem-1.2.7-20200314.tar.xz source archive
  2. meh, it throws error 75, and repair doesn't fix it. will keep trying.
  3. Hi, some better news, I tweaked the tool a bit more and now both tags and data is a lot better, I'm able to run the "dir" command in Lisafsh tool and it's also able to recognize the MDDF, likely this is now working, though I don't have time today to test this in LisaEm due to work obligations. I'll test this later and if all is good and I manage to fix other bugs I'll push the code to github, and cut a binary release as well. Hope this helps. __-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk)_blu.dc42.xz
  4. Also tried to boot off a good profile image and attach the converted image on a dual port parallel slot (you can do that by changing the preferences, telling LOS there's a 2 port card in one of the slots, and that, say, the upper port is a profile) but the disk isn't recognized. So likely there's some more stuff needed to get this working.
  5. Good news, I found some bugs in the code, it's now producing an image where the tags are correct, however, bad news, attempting to boot from it throws a 10726 error. I found a couple of bugs in the converter program, and now, looking with lisafsh-tool, I see that the blocks that have the boot loader on the profile match the converted widget drive. I then tried to repair the Widget image using the LOS install disk #1 and it failed to do so with error 200/663, but not sure what that means. __-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk)_blu.dc42.xz
  6. Ah ok, thank you for that LOS image. I've downloaded both and will check them. btw, compressing the BLU image with xz reduces it down to 3.5MB: -rw-r--r-- 1 ray ray 9.9M Mar 8 21:21 '3_-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk).dc42' -rw-r--r-- 1 ray ray 3.5M Mar 9 19:02 '__-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk).blu.xz' -rw-r--r-- 1 ray ray 410K Mar 9 19:03 'LOS 3.1 1-boots-on-126-but-not-127.image' -rw-r--r-- 1 ray ray 9.9M Mar 9 19:07 '__-_BUILT-IN_PARALLEL_PORT_(10_MB_Widget_Hard_Disk).blu' I'll start looking at this today.
  7. Meh, that ipc list error means there's something wrong with the code on that disk - so likely the conversion isn't working at all. It's indicative of run away code, i.e. a very long string of code (or all zeros) without branches or JMPs since that piece of code works on basic blocks. This sometimes indicates a bug in the cpu core, but more likely it indicates a corrupted disk. So, I guess the take away is I need a lot more BLU images to test that blu-to-dc42 program with. As an aside, I used to provide, and will refresh, https://github.com/rayarachelian/lisafsh-tool-libdc42 once I get these bugs fixed. That repo is meant as a standalone set of disk tools w/o LisaEm. But don't switch to that yet, as that code is even older, just pointing out that I'll update that after 1.2.7 goes to production incase someone comes back to this thread, say a few years from now and runs into similar issues. I think the most likely thing is what Tom said, I suspect, but haven't verified that LOS does interleaving for Profiles and possibly not widgets. Again, I don't know this for a fact, so I can't say 100% yet. I'll test some more. At this point this is just a thought, and it doesn't even have enough evidence to be a hypothesis yet. Thing is I only have one working Widget drive and it has MacWorks on it, so the number of BLU images I have to work with is very limited. If you guys can do me a favor, can you take a few BLU images of widgets and a few of profiles (and clearly mark which are which), I can test the code some more and see if I can get it working, and perhaps get it working with LisaEm too. But if what Tom says is true, that Widget LOS images have a different bootloader than Profiles, they'll not work on LisaEm until after 1.2.8 or even 2.0. (When I started on 1.2.7 I intended on building widget support, but then Apple went and announced that they'll do away with 32 bit support and then I got stuck on cleaning up the hidpi aware code, so never finished full widget support.) I've got a few minor cross platform (ie. windows vs macos vs linux) bugs to deal with, and some major ones with the screen handling code before I can publish 1.2.7, and I'd also like to add one or two more features before I ship this beast and move on to 2.0 features, so don't really have cycles to chase too much of this down on actual hardware. But if you guys have the cycles to image a few hard drives, and can save me some time taking a bunch of images, I'll happily work on it. (and I'm not asking you @chesestraws to do all of it, this is a general ask for a favor). Widgets use a completely different protocol than profiles, though they're backwards compatible with profiles, however, if that boot loader on a widget is really expecting to use the multi-read protocol, it will absolutely not work with current 1.2.7 Lying to the OS and labeling the name of the physical device as "WIDGET" or "WIDGET-10" vs "PROFILE" does not activate this mode, the protocol version does that. This is why SunRem was able to make their own profile compatible third party hard drives. The OS doesn't care about that label. As an aside you'd think that centering a rectangle with wxWidgets inside a window should be simple, get the width and height of the window, substract the width/height of the rectangle and divide by two and use that as the origin, right? except that w/GTK on linux and wx3.1.x it returns untrue values (either that or I've got some serious bugs somewhere else). Grrr.
  8. Give this is a try, I just compiled it from the current code, but haven't (much) tested it, restore the contents to c:\program files\sunder.net\lisaem Inside the bin directory should be the tools you're after. https://lisaem.sunder.net/downloads/lisaem-1.2.7-beta-2020.03.03-win10-x86-64.zip It's probably a good idea if you run LisaEm to hit control-+ or control-- as it seems the default zoom level is wrong. I'll take a look at your BLU file when I get a chance. Currently I'm wresting with mountain lion trying to get a working VM, but ofc there's no brew.sh. if that works and I can get wxWidgets to properly compile and clang to build executables I can use that to build LisaEm for older macs as some of my users are still on 10.9 and 10.10 (and ofc others are on catalina). There's still a bunch of bugs around the display modes, and mouse location. Some works, others like 2x3y doesn't.
  9. So, if you go here: https://github.com/rayarachelian/lisaem and do a git clone, you'll have nearly the latest and greatest source code, and inside that, there's a scripts directory, in which you'll find a pair of Windows batch files. I use these to install cygwin with all the required packages to build LisaEm. These batch file expect to be placed on the E:\ drive, (C: is for windows os, D:\ an optical drive and E:\ is the shared folder in virtualbox I use). You only have do these steps once: Assuming a 64 bit machine, you'd also need to download the cygwin installer and save it to e:\e:\setup-x86_64.exe and then right click on the batch file, and run as administrator - if you just run the batch file regularly, it will fail to run properly and go in interactive mode. Once you get cygwin working, you'd copy that lisaem repo inside of cygwin, or just do git clone again, go into the scripts directory and run build-wx3.1.2-cygwin-windows.sh - this will create a copy of wxwidgets 3.1.2 in /usr/local/. Once done, do export PATH=/usr/local/wx3.1.2-msw/bin:$PATH I would also do: echo "export PATH=/usr/local/wx3.1.2-msw/bin:$PATH" >>~/.profile to make this permanent for the next time you run cygwin. Next go back into the top level directory. Type in ./build.sh clean build LisaEm will compile, along with the tools (or possibly not if there are bugs) You could also type in ./build.sh clean build install if you'd like to have it, and the tools install to c:\program files\sunder.net\lisaem All this is documented in the readme here: https://github.com/rayarachelian/lisaem/blob/master/README.md#special-steps-for-windows As this is in active development there probably are bugs, and there's no guarantee that the blu-to-dc42 code will work as intended. And the next time there's an update, you can do git pull, and run just the build command and you're done. It's not that hard to build except for the initial steps where you have to install Cygwin on windows, or if you're on macos X, installing wxWidgets, for which I provide a script, in the, you guessed it, scripts directory. If you're trying to build the tools manually outside of the build scripts, well, yes, you're going to run into issues because you'll first need to build libdc42 and then when you compile the tools, you'll need to link that in, etc.
  10. sunder

    Quadra 950 SCSI

    Not sure about this model, but with SCSI generally you want motherboard->internal-drives->terminator, then the last device at the end of the external chain gets a terminator. You need to make sure there's no conflicts in IDs as well. You'll want something like SCSI probe to help you debug. With some weirdo setups, it helps to have a device in the middle have a terminator. Not sure if this was an old wives tale or real, but it can't hurt to try. Beware that some SCSI devices are differential, so be sure you know what kind you have, as you can't mix differentials with regulars. I think off the top of my head that the IIfx used differentials, so needed special terminators and all differential SCSI devices. http://www.openbsd.org/38.html OpenBSD has a song about SCSIs. Sort of.
  11. sunder

    Sometimes you get a funny feeling...

    Before you take out the DVD drive, you could always burn a copy of the OS on a DVD-R or a 10.4 boot CD-R and try to boot off of that. CD-R/DVD-R media is quite cheap. Sounds like you're gonna have a quite a time cleaning this little beastie out. But look at it this way, you saved it from the junk yard.
  12. sunder

    Power Macintosh 7200/120

    Nice machine, plus it's got PCI slots, and that's useful. Closest thing I've got is a 7100/60.
  13. OS X supposedly still supports SCSI. Long as you get a card that it has drivers for, it should be fine. I've seen a few cards at http://eshop.macsales.com/Search/Search.cfm?Ntt=SCSI%20controller&Ntk=Primary&N=0&Ns=P_Popularity|1 though those are very expensive, they will work inside Mac Pro's so should work in a Hackintosh as long as you get one that matches your PCI slots. It's also a question of finding which chipsets OS X has drivers for. It looks like there are drivers in 10.4, but that's PPC. http://reviews.cnet.com/8301-13727_7-10334774-263.html says to remove certain conflicting drivers under /System/Library/Extensions. Looking there, I see these two under Lion drwxr-xr-x 3 root wheel 102 Jun 18 2011 IOSCSIArchitectureModelFamily.kext/ drwxr-xr-x 3 root wheel 102 Jun 18 2011 IOSCSIParallelFamily.kext/ And also this, which is one of the Atto SCSI cards: ATTOExpressPCI4.kext So look in your kext folder and see if you can find another card. Running this command gives a ton of matches, but most of them are false (i.e. using USB devices under as SCSI), but some look like they might be SCSI cards. So take a look at those and see if you own one, or can find one cheap: find /System/Library/Extensions/ -type f -name Info.plist -exec grep -il scsi {} /dev/null \; | more Some more discussions: https://discussions.apple.com/thread/3632202?start=0&tstart=0
  14. Do we have a way to take a 68K Mac's SCSI hard drive and turn it into a virtual disk for use with either Basilisk II or Mini vMac? (I know of the copyrom program for ROMs and obviously, Disk Copy can be used to make floppy images.) I've got a nice setup on a Mac hard drive I'd like to be able to bring with me on my MBP. :b&w:
  15. sunder


    Yup, they're wonderful machines for kids. I bought one a couple of years ago for my little guys. They love it. The loud fan is a bit annoying, but hasn't been annoying enough for me to take it apart and undervoltage it, or replace it. I upgraded the RAM to 1G and put in a larger HD. I also picked up a gigabit USB ethernet interface for it, and it runs much faster now.