cybppc.device
Greg L. Kimnach
ultra fast wide scsi-3) and plextor
ultaplex wide cd-rom (PX-40TSUWi) on my cyberstorm ppc, but cannot write the
drive's rdb. (error 1001 with pfs3ds's hdinstools). interestingly,
also, the cd-rom does not mount, although the amicdfs dosdriver is set
for the cybppc.device/unit 4.
the harddrive and the plextor are terminated, with the cyberstorm in
the middle of the bus. (i've used both the termpower supplied to bus
option as" on" and "off" on the quantum.)
obviously hdinsttools (and hdtoolbox) will see the quantum, but not
allow the rdb to be saved to the drive. furthermore, the earlystart
screen will not come up--nor will the system boot from a floppy--on a
warm reboot. the system just cycles past the boot device (never scans
the floppy or the 51080a ide bootable devices), on a warm boot.
if, however, i power down and back on, i can get the early start
screen. unfortunately, selecting either the df0: or 51080a: bootable
device results in the aforementioned cyclic behavior of attempting to
boot.
the only way to boot the system is to cold boot with the bootable floppy in the
drive.
i'm hoping that there's something that i'm doing wrong--that it's not a
termination problem. (both the quantum hd and the plextor are
actively terminated devices.) perhaps this quantum is not compatible
with the cyberstorm's scsi?
i've tried prepping the quantum with pfs2ds and pfs3ds, and with the
51080a on the ide bus and not.
it's late. i'm tired. and the baby is crying....
thanks for any insights, as usual.
--
reply to either kim...@en.com or kim...@LERC.NASA.GOV
regards,
greg
Microsoft slogan: How do you want to be aggravated today?
I opted for Betamax, the world for VHS; I for Amiga, the world IBM clones.
"Do or do not, there is no try"--Yoda, Jedi master.
http://www.en.com/users/kimnach
joe
On 04 Jan 2000 05:37:22 GMT, "Greg L. Kimnach" wrote about cybppc.device:
> i have attempted to install my hardrive (quantum wd9100, single ended
> ultra fast wide scsi-3) and plextor
> ultaplex wide cd-rom (PX-40TSUWi) on my cyberstorm ppc, but cannot write the
> drive's rdb. (error 1001 with pfs3ds's hdinstools). interestingly,
> also, the cd-rom does not mount, although the amicdfs dosdriver is set
> for the cybppc.device/unit 4.
>
> the harddrive and the plextor are terminated, with the cyberstorm in
> the middle of the bus. (i've used both the termpower supplied to bus
> option as" on" and "off" on the quantum.)
I have a very similar setup on my CSPPC except I have 50pin Ricoh 7060S burner
instead of a reader as well as an external 25pin Conner tape drive.
I think I remember reading the 40x plextor is the only 68pin CD reader so
I would hesistate to point the finger at the cabling/termination. I hope
that both the Plextor and Quantum SE are ACTIVEly terminated. As I also
own a Quantum SE I'm reasonably sure yours is fine. Maybe check the
term on the 40x ultraPlex.
But the main difference is that I used the supplied Phase5 SCSItools to
write the RDB. Also, my CD software differs in that I'm using MakeCD
and AsimCDFS (both registered). Is it possible that you could try
using the Phase5 RDB tools just to start things off and see if it
will be recognized? Than maybe switch to PFS tools afterwards???
> obviously hdinsttools (and hdtoolbox) will see the quantum, but not
> allow the rdb to be saved to the drive. furthermore, the earlystart
> screen will not come up--nor will the system boot from a floppy--on a
> warm reboot.
Ahh - but which early start screen are you talking about: CSPPC/Mk3,
Amiga, PIV (if you have this card)? Is this a new accellerator card?
If so, have you ever updated the flash and libs? Also, if you're not
using a CVPPC graphics card than you need to hit space to allow the
early startup to work in native modes. Maybe you could list your complete
Amiga hardware/software setup.
> i'm hoping that there's something that i'm doing wrong--that it's not a
> termination problem. (both the quantum hd and the plextor are
> actively terminated devices.)
If you're certain of *active* termination settings then I'd go with my
earlier suggestion of using Phase5's included CSPPC/Mk3 SCSI software.
You can get the latest version from their web site if you need it. I
set up my Quantum Viking2 SE wide ultra HD with the Phase5 SCSITools
using the included readme file. That was back when I had an Mk3 and
it has worked great for more than a year and a half now.
> perhaps this quantum is not compatible with the cyberstorm's scsi?
That seems unlikely since it is an SE Quantum wide ultra like mine.
I could be wrong though. Good luck.........joe
Gavin Kinsey
>
> But the main difference is that I used the supplied Phase5 SCSItools to
> write the RDB. Also, my CD software differs in that I'm using MakeCD
> and AsimCDFS (both registered). Is it possible that you could try
> using the Phase5 RDB tools just to start things off and see if it
> will be recognized? Than maybe switch to PFS tools afterwards???
*NO*! Do not switch tools, the Phase5 HD tools calculate all the RDB values
differently to the rest of the HD prep software out there. Using P5 stuff
and then another tool (or vice versa) *will *mess up your RDB. Pick one tool
that works and then stick with it unless you are prepared to start from
scratch.
--
Gavin Kinsey ICQ #20733693
Email gavin (at) kinsey.u-net.com
You cannot kill time without injuring eternity.
- Thoreau
joe
On Wed, 05 Jan 2000 20:49:16 GMT, "Gavin Kinsey" wrote about Re: cybppc.device:
> I got a message from the man-thing joe,
> >
> > But the main difference is that I used the supplied Phase5 SCSItools to
> > write the RDB. Also, my CD software differs in that I'm using MakeCD
> > and AsimCDFS (both registered). Is it possible that you could try
> > using the Phase5 RDB tools just to start things off and see if it
> > will be recognized? Than maybe switch to PFS tools afterwards???
>
> *NO*! Do not switch tools, the Phase5 HD tools calculate all the RDB values
> differently to the rest of the HD prep software out there. Using P5 stuff
> and then another tool (or vice versa) *will *mess up your RDB. Pick one tool
> that works and then stick with it unless you are prepared to start from
> scratch.
I would not be so sure. I set up my wide ultra Quantum Viking2 hard
drive with Phase5's software (SCSIConfig, UnitControl) but was later
able to modify and/or access the RDB with both "HDToolbox - cybppc" and
JoAnne Dow's RDPrepX programs. If you're implying that the PFS3 tools
may have some sort of conflict with all other HD prep software, I wouldn't
know since I've never used PFS3. But if that's the case, and you're sure
you're right, then I suggest to stick with the Phase5 tools - they WORK.
Otherwise, my wide ultra HD would not be working correctly for the past
year and a half....joe
Greg L. Kimnach
I have a very similar setup on my CSPPC except I have 50pin Ricoh 7060S
burner instead of a reader as well as an external 25pin Conner tape drive.
I think I remember reading the 40x plextor is the only 68pin CD reader so I
would hesistate to point the finger at the cabling/termination. I hope
that both the Plextor and Quantum SE are ACTIVEly terminated. As I also
own a Quantum SE I'm reasonably sure yours is fine. Maybe check the term
on the 40x ultraPlex.
But the main difference is that I used the supplied Phase5 SCSItools to
write the RDB. Also, my CD software differs in that I'm using MakeCD and
AsimCDFS (both registered). Is it possible that you could try using the
Phase5 RDB tools just to start things off and see if it will be recognized?
Than maybe switch to PFS tools afterwards???
Ahh - but which early start screen are you talking about: CSPPC/Mk3,
Amiga, PIV (if you have this card)? Is this a new accellerator card? If
so, have you ever updated the flash and libs? Also, if you're not using a
CVPPC graphics card than you need to hit space to allow the early startup
to work in native modes. Maybe you could list your complete Amiga
hardware/software setup.
If you're certain of *active* termination settings then I'd go with my
earlier suggestion of using Phase5's included CSPPC/Mk3 SCSI software. You
can get the latest version from their web site if you need it. I set up my
Quantum Viking2 SE wide ultra HD with the Phase5 SCSITools using the
included readme file. That was back when I had an Mk3 and it has worked
great for more than a year and a half now.
> perhaps this quantum is not compatible with the cyberstorm's scsi?
That seems unlikely since it is an SE Quantum wide ultra like mine. I
could be wrong though. Good luck.........joe
*************************************************
joe, thanks for the reply. i have also e-mailed ralph schmidt at p5, and
he has no other ideas than proper termination. so i, recalling that many
have said quantums are terrible with their scsi implementation and some
devices "just don't like others", just ordered another harddrive--an
st315150w. (man, are drives getting cheap!)
here are a few items of note:
--the plextor is an actively terminated device, and i am terminating
it.a s well as the quantum.
--last night (tuesday) i had gained access to the cyberstorm's config
screen (esc key). however, it will not display properly on the PIV...looks
like it's being displayed at 15kHz; but the idek shows 31kHz. the
cyberstorm setup screen shows up on each of two halves of a vertically
split screen. (as a result, i've temporarily removed the PIV and have dug out a micronik external scan doubler.)
--so, instead of "esc" to get the csppc setup screen, i should use
"space"? i just tried this alone, in unison with the esc key, and
prior to and after the esc key. so, what's this supposed to do? the
piv manual, in my quick once over, doesn't seem to mention this. nor
does the cyberstorm manual (or the esc key, for that matter.) time to
check the included software readme's, i guess:-)
--as for "which early start screen are you talking about": i was talking
about the amiga's boot menu, since i was attempting the system to force the
system to boot from the floppy after noticing that it would ignore the
floppy on a warm reboot. that didn't work:-(
--the CSPPC is a brandnew card, which i just bought from software hut in
november. i'm assuming it's a dce-produced card, and assume that the ROM
is the latest version. (i'd rather not flash the rom until i get the
harddrive formatted/prepped. but it may be a catch 22.)
--i'm sure it's in the documentation somewhere (but not in the
provided manual), but how do i determine the ROM rev?
--i have tried using the p5-supplied configscsi utility. same result. it
will not write the rdb. (last night i tried with the latest ffs/td-64 and
pdfs3.) it just gives me a "write error" message.
--interestingly, last night's first attempt (after monday night's
failure) at prepping the drive with p5's scsiconfig tool gave me an
"improper dma and cmd[] / either the controller or the device is faulty"
error. that error has not shown up again, because i used the proper values
of 0xfffffffc and 0xffffff for the dma and mask values.) but how
could those values have gotten written, if the rdb refuses to be
written?
--i placed the drive back in the pc from which i yanked it, and the
adaptec 2940uw controller has no problem formatting the drive. so, the
drive is ok.
--i've tried different scsi id's for the quantum: 0, 1, and 8; and
different ids for the plextor: 6 and 9. i thought perhaps the quantum, as
the csppc manual warns, is one of those drives that the csppc doesn't like
to have at id 0.
--i have attempted to use autoconfig of the bus width, bus speed, and
a/synch, and manually set these on the csppc setup. (accordingly
activating or disabling the feature on the quantum.)
--i installed amicdfs on the bootable floppy; however, i have asimcdfs
(v3.10) on the ide boot drive.
-->i discovered that the wb3.5 cd is the culprit in the cd not mounting.
it seems that the cd-rom just spins and locks up the system until i eject
it.
-->booting the system without a cd installed (or even installing a cd
other than wb3.5), the system will boot from the ide harddrive and will
mount the cd.
-->inserting the wb3.5, letting the system lock-up until its removal,
and then inserting another cd causes the system to crash/warm boot.
-->these are problems that i'll address later.
--my complete setup is pretty basic right now...i figured start minimally.
(so, it's not the system, as it will finally be and which i have listed on
my homepage)
--a4000, buster rev11
--csppc 060/60 +603/233. i have placed a fan on the 060rc. csppc rom rev?
--onboard4000 zorro expansion card
--piv, setup in ziii mode.
--the plextor cd and quantum harddrive, each actively terminated and at
a end of the internal scsi bus.
itching to get it working, but thouroughly aggravated after the last two
nights...
thanks for the help, joe. i really appreciate any and all ideas.
Greg L. Kimnach
GK> I got a message from the man-thing joe,
GK> >
GK> > But the main difference is that I used the supplied Phase5 SCSItools to
GK> > write the RDB. Also, my CD software differs in that I'm using MakeCD
GK> > and AsimCDFS (both registered). Is it possible that you could try
GK> > using the Phase5 RDB tools just to start things off and see if it
GK> > will be recognized? Than maybe switch to PFS tools afterwards???
GK>
GK> *NO*! Do not switch tools, the Phase5 HD tools calculate all the RDB values
GK> differently to the rest of the HD prep software out there. Using P5 stuff
GK> and then another tool (or vice versa) *will *mess up your RDB. Pick one tool
GK> that works and then stick with it unless you are prepared to start from
GK> scratch.
GK>
i did switch from the hdinstools, to hdtoolbox, to scsiconfig,
respectively.
too late, but i don't really think i've ever encountered problems in
the past due to doing this.
thanks, gavin.
joe
On 06 Jan 2000 00:39:34 GMT, "Greg L. Kimnach" wrote about Re: cybppc.device:
> joe, wrote in response to me:
> I have a very similar setup on my CSPPC except I have 50pin Ricoh 7060S
> burner instead of a reader as well as an external 25pin Conner tape drive.
> *************************************************
>
> joe, thanks for the reply. i have also e-mailed ralph schmidt at p5, and
> he has no other ideas than proper termination. so i, recalling that many
> have said quantums are terrible with their scsi implementation and some
> devices "just don't like others", just ordered another harddrive--an
> st315150w. (man, are drives getting cheap!)
I think we both have the Quantum wide-ultra SE series. Mine seems to work
with 3 other SCSI devices: 50pin Ricoh burner, 25pin Conner tape drive, and
25pin Zip drive (owned by a friend). So while I wouldn't think it was your
Quantum that was at fault, at least the Seagate is cheap ;)
> here are a few items of note:
> --the plextor is an actively terminated device, and i am terminating
> it.a s well as the quantum.
Excellent. I have had the Quantum actively terminated at one point and it
worked great. However, I now use my active adapters so that my CD burner is
passively terminated on one end and ditto the external tape drive on the
other. And I use 68/25 and 68/50 active adapters to handle the active part
leaving the 68pin cable in the middle.
|-----------|---------|---------|-------|------------|
CDROM 68/50 Quantum CSPPC 68/25 Conner ext tape
passive active wide ultra active passive
term adapter single ended adapter term
> --last night (tuesday) i had gained access to the cyberstorm's config
> screen (esc key). however, it will not display properly on the PIV...looks
> like it's being displayed at 15kHz; but the idek shows 31kHz. the
> cyberstorm setup screen shows up on each of two halves of a vertically
> split screen. (as a result, i've temporarily removed the PIV and have dug out a micronik external scan doubler.)
Yikes - this isn't necessary Greg. All you had to do was hit the Escape key
in the CSPPC early menu and the video would be fixed! This is in the docs
for the P5 flash. I also own the PIV and the setup screen was split into 2
halves exactly as you describe when my CSPPC was new (last Spring). As long
as you have the latest flash and libs in the CSPPC that space bar does the
trick. What's more it REMEMBERS so that you never have to hit the space bar
again! This was done so that the CVPPC and BVPPC cards could display the
early boot menu without a 15KHz monitor using the new BOOTVGA mode.
> --so, instead of "esc" to get the csppc setup screen, i should use
> "space"?
No. Use "esc" to get to the menu. Once there, hit "space" and the video
will change back to 15KHz and the PIV FF will work again. Also, the CSPPC
will remember this so you only have to do it once.
> i just tried this alone, in unison with the esc key, and
> prior to and after the esc key. so, what's this supposed to do? the
> piv manual, in my quick once over, doesn't seem to mention this. nor
> does the cyberstorm manual (or the esc key, for that matter.) time to
> check the included software readme's, i guess:-)
It's nothing to do with the PIV. It's the CSPPC that is doing this with a
new video mode called BootVGA. If the space bar isn't working - you don't
have the latest flash and libs for the CSPPC. That's an easy fix and you'll
be able to use the PIV for early startup again. The space bar toggles
between the BootVGA screen and native video. The PIV FF gets mixed up with
the unexpected new BootVGA screen which is why Ralph added the space bar
business to allow native 15KHz setup screen again. All I can say is it
works on my CSPPC/PIV setup. But you may need the latest flash and libs.
You should get these installed before going any further. They are at
the P5 web site under Amiga, then support. Then there is a link to
the P5 ftp site and these files are in the PPC directory. There you
will find the lastest FlashUpdates, PPC-User, and 060 libs. Get all 3
but do the libs 1st, then the flash. This info in the docs.
> --the CSPPC is a brandnew card, which i just bought from software hut in
> november. i'm assuming it's a dce-produced card, and assume that the ROM
> is the latest version. (i'd rather not flash the rom until i get the
> harddrive formatted/prepped. but it may be a catch 22.)
I don't think it's DCE. You and I both have the identical card bought
from Software Hut (limited production run 60MHz 060/233MHz PPC). And
from what I recall, I did have to update the flash and enable the SCSI
addresses before it would read my Quantum HD. I should add that I had
upgraded from Mk3 060 and that is where I set up my wide ultra bus. So
when I sold that and bought the CSPPC, I thought it would just be hooking
up the cable ;) I'm almost positive that you need the libs, flash, and
then check the SCSI addresses in the flash.
> --i'm sure it's in the documentation somewhere (but not in the
> provided manual), but how do i determine the ROM rev?
Hmmmm. You can do a version cybppc.device iirc. If you download the latest
flash and lib you will see the current version by viewing the history info.
But again, since we both bought the same card from the same place, I'm
going to suggest getting the latest libs, flash, and ppc-user before
doing anything else.
> --i have tried using the p5-supplied configscsi utility. same result. it
> will not write the rdb. (last night i tried with the latest ffs/td-64 and
> pdfs3.) it just gives me a "write error" message.
As a sort of last resort you could try removing the CDROM drive and using
only the Quantum SE hard drive with active terma and power set. To properly
terminate you will need an active term block for the other end of the cable.
However, I've read of folks getting away without that by using a very short
cable with the uw hard drive very close to the CSPPC SCSI3 connector.
Obviously that's not proper termination. But it just may be good enough to
get things running.
*********************************
Sorry, just remembered something. When I purchased my new CSPPC last Spring
it had ALL 15 SCSI addresses turned OFF in the flash!!!!! I'd bet good money
that yours are all turned off to. My advice:
1 -Get the latest libs, flash, (and ppc-user) and get it working. Libs 1st!!!
2 -Then get into the P5 early start, hit space (for PIV FF), and turn on the
appropriate addresses.
> --interestingly, last night's first attempt (after monday night's
> failure) at prepping the drive with p5's scsiconfig tool gave me an
> "improper dma and cmd[] / either the controller or the device is faulty"
> error. that error has not shown up again, because i used the proper values
> of 0xfffffffc and 0xffffff for the dma and mask values.) but how
> could those values have gotten written, if the rdb refuses to be
> written?
>
> --i placed the drive back in the pc from which i yanked it, and the
> adaptec 2940uw controller has no problem formatting the drive. so, the
> drive is ok.
Which combined with my statement above makes me think the addresses are all
turned off. This speeds the boot process and when you get the new flash you
will want to leave all unused addresses turned off again!
> --i've tried different scsi id's for the quantum: 0, 1, and 8; and
> different ids for the plextor: 6 and 9. i thought perhaps the quantum, as
> the csppc manual warns, is one of those drives that the csppc doesn't like
> to have at id 0.
My Quantum is at address 6. I think my burner is at address 2 and my tape
is at address 4. When I hook up a Zip it goes to address 5.
> --my complete setup is pretty basic right now...i figured start minimally.
> (so, it's not the system, as it will finally be and which i have listed on
> my homepage)
> --a4000, buster rev11
> --csppc 060/60 +603/233. i have placed a fan on the 060rc. csppc rom rev?
> --onboard4000 zorro expansion card
> --piv, setup in ziii mode.
> --the plextor cd and quantum harddrive, each actively terminated and at
> a end of the internal scsi bus.
>
> itching to get it working, but thouroughly aggravated after the last two
> nights...
>
> thanks for the help, joe. i really appreciate any and all ideas.
I wish I could be more helpful as we have nearly identical configs. I also
own the limited run 60MHz 060 version of the CSPPC (which I've overclocked
to 72MHz and 252MHz) and the PIV in an A4K and have the IDE disabled with
Warren Blocks IDE eliminator. I rely on the SCSI3 bus for both internal
and external SCSI1,2, and 3 devices and it works great! Maybe a more
detailed email would help to fix the problem: n...@epix.net
> --
> reply to either kim...@en.com or kim...@LERC.NASA.GOV
I would except that my newsreader is pretty basic and will do either news
groups OR email. But if you want to try emailing me directly then use:
n...@epix.net Regards......joe
Greg L. Kimnach
i have succeded in prepping the quantum harddrive!
i attempted to prep it using fastfilesystem 45.1, but it didn't work:
same old write error. then i decided to low level format the drive
with p5's scsiconfig utility. after which i was able to prep the
drive with bootable ffs and pfs3 partitions, and am able to boot from
each!
my cd rom troubles remain. the os3.5 cd will not mount...just locks
up the system. perhs to do with the multiple formats on the cd? so
this has yet to be resolved.
now, why does the piv not display the cyberstorm setup screen
properly. it continues to display twice in two small, unintellible
halves of the monitor:
|
|
tiny | tiny
|
|
the idek shows that it's a 31khz/59hz screen mode.
getting closer to setting up my system.....
Robert J Williams
Greg L. Kimnach <kim...@en.REMOVE.THESE.com> wrote in article
<38740be9$0$14...@news.voyager.net>...
I missed the start of this thread so sorry if any of this has already been
said...
> just a quick update.
>
> i have succeded in prepping the quantum harddrive!
Excellent, I'm using a Quantum Viking II on my CyberStorm and it works very
well.
[SNIP]
> my cd rom troubles remain. the os3.5 cd will not mount...just locks
> up the system. perhs to do with the multiple formats on the cd? so
> this has yet to be resolved.
What CD file system are you using? A friend of mine had a similar problem
with his Ultraplex 40 and AmiCDFS, it would not read some CDs including the
OS 3.5 one, the drive just kept spinning the disc but didn't read anything.
He changed to CacheCDFS (comes with OS 3.5, demo version in the IDEFix
archive on Aminet) and all is well. The problem is peculiar to the
AmiCDFS/Ultraplex 40 combination because I use AmiCDFS with an Ultraplex 32
and the 3.5 CD works fine.
BTW if you do install the demo version of CacheCDFS you'll need to manually
copy over the file from the OS3.5 CD when you get it working to get rid of
the shareware requesters.
HTH
Robert
--
| Vice Chairman and Mag Editor | rob...@williams.demon.co.uk |
| SEAL - South Essex Amiga Link | A3000 CSPPC/060 CVPPC 64Mb OS3.5 |
| http://seal.amiga.tm | PageStream ImageFX Photogenics |
- Clubbed Issue 4 available soon, see website for contents list -
Mike Leavitt
> --the CSPPC is a brandnew card, which i just bought from software hut in
> november. i'm assuming it's a dce-produced card, and assume that the ROM
> is the latest version. (i'd rather not flash the rom until i get the
> harddrive formatted/prepped. but it may be a catch 22.)
> --i'm sure it's in the documentation somewhere (but not in the
> provided manual), but how do i determine the ROM rev?
Just a note here. All those cards were P5 cards. DCE does not have
rights to the CSPPC or any other PPC stuff from P5. Hence they will
not repair it. P5 won't repair it either, as it is no longer
supported. This comes from a dealer I know who tried to get one
repaired. More good news. Ralph, correct me if the dealer is wrong.
I hope he is.
--
Mike Leavitt ac...@lafn.org + team Amiga +
Mike Leavitt
> i did switch from the hdinstools, to hdtoolbox, to scsiconfig,
> respectively.
>
> too late, but i don't really think i've ever encountered problems in
> the past due to doing this.
Putting it back in the PC and reformatting it should have wipped out
the RDB anyway, so you should be able to start over clean on the
Amiga.
Mike Leavitt
> On 01/07/00, "Mike Leavitt" wrote:
> >Just a note here. All those cards were P5 cards. DCE does not have
> >rights to the CSPPC or any other PPC stuff from P5. Hence they will
> >not repair it. P5 won't repair it either, as it is no longer
> >supported. This comes from a dealer I know who tried to get one
> >repaired. More good news. Ralph, correct me if the dealer is wrong.
> >I hope he is.
>
>
> --
> Ralph Schmidt,la...@popmail.owl.de(private),NextMail welcome
Thanks, Ralph. Will you fix my CV64 (not 3D)?
Greg L. Kimnach
in a delusional state claimed thusly:
>> my cd rom troubles remain. the os3.5 cd will not mount...just locks
>> up the system. perhs to do with the multiple formats on the cd? so
>> this has yet to be resolved.
>
>What CD file system are you using? A friend of mine had a similar problem
>with his Ultraplex 40 and AmiCDFS, it would not read some CDs including the
>OS 3.5 one, the drive just kept spinning the disc but didn't read anything.
>He changed to CacheCDFS (comes with OS 3.5, demo version in the IDEFix
>archive on Aminet) and all is well. The problem is peculiar to the
>AmiCDFS/Ultraplex 40 combination because I use AmiCDFS with an Ultraplex 32
>and the 3.5 CD works fine.
>
>BTW if you do install the demo version of CacheCDFS you'll need to manually
>copy over the file from the OS3.5 CD when you get it working to get rid of
>the shareware requesters.
i discovered the problem yesterday: it seems that os 3.5 (whether the
emergencyboot diskette, os 3.1 with the initial 3.5 pre-installation, or a full
3.5 install), will not boot if the a4000's ide interface is left open. 3.1
boots without a hitch, regardless of the ide interface status.
btw, i will be using asimcdfs 3.10 registered.
--
regards, //"I've noticed you're always last, soldier!"
greg //"I'm pacing myself, Sergeant."
------------------------------------------------------------------------------
Multiculturism is a euphemism for national division.
Greg L. Kimnach Kim...@GRC.NASA.GOV
NASA Glenn Research Center at Lewis Field
21000 Brookpark RD. MS 301-5 "ED Beta is simply the best videotape format
Cleveland, OH 44135 available." --Video Magazine (Nov. 22, 1992)
216-433-6251
I opted for Betamax, the world for VHS; I for Amiga, the world for IBM-clones.
Microsoft slogan: "How do you want to be aggravated today?"
------------------------------------------------------------------------------
Thomas M. Beck
>
> "GK" == "in a delusional state claimed the following:
>
> GK> *NO*! Do not switch tools, the Phase5 HD tools calculate all the RDB values
> GK> differently to the rest of the HD prep software out there. Using P5 stuff
> GK> and then another tool (or vice versa) *will *mess up your RDB. Pick one tool
> GK> that works and then stick with it unless you are prepared to start from
> GK> scratch.
> GK>
>
> respectively.
>
> too late, but i don't really think i've ever encountered problems in
> the past due to doing this.
That's strange because I encountered serious problems when I switched
from HDToolBox to P5 SCSI tools. I tried the P5 SCSI tools that came
with my B2060 (I think they are the same than the CSPPC ones) on a HD
that was configured with HDToolBox. IIRC, I just created one new
partition destroying two old ones and wanted to leave some others
untouched. I tried to reboot to format the new partition but the HD
was totally screwed. DiskSalv was not able to recover anything. Then
I used a disk monitor to see what has happened because most of the
data should still have been there since nothing was formatted.
I discovered that the root block ended up at a different location
than with HDToolBox. So I switched back to HDToolBox entered the
partition sizes and blocks by hand and was able to recover all data
besides the one that was overwritten by the wrong root block.
So from my experience I only can confirm Gavin's advice.
Bye,
Thomas - Amiga user since '88 - A500, A2000, A3000D
Robert J Williams
Greg L. Kimnach <kim...@grc.REMOVE.THESE.nasa.gov> wrote in article
<85d70k$gii$1...@sulawesi.lerc.nasa.gov>...
> i discovered the problem yesterday: it seems that os 3.5 (whether the
> emergencyboot diskette, os 3.1 with the initial 3.5 pre-installation, or
a full
> 3.5 install), will not boot if the a4000's ide interface is left open.
3.1
> boots without a hitch, regardless of the ide interface status.
That's odd, I have an A4000 (desktop) with 3.5 and it boots fine without
anything connected to the IDE, however it has a CyberStorm MkI and SCSI
controller not a PPC card (which is in my A3k).
Thomas M. Beck
>
> On 01/11/00, "Thomas M. Beck" wrote:
> >
> >That's strange because I encountered serious problems when I switched
> >from HDToolBox to P5 SCSI tools. I tried the P5 SCSI tools that came
> >with my B2060 (I think they are the same than the CSPPC ones) on a HD
> >that was configured with HDToolBox. IIRC, I just created one new
> >partition destroying two old ones and wanted to leave some others
> >untouched. I tried to reboot to format the new partition but the HD
> >was totally screwed. DiskSalv was not able to recover anything. Then
> >I used a disk monitor to see what has happened because most of the
> >data should still have been there since nothing was formatted.
> >I discovered that the root block ended up at a different location
> >than with HDToolBox.
>
> The RDSK can remain in any block between 0 and 15 and scsiconfig
> always puts it at block2 because of ancient virus rdb overwrites
> which could have been easily possible.
Hmm, I don't think we're talking about the same type of block here.
I don't mean the RDB. It even were several adjacent blocks and the
tool I used named the first root block and the others bit allocation
map blocks or so. What I definitely can remember is that the block
numbers were in the high thousands and that these blocks were moved
some blocks when using the P5 tools.
Now, if I think about it I must have done something else than
creating a new partition. Because then it wouldn't matter where the
new root block of the partition is located. Maybe I just wanted
to increase the buffers for the partition using the P5 tools.
/speculation mode on - I'm not familiar with the file system structure
Maybe it has something to do with the hard disk size. At that time
I used a 2.1GB IBM DORS. Maybe HDToolBox didn't calculate the correct
size of 2.1GB but only 2GB and therefore put the partition root blocks
to a slightly different position than P5's scsiconfig.
How about that?
/speculation mode off
Keith Rigby
Can anyone help me, I have just recently come back to the Amiga scene and
have been given an A1200, can anyone tell me if I need any drivers or how to
get the 3COM USR 56K V90 Fax Modem to work with the A1200 and what I need to
do to the computer so that I can use it on the Internet?
Regards
Keith Rigby
Terrance Richard Boyes
> Can anyone help me, I have just recently come back to the Amiga scene and
> have been given an A1200, can anyone tell me if I need any drivers or how to
You don't need any "drivers" as such for the modem, just plug it in :)
What you do need is some form of comms package or TCP/IP stack (they
come with the required device's).
> get the 3COM USR 56K V90 Fax Modem to work with the A1200 and what I need to
> do to the computer so that I can use it on the Internet?
AmiTCP or Miami (the latter is slightly easier to setup, though
recent releases of the commercial version of AmiTCP aren't much
more difficult).
If you want to use the fax capabilities then STFax is a good package.
--
<URL:http://www.pierrot.co.uk/> Team AMIGA
Wear me as a seal upon your heart, as a seal upon your arm; for love is
strong as death, passion cruel as the grave; it blazes up like blazing fire,
fiercer than any flame. [Song of Solomon 8:6 (NEB)]
Marcel DeVoe
> Hi there,
> Can anyone help me, I have just recently come back to the Amiga scene and
> have been given an A1200, can anyone tell me if I need any drivers or how to
> get the 3COM USR 56K V90 Fax Modem to work with the A1200 and what I need to
> do to the computer so that I can use it on the Internet?
Do you have a hard drive in the Amiga? It's not worth it unless you have a
hard drive.
I have the same modem. But I hope yours is an external one or you can't
use it in the Amiga.
I use Miami as a TCP/IP stack to dial up my provider. That's probably the
easiest one to log on with. Then there are a choice of 3 browsers, but
with a stock 2 meg Amiga I would recommend AWeb as it uses the least
memory.
These files should be available on Aminet for downloading onto your PC on
a PC formatted floppy disk and transferred to your Amiga. You will need to
have a PC mountlist activated in it in order to be able to read the PC
disk. You should have the PC0 driver installed in the Workbench's
DEVS:Dosdrivers drawer.
And if your 1200 doesn't have an HD floppy drive, you will need to
format your disks as 720k ones on your PC.
CC:'ed and posted, if you feel you need to reply, please do so to the
newsgroup post.
--
Marcel J. DeVoe - mde...@shore.net - Team *AMIGA*
A4091scsi CV64 96 megs CDRW M1764-17" Catweasel FUSION/Emplant
A4000/060 CyberStorm MKII overclocked 66mhz - see "How to Overclock!"
and "DIY A4000 Tower for $45" @ http://www.shore.net/~mdevoe
Got an overclocking story to tell of /any/ kind?
Send it to me and I will post it to my "Overclocker's Web Page".