TIP: Click on subject to list as thread! ANSI
echo: cis.os9.68000.osk
to: Bob van der Poel 76510,2203 (X)
from: Carl Kreider 71076,76
date: 1993-10-10 16:29:41
subject: #19054-#Review: 340 Upgrade

#: 19062 S12/OS9/68000 (OSK)
    10-Oct-93  16:29:41
Sb: #19054-#Review: 340 Upgrade
Fm: Carl Kreider 71076,76
To: Bob van der Poel 76510,2203 (X)

Bob and all,

I don't know if this is a definitive primer on inizing, but here is my slant on
it.  It can reduce fragmentation problems.  It can introduce problems since the
init routine in the driver no longer gets run when a path is opened.  My
feeling is that having to iniz is a gross hack and should not be done.
However, it *is* necessary when doing an os9gen. I haven't a clue why.  It acts
the same on my 030 as it does on an MM/1. I have looked for the problem but
can't find it.  But the current incarnation of the floppy driver needs to pass
through init to deal with the cleverness of auto-sizing.  So inizing it can
defeat the auto-sizing and cause the occasional error, like what Zack
mentioned.  I have never seen it actually hose a disk or anything that vile,
but it can report free space wrong.

If I find it, I'll fix it.

Carl

There is 1 Reply.

SOURCE: compuserve via textfiles.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.