LisaList2

Advanced search  

News:

2019.06.07 fixed NChat for the "Curve" theme, will eventually move it to its own page and add it to the default theme as well. Other plugins are next. see post in the Meta board for details

Pages: 1 2 [3] 4 5 ... 10
 21 
 on: May 21, 2020, 06:20:11 am 
Started by blusnowkitty - Last post by jamesdenton
As far as I remember, that's the only check.

Feel free to try this disk image instead:

https://github.com/arcanebyte/uniplus/blob/master/boot-serialization-a-serialized.image.zip

This worked from both a FloppyEmu and a real floppy disk.

 22 
 on: May 20, 2020, 10:45:35 pm 
Started by blusnowkitty - Last post by blusnowkitty
Never mind on that - I found an old post by Ray showing how to patch the boot disk. I also found an installation guide over here: http://www.bitsavers.org/pdf/unisoft/UniPlus+_System_V_Installation_Instructions.html

However, the installer hangs at Step D:

Code: [Select]
D. Re-insert the boot ("A") diskette and enter "sunix". After a
while the diskette will be ejected and you will be asked to
insert the "root filesystem", which is the "B" diskette. Do so,
and then hit return.

You will be asked for the location of the "swap" area. Indicate
"p" and hit Return. Then respond with "0" and hit Return when
asked for the number.

Unix will now start operation! You will see the "#" Unix prompt.
However, it is a very limited system at this point.

Instead of the UNIX prompt, I only get a solid block cursor. No disk activity at all from my X/Profile or floppy, and no keyboard input is accepted. The only thing that is accepted is the power button. Is it possible that there's another serialization check it's failing at?

 23 
 on: May 20, 2020, 09:05:31 pm 
Started by blusnowkitty - Last post by blusnowkitty
I recently found a set of disk images for UniPlus UNIX so I thought I'd give it a try. Unfortunately the boot disk appears to be serialized to another Lisa as it just gives me an error along the lines of "Not the right computer" and ejects the disk. Does anyone know how to deserialize the boot disk, or better yet does anyone have a set of already deserialized images?

 24 
 on: May 20, 2020, 08:02:10 pm 
Started by cheesestraws - Last post by cheesestraws
I've uploaded the source code/build environment to Github to try to make it a bit saner to work with.

Here's the link: https://github.com/cheesestraws/lisa-gemdos

 25 
 on: May 19, 2020, 06:18:14 pm 
Started by rayarachelian - Last post by stepleton
Just use the "NOTIFY" link at the bottom of the thread and you'll get an email for each message.

 26 
 on: May 19, 2020, 04:18:47 pm 
Started by cheesestraws - Last post by rayarachelian
Many thanks! This is very cool!

 27 
 on: May 19, 2020, 03:54:38 pm 
Started by snuci - Last post by snuci
I think my drives sound closer to your "bad" drive  :D  I'm still waiting for my Tri Flow---once it gets here I look forward to seeing if I get similar results.

Were you able to manually turn the lead screw in order to do the lubrication? I couldn't get mine to move, but was not going to try and force it.

I think that will help.  No, you can't move that screw.  I just sprayed it and the first time it was used after spraying was what you heard in that video.  It sounded terrible before.  During the "disk cleaning" or Option N, it would squeak each time it went back and forth.  Now it is okay.

Does your "bad" drive always fail at roughly the same spot of the format? I wonder if your drive has the same head pressure issues that mine has.

No, it usually fails right in the beginning (95%) or a few tracks in. If I change that bad chip, it works fine with no issues.  As a matter of fact, my oldest Twiggy drive didn't have any foam pads for the extra pressure so I cut them myself and with two-sided tape, I put them into both spots on the upper frog arm (if that is the correct term).  I never tried without to be honest.  I had similar issues with single sided drives that have had the pressure pad missing from the arm above (and/or below in this case) as this adds the extra pressure needed for a good read.  I just replaced the foam out of habit during initial drive checks. Perhaps you might check if your pads are missing?


 28 
 on: May 19, 2020, 03:25:52 pm 
Started by snuci - Last post by stepleton
I think my drives sound closer to your "bad" drive  :D

I'm still waiting for my Tri Flow---once it gets here I look forward to seeing if I get similar results.

Were you able to manually turn the lead screw in order to do the lubrication? I couldn't get mine to move, but was not going to try and force it.

Does your "bad" drive always fail at roughly the same spot of the format? I wonder if your drive has the same head pressure issues that mine has.

 29 
 on: May 19, 2020, 01:16:45 pm 
Started by cheesestraws - Last post by cheesestraws
Hi folks,

I have successfully built a working GEMDOS for Lisa from the sources (well, sort of sources) that Caldera/SCO released ages ago (as part of the GEM Porting Kit).  I strongly suspect that nobody has touched this for a very long time, partly because at least one critical bit of it was missing.  A pre-made directory tree with the source and all the necessary tools is downloadable here: http://dump.ecliptiq.co.uk/d/hatari-gemdos-lisa-build.zip

To get it to build:

  • Grab the Hatari Atari emulator (lol.)  Other emulators will likely work, but I've only tried Hatari.  Leave it using the built-in EmuTOS.
  • Unzip the file and point Hatari's "GEMDOS Drive" (which is what it calls its host filing system implementation) to the directory
  • Fire up Hatari, double-click on the C icon and double-click on COMMAND.PRG in that directory.
  • Do:
    • cd SYSBLD
    • SETUP
    • MAKEFI

(you can run MAKEHI instead to make a hard disc image, but since at least for me the hard disc support isn't actually working, this is probably moot). 

When it's chugged away, you should have a GEMDOSFI.SYS file and a COMMAND.PRG file, which are the OS and the command line interpreter, respectively.

To check whether this works, you can use this person's magical boot-disk-o-matic: http://www.alternative-system.com/en/revive-gemdos-for-lisa/ but replacing the GEMDOSFI.SYS that DRI built with the one you just built.

Note that GEM itself won't run, at least on my 2/10; I've tried the GEMDOSFI.SYS that DRI built too and that won't run GEM either, so that's a problem for another day.

To get this to work, I had to:

  • Reconstruct CON.O -- this is the device-independent console driver.  CON.O was missing, and the corresponding CONSOLE.C from the sources for the Atari was too new.  So I replaced chunks of it with the console driver in CP/M 1.2, and the result seems to work, but is probably... questionable.
  • Take too long to work out that it was always building a hard disc image because a #if was never firing (due to a preprocessor incompatibility, perhaps?), so worked around that

The tree contains the Lisa GEMDOS BIOS code (in \BIOSSRC), the GEMDOS BDOS in object form (in \BDOSOBJ), and a build system in SYSBLD.  It also contains the Atari GEMDOS code (under AHC), the Atari GEM compilers (which work to build Lisa binaries too) in \TOOLS.  Also some random source files I was using for testing that got caught up in the ZIPping process.  All the files except the random testing stuff came from the Caldera GPL dump, except for CON.C, which is my hybrid thing.

Hope this is of some interest to someone!

 30 
 on: May 19, 2020, 10:34:42 am 
Started by rayarachelian - Last post by snuci
I do have issues trying to post multiple images even though they fit under the file size limit. 

Is there also an option to automatically subscribe to a thread (get notifications) if you post in a thread and you don't start the thread?

Thanks,
Santo

Pages: 1 2 [3] 4 5 ... 10