Chris Baker <[EMAIL PROTECTED]> writes:
> Andre Berger <[EMAIL PROTECTED]> writes:
>
> > [snip..]
> >
> > Ethan Benson <[EMAIL PROTECTED]> writes:
> >
> > > yes you need a COMPLETE *REAL* 4MB Finder.
> >
> > I have removed the "This is a Emergency Boot Floppy System only" alert box
> > from
Andre Berger <[EMAIL PROTECTED]> writes:
> [snip..]
>
> Ethan Benson <[EMAIL PROTECTED]> writes:
>
> > yes you need a COMPLETE *REAL* 4MB Finder.
>
> I have removed the "This is a Emergency Boot Floppy System only" alert box
> from
> a MacOS 8.1 Emergency floppy system folder and added the Bo
[snip..]
Ethan Benson <[EMAIL PROTECTED]> writes:
> yes you need a COMPLETE *REAL* 4MB Finder.
I have removed the "This is a Emergency Boot Floppy System only" alert box from
a MacOS 8.1 Emergency floppy system folder and added the BootX 1.2.2
Extension plus a kernel image. The whole thing is a
On Wed, Jun 07, 2000 at 04:53:31PM +0200, Olaf Hering wrote:
>
> Ok, I really like to know what MacOS Versions remove that blessing, or
> what ever is the trigger. No Problems here so far. Can you forward such
> stufff to me?
all versions of macos since 7.5. (that is all we ever worked with) as
f
On Wed, Jun 07, Ethan Benson wrote:
> > And please: Don't make it unmaintainable with the Apple_Bootstrap type.
> > Appfle_HFS is the correct type.
>
> Please don't create problems for yourself, Apple_Bootstrap is the
> correct type. using an HFS partition will only cause you problems and
> pa
On Wed, Jun 07, 2000 at 04:00:18PM +0200, Olaf Hering wrote:
>
> Copy it to a HFS Partition, it should be a active Systemfolder. If not,
> open it, move the Finder to the Desktop, close the folder window, drop
> the Finder on the folder icon. The Finder ist only be there to fool
> MacOS. It is nev
On Wed, Jun 07, Ethan Benson wrote:
> On Wed, Jun 07, 2000 at 03:35:17PM +0200, Olaf Hering wrote:
> >
> > I can't solve that /proc /kern thing, its a topic for l-k.
>
> more like a flamewar... ;-)
>
> [snip]
>
> > The support database is nearly empty, for the outside world. I have some
> > en
On Wed, Jun 07, 2000 at 03:35:17PM +0200, Olaf Hering wrote:
>
> I can't solve that /proc /kern thing, its a topic for l-k.
more like a flamewar... ;-)
[snip]
> The support database is nearly empty, for the outside world. I have some
> entries in german, these will be translated and be availabl
On Wed, Jun 07, Ethan Benson wrote:
> > > SuSE wrote an extremely obfuscated shell script to try and figure this
> > > out,
> >
> > Cool! And SuSE's a good company that releases things like this as OSS/DFSG
> > compliant,
> > right? Where can I get it and test it on my machine? (Nothing ob
On Wed, Jun 7, 2000, Ethan Benson <[EMAIL PROTECTED]> wrote:
>BenH has told me that he has fixed /dev/nvram so it really does work
>now, but nvsetenv is unaware of the new nvram format (which differs
>from oldworld's) so all it does is corrupt your nvram. there is
>however a new tool `nvtool' whi
On Wed, Jun 07, 2000 at 08:22:59AM -0400, Adam C Powell IV wrote:
> > machines. fortunatly you don't need to set the boot-device at all on
> > newworlds if you use IDE disks (the defaults will do just fine)
>
> Right, and newworlds don't use quik, right? So what's the probem? Is there
> a way
Okay, I've clearly bitten off more than I can chew. But let's give this a
try...
Geert Uytterhoeven wrote:
> On Tue, 6 Jun 2000, Adam C Powell IV wrote:
> > Ethan Benson wrote:
> > > because there is no way to find out that
> > > /dev/hda3 == /yucky/openfirmware/device/path/ata/@0:0
> > >
> > >
On Tue, Jun 06, 2000 at 11:42:56AM -0400, Adam C Powell IV wrote:
> > Usage: nvsetenv variable value
>
> Cool. I'll try this a bit later, and contribute to the docs on this if I get
> a
> chance. Maybe even an ncurses front-end matching Boot Variables' functions,
> or
> debconf for quik? Oth
On Tue, 6 Jun 2000, Adam C Powell IV wrote:
> Ethan Benson wrote:
> > because there is no way to find out that
> > /dev/hda3 == /yucky/openfirmware/device/path/ata/@0:0
> >
> > this would require kernel modifications becuase the kernel does not
> > know either, and there is no reliable way to figur
Ethan Benson wrote:
> On Tue, Jun 06, 2000 at 10:08:56AM -0400, Adam C Powell IV wrote:
> > Ethan Benson wrote:
> >
> > > 2) why you don't WANT to use yaboot on oldworld hardware:
> > > [snip] first let us go over the main complaints about quik:
> > >
> > > [snip]
> > > b) oldworld macs (
On Tue, Jun 06, 2000 at 10:08:56AM -0400, Adam C Powell IV wrote:
> Ethan Benson wrote:
>
> > 2) why you don't WANT to use yaboot on oldworld hardware:
> > [snip] first let us go over the main complaints about quik:
> >
> > [snip]
> > b) oldworld macs (with very few exceptions) lack the a
On Tue, Jun 06, 2000 at 06:42:45AM -0700, Brian Macy wrote:
>
> >From the FAQ it implies it would work. Last sentence implies you should
> switch to yaboot even if you do not have a NewWorld machine.
i have modifed that section to clarify it.
> This actually isn't true for the StarMax. And my
Ethan Benson wrote:
> 2) why you don't WANT to use yaboot on oldworld hardware:
> [snip] first let us go over the main complaints about quik:
>
> [snip]
> b) oldworld macs (with very few exceptions) lack the ability to
> interface with OF from the console, instead you must use a serial
>
Ethan Benson wrote:
>
> yaboot will not work on oldworld macs, that is why the documentation
> says it won't and does not tell you how to set it up ;-)
>
> this question seems to come up over and over and over and over again,
> for some reason alot of people want to make yaboot work on oldworld
>
On Mon, Jun 05, 2000 at 09:10:24PM -0700, Brian Macy wrote:
> I'm trying to get my StarMax 4400 (OF 2.02) to like yaboot. Simply can't
> get it to work. Since it is not a "New World" Mac 90% of the
> documentation is not quite right.
yaboot will not work on oldworld macs, that is why the documenta
I'm trying to get my StarMax 4400 (OF 2.02) to like yaboot. Simply can't
get it to work. Since it is not a "New World" Mac 90% of the
documentation is not quite right.
Brian Macy
21 matches
Mail list logo
