[Coco] nitros9.org

Wed May 17 11:45:30 EDT 2006

On Wed, May 17, 2006 at 07:31:39AM -0400, Robert Gault wrote:
> *j Means non-existent module. t Means the system has tried to boot. While t 
> normally shows up at the beginning of the sequence, it can appear again. So 
> t*j means that a module can't be found so Boot failed.

Do you know of any method other then trial and error to find out which module is
missing?

> Given what you are attempting, my guess is that you either do not have 
> /term in your bootfile or are missing sysgo or maybe grfdrv. Whatever it 
> is, I doubt you are using the script supplied by Cloud-9 for booting from 
> their systems.

Forgive my ignorance as I'm new to nitros9 where would I find /term and is the
bootfile the same as a bootlist file? When I got the Superide Mark installed
the 6809 version of nitros for me. Since my coco had a 6809 it seemed like the
thing to do. I have since replaced the 6809 with a 6309 and would like to take
advantage of the extra performance and capabilities of it. I got a new CF card
and after formatting it I copied the files from the 6309 nitros distro disks I
got at the fest a few weeks ago. I also installed the drivers for superdrive and
drivewire. I tried using the mb script along with the supplied bootlist file. That
gave me a bootable floppy but I couldn't access the ide controller or CF card.
No amount of uncommenting modules in the bootlist file would result in a kernel
that would allow me to access the CF card. When I got the CF card preconfigured
from cloud9 it included a couple of scripts to build a kernel and the bootlists
that those scripts used. That and the comments in the scripts and bootlists files
led me to believe that they were provided by cloud9. If that's not the case I
apologize to the author of the files.

Frank

> 
> Frank Pittel wrote:
> >Chris,
> >
> >I've been using the "old" os9gen that I have. I've copied the build scripts
> >and bootlists that cloud9 put on the CF card for me to the new card. I've 
> >fixed
> >up the scripts and bootlists with the correct paths for the drivers and 
> >whether
> >or not I boot with a "boot" floppy or from hdb the result is the same. all 
> >seems
> >well at first. I get a line and a half of dots. (.) and then it starts to 
> >load modules
> >for about two and a half lines. At this point all seems well and normal. 
> >At the
> >end of the module list it list i2x0. At this point it should continue with 
> >a capital
> >c (C) and then finish booting. In my case it displays t*j (i2xot*j) and 
> >then displays
> >"boot failed". I've tried booting with both sysgo files included with 
> >nitros and the
> >result is the same. I've run ident on the two sysgo files and they show up 
> >as being
> >good.
> >
> >Frank
> >
> >
> >
> >On Tue, May 16, 2006 at 09:56:44PM -0500, Christopher Hawks wrote:
> >
> >>Frank Pittel wrote:
> >>
> >>>I noticed that the page is now back up. Unfortunatly I couldn't find 
> >>>what I
> >>>was hoping for. As I understand the latest and greatest version of 
> >>>os9gen has
> >>>a bug in it which presents itself when building a kernel for use on a CF 
> >>>card
> >>>that is partitioned for use by HDB and Nitros9
> >>>
> >>>I am having another problem that I'm hoping I can get some help with. I 
> >>>have a
> >>>CF card that I bought today with the idea of installing both HDB and 
> >>>Nitros9 onto.
> >>>(Interestingly enough I think I found a bug with HDB and it's dealing 
> >>>with the
> >>>particular brand of card I have. Any data written to the card with 
> >>>"save" or "copy"
> >>>is lost at reboot. However if written to the virtual file with "backup" 
> >>>it's fine.
> >>>The card works fine with nitros though. <Boisy if you have any interest 
> >>>in this let
> >>>me know and I'll send you the card when I get a replacement>) What I 
> >>>need is a "bootlist"
> >>>and script that will allow me to gen a bootable floppy. Amoung the 
> >>>modules I need
> >>>installed is the hardware clock on my superide card, Superdriver and 
> >>>drivewire. I have
> >>>the modules I need but I just can't seem to build a os9boot file that 
> >>>will boot. :-(
> >>>It would help if someone could email me what you have working for you 
> >>>for the 6309.
> >>
> >>Frank:
> >>
> >>	The os9gen bug shows up first when to you run "link.bas" after 
> >>	backing up the bootdisk to an HDB-DOS disk. It will report the 
> >>	bootfile size and location, but, will say the bootfile size is zero 
> >>bytes! The bug causes _all_ bootfiles to be the fragmented type, and 
> >>"link.bas" can't handle this.
> >>
> >>	If "link.bas" gives a real file size, you don't have the bug. The 
> >>change has been committed to CVS.
> >>
> >>
> >>-- 
> >>Christopher R. Hawks
> >>HAWKSoft
> >>---------------------------------------------------------
> >>Any research done on how to efficiently use computers has been long lost
> >>in the mad rush to upgrade systems to do things that aren't needed by
> >>people who don't understand what they are really supposed to do with them.
> >>	-- Graham Reed, in a.s.r.
> >>
> >>-- 
> >>Coco mailing list
> >>Coco at maltedmedia.com
> >>http://five.pairlist.net/mailman/listinfo/coco
> >
> >
> 
> -- 
> Coco mailing list
> Coco at maltedmedia.com
> http://five.pairlist.net/mailman/listinfo/coco