UWVFP( FP0 ‹؋F&O F&G&G<ʋЋ™Ƌ$6&~&6&F&9EtL2pP3P F&EĞ&(6&>pt*6&>vt TF&EF,6&>~FvFĞ&^&9~Ì~ڹ-F*Ftz8ft F^&8Gui~t F^&8GuWF+F;F| F9Fu~tF@t8F^&8Gt,F+F;F~<.6&>t0^&GĞ&v&@F[FF,6&9~2F^&8Gu FuӋvzvĞ&7X06&?&&DPĞ&&& 26&>|u 46&z66&^&Gȋƻ[؎86&>&I86&&a~t;F*PĞ&&& 46&zF*Pv:6&& ud26&>|u 46&zĞ&&& <6&6&6` P, >6&F&H t8PP  |FPPh P:6&6&6P  |FPPh P*6&>vt BlPP] @6&6&6`Ğ&&& pP B6&R&TĞ&7FD6&FF6& fĞ&7FtH6&&J6&H6&J6&f%=؎L6&FD6&FF6& ^_]ːUVN6&6 &6rP N6&6 &6"P vPrPh P"Ph FPrPXX @uNFP"PXX @uQN6&6 &6"P P6&6(&6&"Ph FP"PXX @uFV9Vvr9Fv~} ~[sPrPC uƆrPrPVj3 6d6brP  udpP~QPVj3 FPF-P86&6&6VP R6&[RPFV-RP ,6&V2 ^]UWV+PP( FVN6&6 &6FP N6&6 &64P PFPh P4Ph FP4PXX @uQN6&6 &64P P6&6(&6&4Ph FP4PXX @u3FV9Vw1r9Fs*FVFV06&X&& FVFVFVPPFPC uP6d6bVh4 pP~QPVh4 3,602&9?~Dv3ɉNރ,.&Gt &u&g[GĞ0&9?ЋvFP[Ğ0&/P86&6&6VW V2 FPFPR ^_]ːUTWVN6&6 &6FP PFPh PFP V t)FPVQpQ~RQx WV ^_]ːU"WVFP( FP0 V<&m&EFT6&F&M FF &EF~,6&F 86&&؉V$6&FN9Nu~t F&u|v&DF&8G tl&G *Fta&G:F t F&D8FuJF&G9F t F&D8Fu0Fw&F;FF&@t+~9~~~[A9N~a~}+FFf~@~F39N86&&>؉V~؃~t Fw&uZFw&*FtJF&F t F&8Eu4Fw&F t F&8EuFw&FF;F}F[A9N~V~t}^_]ːear all searchUWVP V t5P6  u$FPVVP VPƆVPVPh FPVPXX  t$VPP(P P ~WP V u P(P P P-PVP26 FV u$VP0P(P P vvWPvV ;t2VPLP(P vv P vv  t$VPwP(P P F  3RT&7&GLX"3NP&&G&MVv~~؎ZX&&+NjV&&PIuvĞN&F&7&GĞR&&&GÌV&$3& &> & & ߎ&&3&OF&&&ʋH(3JL&&G*3&&F&ʋFPQ" @FĞJ&&?~G~VvN~&&+NjV&&PAĞJ&&9ڋ~v*3&F&7&GĞJ&&@&GF,3&> & M.3& & ^_]ːF7&U.WV4Z9&3\9&6^9&"`9& b9&r d9&bf9&dh9&fj9&h+ɉNNvvZ RP"Pr QP V^V۹^VNVl9&>nu-n9&X&B&@ "P| 3br QP t~ PvvP t!2PP] p9&tN릐2PP] p9&u, QP2PP] p9&u0 ~+PP( FVP+PP( ȋ+FV~9&&SQvvvVr FV~9&&d3SQRP FVdRPvv FVvvRP<RPSQRPvv⚺ RPFމVT SQvvމFډVܚT <3SQvvF։Vؚ FV؋Nڋ^+SQF҉VԚT +FVRPvvvvvvZ RPn9&X&r&p N~9&pr9^F&?tt9&>vt^&?t;^9&>"u\9&>6u `9&> tPvv^&?tMt9&>vtAPPv9&68&66`Px9&GPv9&68&66 tظ[.ظ&&،F&Gt1&9}&Gع&;z ~36&z F&9G|&F u &>tF&Gu & t~u &>tF&Gt & uPvvP t}pr9^F&?tMt9&>vtAPPv9&68&66`Px9&JPv9&68&66+PP( FVz9&>|u |9&z, QP |%^&?tMt9&>vtAPPv9&68&66`Px9&GPv9&68&66PvvPn9&X&F&D PvvPr9&>ptMt9&>vtAPPv9&68&66`Px9&GPv9&68&66^_]UWV P3Z9&P QP 9+&& ~ u19&9>"t2PP] p9&u |] u9&9&F |#[n9&&@t 9&2P P] =tz9&>|u |9&zr9&>ptt9&>vtT9&>"t2PP] p9&t t3Pt9&N& LtsdP FV|] t6~vv`  u!dP FV] |] u͚] 3P9&6N&6LtmpP FVRP`  tP~|] t@2P P] =t* vv`  t 3b2PP] p9&t;3PN^9&>"u\9&>6u `9&> t N(^_]ːUWV9 &?|%[&/9&&~ڹ-Ğ &?}^9&>"t5~t/F*Pn9&X&N&L F*P3~9&& t1B*PWn9&X&R&P B*PFF;r `9&?u \9&>6t?Ğ &?|5~t/F*Pn9&X&V&T F*PO9&& uĞ&?u\9&>6u^9&>"un9&X&Z&X 9&6&6` P, 9&6&6P Ğ &?|FPPh PPP] n9&X&^&\ 9&6&6`pP 9&R&T3^9&"\9&6Ğ&^_]ːU욀"P9&6&6n9&X&& 9&6&6`嚖t9&>vt9&63P] 9&>Ltr 9&>du.] v ]UVv u3, ȋƙ+T؋ʙùdP ^]ːUWV~9&B&DF&9Eu &9U u&E & Eu 9&&9&6&6KP KP" KF^F9&& u~N؋W&9Du&9T tGG u9&&V uVV‹&?u$~9&>t3"PvW ~^FFG&<u^&7"PvW_9&6&6KP KP" K^9&F&9t&9&>uF&5"PDvP K^_]ːUt9&>vur9&>pu3P, 9&@P"Pr QP PQ9&6&6`r QP9&6&6Z9&@P9&6 "Pr QP PP9&6&6`r QP9&6&6Z9&bF t'P9&6&6"Pr QP $9&6&6 #Pr QP PQ9&6&6`#P9&6&6ZPP9&6&6`r QP9&6&6Z3P9&6^ ]ːt9&>vt&r9&>pt P9&6&6ːU.WV~FL^ }dǹ[FԻ9^֌F&&GtFLBƌ@V~t ‹F& ^&^&GtFF&C~t FF& ^&^&GtFF&D~t FF& ~t$^&^&G@tFF&FFF& ^&^&GtFF&H~t FF& ^&^&GtFF&K~t FF& ^&^&GtyFF&L~ti^&^&GF |@P+# +FP0#PFP FڌҋȎڋ6?t!vNG^F&=uv~~t$^&^&GtFF&MFF& ^&^&GtFF&N~t FF& ^&^&GtFF&S~t FF& ^&^&G tFF&R~t FF& ~t^~&=&At FF&XF&FL^_]ÐUt9&>vur9&>pu9&>u3P9&6+RP9&@P5#Pr QP PQ9&6&6`r QP9&6&6Z PP9&6&6`vv9&6&6ZT]UWV3Pz9`b&?}Tt9&>vuEWĞ`&@PXn9\^&&f&ddP PP9XZ&w&7`dPĞX&w&7ZPĞ`&7‹؋F&?tTPVĞ\&&j&hdP PPĞX&w&7`dPĞX&w&7Z9TV&G& u9&w&7dP A#PdPh PJ#PdP26 V uFPVQQNQ FWV ~uvrĞT&w&7dP M#PdPh 3PdQNQ*6 uqvFP ;PdPFP*6 t@2PPĞX&w&7`Ğ\&&n&lĞX&w&7ZT^_]R$bCLSU.WV4 ع4& &QP( 4+&,&*&(&0&.p4^F&9t&4&9vt4&X&&F4^&?u-~ٹ~t%FFF4&F ~FFFP RP4&6&6 Pr QP r QPB FP RP Pr QP r QPB F ~js)+FFFFFF4^ތF&4&>v% 4^ڌF&4&>x ^&4& 4&9s 4&> t^&3PN։VRQQD~u QPP  tuHtpHtHHtMc uW^&^&ub4&h4&d4&X&& 뤚 u ^&^&u2봎4&h3P4&T4&ht F҉NԐ3^&9?~14&t&4 QPF  uG^&9?ҚHuHuGHtvHu}W4&t ;E2PP] 4&u)FPP 3PvvָP4& u^&^&t4&d4&h4&X&&  u^&^&t밐62PP] 4&u_4&>tPFPP 3PvvָP"2PP] 4&uFFPQ F4&^&?tp4&>vtd4&6&6 Pr QP PP4&6&6`r QP4&6&6ZT4&h3PO QPP 4&^&?tp4&>vtd4&6&6 Pr QP PP4&6&6`r QP4&6&6ZT4&T4&h QPP 4&^&?tp4&>vtd4&6&6 Pr QP PP4&6&6`r QP4&6&6ZT3P5& 5&b4&d5&f4&hPvvָPf3PvvָPQ^_]WV+ &&r & &6&"&& & ع^_ːUVXP FVRP`  uuv2PP] 4&tY uP2PP]  tFF& t*<t&P]  vv`  t'2PP] :] P ] 3^]ːU(WVb5&?u]v vFVF tHt#HuHuHu)F396F~(D Pv vWd u F;6F|ۋ~F &}t=&u&uvv PbP F &u/ PFP 2vvbP F &u&u8 PFP FLJFĞ&7bPE PP T PP V us5&& tZFLJFbP Ğ&7bPW PP f PP VF u-~ uyP4&X&>&< UFPV FPbPh bPP<  uX9F t!bP4&X&B&@ FDF^FFV ~~ t+v vZ RP4&X&F&D PB >Fuy396F~%D Pv vWd t F;6F|96F/~ u=v vZ RP4&X&J&H~F &}t=&u&uvvi PbP F &uy PFP 2vvbP F &u&u PFP F?t5&6&6bP FPbPh F;6F}rFFFFDFDFF+ƉF~vF^^F^FF F NuFbPB  u$9F ubP4&X&N&L?~ ubP4&X&R&P 5&& uĞ&7P PbP  PbP RP D5&& t-Ğ&7P PbP bPB 3^_]U($ 5^ތF&?u5^ڌF&G& u  t6 6 `  udP   5&bF tP^&w&7 PNFP ^&w&7 PNFP FPNFPXX  uDNFPB ^&74&X&&  5&z^&7]39&RzLxL9&9ptI9&9vt>PP9&6&6`#P9&6&6ZT#P| ] 9&$PP] P u 9&X&N&L 3n9&>ptJ9&>vt>PP9&6&6`#P9&6&6ZT$P| PV39&RzLxL9&9ptH9&9vt=PP9&6&6`&$P9&6&6ZT H$P| :] 9&$PP] 3PN tz9&>ptK9&>vt?PP9&6&6`S$P9&6&6ZTu$P| 3P u4^ːUWV9& & VȋڀFV$PSQ $PvW QPr9&QPZ RP$P 9&QPZ RPvW'3FF9&9~Q~9&9>t,$PvvPVZ RPvv G9&9>~$PvW89^F+&G&9Ft QP: '~uZzL0QP: ~9^&G& t-P&w&7vv< ^&GSvW%$PvW~t)9&>^u9&>`t$6$1$+9&t$PvW9&u$PvW$PvW9&> بt+& ~u:& #Ft&ِFtvt &6 بt$`~t6t$PvWt$PvWƨt3$"t$t$ ƨt$PvW9&t~t9&>zu$PvW$PvW$PvWw$PvWh9&>ju9&X&&$ډFVRP9&69&6$PP%Pvv vvvW%PvW9&6&69&6&6:&6&6#%Pvv vvvWB:&6&6:&6&6:&6&60%Pvv vvvW=%PvWD:&&&(0T|RPE%Pvv vvvW vW" 9&$PP] FpP FVv~vvO%PvV vV" PvVj! FPQ\%QJ] PvV" PvVJ] PvvvJ] F~~;~v^^؋NJ*3QNJ*&3ZF;v|։~v] v_%PvV PvV" PvVJ] FF=vP FVvv`  t 2PP]  :&uvv`  t|] u t 3P( -*ui%PvV vV2 ui6`#6^#vVF  uN6p#6n#vvF  t~9&X&&e%PFPW ƋFv2PP] 9&X&&V\2PP]  :&u9&X&&ˎ9&X&&k%PFPV NjFvW 3^_]U WVFdžPƆ{dž8o%:dždž@~%BdžD%FdžH%J+NL9& & vx~prt89 +&G&n9&9ptH9&9vt=PP9&6&6`%P9&6&6ZT %P| T :&P FVpP FV+FF{{<vv~uZ6`#6^#%P~V P~V" P~VJ] dd, dump.bsd and cpio (pax MAY work but tar won't since it won't handle special-type files). If the two partitions are the same size, you can use 'dd' (to copy c0d0s0 to c5d0s3, e.g.): $ dd < /dev/rdsk/c0d0s0 > /dev/rdsk/c5d0s3 To use dump.bsd, you can use the following command (this assumes that the destination disk in mounted on /mnt and you want to copy the root file system which is on SCSI 0... of course, you must be root and it would be MUCH better to do this in single-user mode): $ dump.bsd 0f - /dev/rdsk/c0d0s0 | (cd /mnt; restore xf -) To use cpio, you must use it in a pipe with find. For example, to copy /usr (let's assume it's on it's own file system) to another disk|partition (assume it's mounted on /mnt) then you can use (you can add the "-depth" flag to 'find' if you want): $ cd /usr $ find . -print | cpio -pdmuva /mnt The problem with this is that if the mount point of the destination disk falls under the file system's directory you're trying to copy, you'll load up your destination disk. For example, the following would NOT work: $ cd / $ find . -print | cpio -pdmuva /mnt because 'find' would see the stuff in /mnt (which you just put in there) and try to copy in back to /mnt! To way to avoid this is by adding a little filter: $ cd / $ find . -print | grep -v '^./mnt*' | cpio -pdmuva /mnt If you have GNU find, then you can use it with it's '-xdev' option, which prevents find from walking through other file systems: $ cd / $ find . -xdev -print | cpio -pdmuva /mnt dump.bsd creates a "truer" copy of your file system (the access and modification dates aren't mucked with... with the find/cpio pipe, at the least the directory dates are touched) but it won't backup named pipes... These are easy to creat though using 'mknod'. The only named pipes included in the default A/UX distribution are: /usr/lib/cron/FIFO prw------- 1 root sys 0 Oct 18 16:08 /usr/spool/lpd/AppleTalk/pipe prw-rw---- 1 daemon daemon 0 Oct 19 06:11 ======================== A.05) What's with UUCP? ------------------------ UUCP under 3.0 is very improved over it's previous "incarnation" under 2.0.1. 3.0.x uses HDB (for HoneyDanBer) UUCP instead of standard UUCP. Some nice things are bidirectional getty (also known as uugetty in other Unixs) which allows both incoming and outgoing communication over serial lines as well as better performance and reliability. I hear that setting it up is _much_ easier as well. You may seriously consider getting Alexis Rosen's "sendmail.cf" file for use under UUCP sendmail. This config file has been modified to allow UUCP and sendmail to work beautifully together. You may also want to consider simply installing smail to replace sendmail. Under 3.0., be sure that you are running the latest version: 1.16. It can be found on aux.support.apple.com in aux.patches/supported/3.0. Be sure that you get the new dial.o on ftp.apple.com (pub/earlw/dial) to avoid breaking syslog. Under 3.0.1 (and later) all is OK. ============================================== A.06) How can I log anonymous ftp entries?... ---------------------------------------------- ...in.ftpd has a -l option, but it doesn't work. Jim Jagielski (jim@jagubox.gsfc.nasa.gov) has hacked in.ftpd to enable logging via the syslogd daemon. It also pays extra close attention to anonymous ftp logins. It's available (as well as other ports|hacks) on jagubox. Also available on jagubox is a set of patches and files required to compile and run wuarchive's ftpd server under A/UX. This is a super-nice ftp server! The real reason why '-l' doesn't work with in.ftpd is that there's no real way to send this option to the daemon. A/UX 'inetd' doesn't allow you to add options to '/etc/servers'. John Coolidge (coolidge@apple.com) has ported the BSD-reno version of 'inetd' to overcome this limitation. Jim Jagielski has since been updating and maintaining 'inetd'. This version of 'inetd' also has some nice features, such as rereading /etc/servers when sent SIGHUP. It's available via anon-ftp on jagubox. This version of 'inetd' has also been modified to log whenever it spawns a background daemon as well as logging which host requested the daemon. %%% For more info, contact Jim %%% ============================================ A.07) 'df' shows different results for root -------------------------------------------- A.07) How come when I do a 'df' as a regular user, it shows me a different number of free blocks compared to when I run it as 'root'? One of the details about the BSD Fast File System is that it sets aside some amount of the available disk space (if the file system was created by HD SC Setup, then %5 is set aside; if created by 'newfs' then 10% is set aside... this value can be changed by using the 'tunefs' command) and makes it unavailable to regular users. This prevents 2 things: filling up a file system and destroying performance by having a "too full" file system. 'root', however, does have access to this "extra" disk space, hence the difference in the numbers reported by df between 'root' and "regular joe". As mentioned above, if you used HD Setup to create the partitions (or your A/UX came preinstalled), then the "set aside" value for these file systems is 5%, not the "default" of 10%... This was simply to give users more space. Reducing this value beyond 5% is Not A Good Idea. ====================================== A.08) Does A/UX LocalTalk support IP? -------------------------------------- Nope... not at all. ========================================================== A.09) How do I get MPW 3.1 to work? It hangs my system... ---------------------------------------------------------- MPW 3.1 doesn't work under A/UX although 3.2 does. In the meantime, you can make 3.1 work by breaking into MacsBug when it's hung and entering: pc=pc+2;g See Q&A #M.04 for info about entering MacsBug... =============================================================== A.10) Can I refer to a file on my Mac system from within A/UX? --------------------------------------------------------------- A/UX's 'Finder' mode is the only way (currently) to access both file systems. You could write a hybrid application that could attach to the Finder world (a la, CommandShell and cmdo which can "see" both file systems), but you can't access HFS volumes from the A/UX kernel directly. In a similar vein, you can't 'mount' an HFS volupresent disk to create a larger Swap partition (Ack!). c. Add more memory. If you have more memory, then this will reduce the need to augment it with swap space... RAM's cheap too! There is an old rule of thumb that the size of Swap should be about 2 to 3 times the amount of RAM, which would seem to contradict the above. The thing is that if with the _present_ workload you are swapping like crazy, then adding RAM will reduce tha swapping. If, however, you start increasing the work- load, then swapping will start again, and you better have enough of it! This was the original intent of the Rule-Of- Thumb. At the very least, Swap should always be at least as big as the amount of RAM you have. ================================================ A.04) How can I copy a complete file system... ------------------------------------------------ ...from one disk|partition to another? You have three options: book" deals "mostly" with BSD systems). Another must-have is "UNIX Power Tools" from O'Reilly and Associates. For general information about shells and programming there's no better book than "The UNIX Programming Environment" by Kernighan and Pike. For the 'ksh' shell, the best book I've encountered is "Learning the Korn Shell" by Bill Rosenblatt. O'Reilly and Associates has a wide selection of UNIX-based books. You're bound to find what you're looking for from them. You can contact them either via Email (nuts@ora.com) or Phone (1-800-998-9938). There is also a list (with over 160 entries) of UNIX books (and mini-reviews) located on ftp.rahul.net in 'pub/mitch/YABL/yabl'. ======================================== A.19) 'panic ialloc' error when booting ---------------------------------------- A.19) When booting up, I get a "panic ialloc, dup alloc" (or other) error message and A/UX won't boot. What can I do? This is due to the fact that some file system damage exists on the Root file system. By default, A/UX Startup will only run 'fsck' on the root file system if the system is marked as "dirty." So even if damage exists, as long as the disk was cleanly 'umount'ed, 'fsck' won't check it out and fix it. I recommend always having A/UX Startup fully check out the disk before booting A/UX. It takes a while, but it's worth it. To do this, choose Booting from the Preferences menu. Now change the command under "AutoRecovery" to "fsck /dev/default" (it was "fsck -y -p /dev/default"). When you do this, you'll notice that the radio button changes from "Check root file system" to "Custom command"... that's OK. After that, A/UX will always run 'fsck' on Root. If you are doing this, you might as well have A/UX run a full 'fsck' on all file-systems too. Check out fsck(1m) and fstab(4) for how to do this... one way is to just edit /etc/bcheckrc and remove the options to the "/etc/fsck" command. If you don't want to do this but you do have some damage that prevents A/UX from booting, then you can cancel the boot-up process (either select "Exit" or hit "Command-."). Then type "fsck /dev/default" and then, when 'fsck' is done, type "boot" (or "launch"). Sometimes you must run 'fsck' a coupla times to fully fix the file system if there was extensive damage. ::::::::::::::::::::::::::::::::::: ::::: MAC-EMULATION QUESTIONS ::::: ::::::::::::::::::::::::::::::::::: ====================================================== M.01) What Mac applications are compatible with A/UX? ------------------------------------------------------ It would be much easier to list the applications that aren't compatible. The list is much, much shorter... The _vast_ majority of applications that run under System 7 will run under A/UX 3.0.x. In fact, before System 7 was released, A/UX 2.0.x was actually a good litmus test whether the application was 32-bit clean and would run under System 7. The only applications that are _sure_ to fail are those that try to access hardware _directly_, such as HD utilities or backup applications. A/UX 3.0.x provides both 24 and 32-bit modes, so if the application doesn't run under 32-bit mode, try it under 24-bit. One key note: if the program uses a "complex" installation procedure (like for Canvas, Word, Stuffit, etc...) then you should not try to do a fresh install under A/UX. See the above Hints and Words Of Wisdom. =================================================== M.02) What screen-savers are compatible with A/UX? --------------------------------------------------- AfterDark (2.0u and later) works well under A/UX but some displays may not have enough memory under Login so the "low-memory" display will be used. Moire and FMbackup seem a bit incompatible. They both function fine together but the combination prevents FMbackup's "Finishing up..." window from displaying, although FMbackup does, in fact, finish up. Furthermore, Moire seems to screw-up Commando (both version 3.22 and 4.01 exhibit this problem) so all in all, Moire can't be recommended if you desire using Commando (the problem seems to be with all MacOS applications 'launch'ed from the CommandShell window). Using Moire for the Login screen works well however, since you can't access Commando or 'launch' applications from there. Darkside is also available. Unlike other screen savers, Darkside is an application, not an INIT. This means it won't work under the Login screen. The latest version of Darkside is 4.0 and will _not_ work on Pre-System7 systems, so don't attempt to use this under A/UX 2.0.1 or later. Moire is available via anon-ftp on jagubox. ========================================== M.03) Mounting MacOS partition under A/UX ------------------------------------------ M.03) My MacOS partition mounts fine under MacOS but it doesn't show up under A/UX... Why? Whether or not a Mac partition mounts under A/UX depends on a number of factors... Necessary conditions for a partition to mount are: 1. The disk MUST be partitioned using the "new" partitioning scheme detailed in Inside Macintosh V. There is still plenty of disk software out there that uses the "old" scheme and this drives will not mount under A/UX. Generic disk formatters that use the "new" scheme include SilverLining and FWB Hard Disk Toolkit. Most major disk vendors supply A/UX compatible formatting s/w. 2. The partition must mount under MacOS BEFORE A/UX is booted. A/UX only tries to mount partitions that were already when it was booted. So, if you use an application to boot A/UX and this application runs before a partition is mounted, A/UX won't mount it for you. If you have a removable drive (such as SyQuest), you must insert the disk before you boot A/UX... this means you can't swap cartridges under A/UX. Sometimes, the partition map isn't correct for the MacOS partition; In particular, the Logical size may be 0! You can use 'dp' to look at the partition map to see if this is the case. Assuming that the disk us SCSI #2, then: $ dp /dev/dsk/c2d0s31 P Will print out the partition map entries. You can then see if the "Apple_HFS" partition type has the correct logical size. ================================================= M.04|M.05) MacsBug, Interrupts and MacOS Freezes ------------------------------------------------- M.04) I have MacsBug installed. How can I trigger it? -- or -- M.05) Sometimes my MultiFinder environment (and/or CommandShell) freezes up; how can I unfreeze it? Should I hit the Interrupt switch? The "Command-Control-e" keypress will kill the current MultiFinder environment and "unfreeze" (and kill) your MultiFinder|CommandShell. Depending on whether your session-type is Console Mode or 32|24-Bit, you will either get returned to the console or get returned to the Login screen. You should _NOT_ press the Interrupt switch since this puts you into A/UX's kernel debugger. If you have MacsBug installed (which is recommended) then you can press "Command-Control-i" to enter it. This may enable you to clean some things up before the MultiFinder environment is blasted (even just using 'rs' under MacsBug helps...). If MacsBug is _not_ installed, the "C-C-i" behaves almost like a "C-C-e" except that it appears that A/UX doesn't need to "rebuild" your icon/Desktop "environment" the next time Mac-mode is entered. To make sure that MacsBug installs correctly, it's name must be 'MacsBug'. A munged Debugger Prefs file can also prevent MacsBug from installing. This happened to me when upgrading to 3.0.1... To be safe, make a solid safe copy before upgrading. ================================== M.06) Phase 1 EtherTalk and A/UX? ---------------------------------- M.06) My site is not upgraded to EtherTalk Phase 2 yet... can I use Phase 1 under A/UX? A/UX only supports EtherTalk Phase 2. Upgrading to Phase 2 is recommended for a variety of reasons, but most importantly to ensure compatibility with new products from Apple and developers (of course, the added features over Phase 1 are nice too :). ========================================= M.07) A/UX and MacOS file transfer hints ----------------------------------------- M.07) I'm having trouble transfering files between A/UX and my MacOS disk. Also, sometimes things get transfered fine, othertimes not. What's going on? If a file on the A/UX system has Type "TEXT", then when it is copied over to a MacOS disk, all 'newline' characters will be replaced by 'carriage returns'. Sometimes this is what you want (that is when the file is, in fact, a TEXT file). Othertimes it's not. Say for example you download a GIF file onto your A/UX disk. A/UX _might_ think it's a TEXT file. If you then copy it over to your MacOS disk and try to use Giffer on it, it won't work. That's because the 'nl's where changed, which is _not_ what you want. The way to stop this is to convince A/UX that the file is of non-TEXT type. There are many applications out there (including the A/UX included 'setfile' program) that lets you modify this. Do this before you copy the file over to your Mac OS disk and all will be Okay. If you aren't sure what the Type and Creator should be, you can just specify "BIN " and "A/UX" (note space in BIN) and the file won't be massaged during the copy|transfer. You'll still need to eventually change them to the correct ones for their particular application, but this way they'll be on your MacOS disk "uncorrupted." Of course, you could also use 'setfile' to set the Type|Creator fields _before_ you copy the file to the MacOS disk and avoid an additional step. Please note that if you downloaded a BINHEX file, you _do_ want to keep it as a TEXT file if you transfer it over to the MacOS. Once there, you can de-BINHEX it and unStuffIt (if it was a binhexed stuffit archive). Please note that if you transfer Unix-type files (like tar archives or compressed files) between the A/UX file system and a MacOS disk (esp. if these files were "created" on a MacOS disk by a MacOS utility), the Unix application may no longer work correctly with it. This is because the MacOS resource information was attached to the file during the transfer (the file is in Apple Single format). To "fix" this, use 'fcnvt' to change the file to Apple Double format which will detach the resource fork and place it into a "%..." file. See "Hints and Words Of Wisdom" (above) for hints in using ftp file transfers under A/UX. ============================================ M.08) Where to install CDEVs and Extensions -------------------------------------------- M.08) Do I install CDEVs and Extensions in the System Folder on MacPartition or on the "/" A/UX disk. To install these additions to A/UX, you will need to drag-copy them over to the A/UX System Folder. Usually, this is /mac/sys/System Folder on the "/" disk but it will also "appear" in your "home folder" icon. If you have a personal System Folder (i.e. $HOME/System Folder) then they should be dragged there. To add a screensaver to the Login screen, it must be dragged into the correct subfolder in /mac/sys/Login System Folder. That is, if it's an cdev, drag it into /mac/sys/Login System Folder/Control Panels. ================================== M.09) Booting A/UX under System 7 ---------------------------------- M.09) I heard that A/UX requires a special version of System 7 to boot... Is this true? A lot of people believe this but this is not true. There is no difference between the s/w on the MacPartition partition and the "real" System 7. The only _real_ need for MacPartition is that the disk where A/UX Startup lives is where A/UX Startup looks for the A/UX Root partition. When A/UX Startup launches, it looks at "it's" disk and then looks for A/UX partitions on that disk. This means that you _don't_ need to boot-up from the MacPartition disk to boot A/UX. Start your Mac from your standard Startup disk and just double-click on A/UX Startup on the MacPartition icon. You can even do without the MacPartition disk but telling A/UX Startup the exact SCSI number of the A/UX disk. You can do this a couple of ways: 1. create a ROOT variable in A/UX Startup that points to the root partition in this form: (SCSI-ID, 0, 0) 2. Under the General Preferences menu, change the Root Directory to (SCSI-ID, 0, 0). The "device" file /dev/default points to the SCSI-ID of whatever disk is the MacPartition disk, so if you don't have one, you need to tell A/UX Startup it's "real" name. This is kinda messy since you'll need to preface a lot of stuff with this value: e.g. #startup cat (6,0,0)/etc/inittab ================================================== M.10) Screwed up Desktop after crashes or MacsBug -------------------------------------------------- M.10) After the Mac environment crashes (or when I use MacsBug), the Desktop gets all screwed up... Argg!! Ron Flax of Apple (ron@afsg.apple.com) has written a very useful System Extension called FMbackup that creates backup copies of "valuable" Desktop files. When the MacOS-mode is entered, FMbackup restores these files. Thus, when your MacOS "crashes", you no longer need to rebuild the Desktop or reset all your Icons, window "types", etc... Please note that there seems to be some incompatibilty between FMbackup and Moire and QuickMail 2.5.1. FMbackup (1.0.4) is available via anon-ftp on afsg.apple.com as well as aux.support.apple.com (in "unsupported"). %%% For more information about "FMbackup", please contact Ron via E-mail %%% =============================================== M.11) MacOS partitions on desktop only as root ----------------------------------------------- M.11) My MacOS partition(s) only show up on the Desktop when I login as root. Why? Under the Preferences/General Menu of A/UX Startup, there is a radio-box called "Password checking". This is intended to provide some security for the A/UX Startup application. When enabled, two (default) things happen: 1. A/UX Startup requires a password to open. 2. MacOS partition(s) are only mounted for root login. Thus, to enable MacOS partition(s) to be available for all users, you must disable "Password checking". See auxstartuprc(4) for more info. ========================================== M.12) CommandShell ignoring 1st key press ------------------------------------------ M.12) For some reason, my CommandShell only responds to a keyboard event after it receives a second event. For example, typing "a" won't show until I type something else or click the mouse. What gives? This is caused almost 99% of the time by an Extension|CDEV conflict. The way around this is to selectively disable each one at a time and see which one causes the problem... then delete it. "Wild Magic" is prone to do this as are older versions of CEToolbox. ===================================== M.13) Can A/UX 3.0.x run System 7.1? ------------------------------------- A/UX 3.0.x's MacOS interface is based on System 7.0.1. You cannot install Sys 7.1 on A/UX (meaning you can't make A/UX run Sys 7.1) since there are a few system files that are fine-tuned and modified to work under A/UX. These would get overwritten if you tried to install 7.1 and you'd be out of luck. Please recall that this doesn't mean that you can't have 7.1 installed on your MacPartition, to be used when in MacOS-only mode. It just means that you can't have A/UX run 7.1. Just to let you all know, if you really want to, you _can_ install 7.1 on A/UX 3.0.x and the MacOS-stuff will work pretty well. However, all hybrids, such as CommandShell or Commando, will die... not too useful... =============================================== M.14) What version of AppleTalk does A/UX run? ----------------------------------------------- This one is tricky. First of all, the version of AppleTalk under A/UX was designed specifically for A/UX... Don't try installing the Network Software Installer (NSI) disk. Bad Things will happen. With that out of the way, when polled by InterPol, A/UX will respond that AppleTalk v56 is running. However, A/UX's version is really compatible with version 58. This will cause trouble with those applications that rely on version numbers rather than capability. =================================== M.15) Version of MacTCP under A/UX ----------------------------------- M.15) I've just installed MacTCP 2.0.2|4 on A/UX and nothing works! What's going on? The copy of MacTCP that ships with A/UX is specifically written for A/UX. You should _not_ replace it with any MacOS version of MacTCP! Doing so will cause mucho problems for A/UX. This is because A/UX's MacTCP simply offloads all networking functions down to A/UX itself which handles them. Although it's true that some MacOS programs, such as Mosiac, "require" MacTCP 2.0.2|2.0.4, the vast majority work just fine with A/UX's version. In extreme cases, with programs that actually _check_ the version number, a little ResEdit hacking will fix things up. Basically, all you need to do is COPY the 'vers' resource of MacTCP 2.0.2|2.0.4 and PASTE it into MacTCP in your active A/UX System Folder (you want to 'Replace' the previous 'vers' resource). This will cause MacTCP to appear (via 'Get Info' and similar ways) to be version 2.0.4. ::::::::::::::::::::::::::::::::::: ::::: DEVICES AND PERIPHERALS ::::: ::::::::::::::::::::::::::::::::::: ======================================================= D.01) Can I use my Teac|DAT|etc tape drive under A/UX? ------------------------------------------------------- A/UX 3.0's 'tc' device driver (version 1.40) officially and totally supports the following tape drives: Qualstar 9 track Archive 4mm DAT Archive QIC Teac DCAS 600 Exabyte 8500 <> DC2000 Please note that all the devices except for the Qualstar 9-tracks require 8k-blocking when used through 'tc'. This means you will need to use 'tcb' or 'tbb' as a filter ('dd' will also work during reading). You should also specify 8k blocking (or a multiple thereof) when using dump.bsd. Jim Jagielski has created a replacement for 'tc' called 'NEWtc'. It fixes a lot of Apple's 1.4 bugs as well as to provide some nice new features. It supports all the above drives in addition to: CIPHER drives Exabyte 8200, 8205 and 8505 HP DATs SONY SDT line Teac DCAS 150 and 60 WangDAT 1300 and 2600 series WankTEK series 6130 (FS/HF), 5525 and 5050ES. It also has a "Generic" entry that will attempt to drive tapes it doesn't know about. If you have a drive that isn't supported, let Jim know and he'll try to add it. NEWtc is up to version 3.32 and is available via anon-ftp on jagubox. Included in the package are replacement copies of 'mt', 'tc.7.Z' and 'mt.1.Z'. Tony Cooper has written a VERY nice double-buffering copier that greatly increases the speed of backups; it's called 'tbb.' It works quite nicely with 'tc' (assuming the correct blocking factors)... It's included with the 'NEWtc' package. Craig Ruff (cruff@ncar.ucar.edu) has written a Teac device driver also, which works with both the 150 MB and 60 MB drives. You get the complete source so you may "adjust" the driver if you want for other drives. The Teac driver is available via anonymous ftp of jagubox.gsfc.nasa.gov. %%% For more information about 'tc', please contact Jim via E-mail %%% %%% For more information about 'teac', please contact Craig via E-mail %%% =============================== D.02) EtherNet cards and A/UX ------------------------------- D.02) I have an EtherNet card that works fine under the Macintosh OS but not under A/UX. Why? The reason is because to access the card (which is seen as a device by A/UX), you need an A/UX device driver for it. This is NOT the same as the stuff you had to install under the MacOS for it to work. Now A/UX includes drivers for the Apple EtherNet card (they aren't installed by default though), but they don't work with most of the 3rd party cards except for the 3Com "EtherLink NB", the Asante "MacCon" and the StarNet Networking cards. They are 100% register compatible with their Apple counterparts, so you can use Apple's 'ae' driver with them. Drivers for the EtherPort II cards are available via anon-ftp on jagubox. However, the drivers for the "old" EPII cards (full length) only support TCP/IP (they were written for A/UX 1.1 but will work under 2.0.x). As far as other cards are concerned, you will have to ask the vendor for A/UX drivers for it. Please note that there have been numerous reports about problems with the EtherPortII cards, A/UX and the IIfx and IIsi... you are warned :) ======================================= D.03) Can I use my scanner under A/UX? --------------------------------------- A/UX 3.0.x fully supports the Apple OneScanner as well as providing better support for SCSI devices. A/UX will still use its own SCSI driver, however. ===================================== D.04) Using SyQuest disks under A/UX ------------------------------------- D.04) I'm trying to use a SyQuest drive under A/UX but it refuses to work. I keep on getting a "more data than device expected" error message. What's wrong? The "problem" is with the generic SCSI disk driver under A/UX. For SCSI drives, there are certain parameters that may be adjusted by the user; these parameters are grouped in "pages." One such page concerns how the disk responds to and recovers from errors: the Error Recovery Page. A/UX expects the parameters in this page to have certain values. Now the vast majority of SCSI disks have the values set as expected, but this isn't the case with SyQuest drives. There is one parameter (PER) which is opposite than expected by A/UX. When A/UX trys to set this value to what it wants, however, the SyQuest drive reads this "request" wrong (the request is 16 bytes but the SyQuest only reads 4, so the SCSI Manager reports the error. Tony Cooper (tony@marc.cri.nz) has written a Mac application which sets the Error Page values correctly: Fix Error Page. This application must be used under the MacOS. It can be found on jagubox.gsfc.nasa.gov as well as on aux.support.apple.com (aux.patches/unsupported/2.0). You can also use the FWB Hard Disk Toolkit - World Control Application to enable the PER bit in the recovery page (Page #1). This program may also be a help in getting some SCSI-2 devices, such as disks and opticals, to work under A/UX. If A/UX sees that the Error Page parameters are incorrect, it will attempt to send a Mode Select command to fix them, however it will use the SCSI-1/CCS page length instead of the SCSI-2 length, which, depending on the drive, will not work. By the by, here is the /etc/disktab entry for SyQuest: # SyQuest disk # Syquest|syquest|S45:\ :ty=winchester:ns#34:nt#2:nc#1275: ================================================== D.05) What 3-button mice work under A/UX (and X)? -------------------------------------------------- The Gravis SuperMouse was a 3-button mechanical mouse that was completely configurable and compatible with A/UX and was at the time your best bet. At present, however, the Gravis SuperMouse is no longer manufactured or supported at _all_ by Gravis :( The LogiTech MouseMan appears to be compatible with A/UX, as some people have been using it with no problems. Mouse System's A-3 mouse is "fully" compatible with A/UX, but is hard-wired configured for A/UX as: Left Button = Actual Mouse Button; Middle Button = Left Arrow; Right Button = Right Arrow. The "A-3" power cdev doesn't work under A/UX. The A-3 mouse is an optical unit with a nice feel. Please note that A/UX 2 & 3 only support a subset of the ADB Manager. Thus there are a few ADB devices that may not work under A/UX. ===================================================== D.06) Is it worth getting a cache card for the IIci? ----------------------------------------------------- Absolutely! The card makes an amazing difference in performance. However, this performance increase is reduced when an external monitor is used. For more information about extensive benchmarking with the IIci and cache cards, you can snag the benchmarking results via anon-ftp on redstar.dcs.qmw.ac.uk in archive/papers. ==================================================================== D.07) How can I figure out the /etc/disktab entry for my hard disk? -------------------------------------------------------------------- Many hard disk applications will reveal the disk drive geometry for you: FWB Hard Disk ToolKit is very good (SilverLining is a bit wrong on the number of tracks... it includes spares). What you are really looking for are the total number of cylinders ('nc'), the number of sectors per track ('ns') and the number of tracks ('nt'). Also, I'm maintaining a list of /etc/disktab entries. If you have any, send it to me and I'll add them. The file is available via anon-ftp on jagubox. <> Just a note: the number of tracks ('nt') is equal to the number of heads. ========================================== D.08) Which serial cards work under A/UX? ------------------------------------------ There are a number of serial cards that "work" with A/UX. The Apple serial card is NOT one of them. o There is the Digiboard Nu/Xi, which comes in 4 and 8 port versions. Brand new drivers for the card have been coded and are available. This version (3.3.0) however, doesn't currently work with CSlip but otherwise works great. You can snag the drivers via anon-ftp from digibd.com (which is 192.83.159.193) in drivers/mac. Technical Support for DigiBoard is 612-943-9020. If you'd like to contact the main engineer responsible for the drivers, contact Brian Westley at the following Email addresses: merlyn@digibd.com ...uunet!digibd!merlyn AppleLink: merlin o There is also the Creative Solutions, INC (CSI) HQS/HDS v4.4/4.5 Hurdler Serial Nubus cards. These cards have both pure UNIX _and_ MacOS device drivers (i.e. a 'newconfig' code module and a MacOS INIT/DRVR module). The A/UX drivers support baud rates up to 57.6k and 115.2k using the 'B50' and 'B75' flags, true hardware handshaking while monitoring DCD for Dialup security, and full compatibility with CSlip and PPP and their associated daemons. The A/UX-MacOS drivers are fully compatible with all CommToolbox functions and serial drivers. For further info about the drivers, please contact Alan M. Friedman at Intelligent Interfaces, Inc: alan@kether.intellint.com AppleLink: D5620 You can contact CSI at csi@applelink.apple.com (AppleLink: CSI). o Another is Paul Campell's Taniwha CommCard. This card does indeed work with all versions of A/UX including 3.0.x. It has special support for UUCP. It has a few mysterious and not very important problems. It's an excellent buy. The only problem is, it's not on the market anymore. If you can get one used, though, it's worth getting. The one downside is that, like Apple's ports, it won't SIMULTANEOUSLY support modem and hardware flow control. It is immune to many of the nasty bugs which affect the built-in serial ports, including the two (at least) which can crash the kernel. |o Yet another is the Applied Engineering QuadraLink serial card. According | to sources, the board was super easy to setup and use. It also appears | very solid as far as performance. The AE QuadraLink card, like the CommCard and the Apple ports, can't do both hardware handshaking and modem control at the same time. No hardware patch kit will be developed for the AE card... ////////////////////// END OF PART 2 OF 3 \\\\\\\\\\\\\\\\\\\\\\ -- #include Jim Jagielski | jim@jagubox.gsfc.nasa.gov | "Dead or alive, you're coming with me." NASA/GSFC, Code 734.4 | RoboCop Greenbelt, MD 20771 | #! rnews 34320 Xref: pagesat.net comp.unix.aux:15674 news.answers:19201 comp.answers:4165 Path: pagesat.net!news.cerf.net!ihnp4.ucsd.edu!ames!news.gsfc.nasa.gov!jagubox jim From: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) Newsgroups: comp.unix.aux,news.answers,comp.answers Subject: Apple A/UX FAQ List (3/3) Supersedes: <2901@jagubox.gsfc.nasa.gov> Followup-To: comp.unix.aux Date: 16 Mar 94 00:04:40 GMT Organization: NASA/Goddard Space Flight Center Lines: 801 Approved: news-answers-request@MIT.Edu Expires: 30 Mar 94 00:00:00 GMT Message-ID: <2960@jagubox.gsfc.nasa.gov> References: <2959@jagubox.gsfc.nasa.gov> Reply-To: jim@jagubox.gsfc.nasa.gov (Jim Jagielski) NNTP-Posting-Host: jagubox.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Summary: Latest posting of FAQ for A/UX Keywords: FAQ A/UX Archive-name: aux-faq/part3 Last-modified: Tue Mar 15 19:00:38 EST 1994 \\\\\\\\\\\\\\\\\\\\\\ START OF PART 3 OF 3 ////////////////////// =========================================== D.09) lpr printer problems with LW IIg|IIf ------------------------------------------- D.09) I'm using a LaserWriter IIg with A/UX 3.0 and whenever I print some- thing to it through 'lpr', the first line of the page is cut off. Why? This only shows up on versions of the IIg (and IIf) with less than 5MB RAM. The reason is because this makes the LW default to PhotoGrade-mode. You can do 2 things to fix this: 1. Using the LaserWriter Utility program, disable PhotoGrade. Since one of the main advantages of these LW's is PhotoGrade, this option is kinda unpalatable. 2. If you are _only_ using "Letter" mode under 'lpr', then you can edit /usr/lib/ps/pstext.pro to include the following line between "% RCSID:..." and "/StartPage...": %!PS-Adobe-1.0 % Z%Copyright Apple Computer 1987\tVersion 1.1 of pstext.pro on\ 87/05/04 19:02:25 %%Creator: pstext %%DocumentFonts: Courier % RCSID: $Header: pstext.pro,v 2.1 85/11/24 12:19:55 shore Rel $ ====>>>letter /StartPage{/sv save def 48 760 moveto}def This will fix the problem and make it usable again. =============================== D.10) 'tc' errors and blocking ------------------------------- D.10) I'm trying to access my tape drive using 'tc' (with something like "find . -print | cpio -o > /dev/rmt/tc1") but it doesn't work... Except for 9-track magtapes, all I/O to tape drives associated with the 'tc' device files _must_ be blocked at 8k. The 'tcb' program does just that so that should be included. For example, to write: $ find . -print | cpio -o | tcb > /dev/rmt/tc1 And to read: $ tcb < /dev/rmt/tc1 | cpio -i You can get better performance if you increase the buffer size (just make sure that it's a multiple of 8k). For example, you could use 'dd' as your blocking filter with a 'bs=10x8k'. Jim Jagielski's replacement for 'tc' allows for 'tc' to use the tape drive's own physical block size as the logical block size for I/O. Doing so results in a bit of a performance hit so it isn't recommended for normal use. You should use the "mode" only if you need to read tapes written by 'st' or by another platform. Please note you are still limited to an I/O block size of at least the physical block size, which can be anything for 512 to 1024 to 8192 bytes. %%% For more information about 'tc', please contact Jim via E-mail %%% ========================================================= D.11) What CD-ROM drives are compatible with A/UX 3.0.x? --------------------------------------------------------- The original Apple CD-ROM drive (CD SC) is 100% compatible with A/UX as is the newer CD-150. Older versions of the CD-300 (those with pre 1.8f ROMS) would cause problems with A/UX and would do little more than allow you to install A/UX, making it almost useless for day-to-day use. One of the fixes of 3.0.2 is _much_ better support for all versions of the CD-300, although Apple does suggest that you update the CD-ROM drive's ROMs with the latest version if you have problems. I've heard that you can get the latest ROMs by calling 1-800-SOS-APPL or seeing your Apple dealer. The following are also known to be 100% compatible (meaning you can use them to install A/UX as well as when running A/UX): The Toshiba XM3201, XM3301B XM3401B DEC RRD42, RRD40 (LMSI CM-212) Denon DRD 253 Sun CD-ROM (Sony CDU-8012?) CD-Technologies Porta-Drive CD-ROM Chinon CDA-431 There are no doubt more. NECs, however, aren't compatible with A/UX (yet :) ). In fact, NEC even states that their CD-ROMs won't work under A/UX. Despite some scattered reports of "success" in installing A/UX with NECs, I'd stay clear of them if you want to use them in any way with A/UX. ================================== D.12) Audio CD support under A/UX ---------------------------------- D.12) I've tried to install the CD Remote extension to A/UX so that I can play audio CD's, but it doesn't work... At present, the default A/UX setup doesn't support audio CDs. Kelly King and Andrew Kass (at Apple), however, have written the "AUX SCSI Toolbox" extensions that emulates the Mac SCSI Manager. With this extension installed, you can run applications and drivers that talk to the Mac SCSI Manager, including the Apple CD-ROM driver! With this extension, you can listen to your audio CDs under A/UX! This is the latest version of the extension: 1.0b4. "AUX SCSI Toolbox" is available via ftp on jagubox under: /pub/aux/apple.fixes/unsupported/3.0.x/SCSItlbx.tar.gz Please read the included ReadMe before installing and using it. ================================================== D.13) What UNIX CD-ROM formats does A/UX support? -------------------------------------------------- Other than the "normal" A/UX SysV and UFS file system type, A/UX supports ISO-9660 file system format CD-ROMs. However, you can only access these CDs from the MacOS environment; you can't "mount" them in the normal UNIX-way. As distributed, A/UX doesn't include the needed Extensions that allow the MacOS Environment from recognizing these CDs. To fix this, you need to copy the following Extensions from the Apple CD-ROM Software disks (version 3.2 or later) to the System Folder of the user(s) that need access to these CDs: o Foreign File Access o High Sierra File Access o ISO 9660 File Access The docs are a little blurry on this (even though it's specifically mentioned in Chapter 5 of the "Setting Up Accounts and Peripherals for A/UX") since they say that you don't need to add any _kernel_ resources... One of A/UX's quirks is that all files on ISO-9660 CDs are "seen" as TEXT type files. This causes troubles with binary files since when you try to drag them over to the "/" disk, A/UX will perform it's \r->\n translation. To avoid this from happening, you can: 1 Drag the file(s) over to a MacOS HFS disk. Then use ResEdit (or something similar) to change the file Creator to "A/UX" and Type to "BIN " (note the space!). Now you can drag the file over to "/". 2 Use ResEdit to look at the NCOD resource in the "ISO 9660 File Access" extension. Open the "Main" resource in NCOD. Now change the string "TEXT" to "BIN " and "hscd" to "A/UX". Save, logout and login. This changes things so that _all_ files on the CD-ROM appear as non-Text, CommandShell files, so that A/UX will _not_ perform any translation. Again, please note that A/UX will not recognize _any_ of the audio capability of CD-ROMs unless you add the "AUX SCSI Toolbox" extension described in Q&A #D.12. ==================================================================== D.14) How can I add printers other than those available in Chooser? -------------------------------------------------------------------- <> If the printer is in another zone, it is necessary to define the zone in which the printer is located with a full path name. You can then "hardwire" a printer name including the zone for a particular printer queue. The best way to do this is to make a copy the /usr/spool/lpd/AppleTalk directory and give it a name related to the printer we want to use. Modify the file ifilter/ofilter/nfilter (it is the same file with 3 hard links) in this directory. Also modyfy the /etc/printcap file to create a new printer queue. I will use my system as an example so please modify to reflect your situation. The first thing to do is to create the new directory and put the correct files in it. NOTE that I am using mknod to create the pipe file. mkdir Idaho chown daemon Idaho chgrp daemon Idaho cp AppleTalk/ifilter Idaho/ifilter cd Idaho ln ifilter ofilter ln ofilter nfilter mknod pipe p chown daemon * chgrp daemon * In my case I have a printer called "Idaho Spooler" in the zone "SCV CAM2 2nd W" while my system is on the zone "SCV CAM2 2nd E", so all I do is to modify the /usr/spool/lpd/Idaho/ifilter file (you can use vi or TextEditor) and change the line that defines the value for Printer from Printer=`basename "cwd"` -to- Printer="Idaho Spooler:LaserWriter@SCV CAM2 2nd W" In the /etc/printcap file I copy the entry for AppleTalk (all six lines) and change any reference to AppleTalk to the name I used for my new directory. Again, in my case I used "Idaho" as the directory name so my /etc/printcap file looks like: # # pragma ident "@(#)lpr:printcap 5.4 90/03/27 " # # Copyright 1990 Apple Computer, Inc. # All Rights Reserved. ## # Remote AppleTalk printer (selected by Chooser) # For an AppleTalk printer which doesn't support PostScript remove last 2 names. lp|at|AppleTalk|postscript|PostScript:\ :lp=/dev/null:\ :if=/usr/spool/lpd/AppleTalk/ifilter:\ :of=/usr/spool/lpd/AppleTalk/ofilter:\ :nf=/usr/spool/lpd/AppleTalk/nfilter:\ :sd=/usr/spool/lpd/AppleTalk: lp2|Idaho:\ :lp=/dev/null:\ :if=/usr/spool/lpd/Idaho/ifilter:\ :of=/usr/spool/lpd/Idaho/ofilter:\ :nf=/usr/spool/lpd/Idaho/nfilter:\ :sd=/usr/spool/lpd/Idaho: After all these steps are completed restart the printer queue with the command lpc restart all Now you should be able to send a print job to the printer in the other zone with the comma