#4.0 network problem
11 messages in this thread
Make sure you are using the LATEST version of Setpatch. We changed
the AppleTalk support to be an Amiga interrupt (instead of taking
over the machine) ..and early versions of Setpatch did not move the
CIA interrupt to the highest priority.
Jim…
Okay but whatis the latest version of setpatch. Mine is from ADOS 2.05 but I
do have another computer with ADOS 3.0 on it. Would the 3.0 version of
setpatch work?
..Carl
What version of the Amiga's OS are you using on the machine with EMPLANT?
Jim…
I am running OS 2.05 but with 2.04 softkick Kickstart. Will the 3.0 setpatch
work with this (correct some bugs) or should I ignore it?
You had stated we should be running the "latest version" of setpatch.
Thanks….Carl
Carl,
You should be running the latest version of SetPatch for the OS (KickStart) you
are using.
Jim…
Thanks for the reply. I will continue using the setpatch that came with my
2.05 operating system as that is the OS I am running under on the A3000 that
has my EMPLANT.
By the way thank you for including AMAX floppy support in your multios.device.
It has saved me since I can copy my MAC 800k disks to AMAX 800k disks then
access them via EMPL ANT.
..Carl
Commodore releases newer setpatches to fix problems. You should be using
the latest v37 setpatch if you are having problems…
I believe the latest is in the AmigaUser forum libraries.
— Dale L. Larson, Intangible Assets Manufacturing
— INTERNET:dale@iam.com
Jim,
I have installed the latest SetPatch V37.38 on my 16mhz superkickstart A3000.
It sets the ciab.resource priority to 0. It has not solved my appletalk
problems since emplant V4.0. It was also suggested to me on the tech support
line that something was changing the cache settings. I investigated and found
this not to be the case. I'm not running any applications, just using the
chooser. Network resources, servers, printers and zones appear and disappear at
random. Am I forever stuck using V3.9 ?
Setpatch should be setting the priority to 120. If it doesn't, the setpatch is
too old.
Jim –
rm>I have installed the latest SetPatch V37.38 on my 16mhz superkickstart
rm>A3000. It sets the ciab.resource priority to 0.
JD>Setpatch should be setting the priority to 120. If it doesn't, the
JD>setpatch is too old.
My version command yields "setpatch 40.14", and I find that my
ciab.resource priority is 0 also.
. . . . JimDoc, on AutoPilot
v40 setpatch is not for v37/38 machines. If you are running 3.0 use v40
setpatch, otherwise get a current v37/38 setpatch.
— Dale L. Larson, Intangible Assets Manufacturing
— INTERNET:dale@iam.com