CompuServe Thread

#4.0 network problem

11 messages in this thread
#77034From: Jim Drew/UUIMar 16, 1994 11:28 AM
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.
#77100From: Carl HansenMar 17, 1994 11:45 AM
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
#77189From: Jim Drew/UUIMar 18, 1994 10:41 PM
What version of the Amiga's OS are you using on the machine with EMPLANT?
#77338From: Carl HansenMar 21, 1994 7:28 AM
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
#77389From: Jim Drew/UUIMar 22, 1994 1:16 AM
Carl, You should be running the latest version of SetPatch for the OS (KickStart) you are using.
#77407From: Carl HansenMar 22, 1994 10:35 AM
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
#77517From: Dale LarsonMar 23, 1994 4:43 PM
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
#77530From: Ron MoncreiffMar 23, 1994 8:11 PM
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 ?
#77608From: Jim Drew/UUIMar 24, 1994 11:52 PM
Setpatch should be setting the priority to 120. If it doesn't, the setpatch is too old.
#77912From: Jim SakladMar 28, 1994 10:03 PM
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
#77937From: Dale LarsonMar 29, 1994 7:22 AM
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