In article <M4s*8R0rr@news.chiark.greenend.org.uk>,
Theo Markettos <theom+news@chiark.greenend.org.uk> wrote:
Quote:
Rod at Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
I thought I had done this but when I checked I found that while CDFSSoftATAPI and CDFSSoftSCSI2 were unplugged CDFSSoftChinonEESOX, CDFSSoftHitachiEESOX, CDFSSoftPhilipsEESOX, CDFSSoftSonyEESOX and CDFSSoftToshibaEESOX were all active again. Why this is I've no idea; what could have reactivated them? Anyway, I've left CDFSSoftATAPISimtec active as I intend to refit the CD writer next and have '*Unplugged' the rest.
Don't worry about CDFSSoftReallyAncientDrives - they'll only activate when ReallyAncientDrives are attached. Unplugging CDFSSoftATAPI is wise if you don't have any motherboard IDE drives, because otherwise it'll hang waiting for them.
Yes. CDFSSoftATAPI and CDFSSoftSCSI2 are both unplugged.
But the CDFSSoftReallyAncientDrives seem to be in the expansion card (UniPod)
as is CDFSSoftATAPISimtec which would explain why they are all active after a
re-boot or power up even though I've '*Unplugged' them.
Quote:
What is the difference between 'Dormant' and 'Unplugged'? Although I've 'Unplugged' them they are flagged as 'Dormant' (using !Verma).
'Dormant' means 'the module gave an error when the kernel tried to start it so it's not loaded'. 'Unplugged' means 'the user issued a *Unplug command or a *Unplug command last time set the relevant CMOS RAM bit which we remembered'. The difference being that when you reboot the Dormant modules will try to reinitialise (and will succeed if they don't produce an error) while the Unplugged ones won't.
One other thing, does !Boot => Configuration => Discs => CD-ROMs apply just to the native ADFS side or to the UniPod as well?
Both. CDFS scans its CDFSSoftXXXX driver modules for drives of all possible connections, and this tells it how many to expect. I've never quite understood why this is necessary - but at the very least it tells CDFSFiler how many drive icons to put up.
Thanks for that Theo. I'm slowly learning!
What is the function/purpose of '~CDReinit' in Tasks?
Still, after all that the machine still won't boot up on power up. It always
needs at least one re-boot or reset.
In article <4e6e0e739dGroverR@orpheusmail.co.uk>, Rod at
Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
[Snip]
Quote:
Yes. CDFSSoftATAPI and CDFSSoftSCSI2 are both unplugged. But the CDFSSoftReallyAncientDrives seem to be in the expansion card (UniPod) as is CDFSSoftATAPISimtec which would explain why they are all active after a re-boot or power up even though I've '*Unplugged' them.
I haven't been following this thread closely but the above quote
caught my attention. The flash ROM on UNIpod may have to hold
many modules if all the card functions are activated, especially
USB. Mine has 13 at the moment. When un-plugging, you need to
remember that there only 1 CMOS byte/podule is allocated so,
only the first 8 modules can be unplugged. Thus the order of
the modules may be important.
Using !Snafu you can enter the modules in any order you like by
dragging them in one at a time from the deeply nested
directories in !Snafu.handlers where they live, rather than load
defaults when you get over 30 modules and have no control over
their order.
You can of course also directly delete the modules such as
CDFSSoftReallyAncientDrives and re-flash without them.
I hope that is useful even though you have solved your original
problem.
In article <4e6f09a2a5bric-nospam@argonet.co.uk>,
Brian Carroll <bric-nospam@argonet.co.uk> wrote:
Quote:
In article <4e6e0e739dGroverR@orpheusmail.co.uk>, Rod at Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
[Snip]
Yes. CDFSSoftATAPI and CDFSSoftSCSI2 are both unplugged. But the CDFSSoftReallyAncientDrives seem to be in the expansion card (UniPod) as is CDFSSoftATAPISimtec which would explain why they are all active after a re-boot or power up even though I've '*Unplugged' them.
I haven't been following this thread closely but the above quote caught my attention. The flash ROM on UNIpod may have to hold many modules if all the card functions are activated, especially USB. Mine has 13 at the moment. When un-plugging, you need to remember that there only 1 CMOS byte/podule is allocated so, only the first 8 modules can be unplugged. Thus the order of the modules may be important.
Using !Snafu you can enter the modules in any order you like by dragging them in one at a time from the deeply nested directories in !Snafu.handlers where they live, rather than load defaults when you get over 30 modules and have no control over their order.
You can of course also directly delete the modules such as CDFSSoftReallyAncientDrives and re-flash without them.
I hope that is useful even though you have solved your original problem.
Thanks for that Brian. Reminds me, I must check that I've got the latest
UniPod modules.
Theo in <M4s*8R0rr@news.chiark.greenend.org.uk> seem to think that their
presence didn't matter "Don't worry about CDFSSoftReallyAncientDrives -
they'll only activate when ReallyAncientDrives are attached."
I'm still getting problems and it seems to me to be either the UniPod IDEFS
Primary channel or the UniPod IDEFS.
There are a few more things that I want to try but as I'm away again until
next week I may not have the time until I come back.
In article <4e6f8c5ebcGroverR@orpheusmail.co.uk>, Rod at
Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
[Snip]
Quote:
Thanks for that Brian. Reminds me, I must check that I've got the latest UniPod modules.
Since all the modules are provided within !Snafu you merely need
to check you have the latest version of that which is 1.83. See http://www.stdevel.co.uk/supp_uni.html . The modules are a set;
don't be tempted to pick and mix.
You have to load !Snafu to find out the version, but there is no
'info' window. All the files in v1.83 seem to be dated 31 Jan
2005.
Quote:
Theo in <M4s*8R0rr@news.chiark.greenend.org.uk> seem to think that their presence didn't matter "Don't worry about CDFSSoftReallyAncientDrives - they'll only activate when ReallyAncientDrives are attached."
Theo is right. But I was suggesting you can delete them all, or
not flash them in, and other unused modules such a VProtect and
all the RMFSxxx modules as well.
Quote:
I'm still getting problems and it seems to me to be either the UniPod IDEFS Primary channel or the UniPod IDEFS.
I'm using 2 x 80Gb discs on the UNIpod primary channel with no
problems. Both drives were however formatted using HForm when
they were temporarily connected to the motherboard IDE - I will
explain why later if necessary, it has nothing to do with your
problem.
In article <4e6ff6e07cbric-nospam@argonet.co.uk>,
Brian Carroll <bric-nospam@argonet.co.uk> wrote:
Quote:
In article <4e6f8c5ebcGroverR@orpheusmail.co.uk>, Rod at Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
[Snip]
Thanks for that Brian. Reminds me, I must check that I've got the latest UniPod modules.
Since all the modules are provided within !Snafu you merely need to check you have the latest version of that which is 1.83. See http://www.stdevel.co.uk/supp_uni.html The modules are a set; don't be tempted to pick and mix.
Yes, I'm using !Snafu v1.83
Quote:
You have to load !Snafu to find out the version, but there is no 'info' window. All the files in v1.83 seem to be dated 31 Jan 2005.
[snip]
Quote:
I'm still getting problems and it seems to me to be either the UniPod IDEFS Primary channel or the UniPod IDEFS.
I'm using 2 x 80Gb discs on the UNIpod primary channel with no problems. Both drives were however formatted using HForm when they were temporarily connected to the motherboard IDE - I will explain why later if necessary, it has nothing to do with your problem.
I've been doing a bit of experimenting with the following results:
(UniPod 'F' = Fitted; 'PM' = Primary Master, 'PS' = Primary Slave etc.)
ADFS UniPod CD-ROM MYhopper VF Result
Mas Sla F PM PS SM SS R/RW
Y Y - - - - - - - - OK (45 secs)
Y Y - - - - - - Y - OK
Y Y - - - - - - Y Y OK
Y Y Y - - - - - - - OK
Y Y Y - - - - - Y - OK
Y Y Y - - - - - - Y NOK
Y Y Y - - - - - Y Y NOK
Y Y Y Y - - - - - - OK
Y Y Y Y - - - - Y - OK
Y Y Y Y - - - - Y Y NOK
Y Y Y Y Y - - RW - - OK
Y Y Y Y Y - - RW Y - OK
Y Y Y Y Y Y - RW Y - OK (RW - PS)
Y Y Y Y Y Y Y R/RW Y - OK (RW - PS, R - SS)
Y Y Y Y Y - - - Y Y NOK
Y Y Y Y Y - - RW Y Y NOK
I'm running it set up as 14 above without any problems booting up first time
at power up and also no problems with either the CD writer of CD ROM drives.
This seems to suggest that there is some sort of clash or problem between the
ViewFinder and the UniPod. The ViewFinder is firmware version 1.53 (I think)
the card is a Rage 128 Pro 32M SDR.
Has anyone had any experience of ViewFinder and UniPod working together?
Any thoughts would be greatly appreciated.
I won't be able to try anything else until I get back next week.
On 28-Sep-2006, Rod at Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
Quote:
Also, if using a CD reader and a CD writer on a Unipod make sure the writer is the master. But how important is this when using a hard drive and a CD writer? i.e a hard drive as master and CD writer as slave on the same channel?
It's important for CDBurn as it only checks the first CD drive it finds on any filing system to see if it's a writer. If it finds the reader first it won't find the writer.
Could you elaborate? Having a quick look at my code I can see nothing
wrong with it. I did quick tests with a Simtec IDE-equipped Risc PC and
an IYONIX pc (the only two configurations I could quickly test in the
described scenario) and everything worked fine just as expected with
a Master CD-ROM and a Slave CD-RW.
Do you remember where you have encountered that problem - is it a
Unipod problem as suggested above?
In article <4ol4luFep3f9U1@individual.net>,
Steffen Huber <spam@huber-net.de> wrote:
Quote:
Do you remember where you have encountered that problem - is it a Unipod problem as suggested above?
I had problems with writer and reader both the IDE and Unipod busses - CD
burn not finding the writer, which it had done before, until being told to
try the writer as master. And the problems weren't confined to CD burn -
both units were very flaky even just playing a CD. Kept getting drive
empty or not found. Strangely, they'd worked ok in the old configuration
on the IDE bus under 3.7 before I updated to 4.02. At the same time I
change the RapIDE which had the HDs to the Unipod. Too many changes at the
same time. But everything is fine now all running off the Unipod.
--
*A nest isn't empty until all their stuff is out of the attic
On 5-Oct-2006, Steffen Huber <spam@huber-net.de> wrote:
Quote:
David Holden wrote:
Quote:
On 28-Sep-2006, Rod at Orpheusmail <GroverR@orpheusmail.co.uk> wrote:
Quote:
> Also, if using a CD reader and a CD writer on a Unipod make sure the> writer is the master. But how important is this when using a hard drive and a CD writer? i.e a hard drive as master and CD writer as slave on the same channel?
It's important for CDBurn as it only checks the first CD drive it finds on any filing system to see if it's a writer. If it finds the reader first it won't find the writer.
Could you elaborate? Having a quick look at my code I can see nothing wrong with it. I did quick tests with a Simtec IDE-equipped Risc PC and an IYONIX pc (the only two configurations I could quickly test in the described scenario) and everything worked fine just as expected with a Master CD-ROM and a Slave CD-RW. Do you remember where you have encountered that problem - is it a Unipod problem as suggested above?
ISTR seeing something like this in the CDBurn manual ages ago (though I
can't find it now so I could be wrong) and I have therefore often given this
advice to people who have had trouble with CDBurn recognising their CD
writer when they also have a CD reader. Most of the time it has improved
matters, whatever the IDE interface.
The fact that Rod also says the same thing leads me to believe it has some
validity.
NB. I don't regard it as a 'bug' or 'problem' as it's so easily fixed.
The MyLounge.com forum is intended for informational use only and should not
be relied upon and is not a substitute for any advice. The information contained
on MyLounge.com are opinions and suggestions of members and is not a representation
of the opinions of MyLounge.com. MyLounge.com does not warrant or vouch for
the accuracy, completeness or usefulness of any postings or the qualifications
of any person responding. Please consult a expert or seek the services of an
attorney in your area for more accuracy on your specific situation. Please note
that our forums also serve as mirrors to Usenet newsgroups. Many posts you see
on our forums are made by newsgroup users who may not be members of MyLounge.com
Term of Service