I have located the driver “devc-doc” in Patch A for M-sys DiskOnChip
and I was able to use it successfully. Now I’m trying to determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.
The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.
I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.
Duane Mattern <raf5de6k@yahoo.com>
Hi:
I have a client that requires an application to be built on an ADL board
containing a DOC2000, within a very short timescale. We are trying to decide
whether to use QNX4 or NTO; if the current driver for NTO is buggy, then
we’ll definitely be using QNX4 where (presumably), the DOC driver is more
stable.
Could someone from QNX please verify the status of the driver for NTO as
requested by Duane below.
“raf5de6k” <raf5de6k@yahoo.com> wrote in message
news:3acb1001.3596841@inn.qnx.com…
I have located the driver “devc-doc” in Patch A for M-sys DiskOnChip
and I was able to use it successfully. Now I’m trying to determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.Duane Mattern <> raf5de6k@yahoo.com
On Fri, 27 Apr 2001 10:06:15 -0500, “Lionel Johnson”
ljohnson**nospam**@sterling1.com wrote:
Hi:
I have a client that requires an application to be built on an ADL board
containing a DOC2000, within a very short timescale. We are trying to decide
whether to use QNX4 or NTO; if the current driver for NTO is buggy, then
we’ll definitely be using QNX4 where (presumably), the DOC driver is more
stable.Could someone from QNX please verify the status of the driver for NTO as
requested by Duane below.
The DOC driver is written by M-System and it’s their reponsability.
QNX (the compnay) has little to do with it.
Thanks
LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com
“raf5de6k” <> raf5de6k@yahoo.com> > wrote in message
news:> 3acb1001.3596841@inn.qnx.com> …
I have located the driver “devc-doc” in Patch A for M-sys DiskOnChip
and I was able to use it successfully. Now I’m trying to determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.Duane Mattern <> raf5de6k@yahoo.com
Mario:
The M-systems site does not post a driver for NTO. The driver and very good
supporting documentation is posted for QNX4. An entry in M-systems FAQ,
dated 1/13/2001, indicates that the “M-systems is working with QNX to
produce a driver for NTO”. Also, NTO does not appear in the M-systems
compatibility list (QNX4.25 does). I’ve asked them for more info, but does
anyone else have any more information?
Thanks
Lionel
“Mario Charest” <mcharest@nozinformatic.com> wrote in message
news:3ae99b72.10021710@inn.qnx.com…
On Fri, 27 Apr 2001 10:06:15 -0500, “Lionel Johnson”
ljohnsonnospam@sterling1.com> wrote:Hi:
I have a client that requires an application to be built on an ADL board
containing a DOC2000, within a very short timescale. We are trying to
decide
whether to use QNX4 or NTO; if the current driver for NTO is buggy, then
we’ll definitely be using QNX4 where (presumably), the DOC driver is more
stable.Could someone from QNX please verify the status of the driver for NTO as
requested by Duane below.
The DOC driver is written by M-System and it’s their reponsability.
QNX (the compnay) has little to do with it.Thanks
LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com
“raf5de6k” <> raf5de6k@yahoo.com> > wrote in message
news:> 3acb1001.3596841@inn.qnx.com> …
I have located the driver “devc-doc” in Patch A for M-sys DiskOnChip
and I was able to use it successfully. Now I’m trying to determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.Duane Mattern <> raf5de6k@yahoo.com
This keeps and keeps popping up althought it has been answered dozen
times already. Do people ever search newsgroups archives before asking
these days? You often can find answer in archives faster than someone
answers again, believe me.
Now, dozen + 1 times:
The DOC driver for NTO is in QNX6 public repository, it’s been there for
a while. Somewhere in ‘public software’ or alike.
Lionel Johnson wrote:
Mario:
The M-systems site does not post a driver for NTO. The driver and very good
supporting documentation is posted for QNX4. An entry in M-systems FAQ,
dated 1/13/2001, indicates that the “M-systems is working with QNX to
produce a driver for NTO”. Also, NTO does not appear in the M-systems
compatibility list (QNX4.25 does). I’ve asked them for more info, but does
anyone else have any more information?
Thanks
Lionel–
Lionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com“Mario Charest” <> mcharest@nozinformatic.com> > wrote in message
news:> 3ae99b72.10021710@inn.qnx.com> …
On Fri, 27 Apr 2001 10:06:15 -0500, “Lionel Johnson”
ljohnsonnospam@sterling1.com> wrote:Hi:
I have a client that requires an application to be built on an ADL board
containing a DOC2000, within a very short timescale. We are trying to
decide
whether to use QNX4 or NTO; if the current driver for NTO is buggy, then
we’ll definitely be using QNX4 where (presumably), the DOC driver is more
stable.Could someone from QNX please verify the status of the driver for NTO as
requested by Duane below.
The DOC driver is written by M-System and it’s their reponsability.
QNX (the compnay) has little to do with it.Thanks
LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com
“raf5de6k” <> raf5de6k@yahoo.com> > wrote in message
news:> 3acb1001.3596841@inn.qnx.com> …
I have located the driver “devc-doc” in Patch A for M-sys DiskOnChip
and I was able to use it successfully. Now I’m trying to determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.Duane Mattern <> raf5de6k@yahoo.com
Igor:
Mine (and Duane’s) problem is not finding the driver in the repository. The
problem is that there is a concern over whether that driver (version 4.2.0)
has a power cycle issue that can corrupt the contents of the DiskOnChip -
and, if that is the case, whether there is an update somewhere on the
horizon.
A search of my own archives of the newsgroups has not revealed any more
information.
“Igor Kovalenko” <Igor.Kovalenko@motorola.com> wrote in message
news:3AE9E76A.7B22EE8@motorola.com…
This keeps and keeps popping up althought it has been answered dozen
times already. Do people ever search newsgroups archives before asking
these days? You often can find answer in archives faster than someone
answers again, believe me.Now, dozen + 1 times:
The DOC driver for NTO is in QNX6 public repository, it’s been there for
a while. Somewhere in ‘public software’ or alike.
- Igor
Lionel Johnson wrote:
Mario:
The M-systems site does not post a driver for NTO. The driver and very
good
supporting documentation is posted for QNX4. An entry in M-systems FAQ,
dated 1/13/2001, indicates that the “M-systems is working with QNX to
produce a driver for NTO”. Also, NTO does not appear in the M-systems
compatibility list (QNX4.25 does). I’ve asked them for more info, but
does
anyone else have any more information?
Thanks
Lionel–
Lionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com“Mario Charest” <> mcharest@nozinformatic.com> > wrote in message
news:> 3ae99b72.10021710@inn.qnx.com> …
On Fri, 27 Apr 2001 10:06:15 -0500, “Lionel Johnson”
ljohnsonnospam@sterling1.com> wrote:Hi:
I have a client that requires an application to be built on an ADL
board
containing a DOC2000, within a very short timescale. We are trying to
decide
whether to use QNX4 or NTO; if the current driver for NTO is buggy,
then
we’ll definitely be using QNX4 where (presumably), the DOC driver is
more
stable.Could someone from QNX please verify the status of the driver for NTO
as
requested by Duane below.
The DOC driver is written by M-System and it’s their reponsability.
QNX (the compnay) has little to do with it.Thanks
LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com
“raf5de6k” <> raf5de6k@yahoo.com> > wrote in message
news:> 3acb1001.3596841@inn.qnx.com> …
I have located the driver “devc-doc” in Patch A for M-sys
DiskOnChip
and I was able to use it successfully. Now I’m trying to
determine
if this is a new and improved driver, or if this is the same driver
from last December that had a critical error.The driver in Patch A says:
“Driver for M-Systems DiskOnChip, Version 4.2.0”.I would appreciate it if someone from QNX could verify that this is
not the old problem driver for DiskOnChip.Duane Mattern <> raf5de6k@yahoo.com
Yes the DOC driver for NTO is in QNX6 public repository. The driver
in the repository is “devc-doc”, identified as: “Driver for M-Systems
DiskOnChip, Version 4.2.0”. I have been able to use this driver
successfully, but I have not been able to obtain any confirmation from
QNX that this driver is not the same driver that had problems back in
December of 2000. [read: NO CONFIDENCE]
The problem with the old DiskOnChip driver appears to occur during
when power is turned lost during a critical time. The “bug” causes
the DOC to lose its format. I have not experienced this problem, but
I do not have any confidence in the driver because the email I
recevied from M-sys stated that WHEN a valid driver is available for
QNX RTP, then it will appear on their website. Msys does not have a
DOC driver for QNX NTO on their website.
So, this topic will continue to pop-up in the newsgroup until someone
from QNX verifies that the old problem with the DOC driver has been
fixed and that the new driver in the repository is valid. At that
point, hopefully QNX should allow Msys to make that driver available
on their website.
(btw, I started my search at groups.goggle.com before posting to the
newsgroup.)
On Fri, 27 Apr 2001 19:15:37 -0500, “Lionel Johnson”
ljohnson**nospam**@sterling1.com wrote:
Igor:
Mine (and Duane’s) problem is not finding the driver in the repository. The
problem is that there is a concern over whether that driver (version 4.2.0)
has a power cycle issue that can corrupt the contents of the DiskOnChip -
and, if that is the case, whether there is an update somewhere on the
horizon.A search of my own archives of the newsgroups has not revealed any more
information. Thanks LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com“Igor Kovalenko” <> Igor.Kovalenko@motorola.com> > wrote in message
news:> 3AE9E76A.7B22EE8@motorola.com> …
This keeps and keeps popping up althought it has been answered dozen
times already. Do people ever search newsgroups archives before asking
these days? You often can find answer in archives faster than someone
answers again, believe me.Now, dozen + 1 times:
The DOC driver for NTO is in QNX6 public repository, it’s been there for
a while. Somewhere in ‘public software’ or alike.
- Igor
Lionel Johnson wrote:
Hi:
Thanks for the reply, Duane. Here’s the answer that I just got from
M-systems:
So the ball appears to be back over in QSSL’s court.
Lionel
“raf5de6k” <raf5de6k@yahoo.com> wrote in message
news:3aeb0b4c.16807808@inn.qnx.com…
Yes the DOC driver for NTO is in QNX6 public repository. The driver
in the repository is “devc-doc”, identified as: “Driver for M-Systems
DiskOnChip, Version 4.2.0”. I have been able to use this driver
successfully, but I have not been able to obtain any confirmation from
QNX that this driver is not the same driver that had problems back in
December of 2000. [read: NO CONFIDENCE]The problem with the old DiskOnChip driver appears to occur during
when power is turned lost during a critical time. The “bug” causes
the DOC to lose its format. I have not experienced this problem, but
I do not have any confidence in the driver because the email I
recevied from M-sys stated that WHEN a valid driver is available for
QNX RTP, then it will appear on their website. Msys does not have a
DOC driver for QNX NTO on their website.So, this topic will continue to pop-up in the newsgroup until someone
from QNX verifies that the old problem with the DOC driver has been
fixed and that the new driver in the repository is valid. At that
point, hopefully QNX should allow Msys to make that driver available
on their website.(btw, I started my search at groups.goggle.com before posting to the
newsgroup.)Duane Mattern <> raf5de6k@yahoo.com
[I’m using a compact flash adapter until confidence is returned to the DiskOnChip driver].
On Fri, 27 Apr 2001 19:15:37 -0500, “Lionel Johnson”
ljohnsonnospam@sterling1.com> wrote:
Igor:
Mine (and Duane’s) problem is not finding the driver in the repository.
The
problem is that there is a concern over whether that driver (version
4.2.0)
has a power cycle issue that can corrupt the contents of the DiskOnChip -
and, if that is the case, whether there is an update somewhere on the
horizon.A search of my own archives of the newsgroups has not revealed any more
information. Thanks LionelLionel J Johnson
Sterling Computer Systems Inc.
19270 North Hills Drive
Brookfield, Wisconsin 53045
USA.
Telephone: +1 (262) 796-0063
Fax: +1 (262) 796-1225
email: > ljohnson@sterling1.com“Igor Kovalenko” <> Igor.Kovalenko@motorola.com> > wrote in message
news:> 3AE9E76A.7B22EE8@motorola.com> …
This keeps and keeps popping up althought it has been answered dozen
times already. Do people ever search newsgroups archives before asking
these days? You often can find answer in archives faster than someone
answers again, believe me.Now, dozen + 1 times:
The DOC driver for NTO is in QNX6 public repository, it’s been there
for
a while. Somewhere in ‘public software’ or alike.
- Igor
Lionel Johnson wrote:
Lionel Johnson ljohnson**nospam**@sterling1.com wrote:
: =========
: Lionel, I’ve spoken with our driver guy, he suggests that I give you the
: driver which was pulled,
: so it’s attached here, I’m giving it to you as a beta, and regarding its bug
: our driver guy says:
: “driver functions perfectly well in all case except for the case when system
: is hit by the power failure.
: In the latter case, the filesystem’s data structures appear to be corrupt,
: but underlying flash format is fine.
: This seems to indicate that the root of the problem is on Neutrino
: filesystem’s side.” So maybe it will work for you.
: =========
: So the ball appears to be back over in QSSL’s court.
Nice try, but no. The problem with power-fail is “collateral damage”.
The device is flash, after all, and requires erasure. It does not have
a 512-byte block size (the block size of the QNX4 file system) but some
larger value more convenient for flash (8k, if I recall correctly).
If power-fail occurs during a time when a flash block is being written
(erased), then not only is the filesystem block in question lost, but so
too are 7-15 neighbouring blocks from unrelated files/metadata blocks.
So, it is not that “the filesystems data structures appear to be corrupt”
but that they are, having been subject to interruption in the erase/copy
write cycle necessary for flash. If they’ve enabled compression, then the
extent of the cross-file corruption is increased by that ratio. Also,
it is common for flash in this state to raise ATA ECC or IDNF errors to
indicate this situation, allowing the driver to remap/erase the sectors
in question. Since these are all perculiarities of the device media itself
(flash), and not the filesystem, it is something that should be handled by
the DOC driver. It is possible that eschewing the fs-qnx4 format in
favour of fs-dos with an 8k cluster size would constrain the collateral
damage to the single actively-written file in question, but I suspect
eventual troubles with the FAT (which is sector, not cluster, orientated).