#WB2.1 Happy Thanksgiving
33 messages in this thread
It seems that 2.1 is giving me some real headaches. First, it keeps
popping a requester saying that there is no disk in DF0: I have nothing
that uses DF0: on startup. Now, I'm getting read errors on my floppy
drives. I think the new setpatch is to blame for it. What did they do to
this WB?! Big deal, now I got a bell to ring, I wish I could turn the
Flash off, who wants their screen to flash BLACK anyway? Now, in less than
7 hours, I've had my internal hard disk turn belly up, my master disk of
AMAX 2.51 be accused by the OS of having read errors, my PSFONTS: Syquest
cartridge become a DHR:NDOS disk, and Ami-Back 2.0 is now crashing, so is
AMAX locking up on RESTART, and Gee, where else can you get this kind of
value for $45?! Anyone want an Amiga? I'll send you all the pieces, made
to fit inside a matchbox. Maybe I'll just stuff it and serve it instead of
the bird, it seems like its become a bigger turkey.
Chris
ouch! let us know what you learn.
Michael,
Well it seems the drive going south was coincidental. After examining my
user-startup for the umpteenth time I found two lines calling for, what
else, something that was in the broken drive's C: directory! It seems when
the OS can't find the path it looks elsewhere and that includes df0: even
if it isn't in your defined path. I put the files on the (now boot drive)
cartridge and it works OK now. Disksalv couldn't do a thing for my
PSFONTS: cartridge, except get the file structure off it. FixDis.zoo did
an amazing job of soothing my nerves, after unpacking I put it right on
the job, it said "first block should be….can I fix it?…", clicked OK
and cringed, the drive light flashed, and it started reading the blocks
listing the files. I aborted that, and voilla' the correct disk icon
appeared on the WBench! Double-click and it opened to reveal its still
intact contents! Pheeww! The floppy disk error was still on my AMAX master
disk, but this time the floppy drive correctly formatted the new disk, and
disksalv successfully copied Amax's contents to RAM: which I then copied
to the new disk. Guess, I'll mail it back to ReadySoft, maybe they'll give
me a newer version if available. Though all seems to have gotten better,
I'm not too sure yet if all is well. PSFONTS: cart is getting a fresh
backup to tape, and AMI-BACK seems to be having trouble pulling just the
one file, AMAXconfig from the tape. It locks stops after a while and gives
me a requester with the SUSPEND or REBOOT option. I did use verify mode
when I made the backup and the report was all was well. I just can't
remember the pen settings for White and Black in the AMAX config screen.
Anyway, I have to go through one of these every few months just to try
my nerves. I hate it! <grin> At least I got a shiny new Hayes Ultra 9600
modem to play with for a while, 'til the brother-in-law needs it back. He
called me to say that he found ANOTHER one at work in a co-worker's office
<continued>
who ALSO doesn't know what to do with it! So he grabbed it for now for me
to hook up for him at home. Wonder what these things cost a year ago? I
noticed mailorder they're around $600? Oh a question, I set the modem
serial prefs for 19200 and let it log on the 9600 node, I get a connect
response of 19200 although I know CIS is locked at 9600. Is this just the
modem thinking it connected? Anyway,
Happy Thanksgiving, gobble, gobble,
Chris
The 19200 speed is the serial port to modem speed, not the actual rate at
which you are connected to the host… I keep my 'link' speed a t 38400
when online with CIS at 9600 baud.
Sounds like everything is working pretty smoothly now… I guess this is
just the bit gods way of reminding you that while coomputers are look
really neat, they are just still manufactured and used by mere mortals.
Michael,
When I set my link speed greater than 9600, my SuprFax 14,400 baud modem
signals 144 and doesn't connect with CIS. When I back down to 9600 link
speed there is no problem, usually, with connecting. What is the
advantage of setting the link speed at 38400 if you're unable to connect
to CIS at 9600?
Patrick White
<<<<<<Auto User>>>>>>>>>
Patrick,
It sounds like you've got the modem set to disable data buffering
(&Q0 mode).
Don
Patrick: I have no problem using the 38400 link speed with AutoPilot and
the Supra 14.4K modem. It sounds like you don't have the proper cable for
hardware CTS/RTS handshaking, or don't have something set up properly in
the software. The advantage of using the 38400 link speed is that with a
theoredicle 4:1 data compression at 9600 baud your modem -> computer
throughput can be as high as 38400 BPS. At 14.4K baud, the throughput
could be as high as 57600 BPS.
John – K7KB (Flying via AutoPilot)
Chris,
When setup properly, the modem should show both a connect speed and
a carrier speed. Connect speed is the speed between the modem and the
computer, carrier speed is the speed modem to modem…and in your case
would be 9600.
Don
Don,
Ok, so how to I get it to show the carrier speed. All these years using
the 2400 bps modem, I thought CONNECT 2400 meant that that is the speed I
connected to the other modem. Now, I understand that the connection
between computer to modem may be higher than that of modem to modem, but
can I do this with any modem or just the higher 9600/14.2/38.4 type
modems?
Chris
Chris,
You can use the ATW2 command to return modem to modem speeds in the
CONNECT string rather than modem to computer speeds. ATS95=4 will cause it
to display both CONNECT and CARRIER speeds (along with the ATW0 command).
As far as I know, most, if not all, modems that support data
compression on the modem should be able to do this…presuming they're
Hayes compatible.
Don
Don,
Then what is "link" speed?
Patrick White
<<<<<<Auto User>>>>>>>>>
Patrick,
Link speed is the total data thruput speed…including any
compression, error checking, connect and carrier speeds.
It can be as high as 57K or as low as 0, depends on what type of
data is being transmitted, what form of compression is being used, the
connect speed between your computer and the modem…the modem to
modem…and connect speed between the remote modem and it's computer…and
what kind of compression is being used on that end.
It can vary widely during any connect.
Don
Chris,
Something's VERY weird, as I had ZERO problems when I installed 2.1 on my
A2000. Also, you don't see a lot of reports of problem here.
I know how maddening and frustrating it is to have problems like that.
BELIEVE ME I know.
SOMETHING has to be trying to access DF0:, as 2.1 doesn't look at DF0: on
my system on boot.. And I've never encountered the other problems you
had.
Perhaps if you let us know what you're running in Startup/
User-startup/Wbstartup somebody might be able to help you debug your
problem.
Did you upgrade from 1.3 or 2.04?
Denny,
Since I had to setup a boot disk on a cartridge, and I used the dead
drive's user-startup, I found a few files missing the script wanted run. I
looked over this script umpteenth times until I found them, that fixed the
no disk in df0: problem, but why is the OS got that path built-in? I guess
it is a necessary evil, but it can distract a person trying to track down
the culprit.
The Hard drive going south is a coincidence, gotta be one. My PSFONTS:
cartridge got fixed by using FixDis.zoo worked fine, now I'll back it up
again, had most of it on tape already. I got the floppy to reformat
correctly now, AMAX master disk still is munged, but this time DiskSalv
worked as usual.
I've had 2.04 since July I guess, 2.1 seems to be missing its voice stuff.
What happened to it?
Chris
UPDATE:
found the errant lines in user-startup calling for commands that were on
the belly-up drive. Took umpteenth times reading it to find them.
PSFONTS: is back on-line thanks to FixDis.zoo worked like a charm using
the DOOM argument. 🙂
Floppy drive reformatted disk with no apparent problems this time.
AMAX master disk still bad, Disksalv did its job this time and got the
files off intact.
Turkey is in oven, Amiga looks like the old Amiga I've had in past, hood
off laying on floor next to desk, wires sticking out like in past.
Chris
Chris,
I don't know about your other problems, but you might try SnoopDos to
see what's asking for df0:.
-Sean
I just installed 2.1 over 2.0 yesterday. No problem at all. Previously
someone reported compatibility problems with nickprefs, well I don't have
them. In fact, this is the easiest, and most painless upgrade I have ever
had.
My problem in the past was upgrading 1.3 over 1.2. What a stinking mess.
Next headache was 2.0 over 1.3. Now this is so easy, I had no excuse not
to help with the Thanksgiving Dinner.
IMO, 2.1 gives you snapper response and more precise control over the
mounting of different devices. Of course this is amoung other subtle
changes. Well-worth the $50.00 I spent upgrading.
I have not been following this thread, Chris. Are you going from 1.3 to
2.1?
"In case of doubt, make it sound convincing" ***Sensor***
Victor,
I went from 2.04 to 2.1 is all. It seems certain mechanical elements
decided to belly up on me a mere 12 hours after installation. It caused me
quite a problem. I felt 2.1 was out to get me. See, I put 2.1 on a Syquest
cartridge and left 2.04 on the drive that died later. I was booting from
the cartridge trying out 2.1 first, before I put it on my main internal
HDrive. During a later attempt to Update the find.codes for a Find file
type utility I started getting truncated find.codes files, yellow alert
warnings, red crash warnings, LED drive light staying on brightly, and the
floppy drive not formatting properly and thought it had to be 2.1. I don't
know what caused some of the problems, but the patient is stable now, and
moved from the critical list. Still, we'll have to go in and remove the
damaged internal drive and replace it with a donor organ. Hopefully, there
won't be any local rejection and we'll be able to close it up, and move it
into the recovery ward.
Chris
Chris,
I am glad to here the patient AND the family are doing well.
"In case of doubt, make it sound convincing" ***Sensor***
Dear Chris,
Hearing you talk about your Amiga as a patient in the hospital reminds me
of when my Amiga blew its brains out. I was all depressed…people at work
asked me what was wrong…I said that my best friend had just died. They
thought I was a little weird when i told them it was my computer!
I'm very pleased to hear your patient is off the critical list.
– Tom Sawyer
Tom,
Well, I almost felt like a mortician the night the drive went out, but
not before I began to contemplate putting it down completely in a most
graphical manner.
Thanks patient is doing fine now. Its up and around, getting used to
its temporay donor organ, hopefully we'll be able to complete the surgery
later this week and close it up. <grin>
Chris
Chris, glad to see everything doing fine now but I would suggest you buy
something like QuarterBack Tools since these programs are more capable
than most PD programs. I am sure that you can now appreciate what it means
to have the tools to fix it with. The reason I suggest it is because I,
the stupid idiot that I sometimes am, have screwed up my HDs many times,
accidentaly typing `Delete #? DH1:' Instead of `DH1:#?', and watching all
my files apparently go into `The Black Hole' or should that be `The Byte
Hole'?
Anthony,
Anthony,
I have QBTools 1.5, it didn't even recognize the disk! The device
didn't show up in the list of drives available. I have had QBTools since
it was first released, and I wouldn't DARE use some of its features
without first having a current backup tape of the device being massaged by
QBT, especially its defragmentation feature!
Yes, I've typed delete dh0:#? instead of delete df0:#? before too! It
helps if your a fast CTRL C typist. You can at least break the task and
try and get a list of the deleted files before (in past, not now) they
scroll out of sight in the Shell.
I'm getting a copy of AMI-BACK TOOLS to go with my AMI-BACK backup
program. QBT does things I don't care for, like deleting files on its own
instead of letting you do it after it has fixed the disk (like Norton
Utilities for the MAC). It also can't handle large filenotes like MIFONT
adds to its screen fonts for identification purposes by the program's font
mover. QBT wants to erase them on me and that defeats MIFONTS fontmover.
I'll tell you this, I've had Fixdis.zoo for sometime now and never really
used it. Richard Rose had a terrible problem that nothing he had could
fix, he tried FixDisk as his last resort and it got him what he lost. It
sure turned my DHR:NDOS back into PSFONTS: in the wink of an eye. I then
ran QBTools on it and found no errors, except for the filenotes problem
mentioned above.
Chris
> . . . especially its defragmentation feature!
AMEN!
REC
——
Victor, if I'm not mistaken NickPrefs has problems with 3.0, not 2.1. But
I could be mistaken (don't have NickPrefs).
-Dave (via AutoPilot)
David,
So where does one find NickPrefs. I looked in the library of User,
should I also look maybe in Tech.
Chris
David,
I found it, after posting you my last message.
Over in ATech, Thanks,
Chris
Chris,
Well, I put AutoPilot to work and found out that NickPrefs is in LIB 11 of
AmigaTech as NPREFS.LHA. AP's file cataloging is so nifty! 8^)
-Dave (via AutoPilot)
David,
The problems I heard with NickPrefs could have been with 3.0. I just
don't remember.
"In case of doubt, make it sound convincing" ***Sensor***
Victor,
Disregard my previous question, I found NickPrefs over in 'Tech.
Thanks,
Chris
Victor,
Where did you find NickPrefs? I'd like to download it. If it isn't here in
CIS would you mind uploading the archive? Thanks,
Chris
Chris,
From the sounds of it, I am SURE I'll wait to get WB2.1. Since I am
still waiting to get the new ROM from ICD to clear up problems that
happend with the WB2.04 installation. Don't think it would taste quite
the same as the bird. The "kids" wouldn't like it. [g]
Hang in there!
Gail