This is Bugs93-II.gz in view mode; [Up]
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: dave@prim.demon.co.uk (Dave Griffiths) Subject: #import not working? Organization: Primitive Software Ltd. Date: Thu, 1 Jul 1993 13:45:16 +0000 Message-ID: <1993Jul1.134516.3325@prim> Sender: usenet@demon.co.uk I've got a really wierd problem that's only just started happening. Basically, the first time I try to compile a new .m file, I get a load of errors of the type you would expect if you'd forgotten to include a #import directive. But the #import is there, and so is the header file it refers to. I'm not using precompiled headers. The header file in question was actually brought into the project as a result of dragging the class icon in Project Builder from another project's class suitcase. I'm not sure if this is related to the problem. Doing a "make depend" and a "make clean" doesn't help. The header file is there, the #import is there, but the compiler acts as though the header file is empty! The header file is not a link of any kind. Now here's the wierd part: I can make the problem go away by opening the header file in Edit and just saving it without changing it. Hey presto, the compiler now recognizes it and the problem disappears! Anyone know what could be causing this? Dave Griffiths
From: rawyatt@phakt.usc.edu (Robert Alexander Wyatt) Newsgroups: comp.sys.next.bugs Subject: FROM lines in the NeXTmail application Date: 1 Jul 1993 16:44:45 -0700 Organization: University of Southern California, Los Angeles, CA Sender: rawyatt@phakt.usc.edu Distribution: world Message-ID: <20vstd$liu@phakt.usc.edu> We have developed a rather serious problem with our email. Hopefully someone out there can help... Up until three hours ago, our company had a UUCP connection to UUNET for email. We swtiched to PSI and ever since I installed the PSI sendmail.cf file, the FROM lines have disappeared in the NeXTmail application. Except for one user whose FROM line does appear, this happens with all internal (office) mail. As far as outside mail goes, FROM lines are again usually not displayed. I am relatively new to UNIX system administration and have a solid working knowledge, but unfortunately lack the UNIX-jock ability to really work miracles. Hopefully someone out there has experienced a similar problem. I am convinced this has something to do with PSI's sendmail file, as no other modifications to the system have been made. Please send all responses to: rwyatt@ata.com (NeXTmail) Thanks in advance for all of your help! Best Regards, Robert A. Wyatt
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: CDplayer.app Message-ID: <104@boschrt.rt.bosch.de.bosch.de> Date: 2 Jul 93 06:55:12 GMT Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. Hi I tried to listen to a music CD with a CDROM from toschiba XM 3401 I put the CD in started CDplayer.app Then my harddsik was more busy than the manager of IBM and the light of the CDROM flickert, but no musci came out of the head phones. I am using NSFIP 3.1. Any idea? --- /********************************************************************/ /* Kay Schulz, Rheinstr. 24, 72768 Reutlingen, Germany */ /* 07121 / 60 19 61 privat */ /* 07121 / 35-1341 geschaeftlich */ /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Re: #import not working? Organization: Primitive Software Ltd. References: <1993Jul1.134516.3325@prim> Date: Fri, 2 Jul 1993 13:28:44 +0000 Message-ID: <1993Jul2.132844.813@prim> Sender: usenet@demon.co.uk In article <1993Jul1.134516.3325@prim> dave@prim.demon.co.uk (Dave Griffiths) writes: > >I've got a really wierd problem that's only just started happening. Basically, >the first time I try to compile a new .m file, I get a load of errors of the >type you would expect if you'd forgotten to include a #import directive. But >the #import is there, and so is the header file it refers to. I'm not using >precompiled headers. The header file in question was actually brought into >the project as a result of dragging the class icon in Project Builder from >another project's class suitcase. I'm not sure if this is related to the >problem. Doing a "make depend" and a "make clean" doesn't help. The header >file is there, the #import is there, but the compiler acts as though the >header file is empty! The header file is not a link of any kind. > >Now here's the wierd part: I can make the problem go away by opening the >header file in Edit and just saving it without changing it. Hey presto, the >compiler now recognizes it and the problem disappears! Thanks to all the people who responded. It was none of the things you suggested unfortunately. It just happened again. This was after I did a "Save All" in Edit (I think this does something strange to the file modification time?). Once again, the compiler acts as though the file is empty. It's not: /src/Newsagent/Newsagent> touch Vessel.h /src/Newsagent/Newsagent> ls -l Vessel.h -rw-r--r-- 1 dave 661 Jul 2 14:07 Vessel.h Touching it doesn't help. And I can cat the file from the command line and verify that it's there, but still the compiler acts as though it's empty. But saving it again in Edit makes the problem go away. Very mysterious. Dave Griffiths
From: sean@digaudio.byu.edu (Sean Luke) Newsgroups: comp.sys.next.bugs Subject: BIG TCP/IP problems Followup-To: comp.sys.next.bugs Date: 2 Jul 1993 19:28:47 GMT Organization: BYU Distribution: world Message-ID: <sean-020793132558@rm2221m2.cs.byu.edu> Just wondering if anyone else has had this problem. We're running NS/FIP on a Compaq 486 with a 1-meg QVision card, a standard ethernet card, 12 megs of memory, and a 105-meg hard drive (yeah, cramped, I know...). Here's the problem: After booting the machine up in the morning, NS/FIP works wonderfully. But after several hours, the machine hangs. We've traced the problem down to the operating system completely losing control TCP/IP. We don't know if its NeXTSTEP, the drivers, some incompatibility in the card, or some bizarre network problem. It seems that the machine still responds to IPX (we *think*), and the problem can be "fixed" through a soft restart, so we don't think it's hardware. I'm still trying to nail it down, and if I can figure it out (and it's a NS/FIP problem), I'm aiming for that free 486 NeXT is giving out. :-) In the mean time, can anyone help us solve this little mess? Thanks, Sean Luke Brigham Young University sean@digaudio.byu.edu MILK: It Comes From Cows
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.next.hardware,comp.sys.next.bugs Subject: [rtf] BUG FIX: Gateway2000 incompatability fix for model 4DX2-66V Date: 2 Jul 1993 23:45:10 GMT Organization: University of Houston Message-ID: <212ha6$pn1@menudo.uh.edu> Enclosed is a PostScript file that explains the simple fix that will solve the keyboard/mouse problems with NEXTSTEP and the Gateway2000 4DX2-66V. This fix involves setting a jumper on the system board. This fix has been tested and confirmed. -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime." -- NewsGrazer, a NeXTstep(tm) news reader, posting -- M>UQR=&8P7&%N<VE[7&9O;G1T8FQ<9C!<9FUO9&5R;B!#;W5R:65R.WT*7&UA M<F=L,3(P"EQM87)G<C$R,`I<<&%R9%QT>#$S-#1<='@R-C@X7'1X-#`S,EQT M>#4S-S9<='@V-S(P7'1X.#`V-%QT>#DT,#A<='@Q,#<U,EQT>#$R,#DV7'1X M,3,T-#!<9C!<8C!<:3!<=6QN;VYE7&9S,CA<9F,P7&-F,"!<"D5N8VQO<V5D M(&ES(&$@4&]S=%-C<FEP="!F:6QE('1H870@97AP;&%I;G,@=&AE('-I;7!L M92!F:7@@=&AA="!W:6QL('-O;'9E('1H92!K97EB;V%R9"]M;W5S92!P<F]B M;&5M<R!W:71H($Y%6%135$50(&%N9"!T:&4@1V%T97=A>3(P,#`@-$18,BTV M-E8N("!4:&ES(&9I>"!I;G9O;'9E<R!S971T:6YG(&$@:G5M<&5R(&]N('1H M92!S>7-T96T@8F]A<F0N("!4:&ES(&9I>"!H87,@8F5E;B!T97-T960@86YD M(&-O;F9I<FUE9"Y<"EP*"GM[7$Y'1&]C=6UE;G0R-#<@1V%T97=A>3(P,#!& M:7@N<',*,S0R,#8@32=95C`Q7"LP*C<L1S,A6#DL(2@Z,C@O)R$Y4%E@(BDJ M1R1"44A,-BLF(RU*5R1`,4$D/#LB-"1@7&!"0@I-(4A0.RA$1S9&)B1#*31$ M,"Q&6RPX(4<C.%!4.BPV2R1((R8S,41.+RU6*RA,(R8R2%TF0S(I+$HW/$I4 M"DU*/2Y'-"HM*D<T2C4Z2$0P-"HZ5"(D*T9#.4!2*S8R6$`J)D`Q8$1*.CY" M4"HZ+"-1*2A2/CPR7"(R+B<*35,L*B8\3D(X*#XN44$T/%\K6$@L)CTI0E@] M2%DK65(T4#0I12))-$(T)4HX,C`O1S$\(B$A,%Q&*29-5@I-0BE04F!-7R@Z M-4XD,RU*4BDS4B-)22]&0S%,0F!-1B(L(BA'(S!`13T]05A%8"1"(4!8/2Q7 M6R=&+21;"DTQ6%@Y2BA6*#M#3"=-*5!92BA&7"8U+D<S,417/2DQ0T==+#8Q M-E!7.24J0$%!*T8S(4=.*"M0+R$I7D(*32U62$$[7DI@,UXO1B,G4%Q7.UXG M0U-:75Y'-%I9+"4Q04%1,TDJ)R<^-E11-#`X/6!<1B%602Y57S(],`I-.E9: M5"$X-4@]+$`Q449%1BXX)B4X1T,P+#PU8#PE0%%8(5`T34,W(S8J0#5@/5@P M.ULQ05<W."I/)3\F"DTF/S$A*#P]5#124SA50$U54R(G)R)64D0H-#E".3@P M6#A!1C50-20[/4XR+4PT.5DY,T!4(5!`2SQ!.2(*338R8$A104`H+DTK)S9' M54!!0B1%1352.EXE4BHV*RDX8$!`4%!))2<[-CY`,#0].RP^,F!@4%A,/2M$ M.`I-)3=41E@\.#@K33-84$$]/SXD028F-CM,-#$M74)>*"%0055((R5#)B=' M(EQ@,#PH1C9;.CHQ75LK)DDF"DTG5D8X-#`X.U,_-$$A2C!`0BI+8$@X14(H M.#I(0T@H8#HY*C,U3T@Y24E)4E9.3D<^6E`J-TI.+$1&2$H*34I&-DA22DI+ M*U4S,4<A42]"*B4F)C8O,#PV-"PL*"%@15@Y64`H(DA(2%)>*D))73DP,%E( M)3\S-4M.)PI-8$!$1"XP.#I+/3I1.C15040L)#<F/RHB6"Y28%0Z.4LK,$%+ M530\)T\F/S!,-E@B(C912S0K4CLY2TQ/"DU-+2DR7E)</#TX4SE((55!3"PE M3F!,5%Y66E\D-5M(*TM:3"E`+TE)2CH\5DE:7R<D-3P[+$%;3SA`12(*32)3 M-TU2*#E.)2TN03`A7S]23$I,/RXN6C0^6E-:)$I<45PL/TY04B)2(B)81#%/ M+B4_+#Q:6E-!3TE@1`I-33X[3E8K*R$R)E]=/$Q31E0[)%0G33$J6S(G-3E+ M4SI,43`R1%,_4"=#,V`A*"LM3DLW44%!5"M/328["DU+/B-!1DI4/#$P22U1 M44PJ.2Q,5%@N,"Y73S(M*"]0/3XM6$!#+"<F)EQ7(2@Q8#HY3TT\/3Q<6C-' M/SX*32<F43<F6#`\.5Q145PJ+5TR5$DG)T`J(EPH*R(^.E,^/D%%42<M4$Y3 M+R%&)E,]3TU42#H\+"=054,Q)PI-)S8K.$=`(EY&42DW*U5<54(U44M;5BXC M3S8C5$8I3$%63#@I52M@5U<R-U$G/D<X529;/$%?-5)>+DI)"DU)3E(B/D\T M.%%*.3Q13%A=2%]72CE=-2X]3RP^23@^(5U>*5<V(UA0(B=-.#9=3$XA4"M; M3#HD+U=(234*35E<.U!./2,Q.#<R16!<)#DO0RXG4#=41CQ?*5M@/U=(*"-' M*ELD)4A?,BU`8"8O13`K/4$K2"0^-D9@(PI-*3`[(2I7-5`T4B-4)UX[0E%: M4"TU1R$G.EM`-$Y?*E=/44`R)"=$0$0E5#DW8#Q;*#):33U$(UQ7/UTZ"DTP M0TTP1C(E0THT*#E,1E(G3U-'2#M80")+*3@I1E\Z5%(K148C8"@A4#!7/T0D M+"DT32(B4CU)."1*7",*32\F5RE`-4XQ3%@N1%%*(DD[0"8Q+5<F0U8]4SX\ M(RTN-3!2)38E(T$G)",G,$TI(4E6,5LF*B8G,D1#8`I-+#XX,$`Y4SLD,"PG M6CQ@-DU`73DY0U`O)DXD5RTV.R4R1"58.%`M3UE)(B<B23I!(SHZ245.3S@D M*#M:"DU5*"4J.E!$12(M.T!!0S\\4#!48#DJ-$LX-40F-C\K)B\D6B0X2RI$ M2BLJ/BPP3"])-#(C*S!>-DLY2#`*32%722HC*5@X0C8\6UI+4U$O640R)%!# M0B%+54=)1EE/.#$O,T`C(D9&4T1(7%!8.UQ>.U=5*$1+5TLP00I-+5=-.T=` M,D<I5%XQ23TM6S(T2&`N4C=%,T=")C,U3U9(05@H6R@X5U$W-$H_/C!31U]$ M6#X[.4-&1RXY"DU;)DI&4RHC*5%/7"E#64@[3%XY1TPI+2U;)E`S1UDK.BE3 M0#<I)%A91"4N+%E=4#A45#!*5$=?-B17/",*34\Q3T0C14I202<Y2D@Q040U M0RA!1D`B*4)#,CH^44T^7#,I.D%635)=8%<Z62XX5S$U2C,\)BE'1R%%(PI- M2C)73U8T5C!312U,7$(S2#,M)3<T721(72I@64LQ23U5(S4V0%];2DLN/B,P M54,S74@K1E0D)"P\3"0C"DU+72M:-31635TU-55@+BY;*T<U-R@N1E4T030T M,BDC5E1@.EI+*B510BQ6-CA/3TI52U(Z2C4J-E158#L*33,B/%E94%).3"<I M.#!573\B,#PA0#8\+TDC,$4J32Y`4DI?0"(I/4-$(B]844M@5%PF4E8C)EQ0 M."$V3PI-4B-<.4!((E-'3C0K.V!6.%(P2BHI14142R5(/3DL3R,H/TM0/UM" M72-%75@N5"4M7T<Z4T--,4%@2$D["DU645]&(EI!+$-@+EM=3")466!:*T-( M+#(B*D)<,E@Y*RU(/3U4/E=-*4]/.DQ2(45"*%$L3D50,R$E*#L*33(P)C$T M23@B6"16(34]0"PL.#$X2%(K1EY88#0W,40^6RM`0TY66258.34]5E<T5R,I M534K0B,]0EPO6`I-(T927E])54,T,STJ05];-C5:(T`A.B\N)"4[0#%"6RA0 M4%$I5U%;*"I<.U=912(F64=4/RDC3$DW8"Y3"DTZ4$TL5E@M/R=33R15+BLA M-BE26B<E4S\H*D96*T9#*#Q9,$-.4"-88$I42E-,/D`H12M"76`Y12<U3E,* M34@E,C8X63!%,5-$*U!03RHL0C$_44U#,"$Q7T\C*6`Y/29-5%I:-"9=7%I5 M2U%+75-92RE4+C@J6TXF*0I-4B8K3$HR,48O/E%0)5HZ,V`T7C]1-CDO*"%+ M43TV7%1"(25)(5PC(EE'(S!(*4@C)BT\(CHP)BL\-"8P"DTC0ED[.%`V0RU` M0DLC*B]#14Y'.#$T/UDL(D$F048V.%<N,"E/,S0J(R5;)%0R+U<[+#Y;.U`I M-4HJ2BX*339<5UA*(4\T/SA=23X]454G5RTV5$DO.DQ6,C\D-6`X75A--D%& M2BY+-CE`,%DC,"PD)"A(6"9424Y,(PI-3%U16B%40SDT2$%3+3E>5DI1.4=; M)S`[+RU=1E<Z-4XB2"U13%TV328X+",F3"M0.48Z-4906U%'2SY#"DU13BM. M-5556S0].CQ`5D-65"Y<-SXD-S(Q/#<Z/%`Y/EPL7T`K-BPA.5]"5B51,5$N M/"$M3U<Y+5U&2C0*32TZ44U'6R]"(28\-D(D,20H03\Q5#,Q1%!.74=&3S@F M0%M52EDD3B)`7$<_0"\H4T`F(21+,C`C-SQ`4`I-7%E+(TE@.$U`.50W63`S M0%!()4`B5"LI4#!.(C0F5EPK/54L)3)/(U1,/C`A0T4P25!7,3--*S(V/"XF M"DTQ,E<]+2DY(B0V*28Q65Q33R9@*",C,RU3/"@P1BHX+TY@03`G5$%`2B9; M55I&,#TC6"0A+E`W,T`I0$0*34XO5"4R.$);52DM8%U:3S\G/R%:+U!?/S=5 M-B1`,C8F6E597U!-7C\H+T`W+RHG4#U%7"M725Q@/CI$7PI-*#\E0CM=.S]* M4B-8-54T(5Q50S<_*RU@4U\\-SDJ)U(U)2)&)RU3,%DC2S1'0%9,0#`L.UQ/ M8")474!!"DTC-5I'2%E32#DB/"51+F`F+4TC0$,_0SY((RA0(U`\43XH)#@J M3E`F+#TB12XC8$!404U0+2Y%.D)"52\*32Q#(EA4*#A'2"U)6"4R)S%)7"P] M*B(^3V`[-R8P,$)!4#!,)EU)1U--+5]<630N*%1'-#])(SLP*51#0@I-,5-. M3T4A/",D2"-344`Y1BPG74@T)UU1+"A@+4!!0T5(,B587%))030G148T1S8F M25=(,U1'-3(U4EU)"DTD)SI-,5$]15U0*4-$)SE)3"<Y-EQ7/D`P,50C7#)+ M-$!()CE)5S<N75@E6T%104E8)SA0+#$P3T1@.B(*3458+%A,*"Y(/5=#8#%8 M+BI!44`K0$`Z3T!!5$=.(D!04#$H)EU7/5-0."DR+5%44$8G23I55RDK+B@V M3`I-/5(T4C!@+T$U4#U?751),D(E/2%*)T106#$M8$Q(-$]$8#Q=*F`L520G M6",H44I415`].U9@-"HD(DM9"DT\1D%.)&`[-DPV0SHA-&!0-5<J(S!'+44I M4S\P-%9//T13+"HQ,E]62$-84#TS*R<\15M#*%%)0TU%(2@*34A",B(^)RHE M)BA!+%1'+B5>(4=56$%*6S57,B=80B5&/"0N72@P+%A4)BDO.$<M8$4B5$@D M(D]-,#91+PI-.34I,5DT1D8B(D8C64-*(3%`.ELN(T=5,$A*72XF0TM@0"E/ M*$`S-"1`.T8L0D1=541**T!3/T5,43E""DU06$12+5A`7EU474(P0T,F/B<O M4UU!1598,4E4,&`Q-2E3)D)$,#U=/$`_+5I@.SXM4SU%/"%41RU4,4$*330D M(T`F)#%:,%A6/C8A7"I,*%9%4$A13BTD,U1`-2E46#=044TR0$Y8(24S2",_ M6SXF7T8E*2%<4#<](0I-*6`]531@.$Q$*%U/0$A:,3181",X55)"-#5"6BPX M4U-&)R],,F`])4$T3",H42-9,B@H.RE&/STJ*6!*"DTM5#-!24E@2S8U6&!! M)CY).$).,5XC6&`E(DP^0C%5740H75A.(D1:0CA+)"@Q,SI853`W)%4V23TR M-6`*34DS4"$E.3`Y0$5"42E&4#I8424F(C4V6D0U2EA1(S,Z)#A;0S8B5T4Z M*$,_,21.5D$D3UE")R8[3$DW0@I-3B0E/U(S,4%462P^)#0B62HF0U,B)#(A M.#A6)5XD7%@A45A;/5A<5C%3344B-",G2%8B3U5"2D0Q-D)8"DU,559>04), M3SA@,2DP8#(K8%0B*$(B32-.-#\C)4,W02%(1TXL6$0Z/$,M*S%)/5Q:,CXX M5BA%5C(R.BH*328C,BQ@2%A*44,R/SA)+TY<63Q114A>3U(W)U<D0EA&.%4\ M(DE#.#Y$0#(E.3%80U1(22Q50RY:,C(V70I--CA`35XV.%HA25);-C`[(S(R M.%1,(49,-BA#)C4B4C9!25,B6C5?55`U6#XH05<A.C%9+V!@/"<P45))"DTI M(SI&73A<3R0E1T5(4U4B*5))6U133%\B,DA1)"8N3EQ26DU=(S1#)%)8*2@I M74Y0*#1@43$^7%`S5T8*34(U0U@^,C4U.CA.6B0P.EY--RA423-7,$A5,S]< M5%I:)#E%4CTU)4)@8"I++B@Q5B0D7"%9.B)`6$HA(0I-,3-0-#I"3EY!6B=% M/3E,*5`J(EA02B=355<I0B0C3T<H-2-*/C4N2E(U-S1!-BHR,$%?,%8F)U1= M-5Q!"DTE1#A06&`K.EA5.S550E8J734G75(V3TPV(UQ'2B%/+3TZ(T]$4"%; M*"4D(59*)R5<65U,+C-72V!38"L*33%(74]1.BM4+C14,T9**3LN02$]*D)* M.DHZ-$LJ2CHH33$Y7T5!.R940#XS5%)/*EDV4#E%)EP[1$E250I-*$1>44A) M5RE6.5==741&73TB2%),8#Q`4"):*4`P-2-$(R4F2$(D(S`P.3(\8#$B8"(N M,S!2(C905")9"DTX0D<F3C,F)3Y*024L1U914#I"+B)*1D(L,#8S5DHQ+D)% M1B=%.D8H4DI&*U9*02)8(TI`*DI%1BQ$,ET*33(D)U$X-S4C)2HM2EDU3#$Q M0#@[3%`^-3$Q/C=%-DI(3DI&*EI'4DQ.0#5'15`Q)2A@,"9:1U$A7"I!4@I- M)%E:2BU)641",V!/0"8G55$P,2U88#$[6&`H6%0X-$!88"A2*"$P32PQ.5DP M05!.+&`L54`G4T$F03%/"DTF*EA18"=;4$)`+%!((U5#/#`L4E`A3$Y$8"Q& M-#`M/3`C*#P\4#<W+4%@-RA".SU22E]53D,\42PA.%@*341@+3U@)B)-,3`X M+SY7.5PE*DI#(D8C1#!*3251-"%@,4HX1%Y`*4Y`8#U.,3-)0C`D/C%.0#P^ M2$I&*0I-5DI&3%Y*2D(F2DXW440D-5Y14#=:53A&*E%)5U$S)$$B6C,\7$DN M2DU++"LP2RA7*E`\63982B9&2DLE"DTR0#L[/C)'+BA7,"9"1#I*(44P.21) M)R%%)CQ$1D`B2RHF3EQ!2RDG,EI03%Y:1%->6RHT.DLL4RY0/D,*33I"4#M, M6$LR(D0P64PC528R2E9.3%LQ-$@F65M(65LW1D%.64U1.E!`-EPG3CLD35)# M,&`^5ETC.ELX4`I-1E)77R$G0DDH62)4)%983S!@,S0P1RU%3&`W.5!!3$U@ M,U4I+$)=/EY*7R542D]=22%-8"DG,BU>6T$L"DTB*T(L*$HV*%DT4%,H635; M6"M#3UHJ*UE81%A4650]5$@I1D\Z.E5;)E`Y73I:3$XV2TI@15E3.%Y%7D0* M33I0.B,Z2E4B1"$Y4V!@-"-41D8Y*$,P/B4[4DY`4#%%/"@M5DQ+3R)>4"DW M8"=37UA;4#)%0#LI/C4\*`I-/2,A)E%$)4U$8#U++"LR5DQ;(B9@52Y8(40Q M8%4A*3I65#]+1E)?.4!'3T%51EM;2B-5,DXS)R$Q24=%"DU9*B9/(B-@)E!6 M66`M24<\4%,S45938&`W*UU@+4LI1S0K*%,V6S(B+EM;12Y;+EY&22LX*#LP M4T)2-UL*345+6%%`5DPD4R9-74@G)%PB3"134EM5-&!)/3A(*CTT4$H^.C%* M06!&4B0M.RM8+%LL(C%.13I.7%PI(0I-(D5(*R1*,25:53M>5%(A3B0F6%XF M2RQ<5RPH/%!612A66D4K6ELO+210/49*-6!&(R127C9,*STZ5D8_"DU43"@H M/2E-)E92+50L8#$M1&`U*V`B)DPV2D9;8$)33#A*2D`U-$@C+#5*2D$I*29) M-UL^/4`]-TTU25T*34@J3")02DTN/DE%2"4[+4,H+"4C5E`^0%Q$)$(F6S!1 M1RPG+#%%/C]@25T[3R(A/B,L.4);*D,T)E-%2PI-8#I22$5%1%L\64U&6#(I M1$PD(3PW(B\E23`A040R5%8X8"Y+1B(G4U(T2$U:(TM15%I05"Y%8%E*1B5/ M"DU7+$I.3$HR.T4L1T!4,T8S/%`X5CQ%23PK(E]#8#8D(S1"8"=$0F`K5$)@ M36!!6ETC8#Q5.$$[1#@Q65@*35A!6RPS(C=08#,Q13U17$I402M8-D$K3$)* M7CPT,"LM-V`Y.T(Q6TI(-5-".#$[*#XE2S]'+%)?-R=;(@I-*R%,*E!"8"-( M0SI1.$1;33HB53<M(T!9021--DTC7DY002A`0"I?22Y`+2(D,5`O/CQ*430S M0$Y`8"Y*"DU&*EQ55#HL*DL](T,J1#HS74-:/R<L2$`L+$I%2R(G64(\2%@B M,DU'4%Q*3ULL2#DE0T0V0RHL0R\\34<*35TE3"I<+$150#PO/$A`(2A%54)) M/EM+0%U;8%M*0RY:0%)4)4\])"<[/$X[*RE0*UA,3C\O*C!62"$O6PI-.D%3 M)U0[.%=(+2$G4D0E)4A,4$TO/$%4)"HQ)BE<229#/3$I7SQ=+$\T)"9=(DLP M4E`X)3$U2U%.*2U""DU87%XR14,F1UHU)%$O.C%:225`+UI604E+,RPB2S`B M)5%"0T1$0S4E-%)4*B@M(DM!/3T[)%LN(SE',$X*33LQ8"I4(2M/6D8Q6D!0 M*C<P,6`F0#%@03`P+21`8#125&`J0SM@-E-0,2--7#4C2#DM0R0P,"U@65`I M60I-1$(\6%0A*%505CTI7D))2#@Q55-48"DR0"9*6#$M.ETD,SU',S9'4TXM M.BA5/3HM7%TY05PF0D@J,2U4"DT_.4)&6CT_7DA`8%)4/3TD7%T]3B4]0$U$ M,"Y00E8W220W3"Y&.21`*&`J42TQ131%4R1"-"0C7SDP.%L*351`.$!,+4(Y M6#U#.21&*"-80#HE*BU5+EA!-4M8/5<]74-?5"0U0%<T6$!`(CDG2DXH1250 M(4(N8#%'4@I-*F`^.4<U*D0C,"U-0EU#22@R0"-(,4XB*2<C+V`P*S!"(BI. M5#(X*UI1)E%56%,K)B5-(34B1CQ(0S=+"DTO,D0F-DXE02DM53DH,"TM)"%< M2C!0.E5@.%<Z+$)0/B]`-%)<(3E1+#$]550]73,Q/4DC)#4O+D,P*$0*34=` M.$9/1UI94#$_2TXG6CDM,D5)8#)?,B,T*"-(3F!',$(E-S!.)S(K,#$I7&`Q M,U`N)4)44#)$33(O1@I-+S`Y-R1%0"12(3]&,2%%4#`I42%+0E=,7B=/+20Q M63)-/491,S%0(D-`*D%-/#A`*"$\6S598#XL-5]4"DTL.$E))#-$4$-$6SDL M34%92&!@2%PD-",\3CU<*T,Q1$M-15PW3B<F,3$C/R<Q3CE@,"DR7&`Q+6!@ M*2P*35M.,4!00#$U7"XQ2E!.(EA5*BQ:/S`Q*D!@-%-@8"Q--"I=)6!@*3Q` M8"I@0T`I0EPD/4E@/D)$(S$H5`I-(T-'/D`R25I87BU+/"(T*44Y)D=/0S%4 M-#(Q)5-.1CY'0E0K0TXQ/$1@*D=;0"I,-T%1441>.RHT,UDN"DT\+5XM7#%! M,$PM7$`P+B)'8$(Z,ETC1D(\,C5,+%Q$2DQ2*%5(,T-/0S9=73$D/S<U(E9; M55(](T-.0T`*33LQ(3<X0#1-5"(L,3Q.-4H_)$E3/"Y30U9-4E!?1%@U(6`K M4TU#7$DO1$I+3%$Z4R$A/4XW03Q`5"8Y30I--"=80&`N0$]$+4M'5#`K4%0W M-SHK.3P^33$L,D,].ELZ+4\Y0$U,4$@M3EQ#,5<D,S`N7U\R6"HD+5,G"DTO M/5!7)",_2RA=4#)@74)(0C`I)5A@,R]20#$E,&`R8#=-4$L_7RA-1UU03R-> M/S`_,C0H2U]@+DXX63T*33PW-U\H.2-?*BU72TM!1"DX/EQ2)"Y@4DDS0$@L M)5TN8%0W.CQ"-U]71BE9*"]@654N*%L]7R,U-#=970I-)$Y:0%0Y(4)862$E M.$1)7$P^)3=`(2E>*#`I3%Q245@P4#A"."Y113=-0%`X,"U()T\V*4\_,$@Q M,44X"DTC54$C32X[5"-.,U\H754A-UXR1C@T-4),(3E$5"(\0"8R,D\](R\] M,$-<42Q"+41(*3)`7#=-1$!/04$*34M?05PE4#HM6U=35C-*7D\K3S0I33A3 M32,R7B1;751`5C\T)3]27$4_0BE6,UY`+5-;5"\G7R4J*EY:1`I-+3\F7BXH M7#8O74U1/S<P+3\]3R577R9.7R\D6CQ0+%4L+RDH.B\K1TQ#-R1+,U19)U]7 M7EA/*$!742@B"DU'/E%<1U%9*#@D35\J0#U=)$%<(UDU6C$L5E]5+#0S,E<_ M.4!'7R$E2T-#,C,]54Y$+58Y0$(J3%0^(D4*34=`/T175E5=*2,P(DHS0ETB M+%!%3T\J02XB.#P_6TU;5DA>3TD[1RDH-BM`1#%"*2LD+R0M.3(A.#4^,`I- M*$%0*#@G7"-4)3A(23Y',$H^.B9=(2@[,$(M)%0B+2,]4"8[-%]-,SY@52Y. M348M0R(P)SA!7CQ:42=*"DU+52@\3E%%8&!5.3%&0RPM)#A`+TT[13,X-$U* M-U1+(3XV,B,N3D!<-3PK4TQ!7C8X)DE),TQ*+6`R2B<*33LT0SU5)DQ93D(K M5D`X8$<T8#`^-S0I.3Y,+2Y@62I4+5,Z*EHI35DH42\M(TM=(2Y1(S!8+B@Q M(B1%5`I-1B8E04LC62,M4"XM4%Y%*SLA0U!<630O7R8P/E(D8"5/(SDW*TI! M34)'15,I-D`],E])4CQ.)5\O8$P^"DTU*B(F,3I*6R1/6B=`/T-@)BL]+3E, M*#LS8%T^0$!*/$`B3#$A,CD_-DY`-C`V(C`E*34V,$I$1C(G4S@*324M)2U$ M65!7+RI#/2DD-$U.,"XK5"Q362$I,C!92SM@4UXM5R9>6$LW*#Q`2$1$)"1$ M0B(Q2C="8%I470I-3#(G/4I((5DB5SI+0%!0*DM>7T<W04L\)D4Q6D<^6S-! M.T@X6"E!4#@X+3,\03A.5$14(25=8"4[25LJ"DTB6"A,0U!!0B9-,416)F!@ M3TDM6BI"8#Q*0&`P.&`D7S<H03LQ0S\N42Y$6UPS,21`+29"-B)9/CDV(20* M34U51$<F33A@1R1,(E!&3"M`(C$Q52)5*C$P0"A@,%TK7UTT(3XW,%-0(5T_ M)B5>6B-')UPN,#$X)$9@8`I-/#!@*2I>*"U`,#`X-"$M*B99*T(S*#@M*#-1 M(B4A(TY13%(D.B<C/EE34U0B."<H0R4[+E@I(5A"3BQ3"DTZ(30R.F!9)5<A M(2E!5#8N3EPT*"1&0%]23")1/E0L55`[+T5@)R15)R\Q)%9;*B@^3B94)C,Z M0$Q1)"D*35,I(5`W*UU'1$M28"HS(T]62&`K8")>,U`^4"A"3&!2*BQ)8$-< M*%=(7EQ&24M2+48B32@B6U!((B4\0@I-6C5&6%%3)SU8)"\K8#`E)#@O.%U! M6TDG)$@J8"8N)3Y.1CXH*R-+)50Q-$I')"XZ05<M(R]+(2%!1D`C"DT[1")6 M,B<L/F`]8"U!6R90)C0I(C=>43%!,R1$1BLK7#$C6SI0)$L[.55!1#I((E1$ M/CDV-D5%.E0F05,*34@C)TY-(T=@5#$S8%4G2#]6)"@F02-0)2@O*%171%,K M)4)'+R-.)$8K*R)4/D4N5D(A-DU4,TLY1R9340I-6C5+(D`C2$E:2D8B3SLF M.EHB55(T5RE20SY22#=%,"I$,C0[4316.SA1-%1:-U1`(5(S1DTQ.S5412A@ M"DTE,D!:,DP_23(A5DM(5S9<0TU`42Y62R=;/$`]3EHM5U\H6T`L,U(J45\E M*"=*)$,^,U(O6B,D74I,/U4*35(A6SM(5T]<0TX[42\\2R=>.$`]6%(M74\H M7S%4,%-(45]7*"=?3D,_7U(O8",I8"),0"$R,F`K22@D7`I-1&!`4C`Q6RA: M5D`_7#HN(S\I(S8T-"4J4F!%*2@R3D1!/S(O(DXA(CI$0UTB(B<A.%@O3$0N M+5$P4$LH"DTF7"-<1"1=/RLI)24C/T9,2E$S*2A%/D1"45%%*ULI)4-#*#I0 M+U)@0T!74"(S-V`Q3BDH)S5'-#XN,2T*32HF2%A42R]=4BE.,"A8+41$.U(Q M,$TH1U1@8$%2,2HV.2A9-#543E)@3C1@)#A$03`Z,C5)*%TT)$0B,@I-,B%, M0"%/,20N44@C24PH-S0X3%!>,C<C22I$8$1<6D<S(TH_+%1$1E%>,CI)(3D] M4B(P1#%#/31@5RI@"DU:8$XP.#0A+S4J8#LX)U528"53*6`V+V!>23)`/D$D M2%LX-#A()DU$6"),1#)./B,I0"Y%1T@B,3)9*"8*33DL1U\^(C9-6%@^3$4M M35$T3TDG)%=$1DY2,"Y2*2X_-$1?1D`A3&`J3RQ$2C$R-4E3*31)1$M#,")) M40I-4&!50$4V)V`U/"DJ-CY$2CY6,4)=*#DK5$1:)F`_7U@J+S<D-$%-34A? M*3=62"%`3C(^)BD_*$E%2S92"DTV*E@D1R$B3RTJ-5Y3*6`\)$4M*E)?(T@K M+UQ#0CI0(3@[*")!/$DO)C`Y,DD[."1%.R,R*5A9*CPC1$X*35$^-DD_*39# M5$4^4C)'-CDK1C=%2BM2-3PY*3M<1$DW-C)173D[)31@*EDR-BXY*SDD1$(H M5C9<1$`G-0I-5$-=+E)3(5`J,#]&/6!2.%\W)E0X-$U*6#)'5SDL+$Q%6DI2 M-20K+#8X1$XV5C<E0RDT-U1553HS)S4I"DTJ6#Y%2EU0+%PU*2I63$==.B)= M)R905DQ@/S=2-F`I*T4P1$1&-C0L2BD[,$1#7#I3*459)S$D1C];4C8*358S M*39%3$DX7C)?0T4\7#PU5"I!.5`[+4@L1S!"(CLP3R<])U16/U93)U%56U@Z M1E0V,CHH+2Y3/#1,6PI-*C`[5CA<0$1&+UE1-UA:5C9.1$]!."LM5RA<(TQ6 M(S)3)5=9+3Q68$).4C1*(2DT7TQ3040J748P+4U,"DU&5ELS.SQ*8$8](B58 M)CL]6R0I3E103RTS."1&+5U41E96,CHP0"5)7TQ662XQ4D(I3$@T1C8S,R,N M02H*35]=0B4Z0B,K-RDX7B16."I3*R4I+C)-,%8S,",_-R5!6D%2/4HR/EM9 M.UU<1E<],SM'2$$F24!765(Y+PI-2BE.1"17-THS.U<Y+50F1S!@+CPR)RT\ M3S1:1EX^1#)0334\1RQ?4C182"$[041/35([4EHY2&!,5E(F"DU3/$DI)S)? M1U8T428Z-2TO7BQ3,DXS/2,Y7D4L1S-0(3Y/.B1/(T1=5S4C53DI5D!$6B0] M4SHX*2XO+D8*3259*CI"(RU+7D19,DE"*C<Y+C%414,D,SLA*R],-T19+%8_ M+E<I.SI<1R]",STW62\D7T<F5$H]75TM7@I-4T@R-4@J6U9)74]$1UTD4S]3 M*R]/0418+U8^+ETD-49()R<F,C-*26`J6D95/%(Q-RTM7#Y$5T$N,E<E"DTI M3%141T0T+3LT.2Q9,49/1BX_24,I6#]-)T@B5"]<23!'3B(E7BH_*EPE6EA, M7TM>,SLY64DI)$@B,S,*33-#.RXV5T127%HM7CLI4C!,549"4UQ&62]&/49> M7%)`4TX].T9,3R\B,U4M*5!$14<_5#-".BDP7UE%)`I-7358,C<Z*2]%*$<Z M,U,\1"H_-$-&33(]-2\Q-B5(6%E:/45,.F`J72(P350R/#LI.D-$7#Y:0T4K M*4\G"DTD6%!$,UY#,S`_)D9=)5)!+2\B)%M$7CY`)"M)6B%174A'.#0R3BDQ M+5TP6%U2+CHM8%E!."@X1D$K-"D*32TG+R)$35`L*5LM45A$6UY2(TQ=5E@U M+$==)S)#8%LL)UI(65U>,RY1)3XA)%A9(E0T5RHD65-(,S9@*0I-+2\A)D!% M*%U*3SQ<-E(]14A#.F`S0BLP+U)+6EHN,48D*4DH5%]`,$DY3&`L1RY$8%`V M,$,Q,3L[3$!2"DTZ1#HM.5A87$11*%,U,#DM6D!%)U$V0#TG.C8_-2DP2C12 M/SDR/D=(*CY6/T=*55%+12DS8#1`)2HT-B0*34<[(S0Y75HD648P6TA61DY- M*2\\5$A/3E%<56`H,B=))%DF1$1;,4Q03$(\3C)))UD[7CQ'1$140"U;,0I- M-$E)+#!>1$DU.2DM)$E>-E1&)#DN)EXB)U,T-38I,C8C32I"*C-")TE&0UQ% M65@M,D<I,S<O1B8[2"I."DTC*CPU.B,N+"Q!3$`H1T5)(U\V12)5+BT[12-( M7%,X(4HA4S5(7#TT12([,RDU1S1<3D1273!$62@E6D4*354I/2E@7$Q@,UI" M1D%7,C`K3%<O7C,S.2E+1SI)0U`A-T=),R9`(2@I/DA(3%$\4#4D)CHT5S(Z M,TM?1@I-+D!60B0M+30H1%4M4D0S2THS6$5*-$Q263TG*$HD23(T7DDB.%I$ M5%`J-RY@*DY*5"LC)2I55CY`-2U6"DTC2S%<43-(.UHM4RQ'(T%5*3Y!-"XW M1#(R(C`Y2SHC2$TG5UXT3C)9-#@^22)--C\T)2HE0T4Q,SI%*5D*34!%,T5) M6B0M2E9+-44[23)8.C4A13E65#Q765Y4*S@Y*RD^1#!'-DQ-5RI",TQ*03)% M,D59/C0D+DDH4@I-0B<Y*SQ(12E66CA<-3HI5RTJ,SHT52(J-$@U(C53-",R M5RI01DTY43TR3%LZ)4`](T8N-3]*2RY//3HE"DTV)C4Z-3I!)412*3XS2$Y: M+TXU2C%`5D8R3S5-0$U@0UI%0B]:,C\]2E<U,DDS.RM%3TDR13I--RLX4S@* M35A&/R932T=),40M2"0Y5CM'2RDH/T4K)SY.7$@H0%(P1R]644Q%238]-TA# M4%8R6#LE0D-$1D0Z5#M/.@I--2E-2B=$5DXU730L+"T^34Y%2C]:53XM1SLB M-4Y,239@,TD[7%(Y/#0Y020T2B0N,SU5*C`Z-D4A/S9!"DU:1S)..D4Q,R(R M2#-:7DA$24=`55!!*S99.4DU1E9-0#LZ5#1$.CA.53XE8"\V-$M:45)`0CLI M.RQ+7#X*35HU03\Y6#@E2U,I,T\E.RI254D^1SQ=63DY-TI-.$,J5B)%*F!; M1TI.)"I-)3DZ7C=--S8Z0S(W.48J/0I-3#\U4T`I234F0V!(.EXV55LI)51< M5U%>,SU9*B\N-4HY339()2TO(59,5"]*4TA'2R8B54PH-%4L-#DW"DTC.DU! M25Y3/B<J(4`U2U\N0"$A6RLX5$Q<6$X^,D<Z4EQ%8#4B4BA/2E-=54PQ+%-/ M/#DX3$!(6C8Z/BT*34\[*%I-2D]25B@J*C=?3D8A7S9`/24Z7T5--E8R,#M@ M0BE$14=40C(V,#LO*3!--RDZ1C,A.CE;0$PG3@I-0C(K62PG)6!06%(U-44Z M7EE%0$LR5"]353<E541#/R$Q+TLJ+TY$2#!64"E20"9&/4!20#9.33,Z8$9% M"DU*5%4F.3$[63<L3#Q>0RE7.B=!14Q5.S)3-CDV+$\A0E1:-EDM*3=+3$M; M0C8M-EHX7CY$.50V0E$_-2<*32Q+741:,T]5*3Q-1$U(059*/41@/R)%2U%6 M/DPS.S-?/$L\5E9%6CHX*5Q,.5PV."4C+S@A13DM4E%=2PI-.RM04DLC3"%0 M0TDS)D5'-$@N5D@I)C1+)%U80E9&,5DK*3U-3S0V.4Q-.SY'3$!"6C,I,4LO M2R1-,54R"DU564LW+BU-+C=:-E!'.ETV73A%+#(Q2U@U.#PC,U`B03TE,SE8 M14U92E,W*4E;+55-1U<Q5DA85CI'3$(*34A65EU1.S@S12TD.E8K0SH[/S]$ M.BU.5RE?/3HY14HD/E98,U!$245(6$!4.TU)+24A24HV6C(J3RM%)0I-(S0Z M2C(I5CL\52U$0T@R-",M/"PX*$PD6D5!2UDH4BQ&5D16,E4I-D!@3$$A.EE& M33LR/4Q6)"E64C99"DTG7$Q@(STR4TU3*$$N+3DH.C1)6SDK)SQ&/V!3-45; M.DQ@355.,C<Y)SM/,"P^2BXW-6`I*%LM34`\-C0*32%=.4`W13I*1EA05%E, M2T5*/%DU/#);/$$[2#E+)DU10SI+345&-EY663!).U`_3UXN,C=<7SL^5$U. M*0I--E8Y)U8Z4C5(*S4V-%)9/4E.3$`].E<P(R97444^-BI-63\[/$L]3#TL M5E!'53U))4TI3%I#,2E;7D!5"DU**3PW14Q+,E193%0R5E\H33E%+$U'*3XS M15HY/59%0$X\-EM=33<X6D4^)BE#/E5)7DTU1DPC5U=@.S\*350^3"U).DU: M(SHA(RQ%*S)0+5=+/48_3UDJ-EQ=5R=66DP\6RY64CLJ7",L1%-"-D%#6SQ& M-&!44%I)6@I-23I84BU66RXA+2I9,SLT2S-#5CU813]<2T5-33HW5RQ+0"M( M1%Y05S5`22E64D5=-%Y3*#T[,45<7EI*"DU53CU*.30W1TY-5EI87S];/4U< M62I8(E$J/SP\.B<N-#%#*E\T,DU6)E<C.3L[7#`V+E-*0C%022E1/DT*34]8 M5D14(S]:*$132CI73U=8735%2S5$-R%",S1-*TA#-3I:2RTI-U!-4"1?52$Q M3#H_+41?)5<A*T5`)0I-3UY@.2<B3S\[4%%.4#!<52Y%*4!>3TU6*E8W/"LZ M2C,T3UTZ-BM62SHV745=+E(Q+%\K1$Q,26!.,U%6"DTY.B55+T4W4R(R/RI/ M.F!(2E,B2T$L*3@^)21.4D0B*4$P3D531B8X74(H+$`N)$\W(D,A(B%`5E!6 M(40*32%732,M-TU++%M@)DE)*39-4#HN2EDU*CLC/"-94C8Z22,M6EE&)$<^ M,BY7*2LJ1$553#,D)4T\42)-30I-35)&2R\K,B@N+5Y.*E0V7"DZ7$4\-RY< M*B$K2#$F*CXV6"5!6ULZ74HE1S)23EL_*RE-56`W8#PU.D%@"DTT1#<V,DPM M2RM@3T]16C970B\Y*3A,4R9"5RA!+#Q)5%$R.U(V3BD\)5-&*RH_)BQ9+"4T M7$]&6E@_/#@*34$N+#4F6U93*#U`04E%7EHB-R4Y4$A>7$0S8%(F/UT\.212 M(48S)"5722<Z73E.,E(G4CLR2TY/0U-78`I-+TLZ(39.+CHN03%2.TA;)%$V M7U5?1RD[+BU2+ELG(RM;/#-?/5U7(E(F(RDX+3U(+EU:2%@W.3Q91$]&"DU- M6$HW6S)"*U%13%-/,TLM/EX].%`Z5%Q+24$F750Z(EA05DE"5SU1/E!3)T%- M-BA:3B8G4E@_.5LR*#X*35$H/E=6,2E".E]-42=272\C.3HL)B$Y+S4A,TD^ M)5Q$7%=/)"U#*29@255%+RDH2RP\*BQ/.3,S.4,J5`I-141%+$5>75%/,$1' M/5$P7U991CP^+$='42<V-4,M/#XH745:,RA,0UPR4DY1,RA2*BTO*#D[4$,[ M7R0Z"DTU2TE+54(C+U%62RDM(R=+,$A:0S(]*21<1$XL+EDT*3PT-EY20%U9 M,E%+0C@J1C$N6RHI4RE06RU20%<*34];(3Q$23=14UU6,6!912I43%`_0R9@ M55DT2UY)+#)4,BU9/%DC+5@S6R4]74M"3R8N-$I823,K1#4U40I-3TLR64`E M1$0A7C%5,3DP(SQ%)5911&!2*S-?,C]:3C1&5EHV(2E*(RTC*5LU5EQ(1C%6 M.SD[.CU&*412"DTZ7CLK3RE$4RQ6/UY3*5A9+2<_1E0_4CE-4D%(*4Q65D16 M62Y23$LI14E-3%\W5RU,(T1635XG-E<I0#\*34DF4EY3-E-8+3A--U9)4#T\ M.RU/7TQ78#8T,CI4739<.$@N4SPS6RY@5RA8*%8^52,A7S=85RE>4TTC60I- M+B)-1UE'4$4J-C!0*4H_)BXQ02<Y4#!91SL\4T$_,C!30T4A.$8\(2XY64,\ M5T=64TY`62XU3T):1E!`"DU35RXE52Q88#Q#4S\R3UPH1UQ68#Y16D=",21? M/UT_7CXI7U5(5TXV4U!&(2](/T!?/4(]6%\N8"U-(UL*358S6T<Y4#)-1U]- M4T`P,R]:3R5@+D9`*2<Z8#DM)UT^5"]342]5/T@C*U9!73LN8"M(4#\N1"%* M.B$A70I-2#$M5$(F6R\G.TDD/UY`,3,Z8#L]*$DV5"([.C`F*2HB059#*3HR M(SE-)#9&1"\W.B%372=71U1"/3LQ"DTH3TDE6EX\(D,R(5U-*$A>5$-5.C)@ M72@B*50^.C\R)4\M)$\F1$M/6B)!+4DV3E1!5#LR+U])*BE>1TL*32\J)#$] M)U<V5$-<6CE$24DA,T9#-#LR-25,72HF1#E'.C)334=:3U1&0#LR.R%)+E)> M1%=#,B8]/2A8)@I-5%<E6C,B/2@I2%0^)38R-S5-+5$F1%PC6D)774E(5%1# M(SLT7%-%,$U>1%,O.D`I22E;-E0S43HS)BU("DTP-%1`4ELR+5E-*BY>1&`S M6D-.74HN1U1(0#LP0R-),2U>22XO,B-+3%-&-51**#HU*T](-"M603$S-CD* M33M,6#$N0U=?64-<34I<5U1`.3,T0R](6R5>/3I#,V`_+3=@1E1$7%HS,#]) M-R-405X_,5E9+38W7%1,0PI-6E\\3$LO3$-+0CLN33-%.C)5*SXK*E95*%LV M3E5-05HE55]+.RQ6348^6E9;33LR7#5.(UI7)BTS3#15"DU.,ULW42TM/$!> M3C5%32A>0%)3-2=(/C$J7"@H+5%@-2186"M`(R%06"U#65$Y.&`F(45`(5(Q M+RA2/"@*33TI.$M@.2A:0BDP0$!;020A)"$F341`+BLQ431/)"=6)D5<(TXS M6D)#*"@U.EE`5$A40CY?*TU35B%35`I-+3M"6D`V25$A)$I72CA!3TI.*34E M)U0B2U([(DXP3B%#3DLB-B0I5T4P*C<Z)E`K15`G1S911C`B4E0G"DU30T0A M3SXG7UXH*T(T)E5=+"Q#23I27E0D.C8[,B9*(3Y&+"Y-*SXX6#4U.C(^4E@M M3S5!6RA&+4%;*T,*34\H055.(E9`)"D^)%`V/D=74DA62DM'.#A2."]>(U)= M5#@A*%)12#@Q.T,P(R\Q(RQ:(D\W-58Z)%A#10I-8%\Z62XK6V!?5S`C2SY, M,SY>-4!;4B])64`R2C`A+4A@-%%`+D%0-D9./C@G)2E53E@_(DI<6"U/.3@C M"DU,5CQ!5R%96#=,7T`W."1$4&`R.$`K63XZ04\Q(C-0(2I#8$E:1B1*.2T_ M+E$U5S,L239&5C)2)SXU8&`*32\X+CXK,$,H0BQ=1C@[35XG72<L+R5@(2,W M)B)8244Y1&!9)B-33B1,6SM`7"4Z.UM$3")/)EPL2"@X-0I-,&!944=>7T8H M6U,J*R$C3U=,5SHW+4]0(4`E/RLZ4B%$-C=&4SI!)#9>8"U(0R5615@E22U! M7TI`4S<C"DTD34LO72I7*#]8.#`_24595BU723`S7C1,42E04T<H)#0A+2E2 M0E(Z3#,L(U@\6BHV,U-3.B5!8#T]3%,*32LI+R]18$%-6C8_04Y4/5E(,5-` M-B,]0SE7,4@B4E9"*#<B*"E#4$961BY<*$HA+"A6*%1@5ULP-2E%1`I-.V!: M34LI-STF540V*T0Z5UHH.BQ*+%58,%-31%L_358T/R([.B%'3UXI5R97*3M< M6$U)2$LF3B$Y1D$X"DTO6$0Q7$A3.R,M/B8^0"1563-&23%--2PH5EDS2C,K M8$E'5#%$4S)$)4(M1ULF1$4P*2Y%+%-76%`B/#`*33I&,4HQ-E5!.#LV34Y$ M55160#E9*#PZ1SH_(U!%7SLD*CT]-3!6230G(C]<(STO)D8[.4)=/2PZ55I< M*`I-6$,P35-++"@V5$Y@+TU23U%%1V`N+D->4D`_.EA8(BLZ1R8H,"]!1U@R M.R,\46`[0#=/,B(H)$`H-#A&"DTA4$%4(T(R,%XM(B$E0F!((UA.)$`X.B-+ M4D963CM'74X]7EA675(H2U%@)S5!3T]922%.1S@U4S<G+4`*32,P4BXS/R90 M4UQ@1D\G7EA!(5\B3C@X73$C*T!*,DQ,/C(C-S\P-F!`/#XQ1TQ01C,O2S$T M1T`T/UA7*@I-8#U5-D\P)$XH*31:34LZ)6!14D$F4$M&+40B5$@P,D!6+3<^ M3B1'.$(O3B@I+SA;(5-`6#9/.24Z0%H_"DU>4#4D.UDH(C%$2%A<*2U-*BM2 M5DHW(BY97R4\+B\I43]"-R]+0$8M.RM#7$9@0%8G*"DS/E%,.E`W054*358K M2#\B1T`I7B-2/UI7+C(H(4`]2$M#(CI/0$LI6$(E-EM$.296+#-#6%`_(S@N M)TTL2#A40EM#/RTJ+`I-,4]28"A1.CPP(5$T5#%"3R5%03Q'1T0H4B-@)4E` M(4U`.%`P2EI6/"1=+TU$02(H2E\A,T@R,3`F,E97"DU`0#M&4"@P2C-,(4)) M,5Q!15Y86C8K22LG54I4+R%!64LI33145CQ:(S%,6%Q<4D<[5"0N0%PD0B4Q M3$<*33DC7CTZ+49-)C8Z7C=%03%154<B.$,Y-4M3.CXA4#`Y-3D]+4DB038T M*5=$,2P[-D,U5%DS05E"2E4N*0I-7B0S)5%+2%LA(R(J.R9!)4PT3"$Q*$,C M6$]*+#@B13(O*%\T6#E;0"142C`I52I)+5<Z344^-#Q.43PJ"DTD7D]@,2PB M6"9;,C4K.D!:.$<D2T-0+BPX(ELD,T):6B,Q1#@F)#HG3#!,+2TX(30\*$4N M2EA123@T8#0*32(_7$,M2SM@4%)+3")4*T=&*2]*7$-=*D,T/R%745)=+EPD M*#11+RDT)TTV)"0_-3A+-5LE+2TN(5PI,PI-."-'.$M,*CPK.5\W5"%=1E$I M5#@U)3Q!*E92)4M/8#503"DX8&`D/%<P0#A=5EHF)4TR(CLD8"U*0B14"DU# M8#@P*"M@/S!&4"DQ44@B1S<P)C0H,RI=63E,2&!65F`S/T@A2T=!)E<Q8#-- M8"$M*RA8)R@_1$PA4$X*32,U5F`C2SY;35]<)UTC5RY6*"]9,4$B*5DS5R1! M7EE-)UA!+#9103(E(51&5")/-%@B)DA4.C5#)%5'0@I-1BDF(3-.+SM(/"Q. M4E$F,D$H3UU"(F!1*2,[-2DR*%DS*BA<+S!$8#@R.D9!)T90)$95(C)7(BDR M)D--"DU1)#!!0D$H/B='.B-`8"]/)D4R)$988#,]-#(Q6%!$75`R/UPA)BPH M)2@N0C0F050K)&!+)$DN1$`N15L*32,E0TQ=+%`T53LL6D,V1#0O2UI+6ELF M5&!"2BI?*2,O+%1:7CI',"T_5R1-3$@W,$(T64PA/TI!/#HO(0I-*T`A-T]& M(21=4BD_,R=&,$`Z-"8T7"90)SY%*3]*5"P_3B15.24^45(Q0C@Z3%!+0SXB M13A#8#,I22=3"DU?5BI%4R,S7S4C)T15+%]()E,F/$<Q7"U%1"=%(3A+,THD M4E-*6#4Y0S<]7E!;1"9(,C]3-3Q(4$4P524*34=4-%A?+4\X)S]32R0R.5E1 M4R5%0RQ;03XA4BHP5D,L44M$(5I*1RQ9*D`\15@N72HI(4LQ5$0J,CY$6`I- M)S4[150A,#%.2S98-6!)+%0Q55$G-3Q@)3!%12\M2UH_34@[4T(O*3%72TI( M.490(5];*EU@2TI&6E`O"DU<-B4S1D!40C8Q7E$R/25333(P53972"@P.V!- M0D`P*RPI*U\X-"%&,V!)05TX,20](4`R73\I/$DK5R0*33XB)#]9+4HK1"1) M3S!+45TH8"=7138S/$]1(S(O1"XN7R]08"8R629.16`W(2HM2CDG5D)",594 M)TA$*`I-24,Z,C<Z238E*T4I-2@R6DPG3"(\3D)/5$$B/U9/1CY7)5PP+3,K M4%]8/S!<,R4C45A:7$M(7U)/2B(F"DU6*$!$1THO-4)?3S)(-BI27SLY1S\_ M1SY7,5Y8/B5<6E@I+"=%4R8T5T0N8"1$8$4Q24I"32(H,DL\,C0*35Q1*3DH M23E.,C);*5XZ7R0O+#(R.D\]*T1,-CTD,CM0(CQ.7R)&,D)6.4,I5T]`238X M2S<D6317544G)`I-04A$*BHU.D5*.2(T-D<Q,B(A5R(X(D4V23<N*4HC1U8T M1$,^55`\25Y",TQ%4UQ%,31<(B)-+#`\(S)%"DTS(512+U5<53$M.%D\/TI( M0EHH+"E*1B\L+EDM53]<2#4P-5HZ)U8K.#DW3B=,*S!<6"=?1EM`-$U073,* M35@C63=$/T\M24I?3$4C3F!=4CXJ2SA'6C=*2CI%*S)?/U\T35]?/#A?)EY> M1RHR-$Q97UA/7#]"+UA#/0I-*UY85UY;,2)=744J-CU$(SDT-4\G*RI:2$4X M-$\U32$L1$X^749>-D]<*3<E*U5#5C).(3$R,CDC12Q%"DU46#DT3ELG73`X M5U<Q43A>,25$1C8U6D@Y*4LE75XM2UDY*R8Q*$Y40$5,.%]42$E%73PR-EI# M74]%/U<*35(F-UHC6$\]1$HP1"]'(E%=5"(B3B@A5#],74)&+$]+04);65]& M(5Q?42-2+U50+5`S7$)67C<A,2E#3PI-7$\C)T)?0#\T,SPI/D$G44\W4DU7 M6%DG.#Q@-RQ,,T\X15]$(E)7*21<+3]!(S$O5T=%(3@N,5LM1#@B"DU0+E\Y M/U1/)"0^)4!0(3!,,4=-,3A%4#@H/%0F)5TH4",S/RU13V`A3$-81U%"3D,X M2V`X*58A3$!&.UP*32,A-$!#0"4S6B%"7T=<+D8Y/E!#+$`R,E0]+ETE-R4E M)R@D)RLA1%I!2"$S.31`.4!$+C9<-BTX)C0V)0I-/%,L)#Q!1D@W1D9'.3@P M.44L0RTT)CA()CY9/D9+)EI9-TU,04E-45$Z(5\B0$0V,B8^6"8\1C%'2R0V M"DU58%]`4BE<,2Q<8%9!-#@^,$L\0"9-4B(G72E(6R,Y43,Z,#%33R1$14@X M.D%95#@J0R<B25$E2DPC3"<*36!65#=++U!8/5PR3U56230_*R,F1T8^1%0A M2391.E=!3UXP*TY$.D8I7E,A)2],*T=4/U@D,D,T,%](0`I-4$A`+4Q173A( M/D$E)ETM)DTR)4\X(4Q!,5TW8#L\,%%8+#A!-%<C/"9>/28U5V`G12@J73!+ M3%$\.$!;"DU<0#I=7#)'."92-"U'.RLA)2%37T%,*B%8*#(B.RPW(3@T5TA` M02DG53XA4$!@.4Q@+$$Q/"U`3#$\-$X*328C/EPF.3Q`-4X]458A*R9(+$(Q M*28A6%4X0$9$1RM((D%**5)7)T%1,5(_,C5:0CQ=,"5'6$0[)$<S7`I-/E%% M/U0Y)$TH(54O4UTK43U0,"%%-#PP-"@Y2"<T)6!97R55)"(F02%=13$G65`] M*4!`*C1`,E@G.%$G"DU9-20D3R@M6#%616`C6S@^/T@\)"Q'030G2#$G)3<I M6"E@)3LB+B]!/B-`(5Q*(T0X,2$Z)TDW)UDZ)#`*34I!6CPQ43E"/CI`034\ M(T@T-TA4(E`C05I#)#`H0#I/05$S,EPL0#Y-+#Q;/#=/1"L[4B=;4"5<,B%7 M(@I-45E34&`Q1#]2*#]20#(N."1-62@[4"%=,B%?-$%?-3$O3C`I5C0\3BA= M.E!@/DPH7B$F8$0A7TY17T4A"DTD/%0_6E`],D(G7%0T(BHX8$4I7RXH-T\A M5%!@6"DP1U1,.#Q8)UQ8(SA"(2$M,F!@(DPE0F`Q5$`B,$`*35TD/%M<030R M*"Q?(5I<8"]/0%@V,B1"6$`W0#TG0$`H8$@F5"A",2@O3$$J22)@,U@P2#(] M.T!`*#XD+`I-*$$_3B@C02A/22E<7"(A,D)@7")!)5(D-DP\,%Q!/#XH-$4H M65TF)"DA7SM15#`X030P/2%$/2A"*#50"DTH8#LG)4<J)C\B)4%2)#XX-5(B M)E]@,#HT0#Y(*#91*#@\02<J,B%24B%),D%=4$%!3#@Z3B@_5"@P)C\*33-6 M*B]#(CA6(5@R,EI41"I"3$$M8#XX62A#)B-',CXI0B%'(R%/2E`C-CA"06!` M."U@55)`6S%!/"TP-0I-3F`F0R(B6B(A.5!",UA%25TY4C`B/UTK*RXH05,B M*#4P7D(W53PT14]<74DA74X\/3Q0(C8U+BPG(B\I"DU"+DHS0T-00S$X6%1@ M24DP0%E<*2U(*#TZ(BU/4$$P,$1:8$4W.$0E.#A;4"A6(B0N1R@V53%?-D)@ M+E0*34)20"Y,6B152BQ/2"A<*BLQ,2HP7&!48#(T64@M46!$(4!%(BA+4V`I M8%(I)4\P.3,R,SM")#8B3#DE8`I-33@P/%`I)5@\45HE4S<Z5$0R,U-!3%@P M1UDP5")412Y68")>*2(Q0C,O*EU!*"9,(CLK0$1>0$1.0$!8"DU823M8*R19 M*5XS(C1.(B4W03<Z.$4I,5D[,#$S4$$_-$(E(BDH/$(Y-"(U.U=5)5)%/4`A M-C!%+#`Q7DH*32DW*6!-5F`[74=11%(U35(T4E(I621",RHE(E0I-C0I(D`O M.SXB.RDH-5DR3$=6(R\D/5):*3XP(2=-8`I-."LH26`A-S)22R1155=4+T)4 M14-<24-,8#L[02%8+TA5,CDL1T9@)R<F2"PB.")*-#D\*$(N3$$\3$!'"DU% M0CM*1V!/5ULC5$(]1#8K/B5:,"$J7"DB(2([,2=%26!95UA&04!-3#DE3SQ) M4V`Q2UTQ/#`S1$HQ-C,*34A&731'/T!&(ETU5#HG+4`^-$0_23M`245!55=( M8$LC1S=`1UM@*5@T24-,,"H^)5I?(C]((C]$2"=+0@I-6%LT1T-$*3I!7UHL M*C\Y*44L*#M2(2TE4DLB42LP8$A-5BHN4B\U)24T7RL[6R4P.6!=-C$^/R=( M-&!("DU-,"I.-#HF)"HF(SY62SY!4"$L,E)(/4)(.$!(33A.4B(D7F`J-C\J M5U`I,T\B05`B2B9(4R10-R@I544*35E@.SPJ(4L\4%T\6",C)B8G.&!'+5=@ M+U156#\P,&!:*C4A*DPL0TLT,D1043-=44DT0$TJ0$HW*$4C0`I-)DU20D]1 M0EQ%(D8C,%E#,DA,4$\S8$P^4"HZ-")&6RHF4")'0&`\)5@N3V`A3#(B.EU6 M/51),40I5E]@"DU43"I'1R<P4E=97$(R0$!*021+*D1,,DPJ1B$K22(J5E(D M-SA8*C5"2SA"+%,Y)E$T0RDZ*RLE*DM4*UP*32,R35Q'/$\X2D5@3"E.+R4L M2DX\(5LT*DDX*DM5(R9#5R%7,TI?4$I375\L4B,K-D,I6BHD*"),(V`G*@I- M(DLL4EE#4$LP5")43$)((B0W8"M)2BA@.D)//$)+/$(E+#`M+RTF+#A:6#PA M7B8J3DPJ3DY@(TY"2U@B"DU1+%1+(CQ.741*7B0J4$(K3U`J4#8B7",R444P M3"9@)R%43E](2V!0*V!8*U$J*3PS(E!.4EPU0D9&0$P*34U$2R<H250D0"-* M*S4O+S0V,5$G2%I)0BQ?.BTL8$\Y)$I$,"M&+"M1/R=@)B,D0%)1.4<D+T!, M,"@Q,PI--5Q#-"PI,$,\6#!4*T,E+2)313@K*E@\)BHB,&!9)#@_-B=`53DJ M54HB6BDX72LR3$@P32TX3T1>(T(^"DTK.C4B5D0J.$HA*4Q"74\R,5Q@34\P M3C4L*SY4(T,V(5<]*"18(E8T0#U80B0N8$XO.BY7)B,L)"M"-RT*35@G*E$F M(ELS8%XH,BHR0$Y-/"TM)#M*7"A9*BM7)2)9*B=-6%`F*2<O)D!.2%`K1TQ/ M.DDF2F`K6E`J60I-,2,K-4A$7$$I*R@A2EA/2#Q*35Q"44\_0$)"6U0B63<R M7BU2+RXX3B].+E=2*TQ,*S!)0"DH+DDE(E\V"DU@3RA"(5)`3R1%(U-(0UTV M*UTC*R%=,SHW,EXO)SM20$\P4"LZ65=78$1@,"I#.BLG5"\A.V!32%);7E@* M32(F6"I;/$]:6BHV2"9/+2M@+2PJ8$%')R=-5D!/5T(P(512.BA$*%8C8"XL M6TI`.R8C8#M)8$I)4"Y00PI-,RU71#HN75$C(20L7C8J7E<A3B=(4#HS,#PJ M,"182CP^)"$\0$A4(R(Q+DDU*%%9,DPZ6$E=,5XM5C-%"DTV)"X^*R1<1%-* M*4E7(R(V.%4U5U4U)BXO2%%@8"PP*"PS7RHC3"Q-)2)6/DA>*DA-+4!),"0P M,UA0(U8*32)!)T0E)RTD-4,D7%<Q.S@T+6!&04XJ8"0R35`L.%4L)B(L)T,C M)C<H2D%044%`-E4]7#H\7RY!0$<G+`I-)V`O358S)RY15SHQ7EU4-"4Z,"Y> M/&`D+$E)0S1$/UM:-UHJ4R%3*5(G4%$]3C`X6%M0,$,W7T`F1R,I"DTA*&!> M(S(^4R@M,"@J(59`8$T[13M4*3TG0T4J5D<Q/R)"2BE46"8G0%HO6TQ@+E8] M)$0](D@M*B-'-U\*33`P7SDR+UA1,E%5,E5=,#E#24Q#-2L\3%PB631'-3=' M,3%()%-"(4TT0TU>+$$Y/#!'/2I!(S`Z-R1'(PI-4#HT+2$F8$<Z,RU,)U!> M/B9:(RXM(U(Z,$5(-"%-4"%,*5<X6"@Y1")632M.)&`E.2DO.3<S/RDJ22A' M"DTS0"@]7&`W/#U(/24L-"@R2&`C0E0C0EDJ-6!8+B@^-%!@-3PT6R\H04P\ M24PI+TDP,$]`,UPH)TE8.5<*33!47T(F7SA$+T='03HA+CQ((T51.4U`35H^ M,#<L+$DM1")<(2)/(3`Y1S@B23\C(C-+."<O-&`O2"9)1`I-16`U)#5(0B1& M)S)<,E-+.3=80%0G4#DC1C$]7&`]-B(]7BTN/D`P2%`K53%4)E1$)U$D3C`Z M+E0A/T9$"DTM0B4R04$D0E@D0R,T,CHT)U8U*%56)BQ%+%Y$6EY@-6`I-#`H M(R(Y*#$B-2E452@^,#A`13(T15M0*5P*32PI-U]1-2A7(4PP8#LX(S@D)3)6 M)38N8",E(35$23$Q*3-@62%,4&`V7C4U*C9',&`F)44T,T<U0S`D50I-,"5& M.34I6C4M2"$Z5C4R/D4S/F`V744U-4)?5&`U,4DW7V!.*CHU/#XU/38K72\A M,U9%-49)-U%2/#)("DTU6#E46BQ`.2@H55Q@-SE%,BL\)"$P65(S+R$X3D)2 M-ETH)#PH740Q(2U`*T\D(B(H8%E.0"%*,%HT8$P*340F-49*/%Q,(BA<(SDT M/CX]*3E#8&`J0T=)(C9&7"E$2CU#)2E124)!3&`F.RDT.S<F.B<N)R%60DXT M/PI-*5`_6"-80B57.R@D5C!>6"DS0BDU7$@A5#`Y+C8]*"1%5BHC5SXJ*UI@ M-D@C(E8I)S$B-R@]5"TP,5TH"DTC3C4C/$4Q.R%`6#-!*6!2-STH)RXZ)4\V M.U5414$O)#E*13LX23HM4U0B1#<[*C9`-"Y>-#L_4"M/.R,*33Q<1"8Q*3\B M,29522]5,C=./C5/.C-=1$5>6T4B/2D]44D_.RDW(5E`2#(W7B(U2SHS7CA% M6%E%/T9$7PI--2$A.S-77%D_6#`H*2Q85EXY(20I(UE%0BHA/DQ)/CA!+54B M(5@P*%TE7"%4-5DJ1B$Q1C9&(R0V.4`Q"DU91EQ9.#18535.*5@^-45>1B\S M13U?14%723Q"64$K5#@_*C<J-CD^)"(H8$8K-T5!744[+4E!)#@X*$D*35%< M(54F(CDQ7B8A4D8B+"Y;4RE!)$@T-4E',CDX6T@A6SQ6)BHV,5I&)T!@-#!! M/TU)0%])04TP.$(J.0I-,DX[3#@V(DI&)$5&73(E33,I1$XI120H.%E*.#4^ M.BPZ.ST\)E0T(D!28"(G.44S-S@Z,%X\8"LV4"-6"DU=2V`X15XZ)%]5(STF M*4-&0$9`)RM9(CE/+$`I)$8Q/D8D.D4G)R%'/4E#-4)?53`Y)BDF+RXY*T4F M/UX*348_+2E(+D4^64`U5$`Q42,Y55HV4D0V0CHV0SHK/%PA.S(E0D=`/C(Y M1R\I)C@E5"A".DHT)D=*14$L0PI-24%',E(Q(CY)2#-)+UI@0D5555%1)2,V M/4Q0)S$D1#))*6`\0D$C63`P*#$G*$A<+#`_)&`W1R%&/"1("DU.0%D]0#A6 M.31*2CHG1"4_*C(N*",S1T5!5R4S+RDU05$E(BDT4UE<)DE1/THU4CHM(5XF M220E-6!)3R@*35E$*C=@1C@X34XX3S8[5&`C/4<]2TM%,D1$)4)0)$$Y-5@X M,2U,2F!0)E-**BQ)1DPO13\N*4Y0.3LQ*0I-)C16.UTT-E56-R=0*TU#1BU# M13([24\F*44Y455-5#0[1%T^+5-+*B8L/S%.5T5-3D`D1$<[.UE%62$A"DT^ M-C1<+59;7D!@0R1+,$1$8"E1-%!+4%D\+"@A,E8T.$0S)RPA-U`A3TY%(5M) M3TY)13(G.E(J.DXL,E8*33(U5"@C4$PB1S<K.$`Y.BTW-C99*TA9/UA1/#%@ M5#PH+BHT/BI0*3]&)UPY.51!)UA)8"$D4#`Y,"$S4@I-1D$H)#)@/5)02"M3 M44Q"225),CPC,C-18%$M7#U#)BM'*D52*T!03%E9,T$\23@Q(28C(CHV54Y' M(S='"DU3/D516DE044)<0"E63U8\*"@S*3H]0$5'-#=`5$-%)"TI5UU)3#@Y M25Q",U9",%=.,DM20TL^12(C)5`*35Q'3")33U]26C)&/3-@+D=55S52+"\B M(DHD/THJ.54L2"D\,3Q4*CHY0")6+5<A2B0O-B(V5SU@3D!92`I-8"%(0#XB M6B]/+$P]/&`\/$=/-2E=.2@G66`G+5!>(UE@3F`A/B0C1$(W038K63!'.U0A M655`,BI)6%PX"DU40U8^3RPG0S8Q+#1'25I'/DPK3SLY6$!`+D!9+5`R/E\H M6T%"-4`T(R-#1S);8%PC*5,_4EPC621`0#4*34TF/#Q>,$)!1TI)1UE)15HP M25I+*5%&0"\E0#U"3"Q2.B=.,B%@/R4R6"%@)"DF7CE>7BDA6#(^(50G4`I- M+C=16BDQ7R5-3T0R*2E>*"A#3D([*$`M4S8_5%(W329'44HB7"Y%)C0I7R99 M4UHG/S=()%)2/C-,(4I@"DU@+5Y'645%65])6%5@7DPY7E4V/U%:/2<\)UA* M0DU+1UY)15=202%;*5Y>0C=?.#$T7C]?,4<M1$91528*35DO(5]&23]044PS M.#Q:.C=`7"E:)C=.,B$K3T4B.2@S,4HA3%`G52E`/RHW-#HR(T@G4%Y((5@A M(3!)/PI--$<V64E:-T$Y7BHV54(]*4`N1R%"6S@E(3A).TA()F!!259).#`J M.BDV0%Y%4B=8(U\Y(U\X15]12B-8"DU'*CE@0%E80"U&0#8D4"%.2"-!2$\H M0%-(8%P[2BHT(3U"2CQ-3C<K)C@C4BQ0+T@M2T5+/4DX*#HL0DD*34`L.$-' M.C5$,C<I1D<T)$<Z0493*2<X,$%`)#HN)D(V-E)"62@E2D(E2E1%6"LA-3A' M."U01CDW65PR.0I-(4!*7$`H+SXD)CU&2ETA1D%`.UHT/2<Y04@Z0"5*-55@ M15522"582#U"1C`\*3TR.48^*4`^2C(L5$]."DU"."PB2$U4(B(E2B1<1S!' M2BDF,CU"*#<C*CU97"@R2D)3/21!-T8H5DDX2SHH44@P)SA0)C`J048Y7U`* M34@R7R$C(D@P5R$B.EDC63<^7EE3*U@D+BY(248B*C9(+TX^(TU".6!*8%8Z M-TU2/TM20$8\.#!>1S%*)`I-/T4S7BLZ)$\T,2U:(5-202%:0"(V1S4N2#U) M+5@K(B<W2BM363%?6C]52D!?7CQ`(DPL1#TX.D@C/DHA"DTV2$8J.B\Y23HP M(C=-3#0H)D0X0$A2/2@I1$M1)B(Y1TA@3RHH+")`+49`2%Y(0S9(*CA(*B1( M,DHJ*2$*350U,T)"3#HQ5#Y`7E%53S!(2TM'*SY)3TY`6V`Y-TLA0ELX*D]" M0%`V15@J2%!%2"LM0B<D245!*B$Y.@I-5D8F-DDV-2%&2%(P/$E`128C23E# M2B0F.B4U24%!2CQ'*55&45M63$@V+2XF7$HG4$HF0U<Y1TDY33I!"DT[2#8\ M0C@]+D%</D@M*$DY,THB."DS+#HN(T)#058L7$I,7$%(1#]'1TLN*$Y)*S@J M8"1!)U`R/"$^02T*35!823A(0CM)(SXF+3U(/T`J+$I'.5M:0$$R."XZ2%HN M1DI12"-:2BY=24H]43))2E(Z,D--5$1,3DQ?+0I-2$0R2"T\2S-6.BPZ.5DN M42%#4D([3D-@1C9,,D@M6"TU5TD[,2HH,D!6+T0]+5I#.%(\64XT5CI$6U!# M"DTG(6`C,F!(0DE%34HW,RHT+$`A/%Y&1RI@)RQ)+"Q$.5@Y4S11-3]*02XZ M1%`B-D)*-CPZ2"A71C@N234*35@J(T4R,%,P*S(Q62,N-3L^04\^23A-24Q& M0352(2U4*C-=034R,5M74"U%-DM*4$<]5"\Y24173BHS60I-)R8_2E<G0D9` M4"P^6D1)(D@P(DDE(DHP-4HD*DHV+5=$(4I#2CXT-4Y)(SXE04=).B\^)D9) M1#U:,5!:"DTN*")$2#U4/4Y(0C))8%M(*3%(6$@J,S0Y,F`J-T5:.28R04A" M3%\A22TT2%Y*15M;23HB2C%2(T!?*"8*32P^)E)>,T)824!;1"A5*C<\0$E8 M*CH_0$8L2D4[3#$T7#E,3C`X-DD])DHC-$H]54$G-"H])CA/0UQ!5PI-2DE! M4DE;04$]5$@W0BH]-EHU0BI$5TA7+D9$13)(*U9)*BI(5BPB(CQ**2-:,T$Z M12DZ0RDD)5\R2$A*"DU)-#M)+DU*-#9`32DJ-3-:0%8Z/TU61B5,-2,L22L[ M2%I=.5\B0EU)*C%1,#U+*D5.450Q2#8\)B,A/2T*33(N/4A10%564E=12D=+ M6"1<65U-4#<U(B-#/$E%,R(I04$]0F!06DI'*U@D+%))*30J+5HA*T1')2M" M.0I-6F`[7#="+SHQ6B)',2@^8%A:+EY$*2)`(5!%)%)`45DG.ELA+2%2+TXL M,BY`)EPL(2I))C,X(5M<*B9:"DTX-2-!4"1&15Y!4#`H/U(X24E")"=-)C]- M*5%.4UD^2CTK.&`X/DL]5C<W3D=0,"0Z0DE/(RHL(DHW+SD*34`I."]02D0_ M4D$\8$A&,T@R2$H\)$HJ,5)(5%I$)UI`4%HQ+#I)-EI$3TM)+4Q*/R]**#PX M12):1%$J10I-1U9"(EI!)U1)7D-(+EI*2$1$)"LZ2BXZ4UTV0D%2*B0Z2"\N M2%4V23Q62B0V2D%'.C4Z.CHO2CU-7CPX"DTD)3PB1EQ91#(G+3-)*D`D42A) M.F`I)D5.4C@P2#DO*DHE04HO2CY'4TI(.THH63I".U%<74I&*S9((4H*32-1 M5C\E4"9#)$)&.2=)(SHK,$))6UHJ,6!&4#A*/DHK05XI2BI*1%`A.2Y:,5-2 M22M=)C<A7"$P2CM5(@I-,3<S44M@-5I*23E:23]:23<V22TH*CE61S8T2CHZ M2%=$*D134%L\*BXZ(DE`22)(/D@Z4D92129)6DA7"DTP2%%$.5-%63U'.DA/ M-#\K*#)'3$A17D9#/$8G64H]6R%!1T@T-U(X+EXZ0S)&-48B+$M(0C9&/$M) M05<*35I#+%I-(B)((29()UI&*B)&*$5(1UI*-#9!2",Z43,J/%PX0V!`6S-% M52LD2D]!/"E!0T0_.E,J(R@V2@I-+$8B12,R.S92.3XB/2161D]'2BA*2$TM M.4PC.DPA2D`S,CDJ5D8P4DA45$8R74DK.DHB+EI,32HY-#HY"DTD,DXH,CU` M6$HJ/4E%2T8G22HX-SI634H\15H]-R)`+&`_6R$B4"HN5V!$63$A/5I*3#XJ M4B8R2EXN/D8*329+2U%&6SU&1RXK,THC+&!71V!`6"555#-`545@+$M$(28E M2B,T,R%-,B%$6E%&4D)`,5@E154S0%PU70I-+$\G2C9#2D]'03I/0$A44CI" M6CA`0CD[2#@U2D5:72(Y4$8F7$I6-TDT,UHV1U@_0")-2R9&(U9+.4-%"DU% M1$5.1RHP(C(X33E')THW3UHV/2I%6%9%5TI(8%A)0RM*6U]),R%:3B5:-E(R M03]4)BI>154K1EE;23\*33=)1$(I0"Y:055:3E0H.CU.."M"1C9%(U<F259- M0R4]0TM64"I$*BE9*2$Z7DM**B,S32A;(DI-5"I:)PI-6CQ@65XN)C9')DQ7 M)D0[,#XS6TA*7B%'*$I*5B-.3UHJ0#)*7TI'4EI+2CI$7C0I7"LF6T=$*EA1 M+RY:"DTJ3CI.5$Y/3#)+5C(P-R)*6U=)-6`J72M$)%Q:3R%:,#E4.TU6)3E4 M2$Q#2TA213Q5*CE324\I6D]-."4*34A55CHN-S,J1RM+24951E@[03,_2"HK M24]$*D=>+#E`,D8Z7B)/14H]2CY>6DI4+TI>*2I0*2HX0S9.+`I-)C(J0$9@ M2TPV5"9:14I06RE.2"I0)2HX2E)./RX\)R(L,"M**5]*7R=)0%5)0");4#Y: M3#!>3CI.2T8B"DU,)%U&/T-&4T%*6"HK)2<H.$TJ.#==(TD^0THR*$171D=- M14-,0311.R]+6D]5*#=$0"P\8"5.-DI"+RT*33,X)4`Y)R4C,D160%U9,DLC M-5$Z0C4T4"HP2B4]*T5-,D%))BLC7DHZ43I`62Q(,$Q=8"PL/DDJ5EDJ3PI- M2&`Q7S!=74E$6RI*)SPZ.4PV539,,T<H+$,\-#(K)"HC.TXH-4@Z-3921U\R M.D9>(U5#/"-93R-+2DPG"DU95"0G5%I!4#!&4DPL.EI,1C]52"553R5&1317 M,&`L55%<2%0^0#,M+"PY2B-2.R$S3C)/)F!*0BA&7C(*32@[429&2BA"6EE- M1")31&!=(T`I6$0Z14)66R0X/R$F0CI14DQ,0$I!7"XQ1E9)4TLB.25714I7 M,3<E20I-229023I<2CY,2D%,*DI/*DM+*DP[(D]+)"A64DM&4$PJ7$\N3$LQ M3"LV3RLT1#)06R)62U)>6E)/)E!/"DU27$A"(5M93"PB3RPC2R\C*R,A*U,A M6E-2)E!27EQ/1DQ*,TQ(.CLL1TLK+DLB4%M@6%`A4UY03#I<4#8*33%#+6`_ M+SI)-3LO+3LC,TM21CI352)05UY<5%),72U,0"$[+E)%/SM+(T`[0$8V4U=& M4$LZ5#9)3%I73`I-+3A-*$<[+T=+)"\T4TTZ4DT]+%<^7%Y23$8Y8"Y@3R]* M2RM2.R0J,%-?.E-@2E1=)EQ33DQ:.4PM1T\K"DTD2S-?*R0C*U,H*4A?2E$A M6EQ,0DTJ-DPP1D\K+$LP+2LR2#M4+CE')#I5)5)<35I-+R1,,3E/*CA+,#D* M33LT*UM4*2DS)SI572%-*B),544W+U-,,U@F/UY&-"M;-3]),24]2%Q>55<Q M3%,R-#\_.DE,.R\X6RHH5@I-4S5*5%@B42DV72HR3$%,33$M3S-,2R]!.R-$ M2U4O6E0J0E4C2ETS/DTA*TT]5C<P(4LW7E8Z2C93,BI5"DU@1E4S,E19(4TU M,4U`)CLO,4LQ(RLY/395*BI4+SI5+DI:8$DZ+C1,0BX[-3!+-"Y$-"TD4SDZ M4S`F5%T*33I4-RU-(EM--$1/,$U&14DK-"9+5")*5%A9,2I>73@J338E32PC M.S9&2RQ=.S4Z.R0B,E530E$Z,EU"5@I-339'33=53S`D2SE-)D0M2U56.E55 M*E(Z64U!.DTA0DTY,4\X-4LP1ULV*4M6)%I5*3%)039333E-*%A-"DTC)2,Z M740^-2LT6RM50BDR1D)6+$U-*CY-/UI,.4M/.4)+-CU;-DA+5#Y:53@B5BE9 M3%XR34\Z3#I73S8*35-&/DI;-C%+4T=*5"@F541"74(R33LO33TS.SA62SE@ M2S5<2U8O2E0K0E56/4U1*DTQ4TTX0D\\5TLS)`I-2SE*)E8T6E=-1E52,E0O M-4U",4T\7D\V-T8\/E9%/RE63DI53U9555)=.3Y-5S1-.EY/-3M+/C\[-S]+ M"DU7-BI36"95*CI=0#)-4E9-.29//D=+/#(K-#H[5D5*5S@J52=675L^35H\ M33U03SA32SPB.S=5.U8H*E8*339654%)+4I2329434!<3S8J2S<A.S@B2TE$ M-E4E)EE?0EU"2DU`0TY'*C-`3DL_74LX*"950CI5)EY90PI-*ETT5DU67$U` M+D\Y44L^4$LT(UM77"I7*D9:)TI4-C%-7SE-0B]/+DI+-T-;-BH[55%*5#TJ M55$F7BXB"DU.)T5-+SM./ULV/C\S1CL[52%:6"(F64=272PB3C9#34I'.S=8 M2T$S6S5=6U5-6EA>3E8J7ETU,DU1*DX*32%7.S=;2SDV-2-+.U@\.&`I4E1; M0ET_5DTY)$TX(T\S/4LR*%4I(DM863I9/396.SI>)%I,5$].139/-@I-)DM% M.$M(4ULR33963R913CI>/TY..T),+$I/1UQ+1%(K24-+65`J6D$F6C\R7%$F M35@T3D@B3T@G2TDH"DT[2BM+5S):6E$Z42A:7D(F33DA3C!$(B$W.THX.THZ M2UHV6EI'+EI%2E8V/4Q#12%)4D]*0TM*1#M*14L*35I)6EI'(EL_-3Y'-BI3 M22%*44]*.D4O5#<O8"5:52E`2#9:2T92+S5.2EY.2RI/2RI$5%I0.DTK6E]: M6@I-35):4#I>3"Y.6T).3"5/3"%+3R@K2R5+6R):6U(^6E%*7E`J-2@M-"M. M3TDO1BXV*T,]121.4"0\22E'"DTT6EY03DH^3E5--5<_.T\^2TL_.TM:(EI9 M)EI9.EY:/DY91DY*0D]-5TM*6%M*6EM:6BI:3#9234)>6RX*34Y?,4Y/.$]) M,$4_2TM+-2LR4S1'6CI8*#%!)CU.5U,W*D)/3S=+2RU2/"%+6U%:7$<N6E\Z M7EI*3EA',0I-2S]/3S9!7D1$3S5!8%@P(2167RXI/TDD,5T[)R13)$M$*TA. M1%\A)35/1"0G6EQ0,54H24\I1TXH*#=0"DU'2U`I2UQ%2UM.*ELC,ET[+3DH M-2TV)6!'-#(A7#),631,4RM+72)<*3U&2"9?8$XU+%0I+5$U,UX[3"4*35M: M.ELF.B)<,2Y>74I?*C).4%%/.#PS3EE`,SY&+%1;7%4I0#-"7RY64BXQ3DHB M-S,N-35>-%$V.U8Q1@I-7"=90T5&6S%:7S<J-2X\3E):3U0K13!58"9`4"=) M)"$G*EPQ24<W)34C74\S*S=53DM1/CM=)ULR0E9<"DTX3EQ+635712$J(2%1 M-$]16TM56CM=73M`.R$Z4T9:429>7%9.75TX6"Q/3"]+3BA+7B4K7B):7E$J M6D\*35)?0#Y.5$5/(B4X(T(D135553U`*D5"7CE,(3<X+T12(DQ:)THQ3TY" M1F!;0#M?2ULV*"LP12L\.E]+)@I-3SDF3SDF.TDL0$HY6U=9-"T^-5)+7E]+ M5E%>-6`Z/DY.5D];(45>1SM>62M;4CDF3397.2I2(ST[8"@R"DU63D]94TLI M3TM>64M?*$I:2CY?/3Y?/"Y.75DX7%]/4B]+7D4[1%A`7SM*6E4N7U0Z7U4R M3UP]3UU`3T\*325$.ED[*E!$7"9*7U@F7UA"7S-23TA%,45>,TY'2UA0)$1& M1E](.41:5E]1*E]92D]>,4\X-#!-(28O3PI-.U]52U]:*EI2/E].02\W3D]8 M/D]824]8(TM-3C(J52LI5$4D8$-@)25`(U=/4$-06%E,8%];7"H\8"\L"DU@ M(CY?7%I?1#Y?72Y0(3)024E/7U1"3S!%,SDU8#9?8"97(SU&42%83U$I4%<E M3#@A.U0B)3,^5211,EP*33%27"=++U1&3U`J.45$-R]1.U=@)5Y"15I<2V!/ M(ELQ/E]5/D]95TXC,U-,.TM(6EPO,%M:1TM@+&!@*`I-1R<V.4],,D\B2U`B M8%PD33PL+44A+5Y?-%)<)2-@,"M0/2,U)$)0)4%;7$Q,(4%'73M;8",G8#8W M+E`V"DU08#90*SDW+%\U4"-<8"<\6E);8%]&7"]#+U=>3U-*4&!&4"8J6ULI M*U$P7%TE*V!;3EPT2R]--E`R6E`*35PY3UY,2UQ!)CTL6UT]6R$\1R-.7E`Q M0U`G+4\G4E`H5EM.14M0-"PA+ETN-DTZ15I>449.0T)02BM,)@I--5M>,$Q@ M74Q@5#\B+ELB1CI0."]0*%!0*3%0)SQ;5S$[1BE$*4(S(D$_8$`K8$A#3R]% M3S)#-"I'7"I'"DTK42$L*S93(DHG8$LW+EHV4$8T4"8R4"LN7")1+")6+&`C M7R(Z0V!$*V`X2TY6.E`H0%-,*4M>3CPC(BP*35Q`*R-01V!1.RY<(E`\.5`L M2%-.)$PO*EPB,TPB6%Y:8%)<2T=@1E-03$%0+%Y0*D%<*U@[7U-;(4\O8`I- M5$M@54-@24M0559/*#U0+3Y<+D(L(R9<73=)/B4A)2Y(8$5+4#LL4"Y64"M/ M7"]./"-1/")37V!5.V!!"DTK)2XI."Y(4"XQ4"PL7"XV3"I:2R-03R-5-V!> M,RY51C<^+U`O6U`A1EPO8$M/(D4D(3\D/$LC5$)0-S\*34]>+5`O-5-25$M? M+5PJ551?62M@.CY>/59?8%90.S-.3EU,+%A;6#`\-#),)#).73!&7%(Z5$M9 M3RM%-PI-(B(X,$5;3TLD7%H[)#<_(BDK)T%>4$,O42Y,4#,S4#-57&`L3&!1 M4#%&1EPE6E]56#$O5U$D(U$S4E-;"DTW1$%",&!4,%Q=.R)?*R-933Y&6E$I M2$XT65!#6#M1+BPZ/2M<5#LE+$I?+#Y40E%03%0I1S\P-34B(28*32PR8%4G M-S<E3DDI,2<A5ST[)CM//2LP634T/3]6)4-<)3-!-$E26%,C)U)13E4T3S-( M4UXQ2U\]+"4G(@I-*3Y%)SPD-3Y+(3U'3T=+43=`43=-*UE=7#5<3"9@/R9` M5R=&,E]--E$\+$\S(U-47TM37SM,8%M@1R]@"DU>2ELN6E!7731!0SA+3S-7 M1T4M0D8G,30M.$5!4"9=.3LO.E8H54Y1.5-0-D)36CPK54U,6D(Z7TY:6U(* M32972B$W0S51.E90,U5<,"],,BQ<8"5>7#<E*3Y3(3PS44L_43=)4#M16UHD M/#5=7%PX63@N-EY)(E`P,PI-4291-2PL.#!"7&!$2UI!2RY=-EPP6R5,(4%* M.%%*-$XZ0E-+.$M(/#PZ.%LT,S5#4#\D/4]@/3-174%1"DTR*3M>-4P]0RPJ M1ULK7E4J4S,E3CE'5R1/+5=.,B=2/5([33!,.D$K)38N6EM7)5M?(3,C45<W M,C4D42L*32(\/%$L.2146S5+(D0C)#!;8%XW.38F4"Q%.S0C8#<K1B,_1B$X M/EI2-4(O02(B*T!<7T\J(BPN*$8D0PI-5C!-/"%`33];)EDB+V!=/U(N5%`F M4U`\/UM:2$PM3EM`7R9<1S%"6"I?2B)/23M.,T@C33M%+D`K6D%5"DTA*"TL M3CI334Y16$]1)R110RM37U),0%0L0TE<7T):74U67BY+(B\G44PX3RXC4TDE M2U\\*R]`2R<\3EH*34I+)4HW(B\G4B,[4D0S4$,^55A<+$HZ6RDB+RDT+RHS M*R(T3U$N(T]!0%-(*DP_/%LG)%Q;7RD]8#)7-@I-*E`N,TQ#35)&*U!#0EP] M0CQ)14Q>53LI5RI>0UY1*%],54M2+$50+2]5/3L\*E-+)DQ?*4M;)2U?+E\V M"DU2-S-21V!0+RI;6#E53BLK(R0_)B(J75Q#+RI&4&`\3RU)4UU&3"))2T0S M/"DO+R$D*RHM02@S53<H75(*32Q=.$@X7#PP/$HP/"<B7ETO(R%@1R%1+U$H M25$N+%-534Q'4SM%,BPG0UY=44PE7"LE+4E.4T`A2D101`I-23Q`1TPP0B8H M0CTI/5I>*4-@7EM213Q/355,2"1<2"1;64]<)4$_*4I7)D]3(D]?4DTF-3-" M(R9>/$LD"DT\15`L*R%?*U$W*E([(C(C4D(V45Y63$4Q7"9)*RLN7%Y6.E14 M3RM82E%9/U`S-E!&)5-?-TPF2DM?*%L*348]13=8*RL]*E=265`E.$]&35!) M058B)C4J7TLI+#1+-5,F4UDB2E]/755214M00D=<3U\L,2@V*"-.7PI-(2LJ M0T<O+"XA,$%24U@W3$E%*"U,2%=4*"]=/"0[*CP[+U9244(Z4DI93$I27$LR M.UPG2RQ05RLB4RY;"DTK8$5#4B=-4D0V,$5$6U9'+"I9+%M6*R16-E]01E)- M/U)3,%!+6DQ$0UQ1*3Q,1#PI,D\I)D<L4%,A3",*35%&3E%)4$Q2,UM)02L\ M*UM>5ULL72LJ6T)24S]3+$E24TA04UM<4%H\7%U,*2(N7$Q&7S4I(S([(D0[ M3PI-3C!04R-;-%(\6&!$7R5++"@K+RU++$HZ4C4B4U1%,S(Z3"-5*T5>+"5; M/EXS5#,Q.RY`/E,X)4U--5-3"DTW1#Q.7#E@/#\O)RQ*1R8^0R(_0TY-6U(Y M*CA64%Q%5DM>2RLM2T\M.S<M/$<B)R]3/2-.54E0.%P[4$D*32PR25M?)EI6 M7%LK/3LB3"M.4$!//B=34%U,1"8\.CQ+)#`O+D!/*3(S+DLF45E+3DHC4#]% M7$A26UI$7`I-6T=90U!/*T0_(2H_4BI$4D)"4T]$2UA=.U=#7"U<7R%!6RQ6 M+3)1)U,Z1U%$0E-,+$Q`(D<Y+2Q:72M@"DU04RM+.R(N5U-`7%-<8#111EQ! M-"Q/4"LL33\M7U)84E)3,"M/)2U35U10-DTK4EA;4T<F23(W*3I'+EP*33,B M)U=.35=2535,2S)<5R4\4S<[*2H_(CH_*U!#(T\W3$Y94EE'4#-'+"$O/%Y= M7"HO3R=47R9>.V!@)PI-4R]'4CTS4U5<3$Q$-C]).V`C3E\C0RM;6EA563=, M*%)06E!4(SQ,6C`S2#P^2R<K+$\C3%<O)2Y3)S)3"DTN65-<0DQ#/SPF+SQ+ M6#):34\J6S,O8#902E=214(W)B<U*CY3.3E%7D-++BTK+S]?(5XO4$Q=4RQ# M4U$*34E+428\5DU5(D<O+%=/8"0[,%\W4RHT4U(W4%)&7%$S+$!!/2A>3R,F M1S%57R)14U,Y6%(D5E!'2SU@3@I-)F!/33!+/S!&.R8T320D6U0D6U,T(TQ& M1UM245M(5DQ:/3LF+T,E/"@_2UA4)T51-&!1)$A</$8M(BHE"DU95RLM0%<K M2#Y955%.3D\Q24),5E%<(4]<74@\+50_,34O,#0[-#5+3S%<5"5$4%$M6UI= M7$M"/"LU+4`*320V73`K)#@K430C430_4"LW7%!"/$HI6UQ&6RI*+EE9-2$Y M)U$T7%1<75!54%Q$/EP\)#LP.2Y:/RTH+PI-5S0O3U0W250G7U0S)%Q1.EQ: M2CLC)4\D*B)>2%<D,R]48"5-(T905BM=*4<\4C!,8%U/8$,W,BXE)#HS"DU4 M.3-4)BQ4-45<,T<L2DM;)TQ?)T8V6T);(5E?5$`L42955T]"32I&2T%,/2<\ M)S%!5RQ&0R0L4U!`0E(*33TS4"%`7$A<32%<+3$L7S(_*S-58#1"6U,I1E0F M23A;/5M"6BM213U:05LR7SY;32\A52M4-R%3+#15+`I-)UTN2TPS)RTM3B\O M)3\O0SI3(TM2/DXJ*355*35=*48M*R@K(R<O*%$[)5<J4$([5$,I5"PL52%/ M7#9("DTK05U,)S9?)R$K+%8U,54[4D@J4UHP3$I9724A/2--+3)<3S)-3S)% M-R%23TY,,U%47$TI,EPT2SM;5$(*32HC+R4M6EQ=/S](.E1-+#$Z)6!50#`Y M13PW.T0Q)R\O*"<D0TLU8%-423505#-/2T],.C)-(5L])E!?,0I-52\P34LT M3UM3.2Y.7#9-*"1=,CDL-"<]0TE`*BPW,6`_-$LO5"M=4R%$4%I'73!(33T\ M3"=*+ELO+S$D"DU;-%LW5$!05"M)5#`G+25;6T,X/2@W)R97+24A5S,S+U`E M-E0L1U4E,ETD72Q85SPS+$\C4U,Q+2LD1EL*354K55$S7E$C-5TN5EM/6UQ> M,TLF3%Y40%<E)5=5*B51+E,I-4)<.STM*C@[,5Q/,2U+,3Q?)%Y#3E=0,@I- M-$)5-E%=+CI;0$<M65%:7V`K-4@O)2$O53$U*#`R5#U:/3,_+2$Q+2U/3RP] M(S9/2R4J,U(Y)U1.0RDV"DTD7#E=/211730]+S,E1S-!-RY93E4E/54X/%4Q M)UTX0TTS/TTM4C\D35LQ5B,B1TM275M1/5M0)T96-C(*34Q+7%PT-U<G)4\U M-S\^6B95-TQ5-U15-CQ<2BM--3E=-5TN6T93,4)+)%I#3ETI,2Y:*3I+73L\ M)#!84`I-,%!/,D,V7E(F4#I73DLM54PI3%I652I<7"%&+"]#/RA@2RA<1R(D M-U4Z5U$T/54Y*5TU+#TZ0CLE)SY="DU22E!!)3)53U18/E4U.E4Z)ETY3#TY M6U0V2EY;3S):3$)<2T93/"Y37$)1(CM51#E,+EI;,T!?-R13-#$*32,U2"-5 M2$503&!-2CL\*DQ<0RTF7"I+-RHS+#Q#)4I/54\A53\M539#7#HI334Z+30K M7R577R9=7R\J1@I--$A?4CTW4$!%7%TE,SE<+"PH3R\D73=@(R]77E171%4Y M4%4^6EPV-STA)3TP.3\W,S,D2#,Q7S]44EE3"DU'1R-)5TM20UQ-,3LJ1"\N M1DLV6595)R=56E!5.$Q5,3E=-"T])$<]/"@G,T!#-DI>551/5F!35CE152@* M351=,TY+6B1,-B9?-"@G.BU;-3I?5#TN52)943(K7#)$/%<U72%&7S$P)SDG M1R4_+V`B4%91-TTY)5PV,`I-*U%+75XV6E9?+EM'3V`P+S)3(50Z0%4C2UTA M+$PW,DTV*EY:+E<Z-B<R.%=5(V!03DU.+3<].#M&/#`K"DTY1R\D+D<E1B\T M7S-5*"5.3DY-,$A=.3)$2D@[)S1>7$HO,2XW,TLO53<Q5C0L5$0]6TM)32M& M.S57/4,*35PW+CE3(59?5B1!5$)+5$9&74,X3$DY33HH+R1'+EE(4S`D6U8C M+54J.$T]+5LP44U)+4TD8#Y<*S<K5PI-+R-97U-?05)).U!//UPD)%Q=,SLA M,STT5T%`1D<O+E9.7%)4.U-5-"%=1T],)2P]7D1;+B0W.D<F435;"DU42EE6 M4SI,6$9=.")%.B)=+EM>4BLZ7C`G,5HS3E<\5$!&54L\7"I!33%*-B12,S=4 M4RQ)5EY?7E9'-%,*33LJ54M574<L74]86S5:3S)/5SA=3R5@+59<1$Q?.5,J M*$U-4%TV*%TG-%\V1$LJ7ELE7$=2*3I235)41PI-6CPF-ETV-#TV/#Y=0U,V M(4<V6B-675A63EI53DU=3"8L0CHM-#`_-E8C.D9>5#!@.5HA(3A24T\[33=@ M"DU=-"M-.U0O,T,S(R4G8#@\)U-?45=6341'7#U=-#<Q)"I!1SQ%7E\D,E%/ M,U%%4#)10DU1/U`W-48L05P*33I9+S<^)RY=0SY')D\I.%$]/C%0,50\/UU< M/BT_."0F3DDJ-"DA5C57+30Q+3`T,D<L(UM=1U5=.BM?/`I--2\N1BI46U-6 M0"]7(SM@.U!1-$0T15H\/%XO/",C.3Y7)2M35"Q")S)45%0C7")13#5&/50S M*2LP1R@P"DU'(CQ,5RT[,3XW4U%91#Q6-25,/29,+#4Y0E\U-S%4/5%+.3(\ M0E`]6%Q`05U@/TT],E\I-#LO+%,V-3,*34\S)V!0*U=77DPP5RU66DPF4%\M M-5LO,#LA3E=6*BDO7D%14V!=3D(T-B)-6B=;+$@C*%==-#)03TM!.0I-3TM4 M+5==23T\0%`P43A7+4=2650A/DLB5R194DM05"U14&!=32=$+"9'0S4Y6SL] M/S4[0U1,4%)/6DTK"DU67%I5*T1$/#)-+S`Q)RDO0S137U4I6U<L2U1,.ETE M74U.8%TZ3$\B.3\\5"LT5D]72DE76E%4/44\3R8*34TY*$TZ/$\A5%\[.$<_ M."Y7*T0\-3A5-3!=/CP[5CE,*DA@)D%+)#@E04D_53`B-3XJ+55.75-&/2L^ M30I-7TLK.UE?.UI"544_3DU>5DA?45PM7"8H34E9/3Q;3ST^3R<N*S`Y2%=0 M2%96,C`F52PZ.2M?0#T])%\T"DTV/R](+358/U0^4E$O4U5+,EU"12M#7BTF M+2Y<02,S/2Y7(D]5.4915%-5/U==7$$M-$!-/R4_/39?)R4*34Y73T\A/%(M M64=5435=2EHM0"-<+SU?-B,U-%DS/U=.4$9%4#M85%Y=73@E+BM).SU`3SXB M0SHK0S$^7PI-5S%"6%0L5SQ&+5Y@34!@7CM,32E96EI"7S!16U153E)43%9/ M0BU30#0V-$PY.B\\53DD35DX)3-62T16"DU)0%%31UQ'-5TP5DTN1$]`*U4L M+5PA/S\Y1T0R(5)9,R1=2DQ+24TM6EI;*RE7(C$])E@M5"XT-SY.52L*33M< M72$\+C0T(B9?/D(W,"TK0B4W3U`Z4U$X5"LU6UXD/%LD.U$R-T!>/RXD-R<[ M6T\V8%A74DXF05XE1`I-7B%!3D%%3#\B1S$S6S(O3TY775<I7%5>7ETM,5PR M(T4D1B\X5S\F4#TO+C952EU0/E-4)S!=-BHM,2->"DTP)D\\+D0G*",W*"]8 M038H*"5:*"1>*5M;4B9.0B(_0D,G0R4B5T=;4BY#4EXL3TY,2U8M7#TB.R-/ M+EL*33\A/BA+)#%#4R0R3TDJ,2M./3<_1#]832=.12<Y+"$D16`K(U@B.U4C M*EHJ*EU;-BU>+CT]1R\_1R<W5PI-6S<O2U$^*5<R754N-EPX-2U87"Q",CY: M*$M!*2PG7B-5*$!57T)50E503$!=/$%$-3`_/TDG)51;.#`E"DU8)E181551 M24M>*%,N8%!,(4!#/BLG.3\_*"0O44U`6%XQ5U-'15DZ+%$C3EHH2T!3/$=@ M1S`N0%@L+E@*32PN65M'52]%/B8F/39+3T`S4T-.7RA2+U,\1U1,1E!,55TT M64Q5(4TZ0CY>7#A+.2,W6C=16EE/+UY8/PI-7#XL(E1-(3PE)3U#-C]"35LX M5%]5,RI./S5562U2/U==1EU63%LW0UM+0BXS,C$C5D(N5"A"4$TM5$Q?"DU- M)T1,7D@B75<S0BPC-3<_3$U&5"HP3$1)72,V/$T_.T)?/T%+63`P3T='6U@^ M/#@O.3T_)EQ@(BQ'73T*32@M7R%9)R]35S)<)U,L5$\A8%M76$Y@,EQ$1CX^ M8#\O3#,I2#\Y(2-6+EQ/4SY--S5<-%@[44Y>7$,[1`I-3TU%(U=(6D-80CY6 M4BY2,RY=,S4L3BT].E%52SD[)S,[-UU#,5=4,EY*)BLQ7%]++#!!/B-"7T%' M0E]."DU#,48O6$HB6#U4,2TF/5]633$D+2\N7RI=)T)35S-;4U,G*U)*/U=+ M,TY@5DU4,BT\7#]"3#=#+R<W6"<*350T(5<K(E0T.UPX)%XQ,#Y$-D\^)BLL M*5\I)B]0(40V0ULT3C9>*E4M620T*V`N74HC*$LK1UXS2SP\.@I-.4U17S9= M5ETF,TU>0DI?031#0S-*5U)+4UA=53DA54XX73A&*U@D33\_3RM<2S`]+S<A M+S4G7D\A.5@["DU37CE>7#4K75U=23(J(SI0(S@R)UDE+%E;/U4]6C4I75U3 M0#XA.E]$5$9;5U\F7#]976!44$],4C0U,&`*35X^434A2%!23C='1",R.C=/ M+%E03U<I*%PU3S=;0RQ6.R$^75<A,U$A*21;6%)!5#XE6RM(34="/C=$/@I- M0RDG1UE'15HC23I+65Y062HX3CY-7C]&7C=,+D=83T=<3T5<4T,W-U<_.5D_ M3%A"6EX_7%XU(SY'6C]'"DU=/T5?,TY",E50*EH^8%M&)$A@)"@A5$M46%(U M-EXV7DXS/"1,,$]:)C=/)#!"53%++SA0439(+S@N4#4*35Y:(C\K03XM)SU/ M8$TY-#-.2R8X02XX,$(B34,B,2Y@+4HQ*#E51R)$23U%05DP.3@K*T@U3CE@ M72HJ7PI-2U$G3")634\A*CM=6EA524A6+DXD1D`B7E56(DM).3T_/$0F7"D\ M4TY.14I./EM(.C@N(B]*,%!:(B=:"DU22B9$)U<X,EY--"--.S!@4#@F6"Q* M6T`J7T`K(SXB0U4D5RDW)E`C4R,D5#8O2%8D,2U8*E(T,B4]/D,*358E35Q# M/R972U$Q4TM%*SP\(5-</%PU/$-#,%,Q)#`J0S$^4D)$0#HH*THT.T)0+B1! M2"-944H](TLA8`I-*R@^7DDH7"$Y)C8S+T0P7%HX-3U%+EI`+U<F76`X(E,S M,E$I6E(J.DM,*U4J)TDB/"M@-4\^12\S65,N"DU*72M)/3TN/2]`.T1:,%A: M1U=;(5I*3#(K8#PK)T!"4"1"4"HD+$,E12PK,"(U,T1,(UY%(T)`1U)/-"H* M34D]4$DQ4B5$,#Y7(25`(RPK,S4[53I")#8N4TI1,5)+72I/7UI&,4-,+EI+ M5%0X*3,T244G*E!"4B-*5@I-0&`G4R%*03%,/5I+.%LG7T,K,$Y+(B]+-$T^ M4C-*4U-:33U:1EDB35I013`R.RH^*5@C2U,S2"Q<*E%/"DU:7#A:33%:3R@G M+RHG*TA>2SM/2U<[2C8C25=;,DXD6E<S,2A',EA+4$M`4B0Q)"=4,TI7/TI1 M6UI<2%H*34X[62U,+D]4/D,N05HY0TM-02Y<7TI=,UI=,UI"3R)-+%Y/-4Y+ M7RY,)4]+7UM+(R=+(2-;(2Y;42I:4`I-+5Y30DY+.3Y+25]+7S=*6D]+)2\] M)4Y:.%PN3S%>4$(N6SE>3#@_2U-'2R(G2RI?6E)=6T\D6E!.5$LE"DU77"Q" M/BL\32Y`)5%(+%8](DTI.R\K*"51(SE;8%@\,E$L."TP7$LC.$%)-3$K4"%3 M,6`C6"LD,SE(1$X*34E6*CE#4D\T,T%>3$PD33U9-$A@*#Y&(4Y$,%%*(3]* M/DM*,RM-+D@\)%%,0%A;)%E`,DM2(4XB)$,A*PI-63)+1D%*02LM*F!:)$-. M0D]075$R0S%9)4TA3CI8)B,D+5]%.TU$(2XH*#X[)RU`1E=9)U,W04]?359: M"DTR+6!!,4A%,24Y/$4E+E@V)S8G)%\R25A.*4U?8"\K,#U((20Z0#PG4B<Y M,T98/U(Y3C(_45HZ23@]3#$*344H/2537",Q/3DN-%Y0/RDW.T`V1B]/)R52 M35`](5L]7T8B02A.0DM.6#4Z3DHD*4HU3D5,*TL]+%\A)0I-1%=*55='/E-6 M6#DP35\L)SXC3UI12SXK+3Q<.UQ:.ULO)EY?7E\Q1B5.,TY-.4\]-T`H5%M+ M6CU;7%I3"DT\5RPD1%\I-D\J1%8H55,W8#M002I,*CM=(EI<*%9?(4Y00S=6 M03`V.T`C45]+4U=;/4@[/DQ@.T`K1T8*35,G63<\54!37T105BQ;65$L4S8B M/B\R/51;/"5>1U`^2"].4C4T)UY+2U]/6U]16U]>6E]?7EQ@/V!@3PI-4&!? M4"$G4"$[7&`_7&!!7&!*7V`K7V`L/V`O3U`C7U`C6U)?55`X)C\F7D!<0BPG M.$-04CA!5$A34C5:"DU:(5Y'1#`^,B)734`J/20G6T<\(3DZ2#$B*R@Z5U0S M22HC+U1*2$)`5TT])DDI(BTH+S]0(BPX+$0Z(C$*33!(3#A".31`3$HE7BM! M3$`Z7#,H-%=*(E58.C504$Q.2U!-(BI)04XB8$$K5T)%.%1!0U%*6B):2#PB M7`I-0$L[0"LD04Y5*"DS6B)7*"LN,B)4-B,U6&!,1B<E1%PV4R0L,$%3*3@C M(U@[16`\.#M3)4PP45XB3%1`"CQ(6T)</T%115\A8%\G*$A&/R8H(UHG5DPB M5EU<+35`/%9!4$-@05,I"F`*?0JL?5QP87)D7'1X,3,T-%QT>#(V.#A<='@T M,#,R7'1X-3,W-EQT>#8W,C!<='@X,#8T7'1X.30P.%QT>#$P-S4R7'1X,3(P M.39<='@Q,S0T,%QF,%QB,%QI,%QU;&YO;F5<9G,R.%QF8S!<8V8P(%P*7`HM M+5P*4&%U;"!3+B!396%R<R`@("`@("`@("`@("`@("`J("!S96%R<T!U:"YE M9'4@*$YE6%0@36%I;"!/2RE<"E1H92!5;FEV97)S:71Y(&]F($AO=7-T;VX@ M("`@*B`@<W5G9V5S=&EO;G-`=')E92YE9W(N=6@N961U("A.95A47`I%;F=I M;F5E<FEN9R!#;VUP=71I;F<@0V5N=&5R("H@(&-O;6UE;G1S+"!C;VUP;&%I M;G1S+"!Q=65S=&EO;G,I7`I.95A4(%-Y<W1E;2!!9&UI;FES=')A=&EO;B`@ M("H@($1O1",Q.38W("<X,R!.:6=H=$AA=VL@-C4P4T,@7`H@("`@("`@("`@ M/CX^(%-322!$:79I;F<@0V5R=&EF:6-A=&EO;B`C-S4U,#(P,#4Y(#P\/%P* M(E!R;V=R86UM:6YG(&ES(&QI:V4@<V5X.B!/;F4@;6ES=&%K92!A;F0@>6]U =('-U<'!O<G0@:70@82!L:69E=&EM92XB7`H*?0H@ `
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.next.hardware,comp.sys.next.bugs Subject: BUG FIX: Gateway2000 incompatability fix for model 4DX2-66V Date: 2 Jul 1993 23:45:26 GMT Organization: University of Houston Message-ID: <212ham$pps@menudo.uh.edu> (The rtf version includes a PostScript document that has a diagram of the location jumper that needs to be changed) Gateway2000 4DX2-66V Fix This the "official" fix from Gateway2000 concerning the problem with installing and running NEXTSTEP for Intel Processors version 3.1. The cause of the problem was that the PS2Mouse driver and the PS2Keyboard driver would not work with the newer versions of the BIOS that Micronics started shipping with a revised system board. Mainly it concerned the new Gateway ROM BIOS PLUS Version 0.10 GJX30-05E (but it also works for the earlier GJX30 versions). For NEXTSTEP for Intel Processors Release 3.1 to install correctly, the new Gateways V-Series systems must have the PS2 style keyboard jumper ENABLED. This jumper is not documented in the Gateway2000 Manuals as the PS2 style keyboard jumper, instead it is listed as W7 - "Reserved". Gateway ships these systems with the jumper disabled, and usually recommends leaving the jumper disabled for use with system and keyboard drivers. However, ou must change the W7 jumper to the "on" position (you will need to find a jumper to use or locate a spare one). The W7 jumper is located right next to the W40 jumper on the motherboard. See the diagram below. Micronics (Motherboard OEM for Gateway) is currently running NEXTSTEP on a new Gateway with the W7 jumper changed. This setup has worked with both serial and bus mice. NeXT's Quality Assurance group is testing this fix now. [This has been tested and verified at the University of Houston with the GJX30-01D verion of the BIOS.] **** The PS2Mouse driver must be loaded for this to work. If [and only if!!] you followed my earlier installation notes, you were told to remove the PS2Mouse driver from the file /usr/Devices/System.config/Instance0.table which was in the line "Boot Drivers". A simple way to do this is to run the Configure.app located in /NextApps and click on "save". The configure.app will automatically add the PS2Mouse driver to the Instance0.table file. Powerdown, then add the jumper and reboot. No need to mess with the turbo switch or anything, it should come up in NEXTSTEP automatically. To quickly verify if your keyboard will work, check if the NUM-Lock LED is off. If it is not, then your keyboard WILL NOT work. The W7 jumper is located next to the first LocalBus slot near the right-back end of the system board. This diagram is for the Desktop configuration only. The jumper may be located in a different location if you have a tower case. -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.bugs Subject: Re: Serial port Crashes System Message-ID: <1993Jul2.161910.5758@nic.csu.net> From: jtmack@bart.sfsu.edu (James T. Mack) Date: 2 Jul 93 16:19:09 PDT References: <X1JJ6B1w165w@mindvox.phantom.com> In article <X1JJ6B1w165w@mindvox.phantom.com> writes: > This never happens when the serial ports are not in use. I know this is > listed in the Release Notes, but how about a FIX sometime soon, this > renders the entire system I am using nearly useless since I can't connect > it to remote networks using a modem, without making it hang. > > To top it off, once hung it is REALLY hung, typing alt-numlock as > suggested does nothing, the only thing to do is hit the reset button, > which is getting a little hard on the hard disk after doing it two or > three times a day. > > Running fsck after this circumstances produces this message whenever I try > to reboot or log out of the root account: > > Raise RDP exception 6, code 3, subcode 0, C to continue > > of coures typing C or c, produces an endless scroll of the above, with the > only way to break out of it, again, hitting the reset button. I had the same problem as well but it only happened if I decided to turn to modem off or on while the NS was running. Starting NS with the modem off produces the same System Panic when the modem is turned on after NS has booted. After two weeks of having NS/FIP is still have yet to get the dialup working and that serial port error doesn't help things. mack
Newsgroups: comp.sys.next.bugs Subject: Re: Serial port Crashes System Message-ID: <1993Jul2.164014.5760@nic.csu.net> From: jtmack@bart.sfsu.edu (James T. Mack) Date: 2 Jul 93 16:40:11 PDT References: <1993Jul2.161910.5758@nic.csu.net> > I had the same problem as well but it only happened if I decided > to turn to modem off or on while the NS was running. Starting NS with the > modem off produces the same System Panic when the modem is turned on after > NS has booted. After two weeks of having NS/FIP is still have yet to get > the dialup working and that serial port error doesn't help things. > mack I understand that this is a basic UNIX boot-time ordeal and that any device unspecified or on at boot will cause this problem. I was just stating the fact that it gave me the same panic as the others so maybe it is not recognizing something when booting.
Newsgroups: comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs From: chrisl@mindvox.phantom.com (Chris Lesher) Subject: NeXSTEP Intel and SERIAL PORT DRIVER == JOKE Message-ID: <LTo46B3w165w@mindvox.phantom.com> Sender: mindvox@mindvox.phantom.com (MindVox) Organization: [Phantom Access] / the MindVox system Date: Sat, 3 Jul 1993 07:18:32 GMT Having spent more hours than I care to count exposed to the Windows environment at work, and through an extended patronage of MindVox which seems to be something of a NeXT mecca full of converts and true believers, when the time came for me to purchase a new machine this fall for in-house evaluation and future planning, I was quite excited by the prospects of NeXTSTEP technology. After arranging to view some of the NeXT's at Vox I came away with a strange feeling that perhaps I should have listened to. I was stunned by the user environment and in an office full of machinery the only only ones that seemed to have any active use as workstations were two NeXT's, and a Super NES ;-). But for the life of me, other than the obvious observation that a lot of people smoke pot in a closed room, I was unable to figure out what anybody there used the NeXT's for other than $10,000 paper weights which served as terminals to be hooked through an ethernet to the servers, all of which were dull, dreary, with the monitors turned off, but every single machine was some kind of Sun. In fact MindVox which started on the NeXT had moved away from using them for anything except fancy terminals as quickly as they could. But no..... I listened to the advice of the people hanging around, read and re-read the evangelists postings and sunk nearly $10,000 of my company's money into a NeXTSTEP eval machine from Dell. And what I now proudly possess is my very own $10,000 paperweight. I plug it into the ethernet, RDP exception #6, the machine hangs every time within a matter of hours. I plug in a modem, guess what, oh SORRY, the serial port drivers have a few problems. I NEEDED A MACHINE THAT CAN COMMUNICATE WITH OTHER MACHINES. A STAND-ALONE SYSTEM IS NEARLY WORTHLESS TO ME AND RIGHT NOW, THAT'S WHAT I HAVE, BECAUSE ANY TIME I TRY TO PLUG IT INTO A NETWORK OR CONNECT A MODEM, IT HANGS. *EVERY SINGLE TIME* To suggest that the solution is waiting for NS3.2 to arrive in the 3rd quarter, or 4th quarter, or whenever it gets here, is absolutely preposterous. I have paid for something which does NOT work. For all its garbage, Windows DOES work and rarely crashes and right now I'm using a 486dx/33 to get my work done, while I look at the NeXT and realize what I should have known in the first place. The NeXT is a beautiful paper-weight, which is championed by the sort of people who have SGI Indigo^2's sitting in their houses because "they're so cool man", have wardrobes from Armani, cars from Porsche, and make a living selling ATTITUDE. In a word, that's the NeXT, because it certainly doesn't do anything like FUNCTION as expected. When I brought these problems back to the true believers I came away with the tremendous wisdom of "well, I dunno, right now I just use kermit on the SGI or tip out" followed by "NeXTSTEP is pretty to look at, but ya know, its like whatever, the Apple ][+ pretty much did everything I wanted a computer to do. It had a terminal program called AE pro, and a word processor. Everything else are neat toys to play with." BINGO. So now I'm using Windows. And looking at OS/2. NeXT, this is RIDICULOUS. Kindly assign one or two persons to take the 3 hours needed to fix your serial port and ethernet drivers and allow those of us who have invested into what you and your evangelists are espousing, to at least make use of what we have purchased. There is no way I could ever recommend NeXTSTEP to our purchasing department, I have this sinking feeling I'd be left holding the bag, a feeling many people who purchased black hardware in 1993 must be very familiar with. chrisl@phantom.com
From: cjp+@pitt.edu (Casimir J Palowitch) Newsgroups: comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs Subject: Re: NeXSTEP Intel and SERIAL PORT DRIVER == JOKE Message-ID: <15745@blue.cis.pitt.edu> Date: 3 Jul 93 13:21:31 GMT References: <LTo46B3w165w@mindvox.phantom.com> Sender: news+@pitt.edu Followup-To: comp.sys.next.hardware Organization: University of Pittsburgh After my evangelizing here at the Library, we brought in an evaluation copy of NS/FIP. We tested it out and after several installation quirks, got it running. However, it conks out after a period of a several hours on incoming IP packets. Not good. It is back in the box and on the shelf. Oh well, it was only $300. NeXT dropped the ball putting this release out for general consumption. It is UNUSABLE for network applications, the entire reason we are evaluating new operating systems. Unixware is back on the machine. C'est la NeXT! -- ** Casey Palowitch - cjp+@pitt.edu UWSA #570881 ** ** Networked Information Services Group / Technical Services ** ** U. of Pittsburgh Library Systems // NeXTSTEP... ** ** ...the most respected piece of software on the planet BYTE10/92 **
Newsgroups: comp.sys.next.bugs From: mp@rob.cs.tu-bs.de (Martin DL8OAU) Subject: Re: CDplayer.app Message-ID: <mp.741729738@dagobert> Sender: postnntp@ibr.cs.tu-bs.de (Mr. Nntp Inews Entry) Organization: TU Braunschweig, Informatik (Bueltenweg), Germany References: <104@boschrt.rt.bosch.de.bosch.de> Date: Sat, 3 Jul 1993 20:02:18 GMT kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) writes: >Hi >I tried to listen to a music CD with a CDROM from toschiba XM 3401 >I put the CD in started CDplayer.app >Then my harddsik was more busy than the manager of IBM and the light of >the CDROM flickert, but no musci came out of the head phones. I am using >NSFIP 3.1. >Any idea? I have a similar problem with CD-150 (apple). To my knowledge, the commands for audio operation are different. But I do not know the correct ones of my drive. Can anybody help us? Martin.
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Spooky behaviour when adding classes with IB/PB Organization: Primitive Software Ltd. Date: Sun, 4 Jul 1993 17:27:01 +0000 Message-ID: <1993Jul4.172701.7394@prim> Sender: usenet@demon.co.uk Maybe it's the heat. But I'm sure it happened. I have two projects open in Project Builder that both share the same parent directory. I have the associated main nib files open in Interface Builder. I use IB to create (subclass/unparse) a new class in one of the projects. It comes up with the usual alert panels. But the resulting class file is _greyed out_ in the PB classes browser. Sure enough, there are no such files of that name in that project directory, but it _has_ added those files to the _other_ projects directory! This must be a bug in PB or IB. I haven't "messed" with these project files in any way. If it was the heat and I made a mistake, how come the files appeared greyed out in PB? When I immediately tried to reproduce the problem it went away. There's a ghost in my machine. Brrr! Dave Griffiths
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Re: Spooky behaviour when adding classes with IB/PB Organization: Primitive Software Ltd. References: <1993Jul4.172701.7394@prim> Date: Sun, 4 Jul 1993 19:38:38 +0000 Message-ID: <1993Jul4.193838.7806@prim> Sender: usenet@demon.co.uk In article <1993Jul4.172701.7394@prim> dave@prim.demon.co.uk (Dave Griffiths) writes: > >Maybe it's the heat. But I'm sure it happened. I have two projects open in >Project Builder that both share the same parent directory. I have the >associated main nib files open in Interface Builder. I use IB to create >(subclass/unparse) a new class in one of the projects. It comes up with the >usual alert panels. But the resulting class file is _greyed out_ in the >PB classes browser. Sure enough, there are no such files of that name in that >project directory, but it _has_ added those files to the _other_ projects >directory! > >This must be a bug in PB or IB. I haven't "messed" with these project files >in any way. If it was the heat and I made a mistake, how come the files >appeared greyed out in PB? The ghost is busted. It's a bug in IB. I just caught it red-handed and did a screen grab. The evidence is en route to bug_next@next.com. Dave Griffiths
From: lee@zoo.duke.edu (Lee Altenberg) Newsgroups: comp.sys.next.bugs Subject: NS/FIP networking successes? Message-ID: <17268@news.duke.edu> Date: 5 Jul 93 04:21:39 GMT Sender: news@news.duke.edu Organization: Duke University Physics Dept.; Durham, N.C. I read on comp.sys.next.bugs about how, with Intel machines that are networked or using a modem, NS will hang or crash very often. Has anyone out there had any SUCCESS in networking using NS/FIP? Lee Altenberg altenber@acpub.duke.edu
Newsgroups: comp.sys.next.bugs From: jacob@nugget.rmNUG.ORG (Jacob Gore) Subject: NS/FIP hanging and tty access speed Message-ID: <1993Jul6.050446.6779@nugget.rmNUG.ORG> Organization: Rocky Mountain NeXT Users' Group Date: Tue, 6 Jul 1993 05:04:46 GMT We have had many instances of NS hanging while we use the serial port (dialing out to another machine, or even just talking to the modem). The problem seemed to go away when we brought the computer-modem speed down to 19200 bps from 38400. Has anybody else noticed this behavior? Jacob -- Jacob Gore, Eastern NM U. Jacob@BlackBox.ENMU.Edu | Jacob@Gore.Com Member of the League for Programming Freedom (LPF)--lpf@uunet.uu.net
Newsgroups: comp.sys.next.bugs From: ian@mindvox.phantom.com (Ian Bainbridge) Subject: Re: NS/FIP networking successes? Message-ID: <mmD06B1w165w@mindvox.phantom.com> Sender: mindvox@mindvox.phantom.com (MindVox) Organization: [Phantom Access] / the MindVox system References: <17268@news.duke.edu> Date: Tue, 6 Jul 1993 09:02:21 GMT lee@zoo.duke.edu (Lee Altenberg) writes: > I read on comp.sys.next.bugs about how, with Intel machines > that are networked or using a modem, NS will hang or crash > very often. Has anyone out there had any SUCCESS in > networking using NS/FIP? With ethernet, partially to all the time, depends on the system and setup. With the modems, NEVER, EVER, period. They will always hang the system under the current drivers. I have talked with at least 15 people at MindVox and gotten the same response. They don't work. ian ################# @ #Ian Bainbridge # mindvox. # ############################################### phantom. # I am not responsible for my opinons, I don't know or care! # com ###############################################################
Newsgroups: comp.sys.next.bugs From: ian@mindvox.phantom.com (Ian Bainbridge) Subject: Re: NS/FIP hanging and tty access speed Message-ID: <LoD06B2w165w@mindvox.phantom.com> Sender: mindvox@mindvox.phantom.com (MindVox) Organization: [Phantom Access] / the MindVox system References: <1993Jul6.050446.6779@nugget.rmNUG.ORG> Date: Tue, 6 Jul 1993 09:03:32 GMT jacob@nugget.rmNUG.ORG (Jacob Gore) writes: > We have had many instances of NS hanging while we use the serial port > (dialing out to another machine, or even just talking to the modem). The > problem seemed to go away when we brought the computer-modem speed down to > 19200 bps from 38400. > > Has anybody else noticed this behavior? God yes ;-) Also, they don't work at 19200 either. They just seem to take a little longer to crash. ian ################# @ #Ian Bainbridge # mindvox. # ############################################### phantom. # I am not responsible for my opinons, I don't know or care! # com ###############################################################
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP networking successes? Date: 6 Jul 1993 12:36:28 GMT Organization: University of Houston Message-ID: <21brkc$cjo@menudo.uh.edu> References: <mmD06B1w165w@mindvox.phantom.com> In article <mmD06B1w165w@mindvox.phantom.com> ian@mindvox.phantom.com (Ian Bainbridge) writes: #lee@zoo.duke.edu (Lee Altenberg) writes: # #> I read on comp.sys.next.bugs about how, with Intel machines #> that are networked or using a modem, NS will hang or crash #> very often. Has anyone out there had any SUCCESS in #> networking using NS/FIP? # #With ethernet, partially to all the time, depends on the system and setup. # #With the modems, NEVER, EVER, period. They will always hang the system #under the current drivers. I have talked with at least 15 people at #MindVox and gotten the same response. They don't work. # # ian ################# # @ #Ian Bainbridge # # mindvox. # ############################################### # phantom. # I am not responsible for my opinons, I don't know or care! # # com ############################################################### (This is for ETHERNET only) We have 8 Gateway2000 4DX2-66V systems that are on ethernet with the SMC Elite 16 Ethernet cards (truely some of the best). They have been on the network (and on internet for that matter) since the end of May without even a network glitch. No packet overruns, no bad frames or acks, no hiccups... Too many people are blaming misconfigured devices on NeXT. If you make sure your devices are on the compatability guide AND they are configured under the guidelines listed in NeXTAnswers (details below), then you should not have many problems.... Now for info on NeXTAnswers: Here is the help file for NeXTAnswers: **************************************************************************** * If you have trouble reading any message from NeXTanswers, send your request again with the keyword "ASCII". If you still can't read the mail reply, please request the document via FAX by calling (415) 780-3990 [NOT WORKING]. For help using NeXTanswers, send a request with the keyword "HELP". **************************************************************************** * [NeXTanswers help] Welcome to NeXTanswers, NeXT's document retrieval system! This system allows you to request on-line technical documents, which are then e-mailed to you. The documents are sent as NeXTmail attachments by default; you can request that they be sent as ASCII text files instead. To use this system, send requests to NeXTanswers@NeXT.com. To request a document, include that document's ID number in the Subject line or the body of the message. You can request several documents in a single message. You can also include the following keywords in the Subject line or the body of the message: INDEX returns the list of all available documents ASCII causes the requested documents to be sent as ASCII text HELP returns this help file For example, a message with the following Subject line requests three documents: Subject: 21 22 27 A message with this Subject line requests the same three documents be sent as ASCII text files: Subject: 21 22 27 ascii If you have any problem with the system or suggestions for improvement, please send mail to NeXTanswers-request@NeXT.com. -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: ls(1) man page doesn't describe -v option Message-ID: <1993Jul7.065759.29233@csus.edu> Sender: news@csus.edu Organization: San Francisco State University Date: Wed, 7 Jul 1993 06:57:59 GMT [It's like ls -lisg but shows all three dates] -=EPS=-
Newsgroups: comp.sys.next.bugs From: smith@nextone.niehs.nih.gov (Howard C. Smith) Subject: Inaccessible menu cells Message-ID: <1993Jul7.153456.18544@alw.nih.gov> Keywords: screen limitation, services, menu cells Sender: postman@alw.nih.gov (AMDS Postmaster) Organization: National Institutes of Health Date: Wed, 7 Jul 1993 15:34:56 GMT In order to still use my dimming MPixel monitor, I have recently changed my menu font to Helvetica Bold, 18 point. However when I do this several menus (most notibly Services) stretch beyond the full length of the display. I can only access the first 31 menu entries on the Services menu... I believe that even an App such as VirtSpace, or other virtual desktop app can't solve this problem, because the menu of interest gets deactivated. Is there any way to split a large vertical menu into several pieces (wrap the menu), or at least mouse drag the top of the menu beyond the top of the physical screen so the bottom menu cells may be accessed? Is it fixed in 3.1? NS/FIP users with lower resolution screens should run into this roadblock even sooner... Howard Smith
From: grio@next.com (Dan Grillo) Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP networking successes? Date: 6 Jul 1993 08:03:51 GMT Organization: NeXT Computer, Inc. Message-ID: <21bbl7$4oe@rosie.next.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Makemail: v1.9 Dmail: v1.4b lee@zoo.duke.edu writes in comp.sys.next.bugs: > > I read on comp.sys.next.bugs about how, with Intel machines > that are networked or using a modem, NS will hang or crash > very often. Has anyone out there had any SUCCESS in > networking using NS/FIP? Yes. At least one of the posters had a misconfigured enet card. --Dan -- Dan Grillo grio@next.com [NeXTmail, PrivateMail, MIME welcome]
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: Inaccessible menu cells Message-ID: <C9t0x9.7Iv@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota References: <1993Jul7.153456.18544@alw.nih.gov> Date: Wed, 7 Jul 1993 17:02:10 GMT Menus including popup or pulldown menus will scroll on the screen as you drag the mouse near its border. Perhaps the best feature of 3.1. peter Howard C. Smith (smith@nextone.niehs.nih.gov) wrote: : In order to still use my dimming MPixel monitor, I have recently : changed my menu font to Helvetica Bold, 18 point. However when I do this : several menus (most notibly Services) stretch beyond the full length of the : display. I can only access the first 31 menu entries on the Services menu... -- I felt his rocket science training was inadequate. peter@tahiti.umhc.umn.edu (Peter Eisch)
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: dave@prim.demon.co.uk (Dave Griffiths) Subject: perform: with:afterDelay:cancelPrevious: doesn't work from threads Organization: Primitive Software Ltd. Date: Wed, 7 Jul 1993 17:01:42 +0000 Message-ID: <1993Jul7.170142.4824@prim> Sender: usenet@demon.co.uk I think this is a bug, if it's something I'm doing wrong please let me know. As the subject line says, this method doesn't work properly when called from a thread. What happens is that the requests get queued up until the next user event occurs. I've tried delays of 0, 1 and 1000. It's a pity because I wanted to use this method from a thread in order to safely use appkit objects (in this case [window setTitle:]). Is there any way round this other than using distributed objects? Dave Griffiths
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: open -a "App name" doesn't work Message-ID: <1993Jul7.181537.26198@altsys.com> Summary: Try it yourself Keywords: open, bug, TickleServices Organization: Altsys Corporation, Richardson, TX Date: Wed, 7 Jul 1993 18:15:37 GMT Could some other people out there try this please (I think it may be a problem with NS 3.1)? Terminal.app at the prompt type: usr/bin/open -a Edit wait to see if Edit.app opens Check the man page to see how it's *supposed* to work. What happens to me is: > open -a Edit open: can't open connection to Edit on local host. Thanks. Please check to see if it works as advertised. I discovered this using TickleServices. -- Lorin Rivers Lorin_Rivers@altsys.com Altsys Technical Support 214.680.2518 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
From: dillon@moonshot.west.oic.com (Matthew Dillon) Newsgroups: comp.sys.next.bugs Subject: Re: Serial port Crashes System Date: 7 Jul 1993 10:25:17 -0700 Organization: Homeless Electron Distribution: world Message-ID: <21f0tt$q2v@moonshot.west.oic.com> References: <1993Jul2.164014.5760@nic.csu.net> In article <1993Jul2.164014.5760@nic.csu.net> writes: :> I had the same problem as well but it only happened if I decided :> to turn to modem off or on while the NS was running. Starting NS with :the :> modem off produces the same System Panic when the modem is turned on :after :> NS has booted. After two weeks of having NS/FIP is still have yet to get :> the dialup working and that serial port error doesn't help things. :> mack : : : I understand that this is a basic UNIX boot-time ordeal and that :any device unspecified or on at boot will cause this problem. I was just :stating the fact that it gave me the same panic as the others so maybe :it is not recognizing something when booting. This has happened to me too but I discounted it as my doing something wrong trying to get SLIP up and running. I haven't tried to use the serial port for anything else and now I'm afraid to! -Matt Matthew Dillon dillon@moonshot.west.oic.com 1005 Apollo Way dillon@overload.berkeley.ca.us Incline Village, NV. 89451 ham: KC6LVW (no mail drop) USA Sandel-Avery Engineering (702)831-8000 [always include a portion of the original email in any response!]
From: dillon@moonshot.west.oic.com (Matthew Dillon) Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP networking successes? Date: 7 Jul 1993 10:45:51 -0700 Organization: Homeless Electron Distribution: world Message-ID: <21f24f$qjr@moonshot.west.oic.com> References: <17268@news.duke.edu> In article <17268@news.duke.edu> lee@zoo.duke.edu (Lee Altenberg) writes: :I read on comp.sys.next.bugs about how, with Intel machines :that are networked or using a modem, NS will hang or crash :very often. Has anyone out there had any SUCCESS in :networking using NS/FIP? : :Lee Altenberg :altenber@acpub.duke.edu I have encountered two instances where crashes have occured while doing large gnutar's over NFS from a NS/486 machine to a slab. Also, our NS/486 machine has gotten into wierd crashing modes where the SCSI gets a screwed up. The machine would be running fine but would then crash (the initial crash was apparently network-related). The SCSI would then fail during the reboot. A hard-reset did not fix the problem, the SCSI would still fail on boot. I had to power cycle the machine to get the SCSI working again. The problem is especially frightening in that when the machine got into this mode NS would attempt to 'retry' the SCSI operation, and after several attempts failing would then ignore it and attempt to continue the boot, immediately running another SCSI operation on a different sector which would also fail. Apparently something was happenning, because it completely destroyed the partition to the point where I had to power-cycle, boot from CDROM into single-user mode, reformat, and restore from the last tape backup. I hope to hell that NeXT posts a patch to fix these problems, we can't install these things in our customer base as they currently stand and can't wait another 6 months for NeXT to maybe fix the problems. We may be forced to huck NeXT out the window and go with BSDI and X windows. -Matt
From: dillon@moonshot.west.oic.com (Matthew Dillon) Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP networking successes? Date: 7 Jul 1993 14:32:48 -0700 Organization: Homeless Electron Distribution: world Message-ID: <21ffe0$154@moonshot.west.oic.com> References: <21brkc$cjo@menudo.uh.edu> In article <21brkc$cjo@menudo.uh.edu> sears@tree.egr.uh.edu (Paul S. Sears) writes: : :Too many people are blaming misconfigured devices on NeXT. If you make sure :your devices are on the compatability guide AND they are configured under :the guidelines listed in NeXTAnswers (details below), then you should not :have many problems.... Now for info on NeXTAnswers: : :Here is the help file for NeXTAnswers: I have generally found that a misconfigured board either doesn't work at all or crashes the machine every time... I have yet to come across a situation where the machine is able to boot and use a misconfigured board for a period of time before crashing. In general, I have found NS/486 to be extremely fragile compared to other OS's when it comes to dealing with the hardware. It even has problems with the standard floppy controller on boot sometimes. -Matt :-- :Paul S. Sears * sears@uh.edu (NeXT Mail OK) :The University of Houston * suggestions@tree.egr.uh.edu (NeXT :Engineering Computing Center * comments, complaints, questions) :NeXT System Administration * DoD#1967 '83 NightHawk 650SC : >>> SSI Diving Certification #755020059 <<< :"Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs,comp.sys.next.software From: dav@well.sf.ca.us (Paul Davilon) Subject: Buggy SERIAL PORT Drivers Message-ID: <C9txvo.A6J@well.sf.ca.us> Summary: boom crash Keywords: junk Sender: news@well.sf.ca.us Organization: The Whole Earth 'Lectronic Link, Sausalito, CA Date: Thu, 8 Jul 1993 04:59:47 GMT Unfortunately I too am stuck in the same situation that has apparently hit so many others here. My main source of information regarding NeXT has been MindVox and The WELL, along with comp.sys.next, which I unfortunately did not read often enough, or perhaps there were no posting prior to those of the last few weeks about the serial ports. Though (justifiably) angry, Mr. Mercke's (sp) well-stated letter summed up the way I'm feeling right now better than I could do it myself, so I'll let it stay with that and add in that I find it ridiculous that FREEWARE such as Linux or BSDI *CAN* have working, robust drivers, cross all kinds of platforms while NeXT says "A couple of weeks for testing." NeXT I would say to you: Make that as fast as you can, nothing you possibly release could be worse than it is. They plain and simple don't work. I am very slightly pacified by at least some response, but if I don't see some ACTION in the form of updated drivers VERY soon, then I'm going to start writing some letters and having conversations with people I consult for, starting with Viacom and moving on to the NeXT forums on MindVox and WELL, and ending with a direct mailing of every single person covering technology and Cyberspace issues on both Vox and WELL, and their number is quite large. Judging by the heat here I'm going to have a lot of comiserators happy to do the same thing. This is not a threat, its a statement of action. If as you claim NeXT is doing, and some new serial drivers come out, I'll be writing the same group of people letters, only this time it'll be how wonderful NeXT is to customer response, and how quickly they solve problems once they are made aware of them. Please give me the opportunity to say nice things, and give your customers what they paid for in the first place. Paul Pardon the typographic errors, I have grown used to cut and pasting and now I'm running Windows and using vi. dav@well.sf.ca.us dav@mindvox.phantom.com
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: lloyd@world.std.com (Chris Lloyd) Subject: Re: perform: with:afterDelay:cancelPrevious: doesn't work from threads Message-ID: <C9u12D.13v@world.std.com> Organization: The World Public Access UNIX, Brookline, MA References: <1993Jul7.170142.4824@prim> Date: Thu, 8 Jul 1993 06:08:36 GMT In article <1993Jul7.170142.4824@prim> dave@prim.demon.co.uk (Dave Griffiths) writes: > >I think this is a bug, if it's something I'm doing wrong please let me know. >As the subject line says, this method doesn't work properly when called from a >thread. What happens is that the requests get queued up until the next user >event occurs. I've tried delays of 0, 1 and 1000. It's a pity because I wanted >to use this method from a thread in order to safely use appkit objects (in >this. case [window setTitle:]). Is there any way round this other than using >distributed objects? Gerp. The AppKit isn't thread safe, live with it. Keywords: ports, msg_send/recv, DPSAddPort. Have fun! -- :: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: :: LOUDER...LOUDER... ::
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware Subject: NS3.1/fip: Possible bug in formatting floppies? (Survey please) Date: 8 Jul 1993 12:47:11 GMT Organization: University of Houston Message-ID: <21h50f$8ka@menudo.uh.edu> Keywords: Please, read, and, send, an, answer I have found out last night (after talking with a vendor during our NEXTSTEP User Group meeting) that they were having problems formating a floppy under NS3.1/fip. They were using a custom clone box. When the formatting process started, they would get a system panic and this was a consistant crash. Everytime they attempted to format, the system would panic. Well I decided to give it a try on our trusty old Gateway2000 systems (8 4DX2-66V systems). And wouldn't you know, the format fails on these systems also with the following messages: Jul 7 19:30:04 redwood mach: DOS File System: Initialized Jul 7 19:30:21 redwood mach: FloppyCntIo:flushIntMsgs:Stray Interrupt Jul 7 19:30:25 redwood mach: fd0: Disk Unformatted Jul 7 19:30:39 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:40 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:40 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RECALIBRATING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RECALIBRATING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RECALIBRATING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:43 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RECALIBRATING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RECALIBRATING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: RETRYING Jul 7 19:30:47 redwood mach: fd0: Sector 0 cmd = Read; Missing Address Mark: FATAL Fortunately we have 50 NeXTStations around so we can format our disks. Now, I want to do a survey: Try formatting a 1.44M floppy on your Intel box under NEXTSTEP. Let me know the results (send any console messages, if possible). Also, include the specs for your box (i.e, vendor, bios, type of floppy/disk controller [it might be integrated like the Gateways], amount of ram, etc). I will summarize this info and forward it on to a contact a NeXT to see if they are aware of this problem and if they are working on it. Thanks! -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.bugs From: anderson (Ken Anderson) Subject: Re: perform: with: afterDelay:cancelPrevious: doesn't work from threads Message-ID: <1993Jul8.150950.5341@biztech.com> Sender: news@biztech.com Organization: Biztech, Inc. References: <C9u12D.13v@world.std.com> Date: Thu, 8 Jul 1993 15:09:50 GMT > > > Gerp. The AppKit isn't thread safe, live with it. > > Keywords: ports, msg_send/recv, DPSAddPort. > >Have fun! >-- >:: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: >:: LOUDER...LOUDER... :: Also: It's true, the appkit is not thread-safe. However, there are ways to work around this. For an EXCELLENT example, check out Julie Zelenski's SortingInAction example in /NextDeveloper/Examples/Appkit. Ken Anderson anderson@biztech.com Stamford, CT
Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs From: lars@gsblas.uchicago.edu (Lars Andreas Stole) Subject: Re: 3.1 BAD rumors Message-ID: <1993Jul8.170048.27119@midway.uchicago.edu> Sender: news@uchinews.uchicago.edu (News System) Organization: University of Chicago Computing Organizations References: <9307081419.AA15511@its.com> Date: Thu, 8 Jul 1993 17:00:48 GMT In article <9307081419.AA15511@its.com> msb@its.COM (Michael S. Barthelemy) writes: > In comp.sys.next.advocacy article <C9t6E2.D1x@mentor.cc.purdue.edu> you > wrote: > > > I've been trying to reproduce this. I have all the apps in my > > dock open, and about 30 terminal windows open -- still no trouble. > > Has anyone been able to cause the error consistently? > > > I have also attempted to duplicate the problem without sucess. > > My guess at the moment is that it is memory related. Notice when one > boots under 3.1 that it allocates file buffers differently for > different amounts of RAM on-board. Not saying this has anything to do > with number of processes and threads, but since it dynamically changes > the number of buffers why couldn't it change the number of processes > and threads. > > My mono station has 32MB RAM and runs quite well, even though I have > taken it up to over 350 processes and a system load of 15. I have not > had a major problem since installing 3.1. > > Mike Barthelemy > msb@its.com I have also been trying to reproduce the problem, but unfortunately I have had no luck (at least using a reasonable number of applications). I think I have had some success at determining the number of processes allocated by both 3.0 and 3.1. (BTW, why isn't pstat on NeXT machines fro this purpose?). First, I ran the following script to two mono machines. One machine has NS3.1, 20MB memory, at 25Mhz; the other is a turbo (33Mhz) with 24MB memory and NS3.0. #!/bin/sh echo "another one" /tmp/fill.me exit [This script basically spawns processes until there are none left.] Then I suspended the script, killed one application to free a process, and then ran 'hostinfo' to get the current number of precesses (presumably 1 or 2 under the critical amount). [Please be careful if you wish to run this experiment on your machine, as you may need to reboot if you lose control of the spawning.] The result is that the 3.0 machine had 148 processes running; the 3.1 machine had 147 processes running. There doesn't appear to be any difference in process allocation. This leads me to believe that the process problem in NS3.1 is related to something else. Perhaps memory, as the poster above suggests. What I don't understand is how the poster above can get 350 processes running at once! I haven't been able to get it above 150 without running out. As an aside, I should qualify why I originally posted my disappointment with upgrading to 3.1. Because I do _not_ do development, I do not see any gain in upgrading, although a developer would clearly prefer NS3.1's improvements in gcc, etc. Because I _do_ run lots of processes (apparently too many on ocassion), I am annoyed when I have had to shut an application down. (Again, I am presuming that NS3.1 is the cause of this problem; the debate still seems to be unsettled.) [I have cross-posted this to c.s.n.bugs, which is perhaps where this debate should continue if people are interested.] -- Lars A. Stole University of Chicago, GSB (312) 702-7309 lars@gsblas.uchicago.EDU (NeXTMail)
From: cedman@golem.ps.uci.edu (Carl Edman) Subject: Re: open -a "App name" doesn't work Message-ID: <CEDMAN.93Jul8102608@golem.uci.edu> In-reply-to: lorinr@altsys.com's message of Wed, 7 Jul 1993 18:15:37 GMT Newsgroups: comp.sys.next.bugs References: <1993Jul7.181537.26198@altsys.com> Date: 8 Jul 93 17:26:18 GMT In article <1993Jul7.181537.26198@altsys.com> lorinr@altsys.com (Lorin Rivers III) writes: Could some other people out there try this please (I think it may be a problem with NS 3.1)? Terminal.app at the prompt type: usr/bin/open -a Edit wait to see if Edit.app opens Check the man page to see how it's *supposed* to work. What happens to me is: > open -a Edit open: can't open connection to Edit on local host. Thanks. Please check to see if it works as advertised. I discovered this using TickleServices. This is a known 3.1 bug. One workaround which may be acceptable to some is to set public window server. Carl Edman
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: bstone@acs.ucalgary.ca (Blake Stone) Subject: ThreadKit to the rescue! Message-ID: <Jul8.201308.46520@acs.ucalgary.ca> Date: Thu, 8 Jul 1993 20:13:08 GMT References: <1993Jul7.170142.4824@prim> <C9u12D.13v@world.std.com> Organization: The University of Calgary, Alberta > > I think this is a bug, if it's something I'm doing wrong > > please let me know. As the subject line says, this method > > doesn't work properly when called from a thread. What happens > > is that the requests get queued up until the next user event > > occurs. I've tried delays of 0, 1 and 1000. It's a pity > > because I wanted to use this method from a thread in order to > > safely use appkit objects (in this. case [window setTitle:]). > > Is there any way round this other than using distributed > > objects? > Gerp. The AppKit isn't thread safe, live with it. > > Keywords: ports, msg_send/recv, DPSAddPort. Until now! Making world safe for threads it's... ThreadKit! Send a message to any AppKit object safely from any thread! Well. Soon anyway. An EARLY version of ThreadKit (it works just fine, but frills are few and far between) will be uploaded on cs.orst.edu into the submissions directory by the end of the day. I'm looking for feedback et al to turn it into a polished product. -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs From: robocop@lehre24.informatik.Uni-Bremen.DE (Dirk Lehmann + Co) Subject: Mysterious Problem ! Message-ID: <1993Jul8.203224.19279@informatik.uni-bremen.de> Sender: robocop@lehre24 (Dirk Lehmann + Co) Organization: Universitaet Bremen Date: Thu, 8 Jul 1993 20:32:24 GMT Hello out there ! I have a big, big problem. A few day's ago I want to read some sheets of the NeXT-Documentation on my NeXTstation (NS 3.0), but the Librarian nor Edit.app nor the RTFInspector of the Workspace was able to display the graphics in the text. I only got a NXdefaulticon instead of a figure. I tried some other documents and generated one by myself, but this doesn't worked too. Then I switched from my regular account to an other account, where everything was displayed fine. Opening a rtfd-document on my regular account via NXhost from a shell makes Edit.app displaying all graphics. This event makes me erasing my default-database (~/.NeXT folder). After logging in again, I started Edit and all figures were in place. This might be the end, but it wasn't! After I have placed all the icons back in the dock, I got my deja-vu. No graphics ! After I erased the .NeXT-folder again, I placed an icon one by one and let Edit display a rtfd-document. When I placed ImageViewer in the dock, the same magic appeared. So I started again (get lost ~/.NeXT-folder !) and left my ImageViewer in /LocalApps/Graphics. For a few minutes I was happy : figures placed all around the text and everything on my regular account. But this moment of satisfaction didn't last long and all graphics I saw were NXdefaulticons. So ImageViewer is not to blame for this dilemma. Some other trials were also without effect.... Is there somebody out there who had this problem or is able to solve it ?? Thanks in advance Dirk
Newsgroups: comp.sys.next.bugs From: tholland@pars.skidmore.edu (Anthony Holland) Subject: Black Hardware printing to Apple Laserwrite - help please Message-ID: <1993Jul8.214519.6151@scott.skidmore.edu> Keywords: printing Sender: news@scott.skidmore.edu (news manager) Organization: Skidmore College, Saratoga Springs NY Date: Thu, 8 Jul 1993 21:45:19 GMT I recently installed the apple talk portion of 3.0 (fearing the eventual breakdown of our NeXT Laser printer). The test page printed out beautifully, but nothing else will print....I keep getting some message like "printer unavailable (or busy or some such)). Do I have to be root to print to the laserwriter ? Has anyone had any trouble with this ? Any advice ? Thanks Anthony Holland Skidmore College
From: eoliver@ralph.cs.haverford.edu (Erik Oliver) Newsgroups: comp.sys.next.bugs Subject: Re: Black Hardware printing to Apple Laserwrite - help please Date: 8 Jul 1993 23:35:46 GMT Organization: Haverford College Computer Science Department Message-ID: <21ib0i$k5v@venus.haverford.edu> References: <1993Jul8.214519.6151@scott.skidmore.edu> Keywords: printing In article <1993Jul8.214519.6151@scott.skidmore.edu> tholland@pars.skidmore.edu (Anthony Holland) writes: > >I recently installed the apple talk portion of 3.0 (fearing the eventual >breakdown of our NeXT Laser printer). The test page printed out >beautifully, but nothing else will print....I keep getting some message >like "printer unavailable (or busy or some such)). > Hmm, I recall that there may have been some Apple Talk phase 1 phase 2 issues during earlier netnews discussions of the AppleTalk package >Do I have to be root to print to the laserwriter ? >Has anyone had any trouble with this ? >Any advice ? > We use an Apple Laserwrite IINT as our primary printer it is on a different appletalk zone and on localtalk not ethernet without problem. EXCEPT when a macintosh based user tries to print while we are printing the result, deadlock. Nobody gets any more output until the pprinter is reset. -Erik -- Erik Oliver Erik_Oliver@ralph.cs.haverford.edu
From: jmd@cube.handheld.com (Jim De Arras) Newsgroups: comp.sys.next.bugs Subject: ET4000 driver bug Date: 9 Jul 1993 01:02:35 GMT Organization: Hand Held Products, Inc. Distribution: world Message-ID: <21ig3bINNjbh@clem.handheld.com> I've discovered an interesting bug in the et4000 driver, at least on my card. The curser disappears as if going behind the image along a horizontal line that starts between the 8th and 9th dock icon and crosses the whole screen. The curser slowly vanishs until the last pixel is peeking above this line, then when that pixel vanishes, the whole curser appears complete exactly where it belongs below that line. As you go up, as soon as the first pixel crosses that line, the curser vanishes, except for that pixel. The curser then gradually reappears as you continue to mouse up. Strange! Jim -- ----------------------------------------------------------------------- Jim De Arras - WA4ONG | "Unencumbered with facts as I am, I will NRA,ILA | comment." jmd@handheld.com | -Drew Lawson in alt.folklore.computers
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Not so smart pre-processor Organization: Primitive Software Ltd. References: <1993Jul1.134516.3325@prim> Date: Wed, 7 Jul 1993 19:31:12 +0000 Message-ID: <1993Jul7.193112.6474@prim> Sender: usenet@demon.co.uk In article <1993Jul1.134516.3325@prim> dave@prim.demon.co.uk (Dave Griffiths) writes: > >I've got a really wierd problem that's only just started happening. Basically, >the first time I try to compile a new .m file, I get a load of errors of the >type you would expect if you'd forgotten to include a #import directive. But >the #import is there, and so is the header file it refers to. I'm not using >precompiled headers. The header file in question was actually brought into >the project as a result of dragging the class icon in Project Builder from >another project's class suitcase. I'm not sure if this is related to the >problem. Doing a "make depend" and a "make clean" doesn't help. The header >file is there, the #import is there, but the compiler acts as though the >header file is empty! The header file is not a link of any kind. > >Now here's the wierd part: I can make the problem go away by opening the >header file in Edit and just saving it without changing it. Hey presto, the >compiler now recognizes it and the problem disappears! > >Anyone know what could be causing this? Take a look at this: /src/Newsagent/Newsagent> /lib/cpp-precomp -v -lang-objc -D__OBJC__ -D__GNUC__= 2 -D__GNU__ -Dmc68000 -Dm68k -DNeXT -Dunix -D__MACH__ -D__BIG_ENDIAN__ -D__ARCH ITECTURE__="m68k" -D__mc68000__ -D__m68k__ -D__NeXT__ -D__unix__ -D__MACH__ -D_ _BIG_ENDIAN__ -D__ARCHITECTURE__="m68k" Controller.m /usr/tmp/cc006349.cpp NeXT CPP 3.0 /src/Newsagent/Newsagent> grep Vessel /usr/tmp/cc006349.cpp #1 "Vessel.h" 1 @interface Vessel:Object vessel = [Vessel alloc]; /src/Newsagent/Newsagent> /lib/cpp-precomp -smart -v -lang-objc -D__OBJC__ -D__ GNUC__=2 -D__GNU__ -Dmc68000 -Dm68k -DNeXT -Dunix -D__MACH__ -D__BIG_ENDIAN__ - D__ARCHITECTURE__="m68k" -D__mc68000__ -D__m68k__ -D__NeXT__ -D__unix__ -D__MAC H__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__="m68k" Controller.m /usr/tmp/cc006349.c pp NeXT CPP 3.0 /src/Newsagent/Newsagent> grep Vessel /usr/tmp/cc006349.cpp vessel = [ Vessel alloc ] ; /src/Newsagent/Newsagent> cd So this is clearly a compiler problem. The "smart" keyword screws it up. Dave Griffiths
From: doko@cs.tu-berlin.de (Matthias Klose) Newsgroups: comp.sys.next.software,comp.sys.next.bugs Subject: Bug in GNU find 3.8 ? Date: 09 Jul 93 08:50:26 GMT Organization: Technical University of Berlin, Germany Message-ID: <21j803$mv5@news.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit find / -print does not descend in other file systems although the -xdev option is not specified (the fs is NOT a nfs mount). This happens with NS3.0 with cc, gcc 2.4.[35], compiled with and without -O (works correctly on SunOS 4.1, Ultrix ?.?). A workaround is to give find all mount points in the path. Could somebody verfify this on his machine (any version of NS)? Thank you, Matthias
From: doko@cs.tu-berlin.de (Matthias Klose) Newsgroups: comp.sys.next.bugs Subject: Another 'open' bug? Date: 09 Jul 93 09:02:09 GMT Organization: Technical University of Berlin, Germany Message-ID: <21j8m2$n3d@news.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit In NS3.0 open seems to be confused with symbolic links or the /private directory ... % mount /dev/sd1a on /private/MaxBig type 4.3 (rw,noquota) /dev/sd0a on / type 4.3 (rw,noquota,noauto) tango:(autonfsmount[96]) on /Net type nfs (ro,intr,port=695) % ls -l /LocalLibrary lrwxrwxrwx 1 root 28 Oct 2 1992 /LocalLibrary -> /private/MaxBig/LocalLibrary % cd /LocalLibrary % pwd /private/MaxBig/LocalLibrary % ls -l Images/mach.tiff -rw-r--r-- 1 mk 1292 Jan 1 1970 Images/mach.tiff % open Images/mach.tiff open: can't stat file: /MaxBig/LocalLibrary/Images/mach.tiff where is the /private prefix ??? Does open cut it away? Why? workaround is a ln -s /private/MaxBig /MaxBig
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: hsr@cs.Stanford.EDU (Scott Roy) Subject: No file descriptions in Librarian.app Message-ID: <1993Jul9.081453.714@CSD-NewsHost.Stanford.EDU> Sender: news@CSD-NewsHost.Stanford.EDU Organization: CS Department, Stanford University, California, USA Date: Fri, 9 Jul 1993 08:14:53 GMT The helpful file descriptions for the man page entries seem to have disappeared in version 3.1. Worse, ixbuild seems to ignore the -g flag. Has anyone gotten ixbuild to include the descriptions? Scott Roy Department of Computer Science Stanford University
Newsgroups: comp.sys.next.bugs From: nwc (Nick Christopher) Subject: /dev/cua & uucp Message-ID: <C9wF1o.10z@ny.shl.com> Sender: usenet@ny.shl.com (Net News) Organization: SHL Systemhouse Inc. Date: Fri, 9 Jul 1993 13:05:47 GMT The ownership of /dev/cua is set to root every time my machine reboots. This breaks uucp which wants /dev/cua set up as it is by the MAKEDEV script: chmod 600 cua ; chown uucp cua The fix is to put the above line is /etc/rc.local \n Nicholas Christopher Systemhouse nwc@ny.shl.com
From: jholm@jholm.dc.shl.com (Julie Holm) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: DBTableView printing problem. Date: 9 Jul 1993 19:50:14 GMT Organization: SHL Systemhouse Inc. Message-ID: <21ki5mINNknu@technet1.shl.com> I would appreciate some help from you NeXT gurus. One of the programmers here is having a problem printing headers on a report. As Manny puts it: QUESTION> How do you print a DBTableView with column headings included? Using the code below just gives me the . . [myDBTableView printPSCode:nil]; . . rows without headings in the postcript image generated. Please respond to my mailbox or to eericta@dc.shl.com. Thanks. P.S. This is black box 3.0. -- ------------------------------------------------------------------------------- Julie Holm | Some day I will actually think of something to put here. jholm@dc.shl.com | 9617 Verdict Dr. | Vienna, VA 22181| (703)-938-0435 | -------------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: Re: open -a "App name" doesn't work Message-ID: <1993Jul9.185129.15162@altsys.com> Organization: Altsys Corporation, Richardson, TX References: <1993Jul7.181537.26198@altsys.com> <CEDMAN.93Jul8102608@golem.uci.edu> Date: Fri, 9 Jul 1993 18:51:29 GMT Yes, public window server fixes it. Thanks all -- Lorin Rivers Lorin_Rivers@altsys.com Altsys Technical Support 214.680.2518 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
Newsgroups: comp.sys.next.bugs From: frank@dendrite.sps.mot.com Subject: Reading sound files with NS/I Content-Type: text/plain Message-ID: <frank.93Jul9135151@dendrite> Sender: usenet@newsgate.sps.mot.com Organization: SPS Mime-Version: 1.0 Date: Fri, 9 Jul 1993 20:51:51 GMT Anyone had any problems with reading in sound files with Nextstep on an intel processor? I haven't tracked down the problem completely, but I had a working program which read in 16 bit linear sound files. When I re-compiled on the Intel machine, the data seems to be messed up. Anyone have experience with this? - Thanks, Mark
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: robertn@penny.demon.co.uk (Robert Nicholson) Subject: DL Bugs? Distribution: world Cc: nextanswers@next.com Date: Fri, 9 Jul 1993 22:06:53 +0000 Message-ID: <9307092203.AA08623@penny.demon.co.uk> Sender: usenet@demon.co.uk This is an NS3.0 question. Has DL got a retutation for not recognising indexes in a network environment? The .index.store files are there as plain as day but for some reason DL reports that nothing it indexed and I cannot do any searching not even sequential searches.
From: jholm@jholm.dc.shl.com (Julie Holm) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Printing Problems for DBTable View Date: 10 Jul 1993 14:19:27 GMT Organization: SHL Systemhouse Inc. Message-ID: <21mj5fINNd1d@technet1.shl.com> Please Excuse me if this gets posted twice. We were having some problems with our connection, and I don't think the first posting went out! I would appreciate some help from you NeXT gurus. One of the programmers here is having a problem printing headers on a report. As Manny puts it: QUESTION> How do you print a DBTableView with column headings included? Using the code below just gives me the . . [myDBTableView printPSCode:nil]; . . rows without headings in the postcript image generated. Please respond to my mailbox or to eericta@dc.shl.com. Thanks. P.S. This is black box 3.0. -- ------------------------------------------------------------------------------- Julie Holm | Some day I will actually think of something to put here. jholm@dc.shl.com | 9617 Verdict Dr. | Vienna, VA 22181| (703)-938-0435 | -------------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: francisr@stupid.ucs.indiana.edu (Rob Francis) Subject: Empty lock file in a .mbox directory crashes Mail.app Message-ID: <CA31BL.5uJ@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Organization: University Computing Services Date: Tue, 13 Jul 1993 02:52:33 GMT I guess it's a bug that an empty .lock file got created in the first place, but if you try to open a .mbox file (of if your Active.mbox has one) and it has an empty .lock, then Mail.app crashes. This in in Software Version 3.0 (Hyper3B) on Black hardware. -rob --- Rob Francis Unix Systems Specialist, University Computing Services Indiana University, francisr@indiana.edu (812)855-0327
From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) Newsgroups: comp.sys.next.bugs Subject: Frame broken in 3.1? Message-ID: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: 12 Jul 93 14:45:12 GMT Article-I.D.: Tomobiki.MS-C.742538712.1103527590.mrc Organization: University of Washington Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII At least for me it won't work. This evidence appears in my console log: maker: Using /LocalApps/FrameMaker2.0/FrameMaker.app/.fminit2.0 maker: DisplayWidth 1120 DisplayHeight 832 maker: starting postscript download Jul 12 21:44:35 Tomobiki-Cho WindowServer[215]: Can't open `/tmp/debug': context is write-prohibited. maker: finished postscript download maker: Starting FrameMaker 2.0b. Copyright (c) 1986-1989 Frame Technology Corp. maker: Internal error 8.
Newsgroups: comp.sys.next.bugs From: perstoro@uriela.in-berlin.de (Wilhelm Schaefer) Subject: Frame NOT broken in 3.1! Message-ID: <1993Jul13.082939.642@uriela.in-berlin.de> Sender: perstoro@uriela.in-berlin.de Organization: NeXAPP References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: Tue, 13 Jul 1993 08:29:39 GMT In article <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes: > At least for me it won't work. > > This evidence appears in my console log: > > maker: Using /LocalApps/FrameMaker2.0/FrameMaker.app/.fminit2.0 > maker: DisplayWidth 1120 DisplayHeight 832 > maker: starting postscript download > Jul 12 21:44:35 Tomobiki-Cho WindowServer[215]: Can't open `/tmp/debug': context is write-prohibited. > maker: finished postscript download > maker: Starting FrameMaker 2.0b. Copyright (c) 1986-1989 Frame Technology Corp. > maker: Internal error 8. No problem with my machine. Jul 13 10:05:36 uriela su: SU to root by perstoro on /dev/ttyp2 maker: Using /LocalApps/Apps/FrameMaker.app/fminit2.0 maker: Using DEBUG mode maker: DisplayWidth 1120 DisplayHeight 832 maker: starting postscript download maker: finished postscript download maker: Starting International FrameMaker 3.0P1b. Copyright (c) 1986-1991 Frame Technology Corp. maker: Finished loading Everything looks fine. so long *** perstoro *** -- *********************************************************************** *| Wilhelm Schaefer| perstoro@uriela.in-berlin.de | NeXTmail please! |* *| NeXT EnTHUSIAST | Voice +49 30 / 395 31 91 | FAX +49 30/39547 49|* ***********************************************************************
From: grumpl@email.tuwien.ac.at (Gerhard RUMPLMAIR) Newsgroups: comp.sys.next.bugs Subject: Printing white pages after system crash Date: 13 Jul 1993 13:52:25 +0200 Organization: Technical University Vienna, Austria Message-ID: <21u7lp$i1v@email.tuwien.ac.at> Hi, I have a NeXTStation Turbo, running NS 3.0 and a 400 dpi Laser Printer. While printing 20 or so short ManualPages (from CSHell using the man -t command) and trying to start Librarian.app, the System crashed with a message to save an other text document, opened in Edit.app. After reboot, the spooler finished printing without any problem. Since this happened, printing text documents with the following applications results in white pages: Librarian.app, Edit.app, Mail.app, ... ?. - Inspecting the printout with Preview.app also shows nothing in the window, and it is not possible, to print any preformatted *.ps document in this Application. But printing with Mathematica.app, or again printing from the CSHell with ptroff, or testing the printer with PrintManager.app, or if possible, inspecting the printout with Preview.app results in printouts or visible representations respectively, as it should be expected. Has anyone an explanation and can help me to overcome this nasty behavior? It seems, that any obscure interface to the ps-System now is missing or some file has been overwritten. - Searching the manuals on the related item is a little "Searching for Treasure in all the Wrong Places", I can't find anything useful about. Please send responses to: grumpler@micro1.tuwien.ac.at If there are any reactions of common interest, I shall post a summary to this newsgroup. Thanks. grumpler
From: jmd@cube.handheld.com (Jim De Arras) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.next.bugs Subject: NetWare and Partner/Ushare not compatible? Date: 13 Jul 1993 12:58:22 GMT Organization: Hand Held Products, Inc. Distribution: world Message-ID: <21ubheINN2ke@clem.handheld.com> In both beta releases, and now the final release, which I just bought, Partner/UShare does NOT work with NetWare is active. Anyone else had similiar/different experences? Also, I'm STILL having NFS problems with Partner/UShare running, the NeXT stops "sharing" it's drives via NFS. I have the latest Partner/UShare which is susposed to correct that, too. IMHO, Partner/UShare is not ready for release. Jim -- ---------------------------------------------------------------------------- Jim De Arras - WA4ONG | "Government is not reason. It is not eloquence. NRA,ILA | it is a force, like fire a dangerous servant jmd@handheld.com | and a terrible master." -- George Washington
From: mfausett@bbn.com (Mark Fausett) Newsgroups: comp.sys.next.bugs Subject: Re: Frame NOT broken in 3.1! Date: 13 Jul 93 17:55:30 GMT Message-ID: <mfausett.742586130@kirin> References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> <1993Jul13.082939.642@uriela.in-berlin.de> mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes: > At least for me it won't work. > > This evidence appears in my console log: > > maker: Using /LocalApps/FrameMaker2.0/FrameMaker.app/.fminit2.0 > maker: DisplayWidth 1120 DisplayHeight 832 > maker: starting postscript download > Jul 12 21:44:35 Tomobiki-Cho WindowServer[215]: Can't open `/tmp/debug': context is write-prohibited. > maker: finished postscript download > maker: Starting FrameMaker 2.0b. Copyright (c) 1986-1989 Frame Technology Corp. > maker: Internal error 8. Two things; WHY possibly couldn't it open /tmp/debug? does one already exist? The current version of frame is 3.01; 3.0 at least works VERY well under NeXTStep 3.0 (Still deciding whether to go to 3.1...) mf
Newsgroups: comp.sys.next.bugs From: mdixon@parc.xerox.com (Mike Dixon) Subject: Re: Frame broken in 3.1? Message-ID: <mdixon.742602914@thelonius> Sender: news@parc.xerox.com Organization: Xerox PARC References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: 13 Jul 93 22:35:14 GMT i've been using Frame 3.0.1 under NS 3.1 with no problems. .mike.
Newsgroups: comp.sys.next.bugs From: wave@pixar.com (Michael B. Johnson) Subject: Re: Frame broken in 3.1? Message-ID: <1993Jul14.055521.2224@pixar.com> Sender: news@pixar.com (Usenet Newsmaster) Organization: Pixar -- Point Richmond, California References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: Wed, 14 Jul 1993 05:55:21 GMT In article <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes: > At least for me it won't work. > I run Frame 3.0 (I know, I know, you're talking about 2.0 but...) under 3.1 with no problems. upgrade the app or downgrade the OS... -- --> Michael B. Johnson -- wave@media.mit.edu, wave@pixar.com --> MIT Media Lab -- Computer Graphics & Animation Group --> P*I*X*A*R -- IceMan Group (for the summer)
Newsgroups: comp.sys.next.bugs From: anderson@macc.wisc.edu (Jess Anderson) Subject: Re: Frame NOT broken in 3.1! Message-ID: <1993Jul14.121825.21332@macc.wisc.edu> Sender: news@macc.wisc.edu (USENET News System) Organization: Division of Information Technology, UW-Madison References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> <1993Jul13.082939.642@uriela.in-berlin.de> <mfausett.742586130@kirin> Date: Wed, 14 Jul 93 12:18:25 GMT In article <mfausett.742586130@kirin> mfausett@bbn.com (Mark Fausett) writes: >The current version of frame is 3.01; 3.0 at least works VERY well under >NeXTStep 3.0 (Still deciding whether to go to 3.1...) Quite in another direction, I've noticed a very peculiar thing. Recently I got an ISDN connection at home. It runs very nicely through a Combinet bridge, which pops up the connection to the campus network any time there's traffic directed off my local LAN here at the house. FrameMaker (3.0 running under NS 3.0) seems to generate such traffic: while running if I stay in it long enough and in any case (this is the *really* curious part) when I quit it. Maybe it's looking for NFS-mounted volumes (I have none) or something, but it's not especially desirable behavior, since there are cost consequences for spurious connections. Anyone else seen this or have any idea what to do about it, if anything? -- [Jess Anderson <> Division of Information Technology, University of Wisconsin] [Internet: anderson@macc.wisc.edu <-best, UUCP:{}!uwvax!macc.wisc.edu!anderson] [Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888] [----------> We would often be sorry if our wishes were gratified. <----------]
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: Frame NOT broken in 3.1! Message-ID: <Jul14.142155.76188@acs.ucalgary.ca> Date: Wed, 14 Jul 1993 14:21:55 GMT Distribution: na References: <MS-C.742538712.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> <1993Jul13.082939.642@uriela.in-berlin.de> <mfausett.742586130@kirin> Organization: The University of Calgary, Alberta > > Jul 12 21:44:35 Tomobiki-Cho WindowServer[215]: Can't open > > `/tmp/debug': context is write-prohibited. > Two things; > WHY possibly couldn't it open /tmp/debug? does one already > exist? The current version of frame is 3.01; 3.0 at least > works VERY well under NeXTStep 3.0 (Still deciding whether to > go to 3.1...) > > mf Note that the original poster is using FrameMaker 2.x and yes, it is broken you'll need to upgrade to 3.01. I've been using Frame 3.01 under NeXTSTEP 3.1 without any unusual problems. -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
From: ccoffin@coal.Mines.Colorado.EDU (coffin) Newsgroups: comp.sys.next.bugs Subject: SoftPC Windows broken under 3.1 (or at least Windows 3.1 part). Keywords: 3.1 SoftPC Message-ID: <1993Jul14.154126.26584@slate.mines.colorado.edu> Date: 14 Jul 93 15:41:26 GMT Sender: news@slate.mines.colorado.edu Organization: Colorado School of Mines Has anyone else had difficulties getting SoftPC 3.1 "Windows" mode to work under 3.1? It worked fine for me under 3.0, but now, when I type "Win," I get the Microsoft Windows 3.1 banner, but after than only blackness (usually), and an occassional error about something to do with the "DOS Extender" with a printout of 286 register contents. I can get Windows to work, by rebooting the computer and making a new Windows disk file, but as soon as I quit and restart, the problem occurs again. An error message on the Console window says something about and IPC not flushing. I contacted Insignia, but they have yet to find a solution for me. By the way, the system I use is a 25Mhz 040 (16 meg parity) and 8 meg NeXTdimension board cube. The Insignia guys first thought I was running out of memory, but not once has my swap file run out of space. Thanks for any suggestions, C Coffin ccoffin@mines.colorado.edu
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: SoftPC Windows broken under 3.1 (or at least Windows 3.1 part). Message-ID: <1993Jul14.180803.25012@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSO, Stanford University References: <1993Jul14.154126.26584@slate.mines.colorado.edu> Date: Wed, 14 Jul 93 18:08:03 GMT > Has anyone else had difficulties getting SoftPC 3.1 "Windows" > mode to work under 3.1? I've had very mixed results running the SoftPC demo version that came on ther NS3.1/moto CD-ROM. Sometimes it runs, sometimes it hangs after the Windows banner. Going into preferences and increasing the RAM available to Windows seems to help. I also find it obnoxious that this app litters my home directory with files such as "cmos.ram." All in all, not a very convincing demo. Can anybody who has the `real thing' comment on whether these are due to demo being crippled or whether they are actual `features' of the full release? -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@frinext.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
From: wmorse@erasure-sl.cc.emory.edu (William Morse) Newsgroups: comp.sys.next.bugs Subject: Possible Bugs <ie: please check these out and reproduce> Message-ID: <222f9vINN1ac@emory.mathcs.emory.edu> Date: 15 Jul 93 02:27:11 GMT Article-I.D.: emory.222f9vINN1ac Distribution: world Organization: Emory University, Dept of Math and CS Ok... before I list the following possible problems that I have found, let me state that I do not want this stuff used in a nasty "NeXTStep is garbage" flame war. NeXTStep 3.1 for moto. has turned out to be a VERY stable and relatively bug free system for me with a few exceptions listed below. For comparison, Windows 3.1 crashes on me generally four times per day, OS/2 generally 2 and NeXT has crashed four (4) times since I have had my Color Turbo... which is almost one year. That is FOUR TIMES FOLKS! So, while there is no excuse for bugs, we need to put things in perspective. After all, you could be using some other system... (PS - my Sun crashed more than NeXT (about twice per month.) As for the Intel system, I have seen it and it seems to be very robust (I am getting a system shortly). I feel that NeXT has been very open with the serial problems and actually feel *comforted* by their response. I am surprised many of you do not. Most companies I know would simply ignore your complaints... So what is the purpose of this post? To see if other people can reproduce these suspected bugs and to inform you all of work-arounds I have found. 1) Hostmanager - will not properly add (or edit) aliases to hosts. [If you open Hostmanager as root and create a new host in 3.1 and then try to add aliases, you will find that NetInfo knows of the new host, but "forgets" the aliases. You can see this if you save the new host with alias and then reload the host. The aliases are gone. All other settings are saved.] Work around - use NetInfo directly... Go under the machines directory, click on the machine you want to add an alias to, go under the directory menu and click new value. Then type in the alias you wish and then save. This will save the alias properly. To see that this is so, open Hostmanager and it will be there. Finally, it appears that you need Hostmanager to add the hosts initially. I can't seem to get NetInfo to do that part. 2) Terminal and telnetd probs - Telnetd under 3.0 worked properly under 3.0 but now seems to have some problems. For example, using many third party telnet packages to telnet to a NeXT will result in you staring at a "Login:" and not getting any further. This is true with the OS/2 telnet package. (It worked under 3.0.) The solution for many of these packages is to alter the third party telnet package to crlf. (OS/2, for example, works if you type telnet, then "set crlf" and then "open <NeXT machine name>." The terminal seems to be suffering from similar problems. For example, telnet back to your own machine and then <return> past the first "Password:". You should then see "Login:" Now, either with your username or password, make a mistake and don't correct it. You will find that terminal seems to lock. "^]" also seems to do no good at first, but if you keep on doing it, you get to "telnet>" but it locks again as soon as you press return. Work around - don't make mistakes. :) 3) Weird Newsgrazer problem - Install Newsgrazer as root... in somewhere like /LocalApps then run it as a user. It won't show in the "process" area of the Workspace. All other apps show up as usual. However, if you install it as a user in your own /LocalApps, it will now show up in process. Now, if you open a terminal window and type ps -x, it shows up. This behavior was not in 3.0. Anyone have any idea what the deal is here? My version is Release 2.0 72.3... Other than this, I have found no other oddities. (PS - no other app exhibits this behavior and I have replaced my 72.3 with a clean one...) 4) Serious sound problem - Warning: this will and has resulted in crashes on my Color Turbo ADB and does every time. By crashes, I mean a system panic. Ok, what you do is "over tax" the sound buffer of the DSP. As an example, pick a rather long "system beep" (like one that lasts a two seconds or so) and replace the current one you have with it. To do this, go under preferences, click the cube picture and "highlight" the new sound. Now, every time you click this "sound" the computer will demo it. To make your system totally die, click that sound over and over for about 15-25 times. It WILL crash the NeXT. Other things that will are two apps using the DSP at the same time or otherwise PUSHING it... with sound. Playing single mods... sounds etc. at one time is no problem. Work around - don't do the above described. What I would like is if Net Land would please confirm (ie. reproduce) these things on their systems to see if these are bugs. Then, hopefully some of us will be able to determine *why* these things are happening and pass it on to NeXT. Ok... Thanks! - William *My Words are MINE and MINE alone* Consult. / ITD ::::::::::::::::::::::::::::::::::::::::::::: Emory Law Student
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: Floppy Bug? Message-ID: <122@boschrt.rt.bosch.de.bosch.de> Date: 15 Jul 93 12:58:26 GMT Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. Hi here the short description of the bug. If you want to know the whole story read all. I have an EISA/VLB Board with Adaptec 1542B and 486/66Mhz SIS Chipsatz, Award Bios (:-(), ATI GUP VLB and 32 MB RAM When I want to boot, the following message is printed: Floppy Controller Reset: Command Timeout fd0: Sector 0 cmd = Read; fd_ioreq.timeout exceeded: Retrying This happens twice then instead of Retrying Recalibrating occurs. This happens 4 or 5 times then it says failed I get some messages. At the end it says: RDP........(type 'c' to continue) but with c nothing happens. Any idea? I installed NSFIP on an ISA Board with AMI BIOS 16MB RAM and ADAptec 1542B and ATI GU ISA BUS. Everything went fine. I changed the board and card and now I had colours and a fast machine (look above). I could mount floppies and so on. Then I decided to install all, the developpers, too so I had to reinstall everything. I tried, but the message above stopped me. DOes anyone know the problem? Isn't it strange that it works when NSFIP is installed and it works with all other OS? Only the boot disk at boot time. But the disk is ok, with the other board I can boot and install. :-( --- /********************************************************************/ /* Kay Schulz, Rheinstr. 24, 72768 Reutlingen, Germany */ /* 07121 / 60 19 61 privat */ /* 07121 / 35-1341 geschaeftlich */ /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/
Newsgroups: comp.sys.next.bugs From: kunal@passion.pilot.dmg.ml.com (Kunal Singh) Subject: Simon Says Message-ID: <CA7Kop.IFq@tigadmin.ml.com> Sender: kunal@passion (Kunal Singh) Organization: Merrill Lynch Debt Markets Group Date: Thu, 15 Jul 1993 13:41:12 GMT Well, I've read plenty of postings about Simon Says not working in 3.1. And its true !! Did anyone get a response from the company, or a patch perhaps ?
Newsgroups: comp.sys.next.bugs From: imagine.com!michael (Michael Ellis) Subject: a problem freeing vended objects Message-ID: <1993Jul6.142813.1066@imagine.com> Keywords: Distributed Objects, NeXTStep Sender: michael@imagine.com Organization: Imagine Multimedia, Inc., Ann Arbor, MI, USA Date: Tue, 6 Jul 1993 14:28:13 GMT I have a client-server situation where a client calls a server method and asks for a reference to an object, the server's method allocates the object and returns it to the client. The client frees the object by sending a free message to the object's proxy. So far so good, everything works fine. However, when I look at the server using MallocDebug the object allocation shows up as a memory leak, i.e. the server's object isn't being freed! According to the D.O. documentation, the server's object should be deallocated when the reference count on the object drops to zero. I have checked the reference count immediately before calling free and it is 1. So what gives? Why isn't the REAL object being freed? It is easy to reproduce this problem. Try the following: Write a server with a "- doit" method that returns an NXData instance by reference. Write a client program that connects to the server, calls "- doit" twice, each time freeing the NXData instance immediately. You have to call the server's method twice in order for MallocDebug to register the first allocation as a leak. This error occurs for all classes I have tried not just NXData. It also occurs on both Black HW running 3.0 and on White HW running 3.1 Pointers?
Newsgroups: comp.sys.next.bugs From: sanguish@digifix.com (Scott Anguish) Subject: Re: Simon Says Message-ID: <1993Jul15.192522.4317@digifix.com> Sender: sanguish@digifix.com (Scott Anguish) Organization: Digital Fix Development References: <CA7Kop.IFq@tigadmin.ml.com> Date: Thu, 15 Jul 1993 19:25:22 GMT Kunal Singh writes > > Well, I've read plenty of postings about Simon Says not working in 3.1. And > its true !! > > Did anyone get a response from the company, or a patch perhaps ? Metrosoft aquired Simon Says from HSD and made an announcement about the 3.1 incompatiblities and that there is an upgrade. Try info@metrosoft.com -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
From: Conrad_Geiger@NeXT.COM (Conrad Geiger) Newsgroups: comp.sys.next.bugs Subject: Re: Simon Says (voice recognition package for NEXTSTEP) Date: 15 Jul 1993 17:01:03 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9307152115.AA01629@seawolf.next.com> In a recent article: kunal@passion.pilot.dmg.ml.com (Kunal Singh) says: >>Well, I've read plenty of postings about Simon Says not working in >>3.1. And its true !! >>Did anyone get a response from the company, or a patch perhaps ? Here is the response from Metrosoft with news about "Simon Says" - the voice recognition package for NEXTSTEP: Conrad Geiger NeXT _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ From: mary@metrosoft.com (Mary Donnelly) Subject: Simon moves to Metrosoft Currently anyone using SimonSays cannot run the program under NEXTSTEP 3.1. Metrosoft is now the owner of Simon and will be coming out with 2 important updates. SimonSays 2.0 will be out in Sept-Oct and will be fat. Enhancements include... 1. Better voice training 2. More intuitive user interface 3. More macro event types 4. Nested macros - i.e., macros that perform other macros 5. The ability to save and load macro sets 6. Will run on both NeXT and Intel. There is an intermediate upgrade, SimonSays 1.5. Simon 1.5 will run under NEXTSTEP 3.1, but doesn't have any other enhancements. When pre-ordering Simon Says 2.0, you can receive version 1.5 now for free. The 2.0 upgrade is $39. Or if you prefer you can receive SimonSays 1.5 for free now and decide to purchase the 2.0 upgrade later. A $10 materials and handling fee will be charged for the 1.5 update when ordered separately ($39 for Simon 1.5 and 2.0 OR $10 for 1.5 now and $39 for 2.0 later). Please forward a copy of your key when ordering (as proof of registration) and your full postal address to mail the disk (if you prefer NeXtmail there will be a one week delay while we sort out key generation issues). If you have any questions let us know. We accept Visa and MasterCard (please include expiration date). from Sunny San Diego, Mary Donnelly, Metrosoft vox: 619.488.9411 fax: 619.488.3045 info@metrosoft.com [NeXTmail welcome] 740 13th Street, Suite 503 - San Diego, California 92101 USA also..... MetroSuction is a commercial-quality utility for examining and removing support for different hardware architectures in Multi-architecture Binaries (MABs) or "fat binaries". Fat binaries allow the same NEXTSTEP program to run on different types of computers (currently NeXT computers and supported Intel-based computers). Metrosuction allows you to easily see which architectures are supported by a given application and to remove support for a given architecture, freeing up disk space. This is free via anonymous FTP sonata.cc.purdue.edu and cs.orst.edu. Feel free to give away copies! also... MetroTools MetroTools is a package of six utilities to enhance your NEXTSTEP productivity. The dock extender is regarded as the most powerful available and operates as a natural extension of the NeXT dock. You can create groups of applications and documents, show their names, use miniature icons, launch complete groups with a single double-click and much, much more. Font Installer greatly simplifies the process of installing NEXTSTEP fonts, and converting Macintosh-based PostScript fonts for use on your NEXTSTEP computer. In fact you can install megabytes worth of fonts in a variety of formats, using a single drag followed by a button click. NiteLite has screen-locking and backdrop features, run multiple modules simultaneously and run while the NEXTSTEP login window is up. MetroTools will help you find your files and allow you to quickly compress, examine and decompress file archives. MetroTools also offers an expandable shell that other developers can use to develop their own tools. Free technical support. Price $89 / $59 special to SimonSays owners. (add $5 shipping and handling, $10 outside USA)
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: Simon Says Message-ID: <1993Jul15.220149.13352@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSO, Stanford University References: <CA7Kop.IFq@tigadmin.ml.com> Date: Thu, 15 Jul 93 22:01:49 GMT Kunal Singh writes > Well, I've read plenty of postings about Simon Says not working > in 3.1. And its true !! > > Did anyone get a response from the company, or a patch perhaps ? An e-mailing has come out about it from MetroSoft, who recently acquired Simon. A patched version is available and an upgraded version will ship later in the year. I quote: > Currently anyone using SimonSays cannot run the program under > NEXTSTEP 3.1. Metrosoft is now the owner of Simon and will be > coming out with 2 important updates. > > SimonSays 2.0 will be out in Sept-Oct and will be fat. Enhancements > include... [deleted] > > There is an intermediate upgrade, SimonSays 1.5. Simon 1.5 will run > under NEXTSTEP 3.1, but doesn't have any other enhancements. You can get more info from > info@metrosoft.com [NeXTmail welcome] -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@frinext.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
Newsgroups: comp.sys.next.bugs From: royce@splunge.uucp (Royce Howland) Subject: Re: Possible Bugs <ie: please check these out and reproduce> Message-ID: <1993Jul15.132922.7925@splunge.uucp> Organization: Ashley, Howland & Wood References: <222f9vINN1ac@emory.mathcs.emory.edu> Date: Thu, 15 Jul 1993 13:29:22 GMT wmorse@erasure-sl.cc.emory.edu (William Morse) writes: >... >So what is the purpose of this post? To see if other people can reproduce >these suspected bugs and to inform you all of work-arounds I have found. >1) Hostmanager - will not properly add (or edit) aliases to hosts. [If >you open Hostmanager as root and create a new host in 3.1 and then try to add >aliases, you will find that NetInfo knows of the new host, but "forgets" the >aliases. You can see this if you save the new host with alias and then reload >the host. The aliases are gone. All other settings are saved.] Work around - use >NetInfo directly... Go under the machines directory, click on the machine you >want to add an alias to, go under the directory menu and click new value. Then >type in the alias you wish and then save. This will save the alias properly. >To see that this is so, open Hostmanager and it will be there. Finally, it >appears that you need Hostmanager to add the hosts initially. I can't seem >to get NetInfo to do that part. >... >What I would like is if Net Land would please confirm (ie. reproduce) these >things on their systems to see if these are bugs. Then, hopefully some of >us will be able to determine *why* these things are happening and pass it >on to NeXT. Ok... Thanks! I can confirm HostManager's behavior with aliases under NS 3.1 for Intel. I will also add that the same problem applies when trying to use the app to work on a machine's netgroups. No matter what netgroup changes you make in HostManager, they're thrown away. Again, this is under NS 3.1 for Intel, but I wouldn't be surprised if 3.1 black has the same problem. -- Royce Howland, DKW Systems Corp. | "And since OS/2 2.0 is a 32-bit Everything is IMHO | operating system, programs are royce@splunge.uucp (NeXTMail OK) | easier to write and run faster, or kakwa!atlantis!splunge!royce | too." -ad for OS/2 2.0
Newsgroups: comp.sys.next.bugs From: mihe@gordon.enea.se (Mike Henry) Subject: Re: Possible Bugs <ie: please check these out and reproduce> Message-ID: <1993Jul16.084045.27658@enea.se> Sender: usenet@enea.se Organization: ENEA DATA AB, Stockholm, Sweden References: <222f9vINN1ac@emory.mathcs.emory.edu> Date: Fri, 16 Jul 1993 08:40:45 GMT In article <222f9vINN1ac@emory.mathcs.emory.edu> wmorse@erasure-sl.cc.emory.edu (William Morse) writes: >So what is the purpose of this post? To see if other people can reproduce >these suspected bugs and to inform you all of work-arounds I have found. > >1) Hostmanager - will not properly add (or edit) aliases to hosts. [If >you open Hostmanager as root and create a new host in 3.1 and then try to add >aliases, you will find that NetInfo knows of the new host, but "forgets" the >aliases. You can see this if you save the new host with alias and then reload >the host. The aliases are gone. All other settings are saved.] >Work around - use NetInfo directly... Go under the machines I can confirm this on a NeXTstation Turbo Mono after upgrading to NS3.1 >- William -Mike -- Mike Henry INET : mihe@enea.se /// Box 232 /// S-183 23 Taby TEL : +46 8 792-2500 \\\/// SWEDEN TFX : +46 8 768-4388 \XX/
Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin,comp.sys.next.bugs From: jds@aplpy.jhuapl.edu (John D Stanhope) Subject: Dell and Adaptec Message-ID: <1993Jul16.184504.12770@aplcen.apl.jhu.edu> Sender: news@aplcen.apl.jhu.edu (USENET News System) Organization: Johns Hopkins University Applied Physics Lab Date: Fri, 16 Jul 93 18:45:04 GMT Has anyone got the below error on there system and been able to fix it? AHA interrupt: bad status ff sd0: INVALID STATUS (Internal error): FATAL ERROR target:0 lun: 0 op: Read block: some # blockcount: some # I am trying to get NS/i to use the scsi drive with out totally destroying it before any serious work can be done. I tried 3 different irq's (10,11,15) and 3 dma channels (5,6,7) and they gave me this error when booting. And when I woudl try to intialize the disk using disk I would get write error and newfs would fail. If I use the settings specified by NeXT I can init the disk and use it for a while but eventualy causes a system panic. If any out there has been able to get the ATI EISA card and an Adaptec card to work PLEASE respond. If any has an Adaptec card working in a Dell 450[DM]E please tell, especially if you had to do some tweaking to get it to work.o Even though some said this is a conflict between the two cards and the DELL I seem to remember having the same problem using an older ATI card for the VGA display. Could this be a DRIVER BUG? Any and all responses are welcomed. John Stanhope
Newsgroups: comp.sys.next.bugs From: uunet!sci34hub!tybrin4!holli!me (Trey McClendon) Subject: Re: Frame NOT broken in 3.1 (except on print servers??)! Message-ID: <1993Jul17.031930.11798@holli.uucp> Sender: me@holli.uucp (My Account) Organization: TYBRIN Corporation -- Huntsville, AL References: <1993Jul14.121825.21332@macc.wisc.edu> Distribution: usa Date: Sat, 17 Jul 1993 03:19:30 GMT In article <1993Jul14.121825.21332@macc.wisc.edu> anderson@macc.wisc.edu (Jess Anderson) writes: > In article <mfausett.742586130@kirin> mfausett@bbn.com (Mark > Fausett) writes: > > >The current version of frame is 3.01; 3.0 at least works VERY well under > >NeXTStep 3.0 (Still deciding whether to go to 3.1...) > As long as we're on Frame... Framemaker 3.01, when run on a NeXT connected to a printer, goes haywire 90% of the time when someone prints from another computer on the network. We are runnning NS3.0 By 'haywire' I mean one of the following: - the document page goes black - the document window takes on bit-maps of other parts of the screen - any particular frame panel might be sovered with text from the document - the rulers in the document window might replicate and run rampant We haven't noticed any data loss yet, thankfully. Quitting the app and restarting gets things back to normal. Is this just a Frame-ism that must be lived with? Maybe upgrading to 3.1 will end this silly behavior??? Just wondering, Trey tybrin4!trey@sci34hub.sci.com -- Trey McClendon, Madison, AL
From: ctm@ardi.com Newsgroups: comp.sys.next.bugs Subject: set-user-id bit cleared inappropriately under NS 3.1 Message-ID: <CAC3EK.HMw@cobra.cs.unm.edu> Date: 18 Jul 93 00:15:58 GMT Article-I.D.: cobra.CAC3EK.HMw Sender: news@cobra.cs.unm.edu Organization: ARDI The man page write(2) says: If the real user is not the super-user, then write clears the set-user-id bit on a file. This prevents penetration of system security by a user who "captures" a writable set- user-id file owned by the super-user. but apparently a write clears the set-user-id bit on a file even if you are root. This introduces all sorts of (frequently subtle) problems. I most recently was bitten when I was in a disk cleaning frenzy and I did a bunch of "strips". I managed to turn a set-uid-bit off on "queue-pr", the thing that files problem reports sent to us. Luckily I found it two days later and the missing reports could be recreated from a log of all filed reports. yahoo. I submitted this bug to NeXT a long time ago, but this time when I got bitten I remembered c.s.n.b. --Cliff __________________ This .sig, which mentions Executor being on sale until 93-08-31, uses fewer characters than most. ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Re: SoftPC Windows broken under 3.1 (or at least Windows 3.1 part). Message-ID: <1993Jul18.051447.1332@dolphin.com> Sender: zac@dolphin.com Organization: Dolphin Software References: <1993Jul14.180803.25012@leland.Stanford.EDU> Distribution: usa Date: Sun, 18 Jul 1993 05:14:47 GMT Stefano Pagiola writes > I've had very mixed results running the SoftPC demo version that came > on ther NS3.1/moto CD-ROM. Sometimes it runs, sometimes it hangs > after the Windows banner. Going into preferences and increasing the > RAM available to Windows seems to help. I also find it obnoxious > that this app litters my home directory with files such as > "cmos.ram." > > All in all, not a very convincing demo. Can anybody who has the > `real thing' comment on whether these are due to demo being crippled > or whether they are actual `features' of the full release? I have had very good success with the "official" version of SoftPC with Windows. Also, you might try creating a ".hidden" file in your home directory (copy it from the root directory) and add anything that you don't want to see in your home directory. I agree, SoftPC should put these things in ~/Library/SoftPC, but... I've set up SoftPC, used both Windows 3.1 and the installed DOS 5.0 successfully, and had very few problems. I have also managed to upgrade the version of DOS to 6.0, but I might add... DON'T try to use the disk compression of 6.0. You'll make your SoftPC disk unusable, as far as I can tell. Otherwise, it works great. -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Re: Frame NOT broken in 3.1 (except on print servers??)! Message-ID: <1993Jul18.051800.1391@dolphin.com> Sender: zac@dolphin.com Organization: Dolphin Software References: <1993Jul17.031930.11798@holli.uucp> Distribution: usa Date: Sun, 18 Jul 1993 05:18:00 GMT Trey McClendon writes > Framemaker 3.01, when run on a NeXT connected to a printer, goes haywire > 90% of the time when someone prints from another computer on the network. > We are runnning NS3.0 By 'haywire' I mean one of the following: > > - the document page goes black > - the document window takes on bit-maps of other parts of the screen > - any particular frame panel might be sovered with text from the document > - the rulers in the document window might replicate and run rampant I'm afraid these bugs are still present under NeXTSTEP 3.1. It's a Frame problem, not NeXTSTEP. I've experienced these things as well, and have learned in time a general guideline of what causes it to happen and not. One thing that definately helps is using Frame on a machine with plenty of memory. The only solution I know of to any of these problems is to quit the app and restart it. Of course, now that it looks like Frame won't be ported to Intel... what's it matter? Time to buy Pages! :-) :-) -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Re: Frame broken in 3.1? Message-ID: <1993Jul18.052114.1448@dolphin.com> Sender: zac@dolphin.com Organization: Dolphin Software References: <mdixon.742602914@thelonius> Distribution: usa Date: Sun, 18 Jul 1993 05:21:14 GMT Mike Dixon writes > i've been using Frame 3.0.1 under NS 3.1 with no problems. > .mike. Hm. I'd like to know how much memory you have available, how much free disk space, and how large your documents tend to be. With this I might be able to gauge how much strain Frame is under. We encounter problems with Frame periodically, though nothing terribly fatal (sometimes we have to save and quit, but there is no data loss). Most of the problems seem to be postscript bugs, and tend to happen when we are editing very large books (several hundred pages). Just curious... -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Max number of user processes... How to get more? Message-ID: <1993Jul18.052954.1505@dolphin.com> Sender: zac@dolphin.com Organization: Dolphin Software Distribution: usa Date: Sun, 18 Jul 1993 05:29:54 GMT Did anyone find the boot parameter that will allow an increase in the number of user processes under NeXTSTEP 3.1? I've run into the "no more processes" problem a few times now. I have noted that it helps greatly to reboot your machine on a more-or-less daily basis. That helps to keep <mach tasks> and other things down... and seems to help the user process problem as well. The worst thing I've run into on this is that... if you run out of processes, NeXTMAIL doesn't notify you. It continues to blindly attempt to send messages. What it is ACTUALLY sending are empty messages (groan!). If you use your outgoing mailbox, you'll find that NeXTMAIL (not normal mail) fails to bundle up properly--and whomever you send mail to gets an empty mail message (nothing more than the mail header). Sigh. -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: set-user-id bit cleared inappropriately under NS 3.1 Message-ID: <1993Jul18.121526.2747@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <CAC3EK.HMw@cobra.cs.unm.edu> Date: Sun, 18 Jul 1993 12:15:26 GMT In article <CAC3EK.HMw@cobra.cs.unm.edu> ctm@ardi.com writes: -> The man page write(2) says: -> -> If the real user is not the super-user, then write ->clears the set-user-id bit on a file. This prevents ->penetration of system security... [snip] ALSO --- the `tar' command under 3.1 does NOT properly extract links to suid files. Extracting SLIP from the compressed `backup' after the 3.1 upgrade, I found that the dudisc processes had multiplied -- no longer symbolic links to the original, they were now each their own executable. (Submitted last week via Bug-NeXT) This is not a SERIOUS problem under normal circumstances where the suid-root application is not often modified BUT where one IS expected to have the benefits of soft-links i.e. for renaming, it can be a REAL problem if only the base file is updated and the links-now-shadows are not updated in parallel. Bruce Gingery bruce@TotSysSoft.com Total System Software -- the makers of DFax
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: 3.1NS - Workspace: Drag service protocol error Message-ID: <1993Jul18.122229.2850@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Sun, 18 Jul 1993 12:22:29 GMT I presume that this has been posted about before, but not sure, as I've not had the time to closely follow this group. (Bug-NeXT submitted) This bug seems to have something to do with COMPRESSING a folder then attempting to drag the resulting compressed bundle icon. The Workspace generates repeated errors to the console... >Jul 18 05:30:21 Workspace: Drag service protocol error. though I have my syslogd.conf set down to the debug level so can't say if this appears in all cases. The Browser symptoms are sluggish and odd with regard to mouse events. The dragged icon moves slightly (double-images) and slides back, refusing to follow the mouse cursor. Releasing the mouse button causes any subsequent clicks to affect the right hand browser column, even if off-the-side of the actual window. Recovery is logout OR get to an unmodified directory in the browser on a leftward column -- then return and drag to your hearts content (until the next time). Unix expert setting helps in finding unmodified directories. :) Bruce Gingery bruce@TotSysSoft.com Total System Software the makers of DFax
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: sendmail launced uux hangs == no lock Message-ID: <1993Jul18.122650.3001@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Sun, 18 Jul 1993 12:26:50 GMT With the `-r' switch removed from sendmail.cf in the uucp configuration for uu mail links (causes non-delayed launch of outgoing mail) IF any other process can get to the port between the uux check and the uucico siezing, the port remains busied when released and the uucico processes can multiply. This is a rare condition, with a quite modified setting for sendmail.cf and contrary to the recommended use of cron events for polling, as such has not been submitted to Bug-NeXT (yet at any rate). Bruce Gingery bruce@TotSysSoft.com Total System Software the makers of DFax
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: rc (standard) uu-LCK cleanup is AFTER rc.local Message-ID: <1993Jul18.123002.3065@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Sun, 18 Jul 1993 12:30:02 GMT This applies only to such processes as SLIP which may dial out DURING rc.local time. The cu LCK file cleanup in /etc/rc occurs AFTER the invocation of rc.local. Any processes which dial out from rc.local (i.e. invoked rc.uucp or rc.slip) will find the LCK queue in the state it was in when the system was halted or rebooted, and have their own VALID LCK.. files deleted by subsequent rc processing. This has been submitted to Bug-NeXT Bruce Gingery bruce @TotSysSoft.com Total System Software the makers of DFax
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Class-name parameter-name collisions Message-ID: <1993Jul18.123824.3163@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Sun, 18 Jul 1993 12:38:24 GMT Submitted to Bug-NeXT as either a documentation or compiler bug... #import <objc/Object.h> @interface MyClass : Object { } - doSomething; - doSomething:withSomething; - doSomething:withSomething MyClass:(BOOL)someTest @end Compiler barfs on the second usage of the Class name in the method declaration, stopping its parsing BEFORE the Class name. Why would one WANT to use it there? Obviously, to select in or out the usage of the class as a potential target of message forwarding. Not necessary, just in-code documentation. Bruce Gingery bruce@TotSysSoft.com Total System Software the makers of DFax
Newsgroups: comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Re: Frame broken in 3.1? Message-ID: <1993Jul18.222438.593@dolphin.com> Sender: zac@dolphin.com Organization: Dolphin Technologies Inc. References: <1993Jul18.052114.1448@dolphin.com> Distribution: usa Date: Sun, 18 Jul 1993 22:24:38 GMT John Bartley <john@wpa.com> writes: How do YOU know this? Are you guessing, or just blowing? I've been using FrameMaker for very large and complex documents since July 1990, through every version of NeXTSTEP and every version of FrameMaker and have NEVER experienced ANY of these problems, nor have I ever seen them complained about on the net until the last week. I've gotten black pages a few times with Word Perfect, but never with Frame. I say: In response to your message, I'll lead in by saying that there are few people who know more about FrameMaker on NeXTSTEP than I do, at least outside of Frame (sounds rude, I know, but I've been using it for a long time). I'll add that everything I wrote is correct and true, and I'll justify it too: I know from experience. I've been using FrameMaker for almost everything that I do on NeXT since it was first released on the platform. I also use it on Windows, Sun and Macintosh systems, since the books and other documentations that we produce must be sent to press. There is nothing that beats Frame when it comes to cross-platform capabilities. However, I also experience the problems I described on a regular basis. So does our entire editing staff. For example, I have recently finished updating a 300+ page technical specification for the Los Angeles County Sheriff on the project we are staffing there. Jennifer, who is writing our user documentation, is in the midst of finishing a 250+ page user manual for the same system. And of course, I use Frame for daily business, technical documentation, and the like. Throughout it's entire life I have been having some trouble with FrameMaker. Nothing that would keep me from using it... until something better comes along. My fingers are crossed with Pages, but there are some shortcomings there. For instance, it will not have the vast cross-platform base that Frame does, so output is going to be harder. You say: Now, my friend, for the real complaint about this post. Your smart alec comments about Frame not porting and the "time to buy Pages" comment illustrate what's screwed up about your opinions. No decision about porting to Intel has been made by Frame. It doesn't "look" like Frame will or will not port - nobody knows. But people like you loudly proclaiming indefensible positions like this on the net make it look like a decision has been made when it hasn't. I say: The position is defensible. We are currently involved in a large, highly visible contract in which FrameMaker is involved. Frame has directly relayed to us through several channels that "there are currently no plans to continue releasing FrameMaker on NeXTSTEP or to port it to NeXTSTEP Intel." This has prompted very significant changes be made in the fixed bid contract, and the client involved is now planning a shift from FrameMaker to another technology (probably WordPerfect, as they already have it installed and their 400+ users trained on it). You say: But worst of all, I take great offense at your "time to buy Pages" comment. They've got great egos, lots of PR and trade show experience, and I'm sure they're having a great time playing on somebody else's venture capital. But Pages hasn't been helping get the work done for the last three years. Pages isn't shipping, the last I checked, and at the expo when I showed the people from Pages the kind of stuff I do with Frame, they hemmed and hawed and said that they might be able to do some of the stuff in future versions. What future version? Who cares? For now, Pages is vaporware, but they've sure done a good job of convincing all the know-it-alls in NeXTdom that they are alive and well and a better solution than anything else out there. Yeah, right. If their product is so great, and they're such hot shit programmers, why aren't they shipping? They've had Pages under development for as long as I've been using Frame. No, it is NOT time to buy Pages - even if you could! I say: Well, I probably shouldn't but: I am testing Pages. I believe that comment is public domain so I'm not liable to be shot yet. I'll add that I love it, and I think it's going to be a great product. Better leave it at that, though, or they'll be sending Guido and Iggy out to get me... You are right, though, about features. Pages is not going to be a FrameMaker replacement. Perhaps someday it will evolve to that (I can certainly hope), but it is obviously not going to have the richness of capabilities that FrameMaker has now. It won't be as easy to work with when it comes to these huge, custom publications which require output through a Sun or Mac to a Linotronic. On the other hand, the user interface is going to make up, at least in my mind, for the complete lack of a user interface in FrameMaker! :-) FrameMaker is one of the most infuriating systems I've had to work with over the years in publishing. You say: I realize that you developer types have your little high-school cliques of who's cool and who's not (and a corporate entity like Frame can't possibly be Zac-cool) but the point is that they have an excellent product that has been around from the beginning while all most of the cool guys have are a bunch of plans and promises. Know why Pages isn't out yet? Because they all want to keep their paychecks a little longer before they're fired after the product is released, flops under a mound of criticism and problems, and a bunch of angry investors want to know where their money went. I say: An interesting comment. Just for your information, I am the founder of three companies, one of them being BOSS Logic Inc. (which you may have heard of, in the NeXT community)... with BOSS I was the fourth person to join and help build the company. Dolphin Technologies Inc. is my third company, and is completely dedicated to NeXTSTEP development. We are currently staffing the Los Angeles County Sheriff project, which is one of the most highly visible law enforcement systems under design. We also have established partnerships with TRW, and are pursuing very exciting avenues in medical imaging systems. I wanted to mention this to dispell the idea that you have about my being involved with high-school. It's been some time since I've hovered around those hallowed halls... You say: I can hardly wait to see how you react when someone drops a mis-informed load on the net about your stuff. I can hear those howls of indignation now. I say: It's happened too many times to remember. I usually try to address the problem in a message such as this, then go about my business. There are many people who don't agree with me or misinterpret the information at hand (or jump to hasty conclusions). You say: John "tired of people with no better solution trashing FrameMaker" Bartley I say: That's just the problem. FrameMaker is currently the only solution available for NeXTSTEP. I certainly hope that Pages, as well as other products, ship soon. New features for PasteUp. Another WordPerfect release. We need these things... because when FrameMaker vanishes, NeXTSTEP is going to be left relatively high-and-dry without a complete publishing solution. Personally, I don't care for FrameMaker--it's got the worst user interface around--but, I'll be the first to admit: we need it, at least for now. I hope they change their minds and do the 'port... -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs,comp.sys.next.software From: dav@well.sf.ca.us (Paul Davilon) Subject: NS Serial Port Drivers Message-ID: <CAE5ys.HFu@well.sf.ca.us> Keywords: Is there anybody home? Sender: news@well.sf.ca.us Organization: The Whole Earth 'Lectronic Link, Sausalito, CA Date: Mon, 19 Jul 1993 03:06:28 GMT Looking up from my Windows desktop and gazing over at my personal edition of the "$10,000 paperweight" as someome so succiently put it I look at the calendar and am struck with the thought: hey, there are only a very few days left in mid-July, gosh I guess that means NeXT will be coming out with the new serial port drivers ANY MINUTE NOW! Looking at some of the glossy, shiny and happy junk mail that NeXT keeps sending me, to let me know its doing JUST FINE!(tm), I find myself lulled into a happy, idiotic stupor and am nearly certain that NeXT really can do things and deliver what it promises without a fire lit under its ass. Although, I must surely admit, I just haven't seen it happen yet I guess, since as all the mail I've received has been mixed in content, but very straightforward in pointing out that this "new" OS I'm trying to use, was WRITTEN ON the machine I'm trying to use it with (a Dell DGX), and so NeXT has had roughly 2+ years to write a f--king serial port driver for this piece of junk. "Woops, heh heh, who would have thought someone would want to use a modem or a printer? Gosh Steve, back to the drawing board, and lets rip out the disk drives while we're at it" * ANY DECENT Modem use ....... WHEN, where are the drivers? PS: To the "helpful" people who suggest running the serial port at 9600 until the "new drivers that work" come out somewhere over the rainbow. Nice thought, except, it doesn't work either. ANY use of the serial ports at ANY speed crashes the machine. (Ok, so being honest I DIDN'T try 300 or 1200 baud ;-)
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: louie@TransSys.COM (Louis A. Mamakos) Subject: Re: detecting carrier for ttyfa - mystery solved? Message-ID: <22d3s7$3gk@wa3ymh.transsys.com> Followup-To: comp.sys.next.programmer Sender: usenet@grebyn.com Organization: TransSys, Inc. References: <22b8ko$a7j@cheltenham.cs.arizona.edu> <1993Jul18.124450.3270@totsyssoft.com> <22clk0$qba@cheltenham.cs.arizona.edu> Date: Mon, 19 Jul 1993 03:19:35 GMT In article <22clk0$qba@cheltenham.cs.arizona.edu> kline@CS.Arizona.EDU (Nick Kline) writes: >In article <1993Jul18.124450.3270@totsyssoft.com> bruce@TotSysSoft.com (Bruce): >> >>- (BOOL)is_connected:(int)openModemDevice >>{ >> char statusByte; >> >> ioctl( openModemDevice, TIOCMODG, &statusByte ); >> return(( statusByte & TIOCM_CAR ) == TIOCM_CAR ); >>} >> >> > >Thanks again Bruce. You seem to know all the answers. Is there a reference >to point me to? (Other than the zs(4), tty(4), ioctl.h include file). > >strangely enought, the above always returns 0 for me. and I checked the return >from ioctl and it wasn't -1. TIOCMODG always sets the statusByte to a 0 >(and works the same for an int). This is just weird. After my previous posting, I decide to go investigate just what TIOCMODG and TIOCMGET are and how they differ. The tty(4) man page on the NeXT is silent on these. I then consulted the various bibles on these sorts of matters: Leffler, McKusick, Karels, Quarterman, "The Design and Implementation of the 4.3BSD UNIX Operating System", Stevens, "Advanced Programming in the UNIX Environment" Stevens, "UNIX Network Programming" these were also lacking in helpful advice in this area. Now, having just watched the Star Wars trilogy on the SciFi channel on cable, I recalled the hacker's motto: "Use the source, Luke." I then grepped the source for NET2 and NetBSD (derivitive from 386BSD which is derivitive from NET2). This is a likely path to pursue given that the non-pure Mach part of the kernel appears to be something close to the NET2 BSD code. (At least if you match up the bugs and features). I think I have gotten to the bottom of what's going on. For those of you that don't skip to the last page of mystery novels to see "who did it", read on. Or skip to the end if you're bored by kernel drivers, etc. [Begin long digression into the kernel-level implementation of tty drivers] The BSD sources were somewhat more helpful. There is, of course, no code in the tty.c module since these are likely functions implemented by the hardware drivers rather than the higher level drivers. Happily, in the NET2 code there are drivers for 386 standard ISA COM port serial ports. There are also drivers for a few HP serial drivers. Both of these implement TIOCMGET to return something useful; neither had any code to implement TIOCMODG. For example, the i386 COM port driver has code like this: comioctl(dev, cmd, data, flag) dev_t dev; caddr_t data; { register struct tty *tp; register int unit = UNIT(dev); register com; register int error; tp = &com_tty[unit]; error = (*linesw[tp->t_line].l_ioctl)(tp, cmd, data, flag); if (error >= 0) return (error); error = ttioctl(tp, cmd, data, flag); if (error >= 0) return (error); com = com_addr[unit]; switch (cmd) { [...] case TIOCMSET: (void) commctl(dev, *(int *)data, DMSET); break; case TIOCMBIS: (void) commctl(dev, *(int *)data, DMBIS); break; case TIOCMBIC: (void) commctl(dev, *(int *)data, DMBIC); break; case TIOCMGET: *(int *)data = commctl(dev, 0, DMGET); break; [...] } Looking at commctl.. commctl(dev, bits, how) dev_t dev; int bits, how; { register com; register int unit; int s; unit = UNIT(dev); com = com_addr[unit]; s = spltty(); switch (how) { case DMSET: outb(com+com_mcr, bits | MCR_IENABLE); break; case DMBIS: outb(com+com_mcr, inb(com+com_mcr) | bits | MCR_IENABLE); break; case DMBIC: outb(com+com_mcr, inb(com+com_mcr) & ~bits | MCR_IENABLE); break; case DMGET: bits = inb(com+com_msr); break; } (void) splx(s); return(bits); } We see that it indeed grabs some bits off the com port control register, which presumably map one-to-one with the various TIOCM_* definitions. I've seen other drivers where there is a mapping function betwixt the TIOCM_* bit and what the hardware returns. This preserves the model of the virtual DH/DM-11 hardware (UNIBUS, anybody? :-) --- begin tangent --- In the NET2 code, interestingly enough, if you look at the hardware bits and the ioctl.h definitions, you don't see too many matches! Ooops! From i386/isa/comreg.h: /* modem status register */ #define MSR_DCD 0x80 #define MSR_RI 0x40 #define MSR_DSR 0x20 #define MSR_CTS 0x10 #define MSR_DDCD 0x08 #define MSR_TERI 0x04 #define MSR_DDSR 0x02 #define MSR_DCTS 0x01 From sys/ioctl.h: #define TIOCM_LE 0001 /* line enable */ #define TIOCM_DTR 0002 /* data terminal ready */ #define TIOCM_RTS 0004 /* request to send */ #define TIOCM_ST 0010 /* secondary transmit */ #define TIOCM_SR 0020 /* secondary receive */ #define TIOCM_CTS 0040 /* clear to send */ #define TIOCM_CAR 0100 /* carrier detect */ #define TIOCM_CD TIOCM_CAR #define TIOCM_RNG 0200 /* ring */ #define TIOCM_RI TIOCM_RNG #define TIOCM_DSR 0400 /* data set ready */ --- end tangent --- [End of kernel diversion..] "The Chase" In any case, I don't see any reference to the TIOCMODG ioctl. Perhaps this was meant to be defined to return a "generic" representation of the device status bits, rather than (what appears to be) a direct set 'o bits right off the hardware that TIOCMGET returns. Now, I don't know what the NeXT actually does with the TIOCMODG ioctl(), it appears to do the "right thing" with TIOCMGET mapping at least the bit that corresponds to the hardware DCD signal to TIOCM_CD. I have code that seems to successfully use TIOCMGET and checks against TIOCM_CD; it does this once per minute and it seems to do the ``right thing.'' So, I hacked up this silly program: #include <sys/ioctl.h> main(int argc, char **argv) { int fd = open (argv[1], 0); int foo; if (fd < 0) { perror(argv[1]); exit(1); } if (ioctl(fd, TIOCMODG, &foo) < 0) { perror("TIOCMODG"); } else { printf("TIOCMODG: 0x%x\n", foo); } if (ioctl(fd, TIOCMGET, &foo) < 0) { perror("TIOCMGET"); } else { printf("TIOCMGET: 0x%x\n", foo); } } and ran it on a 3.0 system: louie[146] $ a.out /dev/cub TIOCMODG: 0x0 TIOCMGET: 0x66 louie[147] $ a.out /dev/ttyb TIOCMODG: 0x0 TIOCMGET: 0x66 louie[148] $ a.out /dev/ttydb TIOCMODG: 0x0 TIOCMGET: 0x66 and on a 3.1 system: # ./a.out /dev/cub TIOCMODG: 0x0 TIOCMGET: 0x46 # ./a.out /dev/ttyb TIOCMODG: 0x0 TIOCMGET: 0x46 # ./a.out /dev/ttydb TIOCMODG: 0x0 TIOCMGET: 0x46 I conclude from this experiment that TIOCMODG really isn't doing much of anything. The values we get back 0x66 == 0146 == <TIOCM_CAR,TIOCM_CTS,TIOCM_RTS,TIOCM_DTR> and 0x46 == 0106 == <TIOCM_CAR,TIOCM_RTS,TIOCM_DTR> are consistant with an open line (with nothing plugged in for 0x66 and the device turned off for 0x46). Thus, I assert that TIOCMGET looks like its returning plausable values. What I think is going on here is a kernel bug that's biting us: the TIOCMODG ioctl is probably failing, but the error status is not being returned to the user. This could be a bug that I reported in a October 1991 where a user-installed line discipline (e.g., SLIP) can't return an error on an ioctl() that it implements. The zs serial driver would always return a 0. > To: bug_next@next.com > Subject: User-installed line disciplines can't return an error from ioctl() > Date: Sun, 20 Oct 91 11:51:48 -0400 > From: "Louis A. Mamakos" <louie> > > > I discovered that it seems to be impossible to return an error from a > user installed kernel driver that uses a line discipline. It seems > that the zs kernel driver will always return a 0, rather then > preserving the return value from ld_ioctl function in the line > discipline switch table. > > > louie To continue the experiment to test this theory, I modified the silly program above to: #include <sys/ioctl.h> #define TIOCBOGUS _IOR('t', 55, int) /* unused bogus ioctl */ main(int argc, char **argv) { int fd = open (argv[1], 0); int foo; if (fd < 0) { perror(argv[1]); exit(1); } foo = 0x1234; if (ioctl(fd, TIOCMODG, &foo) < 0) { perror("TIOCMODG"); } else { printf("TIOCMODG: 0x%x\n", foo); } if (ioctl(fd, TIOCMGET, &foo) < 0) { perror("TIOCMGET"); } else { printf("TIOCMGET: 0x%x\n", foo); } if (ioctl(fd, TIOCBOGUS, &foo) < 0) { perror("TIOCBOGUS"); } else { printf("TIOCBOGUS: 0x%x\n", foo); } } This version will attempt to perform a bogus, unimplemented TTY ioctl (of the "return data to user" type) to see what happens. And now I get this: $ ./a.out /dev/cub TIOCMODG: 0x0 TIOCMGET: 0x46 TIOCBOGUS: 0x0 It appears that any random, bogus TTY ioctl will return a 0 in the parameter passed by reference in the third argument of the ioctl. I therefor conclude and assert that TIOCMODG is actually unimplemented and doesn't do anything useful. [It's because of diversions like this that the new Intel version of SLIP isn't ready yet, sigh.] -- Louis A. Mamakos TransSys, Inc.
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: Tape and CU error Message-ID: <135@boschrt.rt.bosch.de.bosch.de> Date: 19 Jul 93 05:32:56 GMT Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. --- /********************************************************************/ /* Kay Schulz, Rheinstr. 24, 72768 Reutlingen, Germany */ /* 07121 / 60 19 61 privat */ /* 07121 / 35-1341 geschaeftlich */ /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/ Hi I had some bad experiences this weekend, hopefully someone can help me! I used the serial port 2 for my modem (1 is the mouse). I always used cu -s 2400 -l cufb to connect to the modem and talk in hayes mode. Everything went fine. Suddenly if I use the same command i get an Bus error! I only changed the name of the system! Second: I am unable to read or write (!!!!) QIC2 Tapes used before. I can't read Linux or ISC tapes, written in tar or cpio format. I am also unable to erase them and write them with NSFIP. Any idea?
Newsgroups: comp.sys.next.bugs From: john@wpa.com (John Bartley) Subject: Re: Frame broken in 3.1? Message-ID: <1993Jul19.055820.875@nimno.wpa.com> Sender: john@nimno.wpa.com Organization: Workgroup Productivity Associates References: <1993Jul18.222438.593@dolphin.com> Distribution: usa Date: Mon, 19 Jul 1993 05:58:20 GMT In article <1993Jul18.222438.593@dolphin.com> Zacharias J. Beckman <zac@dolphin.com> writes: > John Bartley <john@wpa.com> writes: [......] Yes, as a matter of fact, I did send the quoted material via private e-mail to Mr. Beckman. I did NOT post it, nor did I intend for it to be posted, nor did I give him permission to post it on my behalf. Since I already received this reply earlier today via e-mail from Mr. Beckman, it is obvious to me that he has not posted this "accidentally." I suppose he is serving as one-man judge and jury and has convicted me of daring to disagree with him. For this I must be punished by having my e-mail forged as a comp.sys.next.bugs posting! :-) I'm still working on suitably witty epithets to hurl at him for doing this. My opinions and editorial comments were intended solely for consumption by Mr. Beckman, so anyone who got their feathers ruffled can forward their flames to him, not me. Sheesh. A couple of weeks ago I got roasted publicly on the net for sending somebody NeXTmail who had never seen it before and thought I was trying to sabotage their computer! Now this. I guess private phone conversations will be the next thing to get posted on the net. John "sorry, only a mono-syllabic first name" Bartley
Newsgroups: comp.sys.next.bugs From: Zacharias J. Beckman <zac@dolphin.com> Subject: Re: Frame broken in 3.1? Message-ID: <1993Jul19.074134.306@dolphin.com> Followup-To: comp.sys.next.advocacy Sender: zac@dolphin.com Organization: Dolphin Technologies Inc. References: <1993Jul18.222438.593@dolphin.com> Distribution: usa Date: Mon, 19 Jul 1993 07:41:34 GMT John Bartley <john@wpa.com> writes: Did it ever occur to you that maybe, just maybe, the crimes that you accuse Frame of were installation dependent, and that the possibility exists that user error was responsible for the "problems" cited, not Frame? You mention hundreds of users, and a variety of types of systems. I think you'd have a hard time proving in court that nothing but Frame was responsible for the things you mentioned. If those things were inherent problems with Frame/NeXT, don't you think somebody else would have them? You don't suppose that documents could have gotten munged on somebody's Sun or Macintosh, do you? I have seen problems on the Mac side. I say: Certainly. But I don't think I mentioned hundreds of users- perhaps twenty. However, if that is the case, Frame needs to work on their installation system (which, I might add, has very few steps to make an error in). If it is installation dependant, it has now consistantly failed on over six different networks and for approximately fifteen to twenty full time users. As for "don't I think someday else would have [these problems]?" Well yes! As a matter of fact, your the first person I've spoken to that hasn't had them! I'd really love to know what it is that you are doing that makes Frame behave so well for you. :-) You said: As for your comments regarding the Frame port, what you claim is significantly twisted from the "official" language currently being used by Frame. I received e-mail from their tech support manager just about three weeks ago. She made it quite clear that the matter is still under consideration and that NO decision, favorable or unfavorable, has yet been made. With all due respect to your superior wisdom and intellect, I'll take her word for the situation before I take yours. I say: Apparently their lack of commitment, then, is strong enough to turn away a client like the Los Angeles County Sheriff, who has purchased very large licenses of the software. It has been made clear to us that there are no plans to continue the product at the present time. Perhaps that will change, but we certainly can't wait any longer to find out. Several hundred Intel based machines arrive within a matter of weeks. Frame has told us they won't be on Intel, so we have changed the project to integrate with RTF and WordPerfect, not Frame. You said: I just love comments from people like you who always want to show off your great knowledge of products and put them down. You go on and on about how much publishing experience you have and how Frame's user interface sucks. What nerve! I remember BDMS ....and you're criticizing Frame!!!??? Ha. I suppose you've never worked with Ventura or Interleaf. I work with Frame every day (gee, maybe I've mastered it and that's why it doesn't infuriate me) and it doesn't infuriate me. People who forge postings with my name on them infuriate me, but not Frame. I say: I never said that BDMS had a great interface! :-) Actually, I do think the new version is a considerable improvement, but it still needs work. One of the reasons I am no longer a Founder at BOSS Logic, I suppose. Couldn't come to agreement on certain things, such as the direction to take the BDMS user interface. As for mastering Frame... I can do whatever I need to in it. Still doesn't change the fact that the user interface is one of the poorest available, at least on NeXTSTEP. Compared to the interfaces of certain Windows and Sun programs, it's great. But I'm not using Windows or Sun, am I? You say: I forgot though, you're the hotshot who decided last week that he would go ahead and post his own self-aggrandizing "press release" instead of sending it through channels according to the "rules." I say: You are the second person to make a negative mention of that. Considering that I received well over thirty, perhaps forty, inquiries, I'm not complaining. Those users seemed to appreciate the posting (and some outright said they did), and I will continue to post information (properly marked, of course, with "PR" or whatever) to the relevant groups. A new NeXTSTEP programming tool definately deserves posting in c.s.n.p. as well as c.s.n.a. You say: Time will tell, but I think my rendition of what will happen with Pages and FrameMaker will be pretty close to the truth - i.e., Frame will port, and Pages will go down in history as the product that never was. The three-pronged blivet of the NeXTSTEP world. I say: I won't dispute you yet. I've seen too many companies follow such a model--Pages is not out yet, and until it is the odds (statistically) on a new company are over 10-to-1 against. Still, I cross my fingers and hope that Pages will outlast Frame, because I like it better. If it does, it will definately have to adopt many of the features that Frame has become known for. Of course, if NeXTSTEP is successful, and if Frame is still here one or two years from now, I'm sure we'll see Frame ported. The problem is, they aren't interested now. At the moment, they are concerned with getting their stock back on firm ground, since this past six months they have lost so much. Apparently they feel that the way to do that is to "retreat" to more familiar territory, get out of ventures like partnerships with document management companies and other speculative investments, and try to do what they built the company up on in the first place. NeXTSTEP is still considered speculative. As for Frame Corporation, I'm not putting my stock there anymore. With the turn of events that Frame has suffered in the past six months, and the "potential" lawsuits (at least, only potential lawsuits at present) which are heading their way... I am skeptical that they will survive much longer. The technology is old, and while it is still the most widely used product with the best cross-platform capabilities, it is beginning to see significant competition--and buyers are becoming more wary. That competition takes the form of better, faster and friendlier programs based on a technology that is superior (I know--as part of the partnership between BOSS Logic and Frame I've seen the inside and outside of their technology). Well, I hope you don't mind if I post this. The amount of time I'm spending on this thread, and the interesting topics which are being discussed, are bound to interest other readers. Plenty of good information and heated opinion. I've changed the follow-up-to over to c.s.n.advocacy, since this really is getting away from bugs... -- Zacharias J. Beckman - Dolphin Technologies Inc. - zac@dolphin.com - NeXTMAIL! To be "matter of fact" about the world is to blunder into fantasy.... and dull fantasy at that, as the real world is strange and wonderful. --- R. A. Heinlen Those opinions I express herein are my own, I'm fairly sure. --- Z. J. Beckman
Newsgroups: comp.sys.next.bugs From: bnocker@cosy.sbg.ac.at (Bernhard Nocker) Subject: NSFIP: 800x600 broken? Message-ID: <CAF07o.DEH@cosy.sbg.ac.at> Keywords: NSFIP graphic 800x600 Sender: news@cosy.sbg.ac.at Organization: University of Salzburg / Austria Date: Mon, 19 Jul 1993 13:59:47 GMT Dear netters, has anyone observed problems with 800x600x16? My LocalBus ATI Mach32 compatible grphic card displays stripes (small but annoying) on the right side of the screen. Maybe a bug in the driver or bus timing problems! Any suggestions welcome, Bernie -- Bernhard Nocker University of Salzburg's Department of Computing Studies Jakob-Haringerstr. 5 5020 Salzburg Austria, Europe Tel: +43-662-8044/6316 bnocker@cosy.sbg.ac.at Fax: +43-662-8044/6316 or +43-662-8044/611
From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.bugs Subject: This is a worthless group Message-ID: <1272@rtbrain.rightbrain.com> Date: 19 Jul 93 18:19:02 GMT Sender: glenn@rightbrain.com This group should be moderated or something. There is speculation and discussion about things, but no bug lists, no steps to reproduce, no official or unofficial news about bug fixes. What was the original charter of this newsgroup? How is it supposed to be used? I thought it was supposed to be used sort of like the FAQ mechanism, to make people aware of confirmed bugs and their workarounds. -- Glenn Reid NeXTmail: glenn@rightbrain.com RightBrain Software 415-326-2974 (NeXTfax 326-2977) Palo Alto, California Electronic Frontier Foundation, member #054
Newsgroups: comp.sys.next.bugs From: esky@marathon.cs.ucla.edu (Eskandar Ensafi) Subject: Workspace Error when Copying Files to Floppy Disk Message-ID: <1993Jul19.173037.27160@cs.ucla.edu> Sender: usenet@cs.ucla.edu (Mr Usenet) Organization: UCLA CS Department, Los Angeles, CA Date: Mon, 19 Jul 93 17:30:37 GMT Hi, I needed to backup a file onto a floppy while someone else was logged in on our NeXTstation. I opened a new shell and logged in under my account, retrieved the file I wanted via ftp, and inserted a floppy. I then went over to the Workspace Manager, located my file's icon, and dragged it into my floppy disk. It was successfully copied, but when the operation ended, a 'Workspace Error' alert panel came up telling me to try to save all changes before being forced to log out. So much for being considerate and not logging the other person out :-( I looked in console.log and noticed that the Worspace Manager was being abruptly terminated due to WindowServer death. What could have caused this? All I did was try to copy a file!!! Thanks. E-mail preferred. - Esk. -- "Dance with the dead in my dreams Listen to their hollowed screams The dead have taken my soul Temptation's lost all control" -- Slayer (Dead Skin Mask)
From: rbp@investor.pgh.pa.us (Bob Peirce #305) Newsgroups: comp.sys.next.bugs,comp.sys.next.software Subject: Thrid Party CDs hang NS3.1 Message-ID: <1993Jul19.114135.17143@investor.pgh.pa.us> Date: 19 Jul 93 11:41:35 GMT Organization: Cookson, Peirce & Co., Pittsburgh, PA I sent a bug report on this to NeXT and I posted a question to these groups about a week ago. There has been no reply from anyone so I am trying again. I need a way to mount a CD from the console on a freshly booted system. I am running NS3.1 on a 68040 Cube with 24Mb of RAM. My CDRom is on sd2. My boot device is sd0 and my old internal drive is sd1. I don't know if any of this matters. NeXT CDs automount on /dev/sd2a. Third party CDs automount on /dev/rsd2h. I don't know if that matters. Under NS3.0, a command like ls -lR on a mounted CD would run to comple- tion. Under NS3.1, this command works for NeXT CDs but with third party CDs the computer eventually will hang and the plug must be pulled to re- boot. There also will be a large number of files "not found." Tar on a large directory will do the same thing. Using workspace to copy a large number of files, say a big app, will produce errors from not being able to locate files. Since NS3.0 worked, I thought I could boot a 3.0 kernel, log into the console, mount the disk, do my work and re-boot under 3.1. However, I found that under both 3.0 and 3.1 I could not mount a CD with the mount command unless it had previously been mounted from within the workspace However, as you would expect, the 3.1 workspace crashes under the 3.0 kernel. Having gone to the trouble of loading 3.1, I don't want to go back to 3.0 just to read CDs. Does anybody have a command that will mount a CD from the console on a freshly booted system? -- Bob Peirce, Pittsburgh, PA rbp@investor.pgh.pa.us 412-471-5320 venetia@investor.pgh.pa.us [NeXT Mail] !uunet.uu.net!pitt!investor!rbp [UUCP]
Newsgroups: comp.sys.next.bugs From: tacchi@ccu.umanitoba.ca (Mark G. Tacchi) Subject: Re: NSFIP: 800x600 broken? Message-ID: <CAFCus.70u@ccu.umanitoba.ca> Keywords: NSFIP graphic 800x600 Sender: news@ccu.umanitoba.ca Organization: University of Manitoba, Winnipeg, Canada References: <CAF07o.DEH@cosy.sbg.ac.at> Date: Mon, 19 Jul 1993 18:32:51 GMT In <CAF07o.DEH@cosy.sbg.ac.at> bnocker@cosy.sbg.ac.at (Bernhard Nocker) writes: >Dear netters, >has anyone observed problems with 800x600x16? My LocalBus ATI Mach32 compatible >grphic card displays stripes (small but annoying) on the right side of the >screen. Maybe a bug in the driver or bus timing problems! >Any suggestions welcome, >Bernie >-- Check your refresh rate in Configure.app. Use the Select... button. Also, your card may not be 100% compatible with the ATI. -Mark -- Mark G. Tacchi tacchi@ccu.umanitoba.ca "Medicine will cure death and government will repeal taxes before Steve will fail." -G.Kawasaki
From: edc@crick.bchs.uh.edu (edward s. chen) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Internal Error # 3007 Date: 19 Jul 1993 21:20:28 GMT Organization: University of Houston Message-ID: <22f36s$i71@menudo.uh.edu> Any clues as to what the mysterious "Internal Error # 3007" is? Periodically, my NeXT will have a pop-up window indicating this error has been discovered, and "Continue at your own risk." If either the "Continue" button, or the "Log Out" button is chosen, the machine hangs. Any advice welcome. Thanks much, <ESC> Ed Chen -- When I'm driving, I sometimes close my eyes and meditate. Is that dangerous? No. My chauffeur actually does the driving. Ringo Starr, 1968
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: archetyp@uxh.cso.uiuc.edu (Joseph R Pickert) Subject: Floppy drive problems under NextStep 486 Date: Tue, 13 Jul 1993 12:58:28 GMT Summary: Can't write floppy under nextstep 486 Message-ID: <CA3tDH.MoK@news.cso.uiuc.edu> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Keywords: floppy, nextstep Organization: University of Illinois at Urbana I have a NCR system 3333 on which I can't seem to get the floppy working correctly. I can format, read, and write to the floppy just fine under DOS, so I am pretty sure there is nothing wrong with the drive itself. I can use the disk utility to format a disk, and that seems to work ok. I can also seem to read it with the disk utility. If I try to write a label or use newfs to write a filesystem, I get many messages like: mach: fd0: Sector XX cmd = Write; DMA Over/underrun: RETRYING mach: fd0: Sector XX cmd = Write; DMA Over/underrun: RECALIBRATING . . . mach: fd0: Sector XX cmd = Write; DMA Over/underrun: FATAL I tried formating and putting a fs on a disk on my slab and then mounting it on my 486 and the 486 crashes. Can anyone clue me in to what is happening, and, if possible tell me how to fix it? Thanks. Joe Pickert
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: jeffo@uiuc.edu (J.B. Nicholson-Owens) Subject: Re: Max number of user processes... How to get more? Date: Sun, 18 Jul 1993 07:35:37 GMT Message-ID: <CACnrD.9ow@news.cso.uiuc.edu> Distribution: usa References: <1993Jul18.052954.1505@dolphin.com> Sender: jeffo@uiuc.edu (J.B. Nicholson-Owens) Originator: jbn35564@uxa.cso.uiuc.edu Organization: University of Illinois at Urbana Zacharias J. Beckman writes: >Did anyone find the boot parameter that will allow an increase in the number >of user processes under NeXTSTEP 3.1? I've heard from numerous e-mail reports that this is a parameter only NeXT can change since it's something that is compiled into the kernal and (of course) only NeXT has the source to the kernal. I hope that what I've been told is incorrect, it would be a shame to continue losing mail and not being able to run certain image programs multiple times before having to reboot the machine (as another poster said he had to do with his 3.1). > That helps to keep <mach tasks> and I've heard that 3.0's Terminal app created one of these zombie processes with each closed terminal window. Perhaps this is also your problem and switching to Stuart might help?
From: lusty@lusty.tamu.edu (Lusty Wench) Newsgroups: comp.sys.next.bugs Subject: Re: This is a worthless group Date: 19 Jul 1993 23:01:34 GMT Organization: Me Message-ID: <22f94e$1td@tamsun.tamu.edu> References: <1272@rtbrain.rightbrain.com> In article <1272@rtbrain.rightbrain.com> glenn@rightbrain.com writes: > >This group should be moderated or something. There is speculation and >discussion about things, but no bug lists, no steps to reproduce, no >official or unofficial news about bug fixes. What was the original >charter of this newsgroup? How is it supposed to be used? I thought >it was supposed to be used sort of like the FAQ mechanism, to make people >aware of confirmed bugs and their workarounds. > Yes, I agree that this group is not performing up to the standards that were expected of it upon creation. I have to admit I feel somewhat responsible (read: guilty), since I was the one who handled the original vote-taking process. For what it's worth, the charter is included below. What can we do to turn it around? Diana comp.sys.next.bugs Discussion and solutions for known NeXT bugs. (unmoderated) With the release of version 3.0 of NeXTStep has come a rash of bug reports, as would be expected with any major software upgrade. This group will provide a forum for discussion of new bugs and a resource for those looking for bug fixes and workarounds. A master list of confirmed bugs will be maintained and will be posted periodically, as well as being made available from one or more archive sites. This list will include known fixes and/or workarounds.
Newsgroups: comp.sys.next.bugs From: sanguish@digifix.com (Scott Anguish) Subject: Re: This is a worthless group Message-ID: <1993Jul19.225938.4985@digifix.com> Sender: sanguish@digifix.com (Scott Anguish) Organization: Digital Fix Development References: <1272@rtbrain.rightbrain.com> Date: Mon, 19 Jul 1993 22:59:38 GMT Glenn Reid writes > > This group should be moderated or something. There is speculation and > discussion about things, but no bug lists, no steps to reproduce, no > official or unofficial news about bug fixes. What was the original > charter of this newsgroup? How is it supposed to be used? I thought > it was supposed to be used sort of like the FAQ mechanism, to make people > aware of confirmed bugs and their workarounds. > I have to agree with Glenn on this. A large amount of what is piped through here is not bugs, but speculation. Who has the charter for this group? -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
Newsgroups: comp.sys.next.bugs From: bebeada@elof.iit.edu(Adam Beberg) Subject: Re: Internal Error # 3007 Message-ID: <1993Jul20.005854.2474@iitmax.iit.edu> Sender: news@iitmax.iit.edu (News) Organization: Illinois Institute of Technology / Academic Computing Center References: <22f36s$i71@menudo.uh.edu> Date: Tue, 20 Jul 93 00:58:54 GMT In article <22f36s$i71@menudo.uh.edu> edc@crick.bchs.uh.edu (edward s. chen) writes: > > Any clues as to what the mysterious "Internal Error # 3007" is? > > Periodically, my NeXT will have a pop-up window indicating this > error has been discovered, and "Continue at your own risk." > > If either the "Continue" button, or the "Log Out" button is chosen, > the machine hangs. Any advice welcome. > No advice but I've gotten the same error 5 times in 2 days, one of those times caused a panic :-( However, I have figured out what seems to be causeing it. It occurs when I attempt to drag&drop a "# files" icon, and occurs as soon as I start to move the icon. It's intermitant too :-( quite frankly this is getting quite annoying, as I tend to drag&drop alot. - Adam Beberg. Golden Sphinx (tm) bebeada@elof.iit.edu NeXTMail Welcome. ))) In Sterio Where Available (((
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.bugs Subject: Re: This is a worthless group Date: 20 Jul 1993 03:35:22 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <22fp5q$cia@usenet.rpi.edu> References: <1993Jul19.225938.4985@digifix.com> sanguish@digifix.com (Scott Anguish) writes: > Glenn Reid writes > > This group should be moderated or something. There is speculation and > > discussion about things, but no bug lists, no steps to reproduce, no > > official or unofficial news about bug fixes. What was the original > > charter of this newsgroup? How is it supposed to be used? > > I have to agree with Glenn on this. > > A large amount of what is piped through here is not bugs, but > speculation. Who has the charter for this group? In a sense I agree too, but as I remember the charter of the group this is exactly what I expected to happen. I don't actually remember the charter itself, I just remember arguing that the group was going to wind up like it is, mainly because it was not moderated. -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
From: zmonster@athena.mit.edu (Eric M Hermanson) Newsgroups: comp.sys.next.bugs Subject: Re: This is a worthless group Date: 20 Jul 1993 03:48:08 GMT Organization: Massachusetts Institute of Technology Message-ID: <22fpto$60m@senator-bedfellow.MIT.EDU> References: <1272@rtbrain.rightbrain.com> <1993Jul19.225938.4985@digifix.com> >Glenn Reid writes >> This group should be moderated or something. There is speculation and >> discussion about things, but no bug lists, no steps to reproduce, no >> official or unofficial news about bug fixes. What was the original >> charter of this newsgroup? How is it supposed to be used? I thought Someone has to volunteer to act as a semi-moderator for this group. I would do it myself, but I really don't have the time! I know this sounds typical, but it is true. As an aside, I have been keeping records of postings to this newsgroup that looked like real bugs. I have about a week's worth of "bugs" stored on disk, but I have not had a chance to check them out. I think this group would be well served if someone from NeXT could contribute their knowledge. All of those emails going to Bug-NeXT@next.com should be sorted through by NeXT, and posted to this group if they are actually confirmed bugs. Is anyone from NeXT listening? -Eric
Newsgroups: comp.sys.next.bugs From: sanguish@digifix.com (Scott Anguish) Subject: Re: This is a worthless group Message-ID: <1993Jul20.044858.8581@digifix.com> Sender: sanguish@digifix.com (Scott Anguish) Organization: Digital Fix Development References: <22fpto$60m@senator-bedfellow.MIT.EDU> Date: Tue, 20 Jul 1993 04:48:58 GMT Eric M Hermanson writes > Someone has to volunteer to act as a semi-moderator for this group. I would > do it myself, but I really don't have the time! I know this sounds typical, > but it is true. > > As an aside, I have been keeping records of postings to this newsgroup that > looked like real bugs. I have about a week's worth of "bugs" stored on disk, > but I have not had a chance to check them out. I think this group would > be well served if someone from NeXT could contribute their knowledge. All of > those emails going to Bug-NeXT@next.com should be sorted through by NeXT, and > posted to this group if they are actually confirmed bugs. Well, I could moderate, I have all that in place already. Personally, I think that it would be better for all if Next just made the bug database available via ftp like the NextAnswers, or via gopher. However, I have to say that a network plea to NeXT for someone to listen is probably not going to work. -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: Re: NS Serial Port Drivers Message-ID: <152@boschrt.rt.bosch.de.bosch.de> Date: 20 Jul 93 05:07:08 GMT References: <CAE5ys.HFu@well.sf.ca.us> Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. Hi With 2400 Baud they work for me. A NeXT reseller suggested a Zyxel Modem. The drivers will come soon. --- /********************************************************************/ /* Kay Schulz /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: Re: This is a worthless group Message-ID: <153@boschrt.rt.bosch.de.bosch.de> Date: 20 Jul 93 05:21:54 GMT References: <1272@rtbrain.rightbrain.com> Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. In article 1272@rtbrain.rightbrain.com, glenn@rightbrain.com (Glenn Reid) writes: > >This group should be moderated or something. There is speculation and >discussion about things, but no bug lists, no steps to reproduce, no >official or unofficial news about bug fixes. What was the original >charter of this newsgroup? How is it supposed to be used? I thought >it was supposed to be used sort of like the FAQ mechanism, to make people >aware of confirmed bugs and their workarounds. > >-- > Glenn Reid NeXTmail: glenn@rightbrain.com > RightBrain Software 415-326-2974 (NeXTfax 326-2977) > Palo Alto, California Electronic Frontier Foundation, member #054 Sorry,but I got a lot of help here. I am happy that this group existst --- /********************************************************************/ /* Kay Schulz, Rheinstr. 24, 72768 Reutlingen, Germany */ /* 07121 / 60 19 61 privat */ /* 07121 / 35-1341 geschaeftlich */ /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/
Newsgroups: comp.sys.next.bugs Subject: Re: This is a worthless group Message-ID: <1993Jul20.010405.5866@nic.csu.net> From: eps@futon.SFSU.EDU (Eric P. Scott) Date: 20 Jul 93 01:04:03 PDT References: <1272@rtbrain.rightbrain.com> <22f94e$1td@tamsun.tamu.edu> <1993Jul19.225938.4985@digifix.com> Organization: San Francisco State University I agree with Glenn, Diana, and Scott. :-) Unfortunately, the problem is not confined to comp.sys.next.bugs, although it is probably most severe here. Perhaps it would help to have a regular (weekly?) posting to .announce that explains what the various newsgroups are all about. (Not that I expect it to do much good...) Anyway, here's something to start with. -=EPS=- ------- Once upon a time there was but one newsgroup (comp.sys.next) for all NeXT-related articles. Eventually, the volume became so high that many people felt they couldn't keep up with it, and found it difficult to find specific information they were interested in. Thus it was split into four newsgroups, with .misc being reserved for those things that didn't fit into the other three. Then those four became eight and later nine. While some advocate subdividing the namespace further, many consider the current arrangement too complicated and unwieldy as it is. The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups.
Newsgroups: comp.sys.next.bugs From: bauer@galilei.lbm.mw.tu-muenchen.de (Sebastian Bauer) Subject: Re: This is a worthless group Message-ID: <1993Jul20.091617.259@news.lrz-muenchen.de> Sender: news@news.lrz-muenchen.de (Mr. News) Organization: Leibniz-Rechenzentrum, Muenchen (Germany) References: <1993Jul20.044858.8581@digifix.com> Date: Tue, 20 Jul 1993 09:16:17 GMT In article <1993Jul20.044858.8581@digifix.com> sanguish@digifix.com (Scott Anguish) writes: > > Well, I could moderate, I have all that in place already. Personally, > I think that it would be better for all if Next just made the bug database > available via ftp like the NextAnswers, or via gopher. > > However, I have to say that a network plea to NeXT for someone to > listen is probably not going to work. > > > -- > - Scott Anguish - > sanguish@digifix.com (NextMail) > next-announce@digifix.com (comp.sys.next.announce submissions) I think, it would be a good idea, if Scott would moderate. Sebastian -------------------------------------------------------------------- Sebastian Bauer e-mail: <bauer@lbm.mw.tu-muenchen.de> at the Institute B for Mechanics (NeXTmail welcome) Technical University Munich, Germany --------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: jdeclari@is.rpslmc.edu (John-William DeClaris) Subject: MAc format on NeXT Message-ID: <1993Jul20.134511.19184@rpslmc.edu> Sender: news@rpslmc.edu Organization: Rush-Presbyterian-St. Luke's Medical Center Date: Tue, 20 Jul 1993 13:45:11 GMT I have a rather frustrating problem with the NeXT. I was under the impression that NeXTStep could write in Mac format, just as it can in DOS, but I can not seem to to do that. It used to be able to read a Mac disk in NS 3.0, sometimes, but now, under 3.1, which is supposed to have fixed the quirky nature of reading and writing to Mac format, the NeXT, can not do that at all. What is the problem, and does someone know the answer? --- John-William DeClaris All comments made by me are mine and not reflective of RUSH or anyone else... even any spelling errors I most likely made. Live each day as if it were your last, because someday it will be.
Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin,comp.sys.next.bugs From: laux@lxki.toppoint.de (Thorsten Laux) Subject: Re: Dell and Adaptec Message-ID: <1993Jul20.120709.6512@lxki.toppoint.de> Organization: Private uucp site References: <1993Jul16.184504.12770@aplcen.apl.jhu.edu> Date: Tue, 20 Jul 1993 12:07:09 GMT jds@aplpy.jhuapl.edu (John D Stanhope) writes: >Has anyone got the below error on there system and been able to fix >it? >AHA interrupt: bad status ff >sd0: INVALID STATUS (Internal error): FATAL ERROR > target:0 lun: 0 op: Read block: some # blockcount: some # I have exactly the same problem trying to install Nextstep for Intel on 2 different Eisa Systems with ATI ISA Ultra Pro and another Graphics Card and a 1542b Controller. I suspect you cannot get the 1542b to work in an Eisa System. Has anybody succeeded in doing this ? Thorsten Laux -- Thorsten Laux, Schuhmacherstr. 27/29, 2300 Kiel, FRG, Voice: +49 431 96334, email: laux@lxki.toppoint.de
Newsgroups: comp.sys.next.bugs From: ivor@binkley.cs.mcgill.ca (Ivo ROTHSCHILD) Subject: Re: This is a worthless group Message-ID: <22h032$864@binkley.cs.mcgill.ca> Sender: news@sifon.cc.mcgill.ca Organization: SOCS - Mcgill University, Montreal, Canada References: <22f94e$1td@tamsun.tamu.edu> <1993Jul19.225938.4985@digifix.com> <1993Jul20.010405.5866@nic.csu.net> Date: Tue, 20 Jul 1993 14:39:30 GMT In article <1993Jul20.010405.5866@nic.csu.net> eps@cs.sfsu.edu writes: >I agree with Glenn, Diana, and Scott. :-) > I have to disagree. From reading the charter, most of the posts I read here do seem to belong. The postings could be improved by people providing the steps to reproduce bugs, but often people can only identify the symptoms- not the cause. The verified bug lists and work arounds all take a certain amount of time that most people may not be able to give. And even still, listing symptoms can be helpful. Perhaps people should clearly label their postings as verifiable bugs or not. > >comp.sys.next.bugs > A place to report verifiable bugs in NeXT-supplied > software. Material e-mailed to Bug_NeXT@NeXT.COM > is not published, so this is a place for the net > community find out about problems when they're > discovered. This newsgroup has a very poor signal/noise > ratio--all too often bozos post stuff here that really > belongs someplace else. ^^^^^^^^^^^^^^ Where does it belong??? Perhaps this thread belongs "someplace else" -ivo
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: bill@bilver.uucp (Bill Vermillion) Subject: Re: Floppy drive problems under NextStep 486 Organization: W. J. Vermillion - Orlando / Winter Park, FL Date: Tue, 20 Jul 1993 15:08:10 GMT Message-ID: <1993Jul20.150810.4935@bilver.uucp> Keywords: floppy, nextstep References: <CA3tDH.MoK@news.cso.uiuc.edu> In article <CA3tDH.MoK@news.cso.uiuc.edu> archetyp@uxh.cso.uiuc.edu (Joseph R Pickert) writes: >I have a NCR system 3333 on which I can't seem to get the floppy working >correctly. >I can format, read, and write to the floppy just fine under >DOS, so I am pretty sure there is nothing wrong with the drive itself. That can be a very wrong assumption! Ask the tech who got fired because they wouldn't come out to replace a floppy that worked under DOS but failed under Unix. The quote was "If it works under DOS it has to be a Unix problem". Bad move Bix! DOS looks at the media to determine the disk type. It tries to read the first track. If it can do that then it formats to the density that was on the disk. And Unix systems can vary, but this one looked to see if there was a disk in the drive and that it was not write protected. (3.5" media). You could format 'air' in the UNIX device, it just failed when it tried to verify the non-existant disk it just formatted. Of course, loading the heads together with no media between them is a bit hard on heads too. The problem was a failed sensor or LED. That would have also over-written and disk that was write-protected too. I'm not saying that your problem is a failed drive, but the reasoning that "it works under DOS so it must be okay" is flawed because they access their devices in differing ways. -- Bill Vermillion - bill@bilver.uucp OR bill@bilver.oau.org
Newsgroups: comp.sys.next.bugs From: scott@parsec.mixcom.com (Scott Violet) Subject: Problem opening FD controller on Intel machines Message-ID: <1993Jul20.135736.1314@parsec.mixcom.com> Organization: SmartSoft Distribution: usa Date: Tue, 20 Jul 1993 13:57:36 GMT HI all, I am wondering if this is a bug, or if something was set up wrong on the machine that I tried the following on. The following snipet returns errno == 6, "No such device or address". open("/dev/fdc0", O_RDONLY, 0); I tried this is as root on the Intel machine and it didn't work. I also verified that /dev/fdc0 did indeed exist. The above line works fine on the NeXT's here, but then on the Intel machine I tried it barfed. Does this work for other people on Intels? Thanks in advance, -Scott Violet (scott@parsec.mixcom.com)
Newsgroups: comp.sys.next.bugs From: thf@zelator.in-berlin.de (Thomas Funke) Subject: Re: Thrid Party CDs hang NS3.1 Message-ID: <1993Jul20.145754.424@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization References: <1993Jul19.114135.17143@investor.pgh.pa.us> Date: Tue, 20 Jul 1993 14:57:54 GMT In article <1993Jul19.114135.17143@investor.pgh.pa.us> rbp@investor.pgh.pa.us (Bob Peirce #305) writes: > > Since NS3.0 worked, I thought I could boot a 3.0 kernel, log into the > console, mount the disk, do my work and re-boot under 3.1. However, I > found that under both 3.0 and 3.1 I could not mount a CD with the mount The kernel (3.0) is not enough to mount a foreign CD-Rom. You need the old, 3.0, file-system, too. /thomas> l /usr/filesystems/CDROM.fs/ !!!!! 3.0 System !!!!!! total 80 -r--r--r-- 1 root 3546 Mar 26 1992 CDROM.fs.tiff -rw-r--r-- 1 root 5 Jul 20 16:46 CDROM.label -rw-r--r-- 1 root 16 Jul 20 16:46 CDROM.name -r--r--r-- 1 root 3546 Mar 26 1992 CDROM.openfs.tiff -rwsr-xr-x 1 root 24576 Jul 22 1992 CDROM.util* -rw-r--r-- 1 root 46224 Jul 22 1992 CDROM_reloc You could check, if your upgrade script made a mistake copying all those files. At least this was the case with the upgrade of 2.1 -> 3.0. -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brook's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: sanguish@digifix.com (Scott Anguish) Subject: Re: This is a worthless group Message-ID: <1993Jul20.180040.2088@digifix.com> Sender: sanguish@digifix.com (Scott Anguish) Organization: Digital Fix Development References: <1993Jul20.010405.5866@nic.csu.net> Date: Tue, 20 Jul 1993 18:00:40 GMT EPS writes > I agree with Glenn, Diana, and Scott. :-) > > Unfortunately, the problem is not confined to comp.sys.next.bugs, > although it is probably most severe here. Perhaps it would help > to have a regular (weekly?) posting to .announce that explains > what the various newsgroups are all about. (Not that I expect it > to do much good...) Eric... Well, thats no problem. I will post that every week in announce. The only reason I haven't been posting the groups charters is because nobody seems to have a copy! :-) If there are no complaints about Eric's "charters" then I will start using them with the summaries today. -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
Newsgroups: comp.sys.next.bugs From: prail@doc.tip.ameslab.gov (Joel Prail) Subject: New, and Useful, Serial Port Drivers Message-ID: <CAHGy5.Dow@news.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA Date: Tue, 20 Jul 1993 21:56:25 GMT I had a chat with a developer of some serial communications software about these nice serial drivers that NeXT designed. She said that they are currently using some new drivers that WoRK just fine, and she would be able to give these out to developers who begged enough and could get special permission from NeXT. Then she said that they would be available at the end of July along with several other drivers (right from NeXT). Yeah. Now if someone would write drivers for the DigiBoard multiport serial card....
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: set-user-id bit getting stripped by write from root Message-ID: <CAHG7D.12A@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI Date: Tue, 20 Jul 1993 21:40:28 GMT Dear Folks, I didn't set a good example with my last post on this issue. I made the claim that write(2) would strip the set-user-id bit, even when done as root, and I also mentioned how this caused the "strip" command to bite me, but I didn't provide examples. Since to the best of my knowledge these bugs occur only under 3.1 (we don't have a 3.0 system to verify this on) and because people frequently complain of non-existent problems, it makes sense that I actually post a small program that illustrates this problem. Here it is, directly from Stuart (Scott Hess's Terminal replacement). bash# cat write_demo.c #include <assert.h> #include <sys/file.h> #include <sys/stat.h> #include <stdio.h> #include <stdlib.h> #include <libc.h> #define TESTFILE "testfile" int main(void) { int fd; struct stat sbuf; char buf[512]; int retval; assert(getuid() == 0); unlink(TESTFILE); fd = creat(TESTFILE, S_ISUID|0755); assert(fd >= 0); assert(fstat(fd, &sbuf) == 0); assert(sbuf.st_mode & S_ISUID); assert(write(fd, buf, sizeof(buf)) == sizeof(buf)); assert(fstat(fd, &sbuf) == 0); if (!(sbuf.st_mode & S_ISUID)) { fprintf(stderr, "Write fried the set-user-id bit\n"); retval = EXIT_FAILURE; } else retval = EXIT_SUCCESS; return retval; } bash# make write_demo CFLAGS='-O -Wall' cc -O -Wall write_demo.c -o write_demo bash# ./write_demo Write fried the set-user-id bit Since we now have an executable hanging around, here's an example of the evil strip bug: bash# chmod u+s write_demo bash# ls -l write_demo -rwsrwxr-x 1 root wheel 50144 Jul 20 14:47 write_demo bash# strip write_demo bash# ls -l write_demo -rwxrwxr-x 1 root wheel 16384 Jul 20 14:50 write_demo Lest you think this has to do with networked filesystems, here is proof that all this is being done in "/tmp" on the root disk. bash# df . Filesystem 1024-blocks Used Available Capacity Mounted on /dev/sd0a 402253 324385 37642 90% / --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: df@watershed.com (Dirk P. Fromhein) Subject: Re: Dell and Adaptec Message-ID: <CAHqpo.KK@ripple.uunet> Sender: jaeger@ripple.uunet (Dirk P. Fromhein) Organization: Watershed Technologies, Inc. References: <1993Jul20.120709.6512@lxki.toppoint.de> Date: Wed, 21 Jul 1993 01:27:24 GMT We use the Adaptec 1542B in all our Intel GX systems, and for those that we send out the door with NS installed we use the 1542B for the install. The Intel GX is an EISA system and it does work. We have also used it on a generic EISA system and it worked.... well almost, but that was a problem with the keyboard and mouse that we were trying to use. Are all the jumper setting correct? (I can send you our settings if you would like) Dirk Fromhein df@watershed.com Watershed technologies, inc. In article <1993Jul20.120709.6512@lxki.toppoint.de> laux@lxki.toppoint.de (Thorsten Laux) writes: > jds@aplpy.jhuapl.edu (John D Stanhope) writes: > > >Has anyone got the below error on there system and been able to fix > >it? > > >AHA interrupt: bad status ff > >sd0: INVALID STATUS (Internal error): FATAL ERROR > > target:0 lun: 0 op: Read block: some # blockcount: some # > > > I have exactly the same problem trying to install Nextstep for Intel > on 2 different Eisa Systems with ATI ISA Ultra Pro and another > Graphics Card and a 1542b Controller. I suspect you cannot get the > 1542b to work in an Eisa System. Has anybody succeeded in doing this ? > > Thorsten Laux > -- > Thorsten Laux, Schuhmacherstr. 27/29, 2300 Kiel, FRG, > Voice: +49 431 96334, email: laux@lxki.toppoint.de > >
Newsgroups: comp.sys.next.bugs From: zulu!errol (Errol Ginsberg) Subject: Re: NSFIP: 800x600 broken? Message-ID: <1993Jul20.210600.2502@ridgeback.com> Sender: errol@ridgeback.com Organization: Ridgeback Solutions References: <CAFCus.70u@ccu.umanitoba.ca> Date: Tue, 20 Jul 1993 21:06:00 GMT In article <CAFCus.70u@ccu.umanitoba.ca> tacchi@ccu.umanitoba.ca (Mark G. Tacchi) writes: > In <CAF07o.DEH@cosy.sbg.ac.at> bnocker@cosy.sbg.ac.at (Bernhard Nocker) writes: > > > >Dear netters, > > >has anyone observed problems with 800x600x16? My LocalBus ATI Mach32 compatible > >grphic card displays stripes (small but annoying) on the right side of the > >screen. Maybe a bug in the driver or bus timing problems! > > >Any suggestions welcome, > >Bernie > > >-- > > > Check your refresh rate in Configure.app. Use the Select... button. Also, > your card may not be 100% compatible with the ATI. > > -Mark > -- > Mark G. Tacchi tacchi@ccu.umanitoba.ca > "Medicine will cure death and government will repeal taxes > before Steve will fail." -G.Kawasaki I too have an ATI Mach32 LocalBus video. It displays stripes on the left side when windows are moved around. This problem is less evident when using 1024x768 resolution. The problem is that 1024x768 only works in non-interlaced mode. -- Regards, Errol Ginsberg Ridgeback Solutions Tel: 310/456-6094 Fax: 310/456-9715 -- Regards, Errol Ginsberg Ridgeback Solutions
Newsgroups: comp.sys.next.bugs From: strebel1@gwdu03.gwdg.de (Stephan Trebels ) Subject: timezone Preferences Message-ID: <VOKFBLQB@gwdu03.gwdg.de> Organization: GWDG, Goettingen Date: Wed, 21 Jul 1993 11:54:05 GMT Hi folks, since I have my NeXT in Germany I wondered, why one has even the Poland choice in the timezone Preferences, but the standard MET is missing. Ok, one can link /etc/zoneinfo/localtime, and disable setting the time... Somehow I do not like it. So does anyone know where Preferences get the Information "Poland and GMT+1 belong to this part of the world, but MET does not" from? Or is this bug fixed in 3.1 (still waiting for 3.1 to be delivered :-(, so I can't try) Ciao, Stephan
From: droege@infko.uni-koblenz.de (Detlev Droege) Newsgroups: comp.sys.next.bugs Subject: Re: Frame NOT broken in 3.1! Date: 21 Jul 1993 17:10:33 GMT Organization: CC/CS Uni-Koblenz Distribution: world Message-ID: <22jta9INN5g5@mailhost.uni-koblenz.de> References: <1993Jul14.121825.21332@macc.wisc.edu> In article <1993Jul14.121825.21332@macc.wisc.edu> anderson@macc.wisc.edu (Jess Anderson) writes: > FrameMaker (3.0 running under NS 3.0) seems to generate such > traffic: while running if I stay in it long enough and in > any case (this is the *really* curious part) when I quit it. > > Maybe it's looking for NFS-mounted volumes (I have none) or > something, but it's not especially desirable behavior, since > there are cost consequences for spurious connections. > > Anyone else seen this or have any idea what to do about it, > if anything? It's FrameMakers license protection mechanism. It scans the network for other copies of FrameMaker running with the same license string. When you start FrameMaker twice on different machines using the same license string, periodically a panel pops up telling you just that. It's so annoying that you want another license ... Detlev -- Detlev Droege, Universitaet Koblenz, | droege@infko.uni-koblenz.de Institut fuer Informatik | (NeXTmail ok) Rheinau 1, | Voice: +49 261 9119-421 D-56075 Koblenz, Germany | Fax: +49 261 9119-499
From: jmb@merit.edu (Jim Blum) Newsgroups: comp.sys.next.bugs Subject: S3 video bugs? Date: 21 Jul 1993 18:08:53 GMT Organization: Merit Network, Inc. Ann Arbor, MI Distribution: world Message-ID: <22k0nl$f3p@terminator.rs.itd.umich.edu> I can't seem to get my STB PowerGraph to work with NS/I. Has anyone else had problems with S3 cards? I get an image, but it look to be out of sync, but I'm using a CTX multisync monitor. Anybody know if NeXT will be releasing new S3 drivers? What's the deal? Should I just go out and buy an ATI? ---------------------------------------------------------------- jmb@merit.edu "NEXTSTEP - the real hackers operating system"
Newsgroups: comp.sys.next.bugs From: debaud@cc.gatech.edu (Jean-Marc Debaud) Subject: INSTALLATION BUG SOLVED. Message-ID: <1993Jul21.194729.5664@cc.gatech.edu> Sender: news@cc.gatech.edu Organization: Georgia Tech College of Computing Date: Wed, 21 Jul 1993 19:47:29 GMT To everyone on the net who may have had this problem. System: Compaq 486/66M Qvision graphics NEC CD-ROM 74-1 SCSI id 1 Quatum 1225S SCSI id 0 NEC Multisync 5gf DPT 2012/B/90 SMC elite 16 card. Problem 1. Would not recognize cd-rom in system. Then: Configure DPT card for IRQ 15 edge trigerred. Choose I/O mode to secondary/non bootable. This with the EISA configure utility. then, Problem 2. System would then recognize the CD-ROM but still crashed later on after resetting the SCSI BUS. Actually it would loop forever on the cd-rom. then: Configure DPT card with a maximum SCSI bus transfer rate of 5 M/sec. I had 10 M/sec and it didn't work. Note: That may have been a problem with my particular CD-ROM. Installation will then proceed. JM debaud@cc.gatech.edu NOTE: FLAMES TO NeXT FOR THEIR INCAPACITY TO GIVE US MORE INSTALLATION DETAILS ON THE PLATFORM (HARWARE SUCH AS THE DPT CARD) THEY RECOMMENDED. THIS IS NOT ACCEPTABLE FROM A COMPANY THAT NOW RELIES ON SOFTWARE. I NEARLY GAVE UP. I MUST NOT BE THE ONLY ONE.
Newsgroups: comp.sys.next.bugs From: eboltz@acoustica.mrd.bldrdoc.gov (Eric S. Boltz) Subject: nextspell strange guess!? Message-ID: <CAJ8rq.9tv@dove.nist.gov> Sender: news@dove.nist.gov Organization: NIST Date: Wed, 21 Jul 1993 20:55:01 GMT In Edit.app (under NS3.0) I ran the spell check and it came across this misspelling: performace It's first guess at the correct spelling was: performqce ************************* WHAT?? *********************** There's no way I added that to the dictionary! I also can't get it to "Forget" this word(?). Any clues what's up here?? Thanks, Eric -- Eric S. Boltz, M.S.E. *eboltz@nist.gov* Materials Research Engineer eboltz@jhunix.hcf.jhu.edu National Institute of Standards and Technology NeXTMail Accepted (Ph.D. Candidate, Johns Hopkins University) My views, opinions and statements in no way reflect those of the U.S. Gov't, the U.S. Department of Commerce or NIST.
Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin,comp.sys.next.bugs From: mark@cyantic.com (Mark T. Dornfeld) Subject: Re: Dell and Adaptec Organization: CYANTIC Systems Date: Wed, 21 Jul 1993 14:45:42 GMT Message-ID: <1993Jul21.144542.2229@cyantic.com> References: <1993Jul16.184504.12770@aplcen.apl.jhu.edu> <1993Jul20.120709.6512@lxki.toppoint.de> In article <1993Jul20.120709.6512@lxki.toppoint.de> laux@lxki.toppoint.de (Thorsten Laux) writes: >jds@aplpy.jhuapl.edu (John D Stanhope) writes: > >>Has anyone got the below error on there system and been able to fix >>it? > >>AHA interrupt: bad status ff >>sd0: INVALID STATUS (Internal error): FATAL ERROR >> target:0 lun: 0 op: Read block: some # blockcount: some # > > >I have exactly the same problem trying to install Nextstep for Intel >on 2 different Eisa Systems with ATI ISA Ultra Pro and another >Graphics Card and a 1542b Controller. I suspect you cannot get the >1542b to work in an Eisa System. Has anybody succeeded in doing this ? According to the June 8 HW Compatibility Guide, NS/FIP does not support an EISA Adaptec Controller (1740/1742). I wonder if this lack of support will also prevent the ISA version from working in the EISA bus. -- Mark T. Dornfeld, CYANTIC Systems Voice: (416) 234-9048 101 Subway Crescent Suite 2103 Facsimile: (416) 234-0477 Etobicoke, Ontario, M9B 6K4 CANADA Email: mark@cyantic.com
From: toon@moene.indiv.nluug.nl (Toon Moene) Newsgroups: comp.sys.next.bugs Subject: Introduced in 3.1: set-user-id bit getting stripped by write from root Message-ID: <481@moene.indiv.nluug.nl> Date: 21 Jul 93 19:52:14 GMT References: <CAHG7D.12A@cobra.cs.unm.edu> Sender: toon@moene.indiv.nluug.nl Organization: Moene Computational Physics, Amsterdam, The Netherlands In article <CAHG7D.12A@cobra.cs.unm.edu> ctm@ardi.com writes: > Dear Folks, > > I didn't set a good example with my last post on this issue. I made the > claim that write(2) would strip the set-user-id bit, even when done as > root, and I also mentioned how this caused the "strip" command to bite > me, but I didn't provide examples. Since to the best of my knowledge > these bugs occur only under 3.1 (we don't have a 3.0 system to verify this > on) and because people frequently complain of non-existent problems, it > makes sense that I actually post a small program that illustrates this > problem. Here it is, directly from Stuart (Scott Hess's Terminal replacement). [ ... example deleted ... ] Under NeXTSTEP 3.0: # hostinfo Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 3 Board revision: 0x0 Primary memory available: 12.00 megabytes. Default processor set: 40 tasks, 69 threads, 1 processors Load average: 1.16, Mach factor: 0.06 # pwd /private/tmp # cat > write_demo.c # Copied directly from Cliff's post #include <assert.h> #include <sys/file.h> #include <sys/stat.h> #include <stdio.h> #include <stdlib.h> #include <libc.h> #define TESTFILE "testfile" int main(void) { int fd; struct stat sbuf; char buf[512]; int retval; assert(getuid() == 0); unlink(TESTFILE); fd = creat(TESTFILE, S_ISUID|0755); assert(fd >= 0); assert(fstat(fd, &sbuf) == 0); assert(sbuf.st_mode & S_ISUID); assert(write(fd, buf, sizeof(buf)) == sizeof(buf)); assert(fstat(fd, &sbuf) == 0); if (!(sbuf.st_mode & S_ISUID)) { fprintf(stderr, "Write fried the set-user-id bit\n"); retval = EXIT_FAILURE; } else retval = EXIT_SUCCESS; return retval; } # make write_demo CFLAGS='-O -Wall' cc -O -Wall write_demo.c -o write_demo # ./write_demo # chmod u+s write_demo # ls -l write_demo -rwsr-xr-x 1 root 48944 Jul 21 21:47 write_demo* # strip write_demo # ls -l write_demo -rwsr-xr-x 1 root 16384 Jul 21 21:47 write_demo* New and completely different :-) -- Toon Moene (toon@moene.indiv.nluug.nl) Kantershof 269, 1104 GN Amsterdam, The Netherlands Phone: + 31 20 6982029; Fax: + 31 20 6003411 No Disclaimers; a NeXT@home protects against this occupational hazard. NB: Strictly black hardware here - No Intel inside :-)
Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs From: jespiau@solent.oleane.com (Jean Espiau) Subject: Problem with InterfaceBuilder.app Message-ID: <1993Jul21.154739.10819@solent.oleane.com> Sender: news@solent.oleane.com Organization: solent - Montpellier, France. Date: Wed, 21 Jul 1993 15:47:39 GMT I m working on a NeXT cube (68040, 25 Mhz) whith the release 3.1. With InterfaceBuilder.app I m creating a simple application with the DBKit palette to have acces to a sybase database. After I built (compile and linked) the application, it works correctly but in test mode InterfaceBuilder.app crashes and in the console.log file I have the message Jul 21 15:23:42 mistral InterfaceBuilder[10445]: Error loading /NextLibrary/Adaptors/SybaseAdaptor.adaptor/SybaseAdaptor Has anyone an idea about what happens ? Thanks for your help. -- ----------------------- Jean Espiau Email (NeXT Mail accepted) Societe SOLENT / NeXT VAD jespiau@solent.oleane.com Immeuble le Stratege Z.A. du Millenaire phone : (+33) 67 69 74 14 34000 Montpellier - France fax : (+33) 67 69 74 91
From: kschulz@iva.k8.rt.bosch.de (Kay Schulz K8/IVA Tel. ++49-7121-35-1341) Newsgroups: comp.sys.next.bugs Subject: UUCP Message-ID: <160@boschrt.rt.bosch.de.bosch.de> Date: 22 Jul 93 08:23:45 GMT Sender: news@rt.bosch.de.bosch.de Organization: Robert Bosch GmbH., Reutlingen, Germany. Hi I use NSI 3.1 and the bundled uucp. I am able to connect to the remote machine and I can login. But then the following happens: root gold (7/21-22:19-374) SUCCEEDED (call to gold ) imsg looking for SYNC< login: root gold (7/21-22:20-374) TIMEOUT (gold) Any help? --- /********************************************************************/ /* Kay Schulz, Rheinstr. 24, 72768 Reutlingen, Germany */ /* 07121 / 60 19 61 privat */ /* 07121 / 35-1341 geschaeftlich */ /* */ /* kschulz@iva.k8.rt.bosch.de */ /* */ /* Violence is the last refuge of the incompetent. */ /* -- Salvor Hardin */ /* */ /********************************************************************/
From: peterk@pknms.toppoint.de (Peter Kretzschmar) Newsgroups: comp.sys.next.hardware,comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Dell and Adaptec Message-ID: <743334314peterk.postmast@pknms.toppoint.de> Sender: postmast@pknms.toppoint.de Date: Thu, 22 Jul 93 09:45:14 GMT References: <1993Jul16.184504.12770@aplcen.apl.jhu.edu> <1993Jul20.120709.6512@lxki.toppoint.de> <1993Jul21.144542.2229@cyantic.com> Organization: private site In article <1993Jul21.144542.2229@cyantic.com> mark@cyantic.com (Mark T. Dornfeld) writes: >In article <1993Jul20.120709.6512@lxki.toppoint.de> laux@lxki.toppoint.de (Thorsten Laux) writes: >>jds@aplpy.jhuapl.edu (John D Stanhope) writes: >> >> >>I have exactly the same problem trying to install Nextstep for Intel >>on 2 different Eisa Systems with ATI ISA Ultra Pro and another >>Graphics Card and a 1542b Controller. I suspect you cannot get the >>1542b to work in an Eisa System. Has anybody succeeded in doing this ? > >According to the June 8 HW Compatibility Guide, NS/FIP does not support an >EISA Adaptec Controller (1740/1742). I wonder if this lack of support will >also prevent the ISA version from working in the EISA bus. Last week, i've installed NS/FIP in a machine with EISA board and 1542c, but without ATI. My fine 1742 went's into the shelf. Peter -- Peter Kretzschmar +49 4321 41471 peterk@pknms.toppoint.de Grossflecken 54 24534 Neumuenster GERMANY
From: ctm@ardi.com Newsgroups: comp.sys.next.bugs Subject: Re: Introduced in 3.1: set-user-id bit getting stripped by write from root Message-ID: <CAK5KK.53A@cobra.cs.unm.edu> Date: 22 Jul 93 08:43:35 GMT Article-I.D.: cobra.CAK5KK.53A References: <CAHG7D.12A@cobra.cs.unm.edu> <481@moene.indiv.nluug.nl> Sender: news@cobra.cs.unm.edu Organization: ARDI I received e-mail from a NeXT employee who said the 3.0 behaviour was a bug and that IEEE 1003.1-1988 (POSIX) section 5.6.1.2 says "On a regular file, this bit should be cleared on any write." So it's POSIX's fault. I don't know much about POSIX so I don't know whether it mentions how strip(1) should behave. I'll keep on my toes now and assume that any and all utilities will potentially mess with my file permission settings without any hint that they have done so. I'll also mistrust the NeXT man pages just a little more, but seeing how we originally coded Executor to "Inside Macintosh" specifications, it's amazing that I believe *any* information in any documentation. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: erwin@helsinki.ks.uiuc.edu (Edgar Erwin) Subject: Re: nextspell strange guess!? Date: Thu, 22 Jul 1993 18:13:21 GMT Message-ID: <CAKvyA.9I1@news.cso.uiuc.edu> References: <CAJ8rq.9tv@dove.nist.gov> Sender: usenet@news.cso.uiuc.edu (Net Noise owner) Organization: University of Illinois at Urbana Eric S. Boltz writes > In Edit.app (under NS3.0) I ran the spell check and it came across this > misspelling: performace > > It's first guess at the correct spelling was: performqce > > ************************* WHAT?? *********************** > The dictionary used by the spell checker has many very odd spellings in it. Z's and Q's are oddly common. Use it with caution. In this case, just make it learn the correct spelling of performance and you should be all right, most of the time. Of course, if you do actually type performqce in a file, the spell checker will also think it is ok, so beware! *------------------------------------------------------------* Ed Erwin erwin@lisboa.ks.uiuc.edu 3117 Beckman Institute (NeXT Mail accepted) 405, N. Mathews, Urbana, IL 61801 *------------------------------------------------------------*
From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.bugs Subject: Re: nextspell strange guess!? Message-ID: <1279@rtbrain.rightbrain.com> Date: 22 Jul 93 22:14:51 GMT References: <CAJ8rq.9tv@dove.nist.gov> Sender: glenn@rightbrain.com Eric S. Boltz writes > In Edit.app (under NS3.0) I ran the spell check and it came across this > misspelling: performace > > It's first guess at the correct spelling was: performqce There are a whole bunch of those. The guys at HSD, when creating HSD Spell, found dozens of interesting bugs in the NeXT spell checker. I can only remember one: put the word "asshole" in a document (or just spell check some random usenet posting :-). See what it suggests as a correction.... -- Glenn Reid NeXTmail: glenn@rightbrain.com RightBrain Software 415-326-2974 (NeXTfax 326-2977) Palo Alto, California Electronic Frontier Foundation, member #054
Newsgroups: comp.sys.next.bugs From: elisei@dingo.imag.fr (Frederic Elisei ) Subject: RDP Connection,WindowServer & FrameBuffer bugs. Message-ID: <CAKMp3.GMn@imag.fr> Keywords: Trouble when/after installing 3.1 FIP Sender: elisei@dingo (Frederic Elisei ) Organization: IMAG Institute, University of Grenoble, France Date: Thu, 22 Jul 1993 14:53:26 GMT During installing Next Step 3.1 FIP,I encountered some of the error messages following : * RDP Connection ( What is RDP ?? Since I removed the ethernet card it seemed to arrive very less often ) * class FrameBuffer not linked to application * WindowServer kaput -> no more windows,all goes out , alt-num doesn't work any left : must reset,wich often crashes some files ... All this errors seem to happen randomly,causing the machine to be totally unuseable. I already retried the installation many times and several days ... But as RDP connection usally raised during the installation, the installation is in fact made in 2 or 3 times , wich should explain the further troubles ! Has someone already had this troubles ?? Do you have ANY advice ?? We have an Intel GX , Adaptec 1542B . I shutdowned IDE DMA ... What can I try now ?? Thanks a lot for any Help ! ------------------------------------------- |||||| +------+ =| |= ELISEI Frederic ( ARM Powered ) =| ARM2 |= =| |= Frederic.Elisei@imag.fr +------+ |||||| TEQP PC,#0
Newsgroups: comp.sys.next.bugs From: bnocker@cosy.sbg.ac.at (Bernhard Nocker) Subject: Re: Dell and Adaptec Message-ID: <CAM99K.Ms3@cosy.sbg.ac.at> Sender: news@cosy.sbg.ac.at Organization: University of Salzburg / Austria References: <743334314peterk.postmast@pknms.toppoint.de> Date: Fri, 23 Jul 1993 11:58:32 GMT In article <743334314peterk.postmast@pknms.toppoint.de> peterk@pknms.toppoint.de (Peter Kretzschmar) writes: > In article <1993Jul21.144542.2229@cyantic.com> mark@cyantic.com (Mark T. Dornfeld) writes: > >In article <1993Jul20.120709.6512@lxki.toppoint.de> laux@lxki.toppoint.de (Thorsten Laux) writes: [...] > >According to the June 8 HW Compatibility Guide, NS/FIP does not support an > >EISA Adaptec Controller (1740/1742). I wonder if this lack of support will > >also prevent the ISA version from working in the EISA bus. > > Last week, i've installed NS/FIP in a machine with EISA board > and 1542c, but without ATI. My fine 1742 went's into the shelf. Just to follow up with my experiences: I have installed NS/FIP on an EISA macine with Adaptec-1742C AND LB ATI Graphics Ultra Pro compatible graphics card. Works great! Bernhard -- Bernhard Nocker University of Salzburg's Department of Computing Studies Jakob-Haringerstr. 5 5020 Salzburg Austria, Europe Tel: +43-662-8044/6316 bnocker@cosy.sbg.ac.at Fax: +43-662-8044/6316 or +43-662-8044/611
Newsgroups: comp.sys.next.bugs From: eboltz@acoustica.mrd.bldrdoc.gov (Eric S. Boltz) Subject: Re: nextspell strange guess!? Message-ID: <CAMIAs.326@dove.nist.gov> Sender: news@dove.nist.gov Organization: NIST References: <1279@rtbrain.rightbrain.com> Date: Fri, 23 Jul 1993 15:13:39 GMT In article <1279@rtbrain.rightbrain.com> glenn@rightbrain.com (Glenn Reid) writes: > I can only remember one: put the word "asshole" in a document (or just > spell check some random usenet posting :-). Gosh you're such as asshozle! 8-) At least I don't have to worry too much about that sort of typo at work! -- Eric S. Boltz, M.S.E. *eboltz@nist.gov* Materials Research Engineer eboltz@jhunix.hcf.jhu.edu National Institute of Standards and Technology NeXTMail Accepted (Ph.D. Candidate, Johns Hopkins University) My views, opinions and statements in no way reflect those of the U.S. Gov't, the U.S. Department of Commerce or NIST.
Newsgroups: comp.sys.next.bugs From: amon@lix.polytechnique.fr (Laurent Amon) Subject: Re: nextspell strange guess!? Message-ID: <amon.743444032@mallorne.polytechnique.fr> Sender: news@polytechnique.fr (USENET News System) Organization: Ecole Polytechnique, Palaiseau, France References: <CAJ8rq.9tv@dove.nist.gov> <CAKvyA.9I1@news.cso.uiuc.edu> Date: Fri, 23 Jul 1993 16:13:52 GMT In comp.sys.next.bugs erwin@helsinki.ks.uiuc.edu (Edgar Erwin) writes: >Eric S. Boltz writes >> In Edit.app (under NS3.0) I ran the spell check and it came across this >> misspelling: performace >> >> It's first guess at the correct spelling was: performqce >> >> ************************* WHAT?? *********************** >> > >The dictionary used by the spell checker has many very odd spellings in it. >Z's and Q's are oddly common. [...] Looks like somebody may have had trouble with QWERTY/AZERTY. In France, we use these keyboard... A and Q are inverted, as well as Z and W. M is next to L on the second row, and a few other things. Are correlated errors also common? Lga. --- Laurent Amon | e-mail: amon@lix.polytechnique.fr | So far, the universe is winning. amon@cs.stanford.edu |
Newsgroups: comp.sys.next.bugs From: robert@ictv.com (Robert Patrick Thille) Subject: Problem with assigning to doubles? Please confirm. Message-ID: <1993Jul23.180710.26739@ictv.com> Sender: usenet@ictv.com Organization: ICTV, Santa Clara, CA (408) 562-9200 Distribution: usa Date: Fri, 23 Jul 1993 18:07:10 GMT There seems to be a problem with assigning to doubles. ==================cut here==================== /* atoftest.c */ #include <stdio.h> main() { double base; base = atof("10.0"); printf("%f\n",base); printf("%f\n",atof("10.0")); } /* nextoid_robert> cc atoftest.c -o atoftest nextoid_robert> atoftest 1076101120.000000 10.000000 ATOF(3) UNIX Programmer's Manual ATOF(3) NAME atof, atoi, atol - convert ASCII to numbers SYNOPSIS double atof(nptr) char *nptr; nextoid_robert> hostinfo Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 52.00 megabytes. Default processor set: 70 tasks, 134 threads, 1 processors Load average: 0.40, Mach factor: 0.86 nextoid_robert> cc atoftest.c -o atoftest nextoid_robert> atoftest 1076101120.000000 10.000000 */ ===================cut here============================= -- Robert Thille NeXTMail robert@ictv.com OK At All 1548 Maple Ave. RWC CA 94063 Addresses
Newsgroups: comp.sys.next.bugs From: obrooks@worf.hssc.ksc.nasa.gov (Oscar Brooks) Subject: CD Audio - Problem Message-ID: <1993Jul23.181322.4866@dale.ksc.nasa.gov> Keywords: CD Audio CDPlayer Sender: news@dale.ksc.nasa.gov Organization: NASA Date: Fri, 23 Jul 1993 18:13:22 GMT We have a small network of NeXT machines (8) each equiped with CD-ROMs from NeXT. On one of the machines everytime certain users place a music CD in the drive we get the following error in the console window: sd3 (6,0): ERROR op:0x28 sd_state:4 scsi status:0x0 cdaudio.util: CANNOT OPEN CDPlayer The Last line is the difference from normal operation. We get the preceeding lines of error during normal operation. I have checked permissions on the device and CDPlayer.app. Sticky bit is set on CDPlayer.app and the device is readable by everyone. The thing that is puzzling is that it only happens to certian user ids: 22, 33, etc. Everyone else has no problem with the same CD. Can anyone help??? Please!!! O ------------------------------------------------ Oscar Brooks Mail Code: DL-DSD-24 Kennedy Space Center, Fla. 32899 Internet: obrooks@worf.hssc.ksc.nasa.gov
Newsgroups: comp.sys.next.bugs From: magnus@fisher.Stanford.EDU (Magnus Nordborg) Subject: WM error 38001 Message-ID: <1993Jul23.185459.23299@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: DSO, Stanford University Date: Fri, 23 Jul 93 18:54:59 GMT Several people have reported being logged out by "Error 38001" (you know, the one where you continue at your own risk...:). This has happened to me too, and the following has been in /private/adm/messages every time: Jul 20 18:41:08 fisher mach: sd2: UNIT ATTENTION Jul 20 18:41:08 fisher mach: sd2 (4,0): ERROR op:0x28 sd_state:4 scsi status:0x0Jul 20 18:41:08 fisher mach: sd2 (4,0): sense key:0x6 additional sense code:0x29 Jul 20 18:41:08 fisher mach: SCSI Block in error = 0 (no valid label) Jul 20 18:41:09 fisher WM[171]: Unknown error code 38001 in NXReportError Jul 20 18:49:20 fisher loginwindow[163]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. I'm running 3.1 on a 25MHz station with a NeXT CD-ROM as sd2 (I keep the developer docs there). It seems that the problem is caused by some form of scsi error from the CD. Does this agree with other observations? I have reported this to NeXT as well. If the CD is the problem it clearly needs to be fixed, but an easy work-around for the person who declared 3.1 useless a while back might be to eject the CD (or certainly to disconnect the CD-player). -- Magnus Nordborg magnus@fisher.stanford.edu (NeXT mail preferred) Department of Biological Sciences Stanford University Stanford, CA 94305-5020 +1 (415) 723-4952 (office)
From: croehrig@cs.ubc.ca (Chris Roehrig) Newsgroups: comp.sys.next.bugs Subject: Re: Problem with assigning to doubles? Please confirm. Message-ID: <22pdjkINN7em@jax.cs.ubc.ca> Date: 23 Jul 93 19:19:16 GMT References: <1993Jul23.180710.26739@ictv.com> Distribution: na Organization: Computer Science, University of B.C., Vancouver, B.C., Canada In article <1993Jul23.180710.26739@ictv.com> robert@ictv.com (Robert Patrick Thille) writes: > There seems to be a problem with assigning to doubles. > #include <stdio.h> > > main() > { > double base; > base = atof("10.0"); > printf("%f\n",base); > printf("%f\n",atof("10.0")); > } > > /* > nextoid_robert> cc atoftest.c -o atoftest > nextoid_robert> atoftest > 1076101120.000000 > 10.000000 Good ol' C. If you compile with -Wall, you'll see the problem: % cc -Wall atoftest.c -o atoftest atoftest.c:6: warning: implicit declaration of function `atof' so that atof is implicitly declared to return an int, not a double, and the compiler converts what it thinks to be a 32 bit int to a 64 bit double. Solution: #include <stdlib.h> (where atof is declared) and always compile with -Wall! -- Chris Roehrig (croehrig@cs.ubc.ca) Small Neural Systems Group Dept. of Computer Science, University of British Columbia, Canada -- Chris Roehrig (croehrig@cs.ubc.ca) Small Neural Systems Group Dept. of Computer Science, University of British Columbia, Canada
From: dittrich@stein2.u.washington.edu (Dave Dittrich) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin,comp.sys.next.misc Subject: Bug in sendmail under NS 3.0? Date: 23 Jul 1993 21:33:25 GMT Organization: University of Washington Message-ID: <22plf5$43e@news.u.washington.edu> I am trying to set up a program designed to process email messages automtically for automating and tracking help desk messages. I have been encountering a problem indicated by this message: ... ----- Transcript of session follows ----- sh: 24739 Memory fault 554 "|/usr/redusers/qna/bin/qna -t testers@3pin.cac.washington.edu -r helptest@3 pin.cac.washington.edu"... 554 unknown mailer error 139 ----- Unsent message follows ----- ... Some of the messages make it through fine, and others produce this message. Does anyone know what consitutes a "Memory fault" in the Borne Shell and what I can do to get around (or debug) this problem? You can reply to me via email at dittrich@cac.washington.edu, since I don't frequent these particular newsgroups. Thanks in advance.
From: karthy@dannug.dk (Karsten Thygesen) Newsgroups: comp.sys.next.bugs Subject: Re: nextspell strange guess!? Date: 24 Jul 1993 21:15:39 GMT Organization: Dannug - Danish NeXT Users Group Message-ID: <KARTHY.93Jul24231540@dannug.dannug.dk> References: <1279@rtbrain.rightbrain.com> <CAMIAs.326@dove.nist.gov> In-reply-to: eboltz@acoustica.mrd.bldrdoc.gov's message of Fri, 23 Jul 1993 15:13:39 GMT >>>>> Regarding Re: nextspell strange guess!?; eboltz@acoustica.mrd.bldrdoc.gov (Eric S. Boltz) adds: > I can only remember one: put the word "asshole" in a document (or just > spell check some random usenet posting :-). Eric> Gosh you're such as asshozle! Eric> 8-) Eric> At least I don't have to worry too much about that sort of typo at work! And if you did: Try to check out what Webster suggests as substitute for "asshozle". I think we have an infinite loop here... Karsten.
Newsgroups: comp.sys.next.bugs Subject: DBKit bug(s) Message-ID: <5993204.78559.8491@kcbbs.gen.nz> From: David_Boyle@kcbbs.gen.nz (David Boyle) Date: 24 Jul 93 21:49:19 GMT Organization: Kappa Crucis Unix BBS, Auckland, New Zealand Hi, We have found two 'behaviours' of the DBValue object quite dangerous, and were wondering if we are misunderstanding the way they work. The behaviours result in the same problem. 1 - When you use the DBRecordList methods: getValue:forProperty: getValue:forProperty:at: strings and objects are NOT copied. This means that after a call to one of those routines, the DBValue may hold a pointer to a piece of data *inside* the record list (in the case of string and object). If you free the DBValue, then the record lists copy of the string is freed. i.e. DBValue *value = [[DBValue alloc] init]; ... [[[module rootFetchGroup] recordList] getValue:value forProperty:aProperty at:0]; ... [value free]; may cause a crash if aProperty is of type string. 2 - DBValue copy is the default bitwise copy which means that you get the same behaviour when using it. i.e. DBValue *value; ... value = [someValue copy]; ... [value free]; may cause a crash if someValue holds a string, since someValue's copy of the string has just been freed. Is my understanding of this behaviour correct. i.e. are strings not being duplicated (we are sure about that) and free is freeing the string pointed to by a DBValue. Thanks for any guidance. David Boyle.
From: rbp@investor.pgh.pa.us (Bob Peirce #305) Newsgroups: comp.sys.next.software,comp.sys.next.bugs Subject: Re: Third Party CDs hang NS3.1 Message-ID: <1993Jul24.054336.27028@investor.pgh.pa.us> Date: 24 Jul 93 05:43:36 GMT Organization: Cookson, Peirce & Co., Pittsburgh, PA The other day I posted about a problem with third party CDs under NS3.1. N. Tomczak-Jaegermann at vega.math.ualberta.ca provided a solution that works. Here's what I did, based on his info. As ROOT cd /usr/filesystems mv CDROM.fs CDROM3.1.fs Load the NS3.0 CDRom and copy the CDROM.fs directory to /usr/filesystems. cd /usr/filesystems/CDROM.fs chmod u+s CDROM.util The last command is necessary so users other than root can use it. As near as I can tell you don't have to re-boot. When you put a CDRom in the OS goes out looking for these files fresh, each time. I had already re-booted before I noticed this. -- Bob Peirce, Pittsburgh, PA rbp@investor.pgh.pa.us 412-471-5320 venetia@investor.pgh.pa.us [NeXT Mail] !uunet.uu.net!pitt!investor!rbp [UUCP]
From: marcus@ursula.ee.pdx.edu (Marcus Daniels) Newsgroups: comp.sys.next.bugs Subject: What happens when terminal closed, and/or on logout? Date: 25 Jul 1993 17:22:34 -0700 Message-ID: <22v84a$2ol@ursula.ee.pdx.edu> Summary: nohup'ed processes started at terminal prompt hang when terminal closed Suppose you run this perl script under 3.1... I wanted to run ps repeatedly to check on a custom daemon. When the terminal is closed, the process hangs, but does not die. If `Terminal' is not quit, and a new terminal is opened, the process continues. I thought it might have to do with I/O blocking. Redirecting I/O from /dev/null doesn't help. If `Terminal' is quit altogether, and you log out, the process never restarts (but still exists). None of the signals here indicate why it hangs. #!/usr/local/bin/perl/perl require "ctime.pl"; open(pslog,"> psrun.log"); sub sighup { print stderr "sighup 1\n"; } $SIG{"HUP"}=sighup; # 1 sub sigint { print stderr "sigint 2\n"; } $SIG{"INT"}=sigint; # 2 sub sigquit { print stderr "sigquit 3\n"; } $SIG{"QUIT"}=sigquit; # 3 sub sigill { print stderr "sigill 4\n"; } $SIG{"ILL"}=sigill; # 4 sub sigtrap { print stderr "sigtrap 5\n"; } $SIG{"TRAP"}=sigtrap; # 5 sub sigabrt { print stderr "sigabrt 6\n"; } $SIG{"ABRT"}=sigabrt; # 6 $SIG{"IOT"}=sigabrt; # 6 sub sigemt { print stderr "sigemt 7\n"; } $SIG{"EMT"}=sigemt; # 7 sub sigfpe { print stderr "sigfpe 8\n"; } $SIG{"FPE"}=sigfpe; # 8 sub sigkill { print stderr "sigkill 9\n"; } $SIG{"KILL"}=sigkill; # 9 sub sigbus { print stderr "sigbus 10\n"; } $SIG{"BUS"}=sigbus; # 10 sub sigsegv { print stderr "sigsegv 11\n"; } $SIG{"SEGV"}=sigsegv; # 11 sub sigsys { print stderr "sigsys 12\n"; } $SIG{"SYS"}=sigsys; # 12 sub sigpipe { print stderr "sigpipe 13\n"; } $SIG{"PIPE"}=sigpipe; # 13 sub sigalrm { print stderr "sigalrm 14\n"; } $SIG{"ALRM"}=sigalrm; # 14 sub sigterm { print stderr "sigterm 15\n"; } $SIG{"TERM"}=sigterm; # 15 sub sigurg { print stderr "sigurg 16\n"; } $SIG{"URG"}=sigurg; # 16 sub sigstop { print stderr "sigstop 17\n"; } $SIG{"STOP"}=sigstop; # 17 sub sigtstp { print stderr "sigtstp 18\n"; } $SIG{"TSTP"}=sigtstp; # 18 sub sigcont { print stderr "sigcont 19\n"; } $SIG{"CONT"}=sigcont; # 19 sub sigchld { print stderr "sigchld 20\n"; } $SIG{"CHLD"}=sigchld; # 20 $SIG{"CLD"}=sigchld; # 20 sub sigttin { print stderr "sigttin 21\n"; } $SIG{"TTIN"}=sigttin; # 21 sub sigttou { print stderr "sigttou 22\n"; } $SIG{"TTOU"}=sigttou; # 22 sub sigio { print stderr "sigio 23\n"; } $SIG{"IO"}=sigio; # 23 sub sigxcpu { print stderr "sigxcpu 24\n"; } $SIG{"XCPU"}=sigxcpu; # 24 sub sigxfsz { print stderr "sigxfsz 25\n"; } $SIG{"XFSZ"}=sigxfsz; # 25 sub sigvtalrm { print stderr "sigvtalrm 26\n"; } $SIG{"VTALRM"}=sigvtalrm; # 26 sub sigprof { print stderr "sigprof 27\n"; } $SIG{"PROF"}=sigprof; # 27 sub sigwinch { print stderr "sigwinch 28\n"; } $SIG{"WINCH"}=sigwinch; # 28 sub siglost { print stderr "siglost 29\n"; } $SIG{"LOST"}=siglost; # 29 sub sigusr1 { print stderr "sigusr1 30\n"; } $SIG{"USR1"}=sigusr1; # 30 sub sigusr2 { print stderr "sigusr2 31\n"; } $SIG{"USR2"}=sigusr2; # 31 $val=0; for($val=0;$val<100;$val++) { open(pslog,">>psrun.log"); print pslog &ctime(time); close(pslog); system("ps -aux >> psrun.log"); sleep 1; }
From: marcus@ursula.ee.pdx.edu (Marcus Daniels) Newsgroups: comp.sys.next.bugs Subject: Re: What happens when terminal closed, and/or on logout? Message-ID: <22vdug$3ns@ursula.ee.pdx.edu> Date: 25 Jul 93 12:01:52 GMT Article-I.D.: ursula.22vdug$3ns References: <22v84a$2ol@ursula.ee.pdx.edu> marcus@ursula.ee.pdx.edu (Marcus Daniels) writes: >Suppose you run this perl script under 3.1... The previously mentioned script occurs with a similar shell script, also. Just starts sleeping and doesn't wake up.
From: ctm@ardi.com Newsgroups: comp.sys.next.bugs Subject: /bin/as: PC Indirect+Index (8-bit displacement) incorrectly assembled Summary: NS3.1's assembler mishandles a rare bit of assembly Message-ID: <CArFny.E3C@cobra.cs.unm.edu> Date: 26 Jul 93 07:04:48 GMT Article-I.D.: cobra.CArFny.E3C Sender: news@cobra.cs.unm.edu Organization: ARDI Dear Folks, If you don't use assembly language, this bug *probably* doesn't concern you. I say probably because I'm not positive that gcc will never generate this sequence, but I am *fairly* sure. The trouble is that for some reason a negative displacement gets turned to a positive displacement. Before you jump to the conclusion that I have botched, please read all of what I sent to NeXT. Pay close attention to the differences between the two examples. This is of course an instance of the computer science urban legend that you repeatedly hear when you're a campus consultant: I just recompiled my program __and I didn't make *any* changes__ and now it's not working! Of course in my case, I did make a change, but nowhere near where the code that suddenly succumbed to bit rot. When I backed out the change (using RCS no less) the bug was still there. It was hard for me to believe that I hadn't reassembled the particular source file in a long (approx. 3 months) time, but that's the explanation that fits. WORKAROUND: use ":w" instead of ":b" for the displacement. --Cliff ctm@ardi.com [BTW, Executor uses very little assembly, but the file that this comes from is our major source of assembly. It's all the glue that handles the messed up Mac calling conventions. Of course the Intel version doesn't use this file.] Here's what I sent NeXT: I just reassembled some assembly language code that's part of Executor, our Macintosh emulator and it stopped working. I traced it down to the following instruction: pack4here: movel pc@(p4table-pack4here-2:b,d0:w:4), sp@(2) Now before you decide I'm a bozo and that there must be overflow when computing p4table-pack4here-2, please understand that the displacement *is supposed to be negative* and bear in mind two things. The example below shows that the use of 29 long directives between p4table and pack4here produces a different offset than a .space 29 * 4, even though every other instance of the code remains unchanged. Furthermore, our code used to work (the change I made to the assembly source was not related to this dispatch). Here'e an example of the instruction working correctly: iclone 1.179 cat foo1.s p4table: .space 29 * 4 pack4here: movel pc@(p4table-pack4here-2:b,d0:w:4), sp@(2) iclone 1.180 cc -v -g -c foo1.s && otool -tV foo1.o Reading specs from /lib/m68k/specs NeXT Computer, Inc. version cc-210.obj~2, gcc version 2.2.2 /lib/m68k/cpp -lang-asm -v -D__GNU__ -undef -$ -Dmc68000 -Dm68k -DNeXT -Dunix -DNX_COMPILER_RELEASE_3_0=300 -DNX_COMPILER_RELEASE_3_1=310 -DNX_CURRENT_COMPILER_RELEASE=310 -D__mc68000__ -D__m68k__ -D__NeXT__ -D__unix__ -D__MACH__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__=\"m68k\" -D__NX_COMPILER_RELEASE_3_0__=300 -D__NX_COMPILER_RELEASE_3_1__=310 -D__NX_CURRENT_COMPILER_RELEASE__=310 -D__mc68000 -D__m68k -D__NeXT -D__unix -D__NX_COMPILER_RELEASE_3_0=300 -D__NX_COMPILER_RELEASE_3_1=310 -D__NX_CURRENT_COMPILER_RELEASE=310 -D__ASSEMBLER__ -g -D__STDC__ -D_NEXT_SOURCE foo1.s /usr/tmp/cc000759.s GNU CPP version 2.2.2 (68k, MIT syntax) /lib/m68k/as -arch m68k -o foo1.o /usr/tmp/cc000759.s foo1.o: (__TEXT,__text) section p4table: 00000000 orb #0x0,d0 00000004 orb #0x0,d0 00000008 orb #0x0,d0 0000000c orb #0x0,d0 00000010 orb #0x0,d0 00000014 orb #0x0,d0 00000018 orb #0x0,d0 0000001c orb #0x0,d0 00000020 orb #0x0,d0 00000024 orb #0x0,d0 00000028 orb #0x0,d0 0000002c orb #0x0,d0 00000030 orb #0x0,d0 00000034 orb #0x0,d0 00000038 orb #0x0,d0 0000003c orb #0x0,d0 00000040 orb #0x0,d0 00000044 orb #0x0,d0 00000048 orb #0x0,d0 0000004c orb #0x0,d0 00000050 orb #0x0,d0 00000054 orb #0x0,d0 00000058 orb #0x0,d0 0000005c orb #0x0,d0 00000060 orb #0x0,d0 00000064 orb #0x0,d0 00000068 orb #0x0,d0 0000006c orb #0x0,d0 00000070 orb #0x0,d0 pack4here: 00000074 movel pc@(0xffffff8a:b,d0:w:4),sp@(0x2:w) 0000007a nop Here's an example of it not working: iclone 1.181 cat foo2.s p4table: .long _P_ROMlib_Faddx /* 00 */ .long _P_ROMlib_Fsetenv /* 01 */ .long _P_ROMlib_Fsubx /* 02 */ .long _P_ROMlib_Fgetenv /* 03 */ .long _P_ROMlib_Fmulx /* 04 */ .long 0 /* 05 */ .long _P_ROMlib_Fdivx /* 06 */ .long 0 /* 07 */ .long _P_ROMlib_Fcmpx /* 08 */ .long _P_ROMlib_Fdec2x /* 09 */ .long _P_ROMlib_FcpXx /* 0A */ .long _P_ROMlib_Fx2dec /* 0B */ .long _P_ROMlib_Fremx /* 0C */ .long _P_ROMlib_FnegX /* 0D */ .long _P_ROMlib_Fx2X /* 0E */ .long _P_ROMlib_FabsX /* 0F */ .long _P_ROMlib_FX2x /* 10 */ .long _P_ROMlib_Fcpysgnx/* 11 */ .long _P_ROMlib_FsqrtX /* 12 */ .long 0 /* 13 */ .long _P_ROMlib_FrintX /* 14 */ .long 0 /* 15 */ .long _P_ROMlib_FtintX /* 16 */ .long _P_ROMlib_Fprocentry /* 17 */ .long _P_ROMlib_FscalbX /* 18 */ .long _P_ROMlib_Fprocexit /* 19 */ .long _P_ROMlib_FlogbX /* 1A */ .long _P_ROMlib_Ftestxcp /* 1B */ .long _P_ROMlib_Fclassx /* 1C */ pack4here: movel pc@(p4table-pack4here-2:b,d0:w:4), sp@(2) iclone 1.182 cc -v -g -c foo2.s && otool -tV foo2.o Reading specs from /lib/m68k/specs NeXT Computer, Inc. version cc-210.obj~2, gcc version 2.2.2 /lib/m68k/cpp -lang-asm -v -D__GNU__ -undef -$ -Dmc68000 -Dm68k -DNeXT -Dunix -DNX_COMPILER_RELEASE_3_0=300 -DNX_COMPILER_RELEASE_3_1=310 -DNX_CURRENT_COMPILER_RELEASE=310 -D__mc68000__ -D__m68k__ -D__NeXT__ -D__unix__ -D__MACH__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__=\"m68k\" -D__NX_COMPILER_RELEASE_3_0__=300 -D__NX_COMPILER_RELEASE_3_1__=310 -D__NX_CURRENT_COMPILER_RELEASE__=310 -D__mc68000 -D__m68k -D__NeXT -D__unix -D__NX_COMPILER_RELEASE_3_0=300 -D__NX_COMPILER_RELEASE_3_1=310 -D__NX_CURRENT_COMPILER_RELEASE=310 -D__ASSEMBLER__ -g -D__STDC__ -D_NEXT_SOURCE foo2.s /usr/tmp/cc000764.s GNU CPP version 2.2.2 (68k, MIT syntax) /lib/m68k/as -arch m68k -o foo2.o /usr/tmp/cc000764.s foo2.o: (__TEXT,__text) section p4table: 00000000 orb #0x0,d0 00000004 orb #0x0,d0 00000008 orb #0x0,d0 0000000c orb #0x0,d0 00000010 orb #0x0,d0 00000014 orb #0x0,d0 00000018 orb #0x0,d0 0000001c orb #0x0,d0 00000020 orb #0x0,d0 00000024 orb #0x0,d0 00000028 orb #0x0,d0 0000002c orb #0x0,d0 00000030 orb #0x0,d0 00000034 orb #0x0,d0 00000038 orb #0x0,d0 0000003c orb #0x0,d0 00000040 orb #0x0,d0 00000044 orb #0x0,d0 00000048 orb #0x0,d0 0000004c orb #0x0,d0 00000050 orb #0x0,d0 00000054 orb #0x0,d0 00000058 orb #0x0,d0 0000005c orb #0x0,d0 00000060 orb #0x0,d0 00000064 orb #0x0,d0 00000068 orb #0x0,d0 0000006c orb #0x0,d0 00000070 orb #0x0,d0 pack4here: 00000074 movel pc@(0x16:b,d0:w:4),sp@(0x2:w) 0000007a nop
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: /bin/as: PC Indirect+Index (8-bit displacement) incorrectly assembled Message-ID: <CArGxB.E4t@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI References: <CArFny.E3C@cobra.cs.unm.edu> Date: Mon, 26 Jul 1993 07:32:01 GMT Silly me. ":w" doesn't solve the problem. You do get a negative displacement, but not the right negative displacement... --Cliff
Newsgroups: comp.sys.next.bugs,de.comp.sys.next From: thf@zelator.in-berlin.de (Thomas Funke) Subject: Please confirm these bugs for NS3.1/Motorila Message-ID: <1993Jul25.172545.1079@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization Date: Sun, 25 Jul 1993 17:25:45 GMT It has been reported that under 3.1 Motorola PLI - (SCSI-) Floppy drives can no longer format (initialize) NeXT-Disks (NeXT-file system) Foreign (ISO) CD-ROMs (non Next-filesystem) cannot been read. If you have 3.1 running, please check those bugs. Please report your results here, especially if the things mentioned above do work on your machine. Thanks ! -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brook's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
From: wmorse@erasure-sl.cc.emory.edu (William Morse) Newsgroups: comp.sys.next.bugs Subject: Re: Please confirm these bugs for NS3.1/Motorila Date: 26 Jul 1993 17:56:53 GMT Organization: Emory University, Dept of Math and CS Distribution: world Message-ID: <2315t5INNa8n@emory.mathcs.emory.edu> References: <1993Jul25.172545.1079@gamelan> In article <1993Jul25.172545.1079@gamelan> thf@zelator.in-berlin.de (Thomas Funke) writes: > > It has been reported that under 3.1 Motorola <munch> > Foreign (ISO) CD-ROMs (non Next-filesystem) cannot been read. > > > If you have 3.1 running, please check those bugs. Please report your > results here, especially if the things mentioned above do work on your > machine. > > Thanks ! > --------------------------------------------------------------------------------------------- My Color Turbo runing NS 3.1 with a real NeXT CD-ROM drive read every CD-ROM I through at it, NeXT or no. This includes CD-ROMs meant for PC and Apple... All worked. - William Consult. / ITD :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Emory Law Student
From: kiwi@cs.tu-berlin.de (Axel Habermann) Newsgroups: comp.sys.next.bugs Subject: ?bug: ATC decompression aborted. Truncated input file? Date: 26 Jul 1993 20:47:16 GMT Organization: Technical University of Berlin, Germany Message-ID: <231fsk$m1n@news.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit Keywords: sndcompress, sound, bug Hello! After upgrading to NS3.1 (Moto), there are some sounds which can't be played. Under 3.0 there's no problem to play those sounds. On the console the following message appears: ATC decompression aborted. Truncated input file? I tried several tools to play the sound, but it doesn't work. Sometimes the machine produces the message, sometimes it doesn't, but no sound is heard anyway. I would like to ask everyone who has installed 3.1 to try it and report the results to see if this is a bug in 3.1 or not! Try it with the sounds of DarkForest.app, they didn't work with me. Thanks! Axel -- Axel Habermann \\|// FaxFon: +49 30 4543046 Fehmarnerstr. 4 )o o( eMail: kiwi@cs.tu-berlin.de 13353 Berlin (Wedding) \ | / "Wenn Du nicht weisst Germany \~/ was du tust, mach's mit Eleganz!"
Newsgroups: comp.sys.next.bugs From: ntomczak@vega.math.ualberta.ca (N Tomczak-Jaegermann) Subject: printing and scanning formats still broken in 3.1 Message-ID: <ntomczak.743657808@vega> Keywords: fprintf,fscanf Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada Date: Mon, 26 Jul 1993 03:36:48 GMT In version 3.1 of NeXTstep %g format of fprintf and scanf are still broken - exactly like it was reported in 2.0/2.1 days. Deep sigh!!! Here is a result of test run with a newly recompiled on 3.1 an interactive tcl interpreter. Expected results follow what ANSI standard says that they should be. format.test ==== format-4.3 g-format ==== Contents of test case: format "%.3g" 123.412345 ==== Result was: 123.412 ---- Result should have been: 123 ---- format-4.3 FAILED ==== format-4.4 g-format ==== Contents of test case: format "%.3g" 12.3412345 ==== Result was: 12.341 ---- Result should have been: 12.3 ---- format-4.4 FAILED ==== format-4.5 g-format ==== Contents of test case: format "%.3g" 1.23412345 ==== Result was: 1.234 ---- Result should have been: 1.23 ---- format-4.5 FAILED ==== format-4.6 g-format ==== Contents of test case: format "%.3g" 1.23412345 ==== Result was: 1.234 ---- Result should have been: 1.23 ---- format-4.6 FAILED ==== format-4.8 g-format ==== Contents of test case: format "%.3g" .012341 ==== Result was: 0.012 ---- Result should have been: 0.0123 ---- format-4.8 FAILED ==== format-4.9 g-format ==== Contents of test case: format "%.3g" .0012341 ==== Result was: 0.001 ---- Result should have been: 0.00123 ---- format-4.9 FAILED ==== format-4.10 g-format ==== Contents of test case: format "%.3g" .00012341 ==== Result was: 0 ---- Result should have been: 0.000123 ---- format-4.10 FAILED ==== format-4.12 g-format ==== Contents of test case: format "%.4g" 9999.6 ==== Result was: 9999.6 ---- Result should have been: 1e+04 ---- format-4.12 FAILED ==== format-4.13 g-format ==== Contents of test case: format "%.4g" 999.96 ==== Result was: 999.96 ---- Result should have been: 1000 ---- format-4.13 FAILED ==== format-5.3 floating-point zeroes ==== Contents of test case: format "%#.4e %#.4f %#.4g" 0.0 0.0 0.0 0.0 ==== Result was: 0.0000e+00 0.0000 0.0000 ---- Result should have been: 0.0000e+00 0.0000 0.000 ---- format-5.3 FAILED And this stuff for scanning. When scanning octal numbers scanf obviously swallows non-octal digits. Big NO-NO. scan.test ==== scan-1.22 integer scanning ==== Contents of test case: set a {}; set b {}; set c {}; set d {} scan "12345670 1234567890ab cdefg" "%o %o %x %X" a b c d set b ==== Result was: 175304776 ---- Result should have been: 342391 ---- scan-1.22 FAILED ==== scan-1.23 integer scanning ==== Contents of test case: set a {}; set b {}; set c {}; set d {} scan "12345670 1234567890ab cdefg" "%o %o %x %X" a b c d A set c ==== Result was: 171 ---- Result should have been: 561323 ---- scan-1.23 FAILED ==== scan-2.22 floating-point scanning ==== Contents of test case: set a {}; set b {}; set c {}; set d {} scan "4.6 99999.7 876.43e-1 118" "%f %f %f %e" a b c d set b ==== Result was: 99999.703125 ---- Result should have been: 99999.7 ---- scan-2.22 FAILED ==== scan-2.23 floating-point scanning ==== Contents of test case: set a {}; set b {}; set c {}; set d {} scan "4.6 99999.7 876.43e-1 118" "%f %f %f %e" a b c d set c ==== Result was: 87.642998 ---- Result should have been: 87.643 ---- scan-2.23 FAILED Michal Jaegermann ntomczak@vega.math.ualberta.ca
Newsgroups: comp.sys.next.bugs From: gordie@cyclesoft.com (Gordie Freedman) Subject: Re: Please confirm these bugs for NS3.1/Motorila Message-ID: <1993Jul26.213546.2470@netcom.com> Sender: gordie@netcom.com Organization: Cyclesoft Media Works References: <1993Jul25.172545.1079@gamelan> Date: Mon, 26 Jul 1993 21:35:46 GMT In article <1993Jul25.172545.1079@gamelan> thf@zelator.in-berlin.de (Thomas Funke) writes: > > It has been reported that under 3.1 Motorola > > PLI - (SCSI-) Floppy drives can no longer format (initialize) > NeXT-Disks (NeXT-file system) > I just formatted a quad density (2.4) floppy in the standard floppy drive on my NSC (Motorola) running 3.1 - I can also format 1.2 meg floppies for all three file systems (NeXT, Mac, PC). No problems reading/writing the foreign floppy file systems either (DOS, Mac). -- >>> Gordie Freedman -> gordie@cyclesoft.com NeXTMail Yes! >>> Thou shalt not inline functions more complicated than 20
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: ?bug: ATC decompression aborted. Truncated input file? Message-ID: <CAsMo3.I51@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota Hospital and Clinic, Labratory Information Services References: <231fsk$m1n@news.cs.tu-berlin.de> Date: Mon, 26 Jul 1993 22:27:07 GMT From NeXTanswers/1158_Pro_Audio_Spectrum_16: ... - Adaptive Transform Coding (ATC) sound compression (used by the sndcompress command line utility) is unsupported under NEXTSTEP Release 3.1. To use sounds stored under this format, use the sndcompress utility under Release 3.0 to convert them first. ... I don't know if I saw it somewhere else too, but it answers your question... peter Axel Habermann wrote: : After upgrading to NS3.1 (Moto), there are some sounds which can't be : played. Under 3.0 there's no problem to play those sounds. On the : console the following message appears: : ATC decompression aborted. Truncated input file? : I tried several tools to play the sound, but it doesn't work. : Sometimes the machine produces the message, sometimes it doesn't, : but no sound is heard anyway. : I would like to ask everyone who has installed 3.1 to try it and report : the results to see if this is a bug in 3.1 or not! Try it with the sounds : of DarkForest.app, they didn't work with me. -- Carpe Diem? peter@tahiti.umhc.umn.edu (Peter Eisch)
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: [[NXBundle alloc] initForDirectory: ""] returns non-nil Organization: Primitive Software Ltd. Date: Sat, 24 Jul 1993 16:01:10 +0000 Message-ID: <1993Jul24.160110.483@prim> Sender: usenet@demon.co.uk Subject line says it all. access() has the same problem. Dave Griffiths PS: Actually it also returns non-nil for any invalid directory.
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: [[NXApp appIcon] setDelegate: foo] doesn't work Organization: Primitive Software Ltd. Date: Sun, 25 Jul 1993 14:45:04 +0000 Message-ID: <1993Jul25.144504.3483@prim> Sender: usenet@demon.co.uk Subject line sums it up. I had to use object_setInstanceVariable(). Also, the documentation for NXDraggingDestination with regard to windows should be improved. It took me ages to figure out the right combination of draggingEntered, draggingUpdated, draggingExited, prepareForDragOperation, performDragOperation and concludeDragOperation (phew! talk about overkill) that the windows delegate had to perform. The same methods I'd used as part of a view subclass didn't work for a window delegate. Dave Griffiths
From: sean@digaudio.byu.edu (Sean Luke) Newsgroups: comp.sys.next.bugs Subject: Just a test... Followup-To: comp.sys.next.bugs Date: 27 Jul 1993 17:03:52 GMT Organization: Brigham Young University Distribution: world Message-ID: <sean-270793110626@rm2221m5.cs.byu.edu> Just a test, everyone. Sorry about the bandwidth. Sean
From: sean@digaudio.byu.edu (Sean Luke) Newsgroups: comp.sys.next.bugs Subject: SoundView Bug Followup-To: comp.sys.next.bugs Date: 27 Jul 1993 17:12:24 GMT Organization: Brigham Young University Distribution: world Message-ID: <sean-270793110655@rm2221m5.cs.byu.edu> I've discovered (after a year of annoyance) a bug in NeXT's SoundView. It seems that if you change the reductionFactor, the bounds rect for the view is changed to reflect the adjusted zoom, but the actual displayed picture in the view is NOT changed unless the integer component of reductionFactor has changed. This is ludicrous. It means that if you change the reductionFactor, you may not be able to see all the sound. Or even up to half the sound! The problem with this is that although I am perfectly willing to zoom in integer amounts for the reductionFactor, I *also* want to "zoom to selection", changing the reductionFactor so my selection just fills a ScrollView's content view. But if the reductionFactor required to do this is not an integer, the samples I'm looking at in the selection no longer reflect my actual selection. I suppose NeXT did this to avoid having to display fractional reductionFactors (for speed), but it's a MAJOR PROBLEM for anyone who's trying to use the SoundView for any real work. I can give code that will demonstrate this bug, if anyone's intrested. Can anybody provide a workaraound, though? Short of only providing integer values for the reductionFactor? Thanks very much, ____________________________________________________________________ Sean Luke Brigham Young University MILK: It Comes From Cows sean@digaudio.byu.edu ____________________________________________________________________
Newsgroups: comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <1993Jul27.174348.8262@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. References: <ntomczak.743657808@vega> Date: Tue, 27 Jul 1993 17:43:48 GMT In article <ntomczak.743657808@vega> ntomczak@vega.math.ualberta.ca (N Tomczak-Jaegermann) writes: > > In version 3.1 of NeXTstep %g format of fprintf and scanf are still > broken - exactly like it was reported in 2.0/2.1 days. Deep sigh!!! > > Here is a result of test run with a newly recompiled on 3.1 an > interactive tcl interpreter. Expected results follow what ANSI > standard says that they should be. > Let me quote from ansi C: Regarding %g: "The e format is used only when the exponent is less than -4 or when it is greater than the value of the Precision field." I believe the %g format of NEXTSTEP is working correctly. > ==== Contents of test case: > > format "%.3g" .0012341 > > ==== Result was: > 0.001 > ---- Result should have been: > 0.00123 > ---- format-4.9 FAILED Since .0012341 in exponential notation is 1.2341 e-03 , and the exponent is NOT less than -4 the correct output with %.3g is 0.001 > > > ==== format-4.12 g-format > ==== Contents of test case: > > format "%.4g" 9999.6 > > ==== Result was: > 9999.6 > ---- Result should have been: > 1e+04 > ---- format-4.12 FAILED > Since 9999.6 in exponential form is 9.9996 e+03, and the exponent +3 is NOT greater than the Precision field of 4, the correct output with "%.4g" is 9999.6 > > Michal Jaegermann > ntomczak@vega.math.ualberta.ca -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: eric@skatter.usask.ca Newsgroups: comp.sys.next.bugs Subject: Re: printing and scanning formats still broken in 3.1 Date: 27 Jul 1993 20:02:11 GMT Organization: University of Saskatchewan Message-ID: <2341k3$3q5@tribune.usask.ca> References: <1993Jul27.174348.8262@instep.wimsey.bc.ca> From article <1993Jul27.174348.8262@instep.wimsey.bc.ca>, by brad@instep.wimsey.bc.ca: > In article <ntomczak.743657808@vega> ntomczak@vega.math.ualberta.ca (N > Tomczak-Jaegermann) writes: >> >> In version 3.1 of NeXTstep %g format of fprintf and scanf are still >> broken - exactly like it was reported in 2.0/2.1 days. Deep sigh!!! >> >> Here is a result of test run with a newly recompiled on 3.1 an >> interactive tcl interpreter. Expected results follow what ANSI >> standard says that they should be. >> > > Let me quote from ansi C: > > Regarding %g: > > "The e format is used only when the exponent is less than -4 or > when it is greater than the value of the Precision field." > > I believe the %g format of NEXTSTEP is working correctly. > > I absolutely *cannot* let this go unchallenged. NeXT's goofy handling of `%g' has been one of my pet peeves since December 1989 when I got my cube! I've reported the bug in *every* software release from 1.0 to 3.0, inclusive, but it never gets fixed. To hear that it is still in 3.1 is most disappointing. The problem isn't just when to switch between `e' and `f'. The problem is more in the way the `f' format is rendered! The ANSI standard (X3.159-1989) says (Section 4.9.6.1, page 134, line 33): g,G The double argument is converted in style f or e (or in style E in the case of a G conversion specifier), with the precision specifying the number of significant digits. If the precision is zero, it is taken as 1. The style used depends on the value converted; style e (or E) will be use only if the exponent resulting from the conversion is less than -4 or greater than or equal to the precision. Trailing zeros are removed from the fractional portion of the result; a decimal-point character appears only if it is followed by a digit. *** NOTE THE WORDS `significant digits'. *** Let's have a look at the examples from the original article: >> >> format "%.3g" .0012341 >> >> ==== Result was: >> 0.001 >> ---- Result should have been: >> 0.00123 The zero's in 0.00123 are *not* significant. Score 1 against NeXT. >> >> format "%.4g" 9999.6 >> >> ==== Result was: >> 9999.6 >> ---- Result should have been: >> 1e+04 >> The format calls for 4 SIGNIFICANT DIGITS. Rounding 9999.6 to four significant digits leaves 10000, which has an exponent equal to the precision and therefore should be printed in e format. Score 2 against NeXT. -- Eric Norum eric@skatter.usask.ca Saskatchewan Accelerator Laboratory University of Saskatchewan Saskatoon, Canada. NeXTMail accepted.
Newsgroups: comp.sys.next.bugs From: hsr@cs.Stanford.EDU (Scott Roy) Subject: BoinkOut.app Message-ID: <1993Jul27.212702.24055@CSD-NewsHost.Stanford.EDU> Sender: news@CSD-NewsHost.Stanford.EDU Organization: CS Department, Stanford University, California, USA Date: Tue, 27 Jul 1993 21:27:02 GMT The sound is broken in BoinkOut.app: NeXTStation Turbo Color Motorola 3.1 Can anyone confirm? I've reinstalled the 3.0 version, which seems to work fine. Scott Roy Department of Computer Science Stanford University
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: BoinkOut.app Message-ID: <CAuGEn.IwC@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota Hospital and Clinic, Labratory Information Services References: <1993Jul27.212702.24055@CSD-NewsHost.Stanford.EDU> Date: Tue, 27 Jul 1993 22:07:00 GMT The 3.1 ATC sound funcs are broken. I saw this [poorly] documented in Nextanswer 1158. Well, it was well documented, but in the wrong spot for such a comment. The fix is to use sndcompress from 3.0 and decompress the soundfiles and all will be well. peter Scott Roy (hsr@cs.Stanford.EDU) wrote: : The sound is broken in BoinkOut.app: : NeXTStation Turbo Color : Motorola 3.1 : Can anyone confirm? I've reinstalled the 3.0 version, which seems to work : fine. : Scott Roy : Department of Computer Science : Stanford University -- Carpe Diem? peter@tahiti.umhc.umn.edu (Peter Eisch)
Newsgroups: comp.sys.next.bugs From: hsr@cs.Stanford.EDU (Scott Roy) Subject: Re: BoinkOut.app Message-ID: <1993Jul28.032936.29208@CSD-NewsHost.Stanford.EDU> Sender: news@CSD-NewsHost.Stanford.EDU Organization: Computer Science Department, Stanford University, California, USA References: <CAuGEn.IwC@news2.cis.umn.edu> Date: Wed, 28 Jul 1993 03:29:36 GMT Peter Eisch writes | | The 3.1 ATC sound funcs are broken. I saw this [poorly] documented in | Nextanswer 1158. Well, it was well documented, but in the wrong spot | for such a comment. The fix is to use sndcompress from 3.0 and | decompress the soundfiles and all will be well. | | peter | Well... That didn't fix it, though it did seem plausible after reading the NeXTanswer. In fact, the output from sndcompress BoinkOut.app/bricks.snd is indentical under 3.0 and 3.1. ??? Scott
Newsgroups: comp.sys.next.bugs From: gordie@cyclesoft.com (Gordie Freedman) Subject: Netmsgserver bugs? Message-ID: <1993Jul28.044314.6793@netcom.com> Sender: gordie@netcom.com Organization: Cyclesoft Media Works Date: Wed, 28 Jul 1993 04:43:14 GMT I keep seeing tehse messages in the console now that I've upgraded to 3.1 - I'm running EngageDesktop (a great app - highly recommended!), and I know it talks to the Workspace (and vice versa) - but I don't know if this has anything to do with it. Jul 27 20:22:53 yamanote netmsgserver[20]: netname_main.msg_send fails, kr = -102. Jul 27 20:22:54 yamanote netmsgserver[20]: netname_main.port_type fails, kr = 4. Jul 27 20:24:23 yamanote pbs: msg_send error: -102, with msg_id = 55 These will appear right after I log in (I do start up a bunch of Apps, including "rsh localhost -l user /NextApps/Mail.app/Mail" - which could be a questionable thing to do). -- >>> Gordie Freedman -> gordie@cyclesoft.com NeXTMail Yes! >>> Thou shalt not inline functions more complicated than 20
From: marcus@ursula.ee.pdx.edu (Marcus Daniels) Newsgroups: comp.sys.next.bugs Subject: What's the last word on the process-limit? Date: 28 Jul 1993 00:39:06 -0700 Message-ID: <235aeq$n07@ursula.ee.pdx.edu> Summary: Process limit? Is the problem really just a simple process limit? Just by having a couple project builder documents open (only compiling one at a given time), a terminal session, screensaver, preferences, the workspace, edit, maybe a couple other apps running eventualy leads to project builder refusing to compile. The wierd thing is it doesn't start to misbehaving like this for 3-4 hours. Kill a few apps, it will work again. But eventually will start to hang again (even with less apps running). Was the <mach-task> problem fixed with 3.1, or not.. I still see them.
Newsgroups: comp.sys.next.bugs From: jon@afs.com Subject: Re: What's the last word on the process-limit? Message-ID: <1993Jul28.145523.1248@afs.com> Sender: jon@afs.com References: <235aeq$n07@ursula.ee.pdx.edu> Date: Wed, 28 Jul 1993 14:55:23 GMT In article <235aeq$n07@ursula.ee.pdx.edu> marcus@ursula.ee.pdx.edu (Marcus Daniels) writes: | Was the <mach-task> problem fixed with 3.1, or not.. I still see | them. The release notes for 3.1 say this was fixed. I don't think they're a problem as long as they don't multiply like rabbits- a condition I haven't seen. According to the notes, they are caused by the "use of select on asynchronous media". -- Jon Hendry It's a thousand classes, give or take a few, <jon@afs.com> I'll be writing more in a week or two. I can make it deeper if you like the style, I can change it round and I want to be an ObjectWare Writer
Newsgroups: comp.sys.next.bugs From: pete@imagine.com (Peter Wyngaard) Subject: Re: SoundView Bug Message-ID: <1993Jul28.151837.1776@imagine.com> Sender: pete@imagine.com (Peter Wyngaard) Organization: Imagine Multimedia, Inc., Ann Arbor, MI, USA References: <sean-270793110655@rm2221m5.cs.byu.edu> Date: Wed, 28 Jul 1993 15:18:37 GMT In article <sean-270793110655@rm2221m5.cs.byu.edu> sean@digaudio.byu.edu (Sean Luke) writes: > I've discovered (after a year of annoyance) a bug in NeXT's SoundView. > It seems that if you change the reductionFactor, the bounds rect for the > view is changed to reflect the adjusted zoom, but the actual displayed > picture in the view is NOT changed unless the integer component of > reductionFactor has changed. Yep, this is one of the problems with NeXT's SoundView. Before writing my own SoundView class, I used to ensure that the reductionFactor was always integral. In order to do a "zoom to selection", just round non-integral reduction factors up. The SoundView will display a little more than just the selection, but you can center it nicely and it doesn't end up looking too bad. I too wasted some time trying to figure out why I was losing samples in the display. I ended up having to disassemble the code for the class in order to understand what was going on. Almost every application I have written I have come up against some strange "feature" of the AppKit which has cost me some time. It's a shame that NeXT feels they can't make the source code for these classes available. Sure would save me some time in getting applications for their platform to market. I guess it would probably lead to rampant subclassing, causing all sorts of problems between AppKit releases. Pete
Newsgroups: comp.sys.next.bugs From: ntomczak@vega.math.ualberta.ca (N Tomczak-Jaegermann) Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <ntomczak.743827530@vega> Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <ntomczak.743657808@vega> <1993Jul27.174348.8262@instep.wimsey.bc.ca> Date: Wed, 28 Jul 1993 02:45:30 GMT brad@instep.wimsey.bc.ca writes: >In article <ntomczak.743657808@vega> ntomczak@vega.math.ualberta.ca (N >Tomczak-Jaegermann) writes: >> >> In version 3.1 of NeXTstep %g format of fprintf and scanf are still >> broken - exactly like it was reported in 2.0/2.1 days. Deep sigh!!! >> >> Here is a result of test run with a newly recompiled on 3.1 an >> interactive tcl interpreter. Expected results follow what ANSI >> standard says that they should be. >> >Let me quote from ansi C: >Regarding %g: >"The e format is used only when the exponent is less than -4 or > when it is greater than the value of the Precision field." >I believe the %g format of NEXTSTEP is working correctly. Well, if you are quoting standard documents maybe you would do that without skipping some vital information? "An optional precision that gives ... the number of digits to appear after the decimal-point character for e, E and f conversions, the maximum number of significant digits for the g and G conversions", with something similar repeated in a description of "g,G" formats. See the difference? >Since .0012341 in exponential notation is 1.2341 e-03 , and >the exponent is NOT less than -4 the correct output with %.3g is 0.001 No, since it does not not contain three __significant__ digits. The only unclear point is if this should be ".00123", or "0.00123". If you do not have an access to an official test suite, then maybe you should check how few other different machines performs these conversions and why? Michal Jaegermann ntomczak@vega.math.ualberta.ca
From: croehrig@cs.ubc.ca (Chris Roehrig) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Is the -M compiler option broken in NS 3.1? Date: 28 Jul 1993 13:45:30 -0700 Organization: Computer Science, University of B.C., Vancouver, B.C., Canada Message-ID: <236ohaINN110@jax.cs.ubc.ca> Under NS 3.1 (black), cc -M seems to trace #include <file> directives ok, but ignores #include "file" inclusions. Same for -MM: it produces no dependencies at all. When I use cc -M -traditional-cpp, it works ok. Is this a known bug in the new cpp-precomp (it's not listed in the Release Notes), or am I just doing something stupid? -- Chris Roehrig (croehrig@cs.ubc.ca) Small Neural Systems Group Dept. of Computer Science, University of British Columbia, Canada -- Chris Roehrig (croehrig@cs.ubc.ca) Small Neural Systems Group Dept. of Computer Science, University of British Columbia, Canada
Newsgroups: comp.sys.next.bugs,de.comp.sys.next From: trebels@desdemona.theo-phys.gwdg.de (Stephan Trebels) Subject: summary: timezone Preferences Message-ID: <1BTFB09I@gwdu03.gwdg.de> Keywords: MET, DST, timezone, zoneinfo Sender: news@gwdu03.gwdg.de (USENET News System) Organization: GWDG, Goettingen Date: Thu, 29 Jul 1993 06:35:50 GMT Hello, because there still arrive answers, I'm posting a summary. I posted a problem not being able to select the standard european times with DST from Preferences.app. It seems to be a problem in a Mach-O section in the Preferences executable named __INFO.labels. There someone simply forgot to include MET, EET, WET, W-SU, and Canada/Newfoundland. Others can also not be selected, but those are available under another name. There are also many compiled timezone files missing from the NeXTSTEP 3.0 distribution. Somehow I didn't want to beleive that one can even select Poland but cannot select MET. NeXT even included the correct compiled timezone files in /etc/zoneinfo in the distribution, you just can't select them from Preferences. The plain text Mach-O section can easily be modified, so now it works as it should. Ciao, Stephan P.S. Poland is *not* the same as CET or MET. It is also GMT+1 with DST but uses another rule *when* to switch. Therefore Poland differs from MET for exactly two hours a year, so perhaps most people won't care ;-} -- +--------------------------------------------------------------+ / Stephan Trebels voice: +49 551 44690 /| +--------------------------------------------------------------+ | | <trebels@theo-phys.gwdg.de> "No NeXTmail yet, it's a HP" | + | <trebels@desdemona.theo-phys.gwdg.de> "NeXTmail welcome" |/ +--------------------------------------------------------------+
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: What's the last word on the process-limit? Message-ID: <1993Jul29.092343.1801@ToTSySSoft.com> Keywords: tasks, tasktable, compress, uncompress Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Jul28.145523.1248@afs.com> Date: Thu, 29 Jul 1993 09:23:43 GMT In article <1993Jul28.145523.1248@afs.com> jon@afs.com writes: -> In article <235aeq$n07@ursula.ee.pdx.edu> -> marcus@ursula.ee.pdx.edu (Marcus Daniels) writes: -> > Was the <mach-task> problem fixed with 3.1, or -> > not.. I still see them. -> The release notes for 3.1 say this was fixed. I don't -> think they're a problem as long as they don't multiply -> like rabbits- a condition I haven't seen. According to -> the notes, they are caused by the "use of select on -> asynchronous media". .. Which is the only right way to handle asyncronous high-speed I/O... Hmmmm In a (likely) related note... Having ftp'd the NeXTanswers from ftp.next.com, I decided to re-compress by directory rather than by individual file or index entry, reading some as I went. I nearly gave up, I had ``Workspace failure -- try to save...'' so many times. Keeping the Compress jobs at 3 or less and insuring that the Decompress NEVER ran simultaneously with a compress job, eventually allowed me to complete the task. Attempting to find out what the problem was, I opened a console, and a couple of terminals to ``tail -1cf'' various logging files. I repeatedly got the ominous can't fork -- or out of tasks messages! Bruce Gingery
Newsgroups: comp.sys.next.bugs From: mdixon@parc.xerox.com (Mike Dixon) Subject: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <mdixon.743966998@thelonius> Sender: news@parc.xerox.com Organization: Xerox PARC Date: 29 Jul 93 17:29:58 GMT about a month ago i started having a problem with my cube: after i had been logged in for a while, my windows (all programs) started displaying times italic when they were supposed to be displaying ohlfs. exiting the window server fixed the problem temporarily, but it always came back fairly soon. at the time i was running 3.0. i assumed i had somehow corrupted some important system file, and upgraded to 3.1 assuming that this would fix it. after two installations (one fast, one slow) it still hadn't gone away, so i eventually figured out that one of my applications must be doing it. finally, with help from jayson adams at millennium, i determined that an eps graphic i had created in virtuoso and placed on one page of my notebook would, when displayed, cause this problem. presumably it triggers a bug in DPS that corrupts some data structure in the font cache. i've forwarded the (quite simple) graphic to altsys, and they're working with next to track down the problem. in the meantime, i wanted to make sure that noone else wasted so much time trying to track down this problem. .mike.
From: gil@ux5.lbl.gov (gil rivlis) Newsgroups: comp.sys.next.bugs Subject: Bug in math.h in NS3.1 Date: 29 Jul 1993 18:51:25 GMT Organization: Lawrence Berkeley Laboratory Distribution: world Message-ID: <23967d$o48@overload.lbl.gov> Keywords: header math.h compiler-flags The folowing code: /* test.c */ #include <math.h> /* end test.c */ when compiled with cc -ansi -pedantic -c test.c Procudes errors: ... /NextDeveloper/Headers/ansi/math.h:67: warning: ANSI C forbids const or volatile functions ... (Many like that) changing test.c /* test.c */ #undef __STRICT_ANSI__ #include <math.h> /* end test.c */ gives (compiles the same): ... /NextDeveloper/Headers/ansi/math.h:36: warning: ANSI C forbids const or volatile functions ... (many like that) /********************************************/ Notes: (1) line numbers for errors are different between two compilations! (2) compiling with gcc (version 2.4.5) works fine. (3) apparantly is used to work fine with NS3.0 Your comments? Gil -- Gil Rivlis, UC Berkeley gil@asterix.lbl.gov Your com
From: toon@moene.indiv.nluug.nl (Toon Moene) Newsgroups: comp.sys.next.bugs Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <490@moene.indiv.nluug.nl> Date: 28 Jul 93 22:06:15 GMT References: <2341k3$3q5@tribune.usask.ca> Sender: toon@moene.indiv.nluug.nl Followup-To: comp.std.c Organization: Moene Computational Physics, Amsterdam, The Netherlands In article <2341k3$3q5@tribune.usask.ca> eric@skatter.usask.ca writes: [... NeXT produces non-standard conforming results from %.nng conversion by (f|s)printf ...] > *** NOTE THE WORDS `significant digits'. *** > Let's have a look at the examples from the original article: > >> > >> format "%.3g" .0012341 > >> > >> ==== Result was: > >> 0.001 > >> ---- Result should have been: > >> 0.00123 > The zero's in 0.00123 are *not* significant. Score 1 against NeXT. > >> > >> format "%.4g" 9999.6 > >> > >> ==== Result was: > >> 9999.6 > >> ---- Result should have been: > >> 1e+04 > >> > The format calls for 4 SIGNIFICANT DIGITS. Rounding 9999.6 to four > significant digits leaves 10000, which has an exponent equal to the > precision and therefore should be printed in e format. Score 2 against > NeXT. % cat try5.c main() { printf("%.3g\n", .0012341); printf("%.4g\n", 9999.6); } % gcc -v try5.c Reading specs from /usr/local/lib/gcc-lib/next/2.4.0/specs gcc version 2.4.0 snapshot 930518 /usr/local/lib/gcc-lib/next/2.4.0/cpp -lang-c -v -undef -D__GNUC__=2 -Dmc68000 -Dm68k -DNeXT -Dunix -D__MACH__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__="m68k" -D__mc68000__ -D__m68k__ -D__NeXT__ -D__unix__ -D__MACH__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__="m68k" -D__mc68000 -D__m68k -D__NeXT -D__unix -D__MACH__ -D__BIG_ENDIAN__ -D__ARCHITECTURE__="m68k" -D__STDC__ -D_NEXT_SOURCE try5.c /usr/tmp/cc000801.i GNU CPP version 2.4.0 snapshot 930518 (68k, MIT syntax) /usr/local/lib/gcc-lib/next/2.4.0/cc1 /usr/tmp/cc000801.i -quiet -dumpbase try5.c -version -o /usr/tmp/cc000801.s GNU C version 2.4.0 snapshot 930518 (68k, MIT syntax) compiled by GNU C version 2.4.0 snapshot 930518. as -o /usr/tmp/cc0008011.o /usr/tmp/cc000801.s ld -lcrt0.o -L/usr/local/lib/gcc-lib/next/2.4.0 -L/usr/local/lib /usr/tmp/cc0008011.o -lgcc -lI77 -lF77 -lsys_s -lgcc % a.out 0.001 9999.6 OK, this is only gcc 2.4.0, whereas the current compiler is 2.4.5, but you'll get the idea. Clearly the people who produce gcc think that this is the correct interpretation of the standard. Questions about that should be redirected to comp.std.c (hereby done). -- Toon Moene (toon@moene.indiv.nluug.nl) Kantershof 269, 1104 GN Amsterdam, The Netherlands Phone: + 31 20 6982029; Fax: + 31 20 6003411 No Disclaimers; a NeXT@home protects against this occupational hazard. NB: Strictly black hardware here - No Intel inside :-)
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Re: SoundView Bug Organization: Primitive Software Ltd. References: <sean-270793110655@rm2221m5.cs.byu.edu> <1993Jul28.151837.1776@imagine.com> Date: Thu, 29 Jul 1993 11:24:56 +0000 Message-ID: <1993Jul29.112456.13849@prim> Sender: usenet@demon.co.uk In article <1993Jul28.151837.1776@imagine.com> pete@imagine.com writes: >I too wasted some time trying to figure out why I was losing samples in >the display. I ended up having to disassemble the code for the class in >order to understand what was going on. Almost every application I have >written I have come up against some strange "feature" of the AppKit which >has cost me some time. Tell me about it. I swear that I used to write plain ordinary unix programs five times faster that NeXT apps :-) simply because unix library calls are atomic and simple and you don't waste time trying to figure out what's really going on underneath. > >It's a shame that NeXT feels they can't make the source code for these >classes available. Sure would save me some time in getting applications >for their platform to market. I guess it would probably lead to rampant >subclassing, causing all sorts of problems between AppKit releases. I'd just like NeXT to make _all_ the methods that a class uses public. I think we have to realize that the technique of making some methods private has failed - the designer of the class simply can't predict all the different ways in which the class will be used/misused. Sooner or later when writing your subclass you discover that the interesting stuff is being done in an undocumented private method. Perhaps methods could be divided into supported and unsupported, the latter with just minimal documentation. Oh and a list of what other methods a method calls would be really useful too. Dave Griffiths
From: croehrig@cs.ubc.ca (Chris Roehrig) Newsgroups: comp.sys.next.bugs Subject: Yup, the -M compiler option is broken in NS 3.1 Date: 29 Jul 1993 19:34:00 GMT Organization: Computer Science, University of B.C., Vancouver, B.C., Canada Message-ID: <2398n8$epu@cs.ubc.ca> References: <236ohaINN110@jax.cs.ubc.ca> It seems that the preprocessor's dependency building gets screwed up when it encounters a precompiled header. Here's some more detail on the problem (NS3.1 Motorola): Create a null file called snert.h (e.g. 'touch snert.h'). Create snert.m: ---------------BEGIN snert.m ------------------------- #include <objc/Object.h> #include "snert.h" ---------------END snert.m --------------------------- The output should be: jax[113]% cc -MM -traditional-cpp snert.m snert.o : snert.m snert.h But with precompiled headers it's: jax[112]% cc -MM snert.m snert.o : If you switch the two #include lines around, you get: jax[116]% cc -MM snert.m snert.o : snert.h If you replace the #include <objc/Object.h> line with the actual contents of Object.h, the problem goes away. Since Object.h is the only precompiled header in /usr/include/objc, this suggests that the problem is with precompiled headers. Workaround: Create your dependency relationships with the -traditional-cpp option. --- Chris Roehrig (croehrig@cs.ubc.ca) Small Neural Systems Group Dept. of Computer Science, University of British Columbia, Canada
Newsgroups: comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <1993Jul29.190644.15002@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. References: <ntomczak.743827530@vega> Date: Thu, 29 Jul 1993 19:06:44 GMT In article <ntomczak.743827530@vega> ntomczak@vega.math.ualberta.ca (N Tomczak-Jaegermann) writes: > brad@instep.wimsey.bc.ca writes: > > >In article <ntomczak.743657808@vega> ntomczak@vega.math.ualberta.ca (N > >Tomczak-Jaegermann) writes: > >> > >> In version 3.1 of NeXTstep %g format of fprintf and scanf are still > >> broken - exactly like it was reported in 2.0/2.1 days. Deep sigh!!! > >> > >> Here is a result of test run with a newly recompiled on 3.1 an > >> interactive tcl interpreter. Expected results follow what ANSI > >> standard says that they should be. > >> > > >Let me quote from ansi C: > > >Regarding %g: > > >"The e format is used only when the exponent is less than -4 or > > when it is greater than the value of the Precision field." > > >I believe the %g format of NEXTSTEP is working correctly. > > Well, if you are quoting standard documents maybe you would do that > without skipping some vital information? > > "An optional precision that gives ... the number of digits to appear > after the decimal-point character for e, E and f conversions, the > maximum number of significant digits for the g and G conversions", > with something similar repeated in a description of "g,G" formats. > See the difference? > > >Since .0012341 in exponential notation is 1.2341 e-03 , and > >the exponent is NOT less than -4 the correct output with %.3g is 0.001 > > No, since it does not not contain three __significant__ digits. > The only unclear point is if this should be ".00123", or "0.00123". > > If you do not have an access to an official test suite, then maybe > you should check how few other different machines performs these > conversions and why? > > Michal Jaegermann > ntomczak@vega.math.ualberta.ca We seem to be arguing two things here... is NeXT (GNU C) implementing the %g format incorrectly, or is what you'd like out of the ANSI C standard NOT what you expected / desired ? Could someone provide examples of output from a different machine's compiler (ANSI C) that implemenents %g to their satisfaction? If "signicant digits" appears in the final ANSI C spec then I believe the implementation is incorrect. However, I do NOT see the word "siginificant" used in either K & R ANSI C (Second Edition) OR in the UNIX man page: K & R ====== g, G double; use %e or %E is th exponent is less than -4 or greater than or equal to the precision; otherwise use %f. Trailing zeros and a trailing decimal point are not printed. K & R descriptions for %e and %f make NO mention of SIGNIFICANT DIGITS. UNIX Manul Page (printf) f The float or double arg is converted to decimal nota- tion in the style `[-]mmm.ddd' where the number of d's is equal to the precision specification. If the preci- sion is missing, 6 digits are given; if the precision is explicitly 0, no d's and no decimal point are printed. e The float or double arg is converted in the style `[-]m.ddde+_xx' where there is one digit before the decimal point and the number of d's after is equal to the precision specification for the argument. When the precision is missing, 6 digits are produced. g The float or double arg is printed in style e if the exponent printed would be less than -4 or greater than or equal to the precision; otherwise, style f is used. Trailing zeros and trailing decimal points are not printed. Perhaps this "significant digits" requirement is final draught ANSI C and that NeXT (GNU C from FSF) is not fully and correctly implementing ANSI C. -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: npratt@madmax.modsys (Nevin Pratt) Newsgroups: comp.sys.next.bugs Subject: Re: Please confirm these bugs for NS3.1/Moto Date: 29 Jul 1993 23:06:52 GMT Organization: Sun Microsystems, Inc. Distribution: world Message-ID: <239l6c$dl@cnn.sim.es.com> References: <1993Jul26.213546.2470@netcom.com> In article 2470@netcom.com, gordie@cyclesoft.com (Gordie Freedman) writes: > In article <1993Jul25.172545.1079@gamelan> thf@zelator.in-berlin.de (Thomas > Funke) writes: > > > > It has been reported that under 3.1 Motorola > > > > PLI - (SCSI-) Floppy drives can no longer format (initialize) > > NeXT-Disks (NeXT-file system) > > > > I just formatted a quad density (2.4) floppy in the standard floppy drive on my > NSC (Motorola) running 3.1 - I can also format 1.2 meg floppies for all three > file systems (NeXT, Mac, PC). > > No problems reading/writing the foreign floppy file systems either (DOS, Mac). Please note that the "standard floppy drive" of the NSC is *NOT* a SCSI device. The original poster specifically mentioned a PLI (SCSI) drive. Hence the above response neither confirms nor denies the problem... Nevin
From: eric@skatter.usask.ca Newsgroups: comp.sys.next.bugs Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <239knm$eto@tribune.usask.ca> Date: 29 Jul 93 22:59:02 GMT References: <1993Jul29.190644.15002@instep.wimsey.bc.ca> Organization: University of Saskatchewan I've got a whole bunch of mail messages on this, and there have been a whole lot of news postings as well. First of all: - This is a LIBRARY issue, not a compiler issue. It doesn't matter *what* version of cc/gcc I use on the NeXT, the problem is in the library supplied by NeXT - K&R II does *not* conflict with the ANSI standard -- it just doesn't `tell the *whole* truth and nothing but the truth'. It mentions when to switch between e and f, but it doesn't say *anything* else. In particular, it *doesn't* say that %.3g should be rendered as %.3e or %.3f it just says that %e or %f should be used, and when to use each. The appendix at the end of K&R II is, ``a summary of the library defined by the ANSI standard''. As such, it leaves the authors/publisher off the hook when they omit (for space reasons, I presume) parts of the standard. - The ANSI standard isn't that expensive, and isn't that hard to read. I can't figure why more people don't just go out and buy it. Here's a little test program, and some results from the machines I have access to at our lab: ============================================================================ #include <stdio.h> int main (int argc, char **argv) { printf ("Expect 0.00123: %.3g\n", 0.001234567); printf ("Expect 123: %.3g\n", 123.4567); printf ("Expect 123.5: %.4g\n", 123.4567); printf ("Expect 1e+03: %.3g\n", 999.6); return 0; } ============================================================================ On a SUN 4/380 (SUNOS 4.1.1): Expect 0.00123: 0.00123 Expect 123: 123 Expect 123.5: 123.5 Expect 1e+03: 1e+03 So it would appear that at least *one* vendor can get it right! On an HP-715 (HP-UX V8 -- I think): Expect 0.00123: 0.00123 Expect 123: 123 Expect 123.5: 123.5 Expect 1e+03: 1e+03 Hmmm...looks like there are at least *two* vendors that can get it right. On a DEC MicroVAX II (Ultrix version 2.2): Expect 0.00123: 0.00123 Expect 123: 123 Expect 123.5: 123.5 Expect 1e+03: 1e+03 Wow, even an antique computer can do this properly! On a NeXTstation color (NeXTSTEP 3.0): Expect 0.00123: 0.001 Expect 123: 123.457 Expect 123.5: 123.4567 Expect 1e+03: 999.6 Need I say more......... -- Eric Norum eric@skatter.usask.ca Saskatchewan Accelerator Laboratory University of Saskatchewan Saskatoon, Canada. NeXTMail accepted.
Newsgroups: comp.sys.next.bugs From: uunet!lkba!lkb (Larry Blische) Subject: Re: SoundView Bug (long) Message-ID: <1993Jul30.133850.886@lkba.uucp> Sender: lkb@lkba.uucp (Larry Blische) Organization: LKB Associates, Inc. References: <1993Jul29.112456.13849@prim> Date: Fri, 30 Jul 1993 13:38:50 GMT In article <1993Jul29.112456.13849@prim> dave@prim.demon.co.uk (Dave Griffiths) writes: > In article <1993Jul28.151837.1776@imagine.com> pete@imagine.com writes: > >I too wasted some time trying to figure out why I was losing samples in > >the display. I ended up having to disassemble the code for the class in > >order to understand what was going on. Almost every application I have > >written I have come up against some strange "feature" of the AppKit which > >has cost me some time. > > Tell me about it. I swear that I used to write plain ordinary unix programs > five times faster that NeXT apps :-) simply because unix library calls are > atomic and simple and you don't waste time trying to figure out what's really > going on underneath. > > > > >It's a shame that NeXT feels they can't make the source code for these > >classes available. Sure would save me some time in getting applications > >for their platform to market. I guess it would probably lead to rampant > >subclassing, causing all sorts of problems between AppKit releases. > > I'd just like NeXT to make _all_ the methods that a class uses public. I > think we have to realize that the technique of making some methods private > has failed - the designer of the class simply can't predict all the different > ways in which the class will be used/misused. Sooner or later when writing > your subclass you discover that the interesting stuff is being done in an > undocumented private method. > > Perhaps methods could be divided into supported and unsupported, the latter > with just minimal documentation. Oh and a list of what other methods a method > calls would be really useful too. > > Dave Griffiths I've yet to have the opportunity to work on the development on something major with NEXTSTEP, but from the small examples I've done, I can understand the sentiments expressed in these posts. To a beginner, the AppKit is formidable. Having worked with computers for 20 years, I've been a beginner several times. I remember finding the UNIX man pages for the C library concise, and once you learn to drop your assumptions about what you expect a function suite to do, they were clear also. They also had the advantage that they were documenting relatively simple, atomic functions, as Dave puts it. I see the AppKit classes at a higher complexity level. The higher complexity is necessary to bring us greater functionality. Much greater functionality then the simple C library functions. I agree that all methods should be documented, including their support status, but I wouldn't stop there. These classes are sufficiently complex that they require diagrams to explain their inner workings. Verbal descriptions are not enough, I want to see pictures. The NeXT general reference gives good class and method descriptions. They are organized, mostly complete, maybe as concise as they can be given the complexity of the class they are documenting, but they are voluminous. The shear amount of information makes for much reading time. The start-up costs are very great. Following the example used by Dr. Cox, I compare this state of affairs to that in the hardware domain. Think of the class as the black box with labeled pins like a TTL chip. Class methods are represented by the pins and the signals that we place on them. In its documentation, NeXT has given us functional descriptions and pin definitions. I want: block diagrams showing the interconnection of the pins, timing diagrams, electrical characteristics, example circuits (actually they give this to an extent), And I want this information conveyed in graphs, charts and pictures. The block diagram: The function of an 8-bit latch is much clearer when I can see the flip-flops that are inside. The function of the flip-flop is much clearer when I can see the complement of gates that make it up. I understood NAND and NOR gates when I saw the transistors that implemented them. Note that I don't always need to see the transistors. Once I understand the gates and the flip-flop I can understand the latch. Or selector, decoder, ... Timing diagrams: I need the know the interactions of the pins in the time domain. How does the action of pin 4 change after I toggle pin 10? Again, the h/w specs showed this graphically. This made these timing concepts much more understandable then they were with verbal descriptions. Electrical characteristics: I need to know what voltages I need to apply where and the min/max that I can apply. And I need to know what I can expect to come out. I need to know what the current draw will be and what the fan-in/fan-out is for each signal. Yes, these characteristics are measured differently for software, but there are analogous concepts: memory requirements, execution time requirements, limits on the range of input data, etc. Much of this information is available, to some degree or another, in the NeXT documentation, but it is very difficult to extract. I believe that there are valuable lessons to be learned from the h/w example. All of this IMHO, --- Larry Blische lkba!lkb@uunet.UU.NET LKB Associates, Inc. NeXTmail Welcome! 3118 Dunglow Road 410 285 2262 Dundalk, Maryland 21222-5304 USA
Newsgroups: comp.sys.next.bugs From: neil@ms.uky.edu (Neil Greene) Subject: 3.0 to 3.1 compatibility Message-ID: <CAzFzG.1M@ms.uky.edu> Organization: Kentucky NeXT User Group, Inc. Date: Fri, 30 Jul 1993 14:52:27 GMT Has anyone found a problem running 3.1 and 3.0 together. Our setup had a 3.0 NetInfo server and a 3.1 mailserver. Of course, after upgrading the mailserver to NS3.1, all 3.0 machines began complaing about the name server when attempting to send email. Mail from the mailserver worked fine. Upgrading the other machines to 3.1 solved the problem. Which reminds me. Prior to the upgrade, all 3.0 machines were running high. Lots of unnecessary processor activity. Upgrading all machines to 3.1 has also solved this problem. The machines once again run great! Is there something I missed in the release notes?
Newsgroups: comp.sys.next.bugs From: skrbec@tophat4.rtsg.mot.com (Brad Skrbec) Subject: Re: ?bug: ATC decompression aborted. Truncated input file? Message-ID: <1993Jul30.172056.7417@rtsg.mot.com> Sender: news@rtsg.mot.com Organization: Motorola Inc., Cellular Infrastructure Group References: <231fsk$m1n@news.cs.tu-berlin.de> Date: Fri, 30 Jul 1993 17:20:56 GMT In article <231fsk$m1n@news.cs.tu-berlin.de> kiwi@cs.tu-berlin.de (Axel Habermann) writes: > Hello! > > After upgrading to NS3.1 (Moto), there are some sounds which can't be > played. Under 3.0 there's no problem to play those sounds. On the > console the following message appears: > ATC decompression aborted. Truncated input file? > I tried several tools to play the sound, but it doesn't work. > Sometimes the machine produces the message, sometimes it doesn't, > but no sound is heard anyway. > > I would like to ask everyone who has installed 3.1 to try it and report > the results to see if this is a bug in 3.1 or not! Try it with the sounds > of DarkForest.app, they didn't work with me. > I've had this problem with 3.1beta also. I've never been able to duplicate it with other sounds though, so I'm not sure what's special about the DarkForest sounds. Please let me know if there is an outcome to this problem. -- --------------------------------------------------------------------- | Brad Skrbec | "For it is the doom of men that they forget." | | Motorola Cellular | -- Merlin | | Arlington Heights, IL | Internet: skrbec@rtsg.mot.com | | | Home: brad@darby.chi.il.us | ------------------------------- NeXTMail Gladly Accepted ------------
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs From: borrel@ludvigsen.dhhalden.no (Borre Ludvigsen) Subject: Apps that don't work with 3.1 - Icon & VideoApp Message-ID: <1993Jul30.220744.19823@dhhalden.no> Sender: news@dhhalden.no (Network News User) Organization: Ostfold College Date: Fri, 30 Jul 1993 22:07:44 GMT I had Icon working with 3.0, after upgrading to 3.1 only root can launch it. I get the following error message on the console: > Jul 30 22:04:20 mashallah Icon[864]: Pasteboard lookup failed on host mashallah: (Netnameserver: name not checked in) > Jul 30 22:04:21 mashallah last message repeated 12 times > Jul 30 22:04:21 mashallah Icon[864]: Invalid default font name: Helvetica > Jul 30 22:04:21 mashallah Icon[864]: Pasteboard lookup failed on host mashallah: (Netnameserver: name not checked in) Any suggestions? Also VideoApp and DVR refuse to run (I have a NextDimensions): > Jul 30 22:05:26 Workspace: Cannot exec /borrel/Apps/DVR/DVR : Bad executable (or shared library) > Jul 30 22:05:52 Workspace: Cannot exec /NextDeveloper/Demos/VideoApp : Bad executable (or shared library) Any suggestion? (email answers appreciated.) - Barre Ludvigsen <borrel@ludvigsen.dhhalden.no>
From: toon@moene.indiv.nluug.nl (Toon Moene) Newsgroups: comp.sys.next.bugs Subject: Re: printing and scanning formats still broken in 3.1 Message-ID: <492@moene.indiv.nluug.nl> Date: 30 Jul 93 20:49:07 GMT References: <239knm$eto@tribune.usask.ca> Sender: toon@moene.indiv.nluug.nl Organization: Moene Computational Physics, Amsterdam, The Netherlands In article <239knm$eto@tribune.usask.ca> eric@skatter.usask.ca writes: [ ... What should printf("%.3g", <some float>); print ...] > I've got a whole bunch of mail messages on this, and there have been a > whole lot of news postings as well. First of all: > - This is a LIBRARY issue, not a compiler issue. It doesn't > matter *what* version of cc/gcc I use on the NeXT, the problem > is in the library supplied by NeXT Yes, I got this reaction by email too. It's only part of the answer however - to quote K&R ('88, page 241): "This appendix is a summary of the library defined by the ANSI standard." ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The library IS part of the standard - this is shocking to people who took the gospel by K&R ('78) literally: 'Look Ma, a Portable Computer Language with no run-time support', but as soon as you want to define something more useful than a structured assembler, you have to add I/O support :-) The point, of course, here is: If NeXT has so much interest in making their operating system POSIX compliant, this is not a thing to wave away lightly ... why leave this error lying around ? -- Toon Moene (toon@moene.indiv.nluug.nl) Kantershof 269, 1104 GN Amsterdam, The Netherlands Phone: + 31 20 6982029; Fax: + 31 20 6003411 No Disclaimers; a NeXT@home protects against this occupational hazard. NB: Strictly black hardware here - No Intel inside :-)
Newsgroups: comp.sys.next.bugs From: mckelvey@fafnir.com (James W. McKelvey) Subject: No-More-Processes Bug Message-ID: <CB1rGF.A2@fafnir.com> Sender: mckelvey@fafnir.com (James W. McKelvey) Organization: Fafnir Software, Saugus, CA, USA Date: Sat, 31 Jul 1993 20:55:26 GMT If I don't log out at least once a day, I eventually get an error in the shell, "no more processes". If it happens in the Workspace, it's an "error 100000" or some such. This is what NeXT said about it: This is due to the Workspace leaking processes. You can avoid it by not using the Workspace to copy, move, or delete files. It has been fixed for 3.2. As you discovered, logging out and back in clears out the zombies. -- The gentle journey jars to stop. The drifting dream is done. The long gone goblins loom ahead; the deadly, that we thought were dead, stand waiting, every one. -- Walt Kelly Jim McKelvey mckelvey@fafnir.com
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs,comp.sys.next.software From: borrel@ludvigsen.dhhalden.no (Borre Ludvigsen) Subject: MailCall & 3.1 bug Message-ID: <1993Aug1.101344.8577@dhhalden.no> Sender: news@dhhalden.no (Network News User) Organization: Ostfold College Date: Sun, 1 Aug 1993 10:13:44 GMT MailCall has become indispensable. It displays from and subject in a small window in the lower left of the screen. You see the importance of incoming mail at a glance. With NS 3.1 a bug has crept in. Updating the display window after emptying /usr/spool/mail/<user> quits MailCall! How nice it would be if MailCall updated itself occasionally, emptying the window when the spool file is gone. As it is now, my workaround is to echo a space to create an empty spool file before upafating, that way at least it doesn't quit. Any one have a better fix? Is there somewone with programming abilities that feels called upon to fix and recompile the source? - Barre Ludvigsen
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1993Jul31.150445.9571@ToTSySSoft.com> Keywords: DPS, bug, m68k, motorola, Font, corruption Sender: news@ToTSySSoft.com Organization: Total System Software References: <mdixon.743966998@thelonius> Date: Sat, 31 Jul 1993 15:04:45 GMT In article <mdixon.743966998@thelonius> mdixon@parc.xerox.com (Mike Dixon) writes: -> about a month ago i started having a problem with -> my cube: after I had been logged in for a while, -> my windows (all programs) started displaying -> times italic when they were supposed to be displaying -> ohlfs. Exiting the window server fixed the problem -> temporarily, but it always came back fairly soon. -> -> At the time i was running 3.0. I assumed i had -> somehow corrupted some important system file, and -> upgraded to 3.1 assuming that this would fix -> it. After two installations (one fast, one slow) -> it still hadn't gone away, so i eventually figured -> out that one of my applications must be doing it. -> -> finally, with help from jayson adams at millennium, -> i determined that an eps graphic i had created in -> virtuoso and placed on one page of my notebook -> would, when displayed, cause this problem. -> Presumably it triggers a bug in DPS that corrupts -> some data structure in the font cache. -> -> I've forwarded the (quite simple) graphic to altsys, -> and they're working with next to track down the -> problem. in the meantime, i wanted to make -> sure that noone else wasted so much time trying to -> track down this problem. -> -> .mike. Mike, Thanks for posting this! I've encountered this problem ALSO under NEXTSTEP2.1, especially after rather dirty Yap.app crashes.-- Helvetica grab-bar titles switching to Ohlfs or Courier... Often a log-out and log-in would not fix it, and at times it would even survive a reboot (supposedly clean, with overdependance on swapfile info during reboot). This with a (then) 8m-RAM slab running 2.1. I've not (yet) encountered this under 3.1, but have not even cranked up Yap since upgrading. Please don't hesitate to pass along my info to altsys. My suspicion is that swap images are not fully purged during reboot, and therefore even corrupted info is reloaded from swap on occasion. Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: OD disk mounts with FD icon?? Message-ID: <1993Jul31.151140.9633@ToTSySSoft.com> Keywords: bug, OD, diskette, floppy, mismount Sender: news@ToTSySSoft.com Organization: Total System Software Date: Sat, 31 Jul 1993 15:11:40 GMT The other day, I inserted a 3.1 system formatted OD and it mounted with a floppy disk icon inserted on the shelf. This has only happened once, and the entire volume SEEMED to be accessable, but I immediately ejected it and re-inserted it in hopes of this being safe, which it seems to have been. In fairness, this OD had previously been hacked with the Upgrade_3.0.app turning it into a ``boot floppy'' to allow CD-ROM access on a (then) 2.1 system for upgrade to 3.0 BUT The disk had been completely reformatted (presumably) by the 3.1 upgrade app for a clean build of a 3.1 system disk. Has anyone else experienced an apparent mismount? Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Re: SoundView Bug (long) Followup-To: comp.sys.next.programmer Organization: Primitive Software Ltd. References: <1993Jul29.112456.13849@prim> <1993Jul30.133850.886@lkba.uucp> Date: Sat, 31 Jul 1993 10:05:45 +0000 Message-ID: <1993Jul31.100545.21022@prim> Sender: usenet@demon.co.uk In article <1993Jul30.133850.886@lkba.uucp> uunet!lkba!lkb writes: >I agree that all methods should be documented, including their support >status, but I wouldn't stop there. These classes are sufficiently complex >that they require diagrams to explain their inner workings. Verbal >descriptions are not enough, I want to see pictures. For a classic example of a method that is difficult to override in a subclass, here is the documentation for "- tile" in NXBrowser: tile - tile Arranges the various subviews of NXBrowserPScrollers, columns, titles, and so onPwithout redrawing. Your code shouldn't send this message. It's invoked any time the appearance of the NXBrowser changes; for example, when scroll Buttons or scroll bars are set, a column is added, and so on. Override this method if your code changes the appearance of the NXBrowser (for example, if you draw your own titles above columns). Returns self. OK, great. This method is obviously going to call a load of other mainly private methods whose function is unknown. Perhaps it's possible to glean something from the instance variables? Here they are: @interface NXBrowser : Control { id target; id delegate; id _reserved1[3]; SEL action; SEL doubleAction; id matrixClass; id cellPrototype; NXSize _reserved2; short _reserved4[4]; unsigned short pathSeparator; char _reserved3[6]; void *_private; } And this highlights another problem. The interesting information about the layout is all held in private variables! Designing a class in such a way that it's functionality can be modified in subclasses is a tricky business. Even if you're the person who writes both class and subclass! It becomes iterative, and you go back to the superclass and maybe split some method in two so that one of them can be overridden. To do anything serious in an NXBrowser subclass without much more information is practically impossible. Dave Griffiths
Newsgroups: comp.sys.next.bugs From: amlovell@phoenix.Princeton.EDU (Anthony M Lovell) Subject: NS FIP - network NOT work! Message-ID: <1993Aug1.160205.6041@Princeton.EDU> Originator: news@nimaster Sender: news@Princeton.EDU (USENET News System) Organization: Princeton University Distribution: usa Date: Sun, 1 Aug 1993 16:02:05 GMT I have the 3.1 eval deal kit. In trying to get it to run on a no-name 486, we have had NO luck getting it to cooperate in our network. We have an elite 16 card stuffed into it. Our network is not homogenous, and so we are not running NetInfo (we use niload, etc.). We cannot ping our NS box, nor can we ping the other hosts. Que pasa? I think the relative lack of how-to documentation on this point is a loss for NeXT. I'd guess more NS machine get put into heterogeneous nets than not. Why should it be shrouded in mystery while the fantasy NetInfo environment receives such lavish support? -- amlovell@phoenix.princeton.edu ...since 1963.
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.software,comp.sys.next.bugs Subject: Re: MailCall & 3.1 bug Date: 2 Aug 1993 04:19:50 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <23i4l6$be2@usenet.rpi.edu> References: <1993Aug1.101344.8577@dhhalden.no> borrel@ludvigsen.dhhalden.no (Borre Ludvigsen) writes: > MailCall has become indispensable. It displays from and subject > in a small window in the lower left of the screen. You see the > importance of incoming mail at a glance. > > With NS 3.1 a bug has crept in. Updating the display window after > emptying /usr/spool/mail/<user> quits MailCall! > > How nice it would be if MailCall updated itself occasionally, > emptying the window when the spool file is gone. As it is now, > my workaround is to echo a space to create an empty spool file > before updating, that way at least it doesn't quit. > > Any one have a better fix? Just to be precise, these are all bugs in MailCall itself, and not really related to NS-3.1 (I can make all of them happen on a NS-2.1 system). MailCall was a "source code shareware" program, and I sent Dennis Smyers the money to get the source code from him when it came out. Since then I've occasionally played with it, and I have a version which fixes the above bugs (as well as some others) and adds a few new features. I never have to hit the "Update" menu item, for instance, and I added a default so each user can set where the MailCall window will show up. The only trick is, I'm not quite sure I should distribute it... I need to contact the original author and check with him first, I would think, just as a matter of being fair. Due to the above bug report I polished up the last few things I wanted to do, so I'll try to contact Dennis (via snail mail) this week. The version I have is compiled on a NS-2.1 system, is known to work on a NS-3.0 system, and should work fine on a NS-3.1 system. -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1993Aug2.180555.3160@altsys.com> Keywords: DPS, bug, m68k, motorola, Font, corruption Organization: Altsys Corporation, Richardson, TX References: <mdixon.743966998@thelonius> <1993Jul31.150445.9571@ToTSySSoft.com> Date: Mon, 2 Aug 1993 18:05:55 GMT In article <1993Jul31.150445.9571@ToTSySSoft.com> bruce@TotSysSoft.com (Bruce Gingery) writes: >In article <mdixon.743966998@thelonius> >mdixon@parc.xerox.com (Mike Dixon) writes: >-> I've forwarded the (quite simple) graphic to altsys, >-> and they're working with next to track down the >-> problem. in the meantime, i wanted to make >-> sure that noone else wasted so much time trying to >-> track down this problem. >-> >-> .mike. > >Mike, > Thanks for posting this! I've encountered this problem >ALSO under NEXTSTEP2.1, especially after rather dirty >Yap.app crashes.-- Helvetica grab-bar titles switching to >Ohlfs or Courier... Often a log-out and log-in would not >fix it, and at times it would even survive a reboot >(supposedly clean, with overdependance on swapfile info >during reboot). > > This with a (then) 8m-RAM slab running 2.1. I've not >(yet) encountered this under 3.1, but have not even cranked >up Yap since upgrading. Please don't hesitate to pass >along my info to altsys. > > My suspicion is that swap images are not fully purged >during reboot, and therefore even corrupted info is >reloaded from swap on occasion. > >Bruce Gingery bruce@TotSysSoft.com >NeXT-Mail preferred I have been unable to repeat this problem on my NeXTstation color. I'm not sure how to proceed... -- Lorin Rivers Lorin_Rivers@altsys.com NEXTSTEP Sales Manager 214.680.2518 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
Newsgroups: comp.sys.next.bugs From: raf@shell.portal.com (Man Wei Tam) Subject: Audio - Stereo input possible on NSI? Message-ID: <CB5Bxp.B00@unix.portal.com> Sender: news@unix.portal.com Organization: Portal Communications Company -- 408/973-9111 (voice) 408/973-8091 (data) Date: Mon, 2 Aug 1993 19:10:34 GMT I have a NEXTSTEP for Intel machine with a MediaVision ProAudio spectrum running. Unfortunately due to the firmware problem with our Adaptec 1542B we now know it can handle only 8 bit audio, and not 16 bit. This may or may not be fixed in 3.1. Not only this, but why doesn't Sound.app record stereoe sound when it is passed through the LINE-IN socket on the ProAudio card? ONly the left channel appears to be recorded. Has anybody had experience of recording stereo sound on an INtel box, and if so - how? Advise much appreciated, Brian Leake, Fox River Financial Resources, Inc.
Newsgroups: comp.sys.next.bugs From: mikes@ceco.ceco.com (Michael Stepniczka) Subject: "chunks" Message-ID: <CB5BuE.DHs@ceco.ceco.com> Sender: root@ceco.ceco.com (Operator) Organization: Commonwealth Edison Co. Date: Mon, 2 Aug 1993 19:08:37 GMT Hi. I remember a post here (or maybe it was .misc) about avoiding using chunks when archiving directories to floppies because of the problems of a growing swap file when restoring. Having just run into this yesterday, I just wanted to point out that the chunks will unarchive if you do a "uncompress -c chunkfile | tar xvf -" after concatenating the chunks (in the subdirectories) by hand into the chunkfile. I tried restoring the file first using the automatic un-chunking, and ran out of SWAP on a drive with 140MB free disk and 32MB RAM before it ever got to writing any file output to the disk! The original directory (/LocalLibrary) was ~55MB, and compressed was about 40MB. I hope this is something that is fixed in the 3.2 release since it seems pretty ridiculous to have to do something so simple by hand because the system can't handle it when using a built-in feature. Reading the files straight from the floppies into the uncompress|tar chain would probably do the trick. Not buffering the whole thing to memory would help too. Of course, a shrinking swap file would be nicer. Anyway, I just wanted to point out to anyone who does want to use chunks that it should be safe to do so, you just may have to restore them by hand. Thank God they're in a non-proprietary format! Mike Stepniczka mikes@ceco.ceco.com
From: labwm@slab.cc.emory.edu (William Morse) Newsgroups: comp.sys.next.bugs Subject: Re: Possible Bugs <ie: please check these out and reproduce> (Summary) Message-ID: <4139@emoryu1.cc.emory.edu> Date: 2 Aug 93 19:31:43 GMT Sender: news@emory.edu Ok folks, this is the summary of bugs that I promised!!! - William I Speak for Myself Consult. / ITD :::::::::::::::::::::::::::::::::::::::: Emory Law Student --------------- >1) Hostmanager - will not properly add (or edit) aliases to hosts. [If >you open Hostmanager as root and create a new host in 3.1 and then try to add >aliases, you will find that NetInfo knows of the new host, but "forgets" the >aliases. You can see this if you save the new host with alias and then reload >the host. The aliases are gone. All other settings are saved.] >Work around - use NetInfo directly... Go under the machines --------------- Resp. #1: I can confirm this on a NeXTstation Turbo Mono after upgrading to NS3.1 -- Mike Hxxxxx INET : xxxx@xxxx.xx /// Box xxx /// x-xxx xx xxxx TEL : +xx x xxx-xxxx \\\/// SWEDEN TFX : +xx x xxx-xxxx \XX/ ---------- Resp. #2: I can confirm HostManager's behavior with aliases under NS 3.1 for Intel. I will also add that the same problem applies when trying to use the app to work on a machine's netgroups. No matter what netgroup changes you make in HostManager, they're thrown away. Again, this is under NS 3.1 for Intel, but I wouldn't be surprised if 3.1 black has the same problem. -- Royce Hxxxxxx, xxx xxxxxxxx xxxx | "And since OS/2 2.0 is a 32-bit Everything is IMHO | operating system, programs are xxxxx@xxxxxxx.uucp (NeXTMail OK) | easier to write and run faster, or xxxxx!xxxxxx!xxxxxxx!xxxxxxx | too." -ad for OS/2 2.0 --------------- Resp. #3: I've noticed this on my 3.1 Motorola system and used the same workaround as you did. I've never quite understood all the NetInfo ramifications so I didn't know whether I was doing something wrong. I've never been sure of the correct way to set a hostname and I don't know when an alias instead of a new hostname should be used. -- Art Ixxxxxx xxxxxx xxxxxxxxxx xxxxxxxxxxxxxxxxxxxxx NEXTSTEP software development and consulting --------------- Resp. #4: I've experienced this problem when trying to add an alias to my system (from localhost to outland). There is a problem if you give your system a hostname other than localhost when rendering (print) .rib files. You must let the system know that yourhostname=localhost or renderman chokes. I found the best way to correct the host name problem was to edit /etc/hosts directly and then niload it into netinfo. -- John x. Mxxxxxxxxxx (Politically, Fashionably, and Aerodynamically Incorrect) xxxxxxxxxx@xxx.xxx.xxx University of xxxxxxxxxxx --------------- Resp. #5: This would be a heck of a lot easier to read if you'd invited NeXT-mail replies. I frankly can't afford to mess with Host Manager any further. Mine resides on the CD-ROM ONLY. Between the automatic update to NetInfo from my 2.1 system's /etc/* net connection files and the attempt to get things rolling under 3.1 using SNStarter and HostMgr, I got locked out of my own NetInfo and had to rebuild from scratch from the 3.1 CD-ROM. No, the SNS backup .tar.Z didn't help as it was Post problems. I've not had the resources or time to waste to submit a good Bug-NeXT on this. but did alude to it in another Bug-NeXT report. Bxxxxx Gxxxxxx xxxx@xxxxxxxxxx xxxxxxxxxxxxxx -- xxxxxxxxxxxxxxxxxxx NeXT-Mail preferred. --------------- >2) Terminal and telnetd probs - Telnetd under 3.0 worked properly under 3.0 >but now seems to have some problems. For example, using many third party >telnet packages to telnet to a NeXT will result in you staring at a "Login:" >and not getting any further. This is true with the OS/2 telnet package. (It >worked under 3.0.) The solution for many of these packages is to alter the >third party telnet package to crlf. (OS/2, for example, works if you type >telnet, then "set crlf" and then "open <NeXT machine name>." The terminal >seems to be suffering from similar problems. For example, telnet back to >your own machine and then <return> past the first "Password:". You should >then see "Login:" Now, either with your username or password, make a mistake >and don't correct it. You will find that terminal seems to lock. "^]" also >seems to do no good at first, but if you keep on doing it, you get to "telnet>" >but it locks again as soon as you press return. Work around - don't make >mistakes. :) --------------- Resp. #1: Haven't tried that one yet... I'm about to set up a SLIP connection and I *assume* (key word) that this may cause a problem. -- John x. Mxxxxxxxxxx (Politically, Fashionably, and Aerodynamically Incorrect) xxxxxxxxxx@xxx.xxx.xxx University of xxxxxxxxxxx --------------- Resp. #2: Sorry... telnet, rlogin and ftp all seem to work well under TransSLIP NeXT3.1-->NeXT3.1 [Well, there are not buggy, but rather picky is a better word. I have been able to reproduce the behavior on other machines. -wm] Bxxxxx Gxxxxxx xxxx@xxxxxxxxxx xxxxxxxxxxxxxx -- xxxxxxxxxxxxxxxxxxx NeXT-Mail preferred. --------------- >3) Weird Newsgrazer problem - Install Newsgrazer as root... in somewhere >like /LocalApps then run it as a user. It won't show in the "process" area of >the Workspace. All other apps show up as usual. However, if you install it >as a user in your own /LocalApps, it will now show up in process. Now, if you >open a terminal window and type ps -x, it shows up. This behavior was not >in 3.0. Anyone have any idea what the deal is here? My version is Release 2.0 >72.3... Other than this, I have found no other oddities. (PS - no other app >exhibits this behavior and I have replaced my 72.3 with a clean one...) --------------- Resp. #1 I have both 72.2 and 72.3 Newsgrazer's. I'll try this out on both and get back to you. Question: What do you mean "I have replaced my 72.3 with a clean one"? [It means I downloaded a new copy from the net. - wm] -- John x. Mxxxxxxxxxx (Politically, Fashionably, and Aerodynamically Incorrect) xxxxxxxxxx@xxx.xxx.xxx University of xxxxxxxxxxx --------------- >4) Serious sound problem - Warning: this will and has resulted in crashes on >my Color Turbo ADB and does every time. By crashes, I mean a system panic. >Ok, what you do is "over tax" the sound buffer of the DSP. As an example, >pick a rather long "system beep" (like one that lasts a two seconds or so) and >replace the current one you have with it. To do this, go under preferences, >click the cube picture and "highlight" the new sound. Now, every time you >click this "sound" the computer will demo it. To make your system totally >die, click that sound over and over for about 15-25 times. It WILL crash >the NeXT. Other things that will are two apps using the DSP at the same >time or otherwise PUSHING it... with sound. Playing single mods... sounds >etc. at one time is no problem. Work around - don't do the above described. --------------- Resp. #1: Well... I certainly won't try this! Hasn't happened to me before, but I don't overload the DSP as a habit. Under 3.0, however, I did notice that if your mail voice alert was sounding, your error beep could play right over the top of it. Kinda neat. Don't know if 3.1 allows this. -- John x. Mxxxxxxxxxx (Politically, Fashionably, and Aerodynamically Incorrect) xxxxxxxxxx@xxx.xxx.xxx University of xxxxxxxxxxx --------------- Resp #2 I'm running 3.1 PRE on a monoslab & have none of the problems you've described with sound, I have 20 meg of ram & 80 meg for a separate swapdisk too. I DO do alot with sound too, much more than just system beep stuff, (I have allmost all the sound programs avalible) and I also have doen exactly what you've described (ie floodign the DSP with replay requests, & concurrent play requests) and I've nto crashed anything yet. Worst problem I ran into was filling swap under 2.1 when I was runnign that & didnt' ahve alot of disk. Tim Sxxxxxxxx xxx@xxxx.xxxx.xxxx --------------- Resp. #3: I beleive your sound bug. My Turbo ADB, however, has some minor sound oddities, i.e. apps which formerly were quite noisy have no sound. Clicking on a .snd file often doesn't work, (i.e. app set as default player doesn't play). Another thing, of course, which bothers me is that there seems (I don't know how perhaps) to be no Keyboard app for ADB kybd to remap keys, esp. foreign accents. Rxxxxxxx xx xxxxxxxx xxxxxxxxxxxxx Univ. --------------- >General Comments: --------------- Resp. #1: I don't want to get involved in any flame war but PLEASE don't compare a proper OS like NextStep to COMPLETE crap like Windows and mostly crap like OS/2. For a proper comparison look at other UNIX boxes. My Personal Iris, for instance, has crashed twice in the year that I have been here and it is used by 20 people all day every day. By comparison, my Next boxes have crashed more than a dozen times each (usually related to reading DOS floppies but not always) and I HAVE to reboot both of them at least once a week due to swapspace overrun. But even given this I would not even CONSIDER comparing NextStep to ANY DOS replacement! This is what I call `keeping things in perspective'! cxxxxxxxxxxx -- Dxxxxx xxxxxxxxx System Administrator/Research Programmer ".... 2 to the power 759 million to 1 and falling ..." HHGTG
Newsgroups: comp.sys.next.bugs From: mdixon@parc.xerox.com (Mike Dixon) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <mdixon.744340726@thelonius> Keywords: DPS, bug, m68k, motorola, Font, corruption Sender: news@parc.xerox.com Organization: Xerox PARC References: <mdixon.743966998@thelonius> <1993Jul31.150445.9571@ToTSySSoft.com> <1993Aug2.180555.3160@altsys.com> Date: 3 Aug 93 01:18:46 GMT > I have been unable to repeat this problem on my NeXTstation color. > I'm not sure how to proceed... which problem are you referring to? (you included both mine & bruce's in your posting.) if anyone would like to try reproducing my bug on their machine, open the enclosed .eps file in preview and then go look at some ohlfs documents. (note that you'll have to log out and restart the window server to get life back to normal.) .mike. (i just noticed that this eps file claims to need minion-italic, although it isn't actually used. i don't know if this will make it behave differently for people that don't have that font.) --------------------------------------------- %!PS-Adobe-2.0 EPSF-1.2 %%Title: cowards.eps.vrt %%Creator: Altsys Virtuoso 1.0 %%CreationDate: Mon Jun 14 10:27:05 PDT 1993 %%BoundingBox: 149 288 467 714 %%FHPathName: /tmp/cowards.eps.vrt %%DocumentProcSets: Altsys_header 4 0 %%DocumentSuppliedProcSets: Altsys_header 4 0 %%ColorUsage: Color %%DocumentCustomColors: (HighlightColor) %%CMYKCustomColor: 0.258564 1 0 0 (HighlightColor) %%DocumentFonts: Symbol %%+Minion-Italic %%+Times-Italic %%+Courier %%DocumentNeededFonts: Symbol %%+Minion-Italic %%+Times-Italic %%+Courier %%EndComments %%BeginProcSet: Altsys_header 4 0 /AltsysDict 233 dict def AltsysDict begin /bdf{bind def}bind def /xdf{exch def}bdf /defed{where{pop true}{false}ifelse}bdf /ndf{1 index where{pop pop pop}{dup xcheck{bind}if def}ifelse}bdf /d{setdash}bdf /h{closepath}bdf /H{}bdf /J{setlinecap}bdf /j{setlinejoin}bdf /M{setmiterlimit}bdf /n{newpath}bdf /N{newpath}bdf /q{gsave}bdf /Q{grestore}bdf /w{setlinewidth}bdf /sepdef{ dup where not { AltsysSepDict } if 3 1 roll exch put }bdf /st{settransfer}bdf /colorimage defed /_rci xdf /md defed{ md type /dicttype eq { /colorimage where { md eq { /_rci false def }if }if /settransfer where { md eq { /st systemdict /settransfer get def }if }if }if }if /setstrokeadjust defed { true setstrokeadjust /C{curveto}bdf /L{lineto}bdf /m{moveto}bdf } { /dr{transform .25 sub round .25 add exch .25 sub round .25 add exch itransform}bdf /C{dr curveto}bdf /L{dr lineto}bdf /m{dr moveto}bdf /setstrokeadjust{pop}bdf }ifelse /rectstroke defed /xt xdf xt {/yt save def} if /privrectpath { 4 -2 roll m dtransform round exch round exch idtransform 2 copy 0 lt exch 0 lt xor {dup 0 exch rlineto exch 0 rlineto neg 0 exch rlineto} {exch dup 0 rlineto exch 0 exch rlineto neg 0 rlineto} ifelse closepath }bdf /rectclip{newpath privrectpath clip newpath}def /rectfill{gsave newpath privrectpath fill grestore}def /rectstroke{gsave newpath privrectpath stroke grestore}def xt {yt restore} if /packedarray{array astore readonly}ndf /` {false setoverprint /-save0- save def pop pop pop pop pop concat userdict begin /showpage {} def 0 setgray 0 setlinecap 1 setlinewidth 0 setlinejoin 10 setmiterlimit [] 0 setdash newpath false setstrokeadjust } bdf /currentpacking defed{true setpacking}if /min{2 copy gt{exch}if pop}bdf /max{2 copy lt{exch}if pop}bdf /xformfont { currentfont exch makefont setfont } bdf /fhnumcolors 1 statusdict begin /processcolors defed { pop processcolors } { /deviceinfo defed { deviceinfo /Colors known { pop deviceinfo /Colors get } if } if } ifelse end def /printerRes gsave matrix defaultmatrix setmatrix 72 72 dtransform abs exch abs max grestore def /graycalcs [ {Angle Frequency} {GrayAngle GrayFrequency} {0 Width Height matrix defaultmatrix idtransform dup mul exch dup mul add sqrt 72 exch div} {0 GrayWidth GrayHeight matrix defaultmatrix idtransform dup mul exch dup mul add sqrt 72 exch div} ] def /calcgraysteps { /currenthalftone defed {currenthalftone /dicttype eq}{false}ifelse { currenthalftone begin HalftoneType 4 le {graycalcs HalftoneType 1 sub get exec} { HalftoneType 5 eq { Default begin {graycalcs HalftoneType 1 sub get exec} end } {0 60} ifelse } ifelse end } { currentscreen pop exch } ifelse printerRes 300 max exch div exch 2 copy sin mul round dup mul 3 1 roll cos mul round dup mul add 1 add dup maxsteps gt {pop maxsteps} if } bdf /nextrelease defed { /languagelevel defed not { /framebuffer defed { 0 40 string framebuffer 9 1 roll 8 {pop} repeat dup 516 eq exch 520 eq or { /fhnumcolors 3 def /currentscreen {60 0 {pop pop 1}}bdf /calcgraysteps {maxsteps} bdf }if }if }if }if /goodsep { spots exch get 4 get dup sepname eq exch (_vc_Registration) eq or }bdf /bottom -0 def /delta -0 def /frac -0 def /height -0 def /left -0 def /numsteps -0 def /numsteps1 -0 def /radius -0 def /right -0 def /top -0 def /width -0 def /xt -0 def /yt -0 def /df currentflat def /tempstr 1 string def /clipflatness currentflat def /inverted? 0 currenttransfer exec .5 ge def /tc1 [0 0 0 1] def /tc2 [0 0 0 1] def /storerect{/top xdf /right xdf /bottom xdf /left xdf /width right left sub def /height top bottom sub def}bdf /concatprocs{ systemdict /packedarray known {dup type /packedarraytype eq 2 index type /packedarraytype eq or}{false}ifelse { /proc2 exch cvlit def/proc1 exch cvlit def proc1 aload pop proc2 aload pop proc1 length proc2 length add packedarray cvx } { /proc2 exch cvlit def/proc1 exch cvlit def /newproc proc1 length proc2 length add array def newproc 0 proc1 putinterval newproc proc1 length proc2 putinterval newproc cvx }ifelse }bdf /i{dup 0 eq {pop df dup} {dup} ifelse /clipflatness xdf setflat }bdf version cvr 38.0 le {/setrgbcolor{ currenttransfer exec 3 1 roll currenttransfer exec 3 1 roll currenttransfer exec 3 1 roll setrgbcolor}bdf}if /vms {/vmsv save def} bdf /vmr {vmsv restore} bdf /vmrs{vmsv restore /vmsv save def}bdf /eomode{ {/filler /eofill load def /clipper /eoclip load def} {/filler /fill load def /clipper /clip load def} ifelse }bdf /normtaper{}bdf /logtaper{9 mul 1 add log}bdf /lfxform { /yt xdf /xt xdf xt yt translate rotate storerect left xt sub bottom yt sub translate right left sub 0.00001 max top bottom sub 0.00001 max scale }bdf /CD{/NF exch def{exch dup/FID ne 1 index/UniqueID ne and{exch NF 3 1 roll put} {pop pop}ifelse}forall NF}bdf /MN{1 index length/Len exch def dup length Len add string dup Len 4 -1 roll putinterval dup 0 4 -1 roll putinterval}bdf /RC{4 -1 roll /ourvec xdf 256 string cvs(|______)anchorsearch {1 index MN cvn/NewN exch def cvn findfont dup maxlength dict CD dup/FontName NewN put dup /Encoding ourvec put NewN exch definefont pop}{pop}ifelse}bdf /RF{dup FontDirectory exch known{pop 3 -1 roll pop}{RC}ifelse}bdf /FF{dup 256 string cvs(|______)exch MN cvn dup FontDirectory exch known {exch pop findfont 3 -1 roll pop} {pop dup findfont dup maxlength dict CD dup dup /Encoding exch /Encoding get 256 array copy 7 -1 roll {3 -1 roll dup 4 -2 roll put}forall put definefont} ifelse}bdf /fps{ currentflat exch dup 0 le{pop 1}if { dup setflat 3 index stopped {1.3 mul dup 3 index gt{pop setflat pop pop stop}if} {exit} ifelse }loop pop setflat pop pop }bdf /fp{100 currentflat fps}bdf /clipper{clip}bdf /W{/clipper load 100 clipflatness fps}bdf end%. AltsysDict %%EndProcSet %%EndProlog %%BeginSetup AltsysDict begin %%IncludeFont: Symbol 0 dict dup begin end /f0 /Symbol FF def %%IncludeFont: Minion-Italic 0 dict dup begin end /f1 /Minion-Italic FF def %%IncludeFont: Times-Italic 0 dict dup begin end /f2 /Times-Italic FF def %%IncludeFont: Courier 0 dict dup begin end /f3 /Courier FF def end %. AltsysDict %%EndSetup AltsysDict begin /onlyk{false}ndf /ccmyk{dup 5 -1 roll sub 0 max exch}ndf /cmyk2gray{ 4 -1 roll 0.3 mul 4 -1 roll 0.59 mul 4 -1 roll 0.11 mul add add add 1 min neg 1 add }bdf /setcmykcolor{1 exch sub ccmyk ccmyk ccmyk pop setrgbcolor}ndf /setcmykcoloroverprint{4{dup -1 eq{pop 0}if 4 1 roll}repeat setcmykcolor}ndf /findcmykcustomcolor{5 packedarray}ndf /setcustomcolor{exch aload pop pop 4{4 index mul 4 1 roll}repeat setcmykcolor pop}ndf /setseparationgray{setgray}ndf /setoverprint{pop}ndf /currentoverprint false ndf /cmykbufs2gray{ 0 1 2 index length 1 sub { 4 index 1 index get0.3 mul 4 index 2 index get0.59 mul 4 index 3 index get0.11 mul 4 index 4 index get add add add cvi 255 min 255 exch sub 2 index 3 1 roll put }for 4 1 roll pop pop pop }bdf /colorimage{ pop pop [ 5 -1 roll/exec cvx 6 -1 roll/exec cvx 7 -1 roll/exec cvx 8 -1 roll/exec cvx /cmykbufs2gray cvx ]cvx image } %. version 47.1 on Linotronic of Postscript defines colorimage incorrectly (rgb model only) version cvr 47.1 le statusdict /product get (Lino) anchorsearch{pop pop true}{pop false}ifelse and{userdict begin bdf end}{ndf}ifelse fhnumcolors 1 ne {/yt save def} if /customcolorimage{ aload pop (_vc_Registration) eq { pop pop pop pop separationimage } { /ik xdf /iy xdf /im xdf /ic xdf ic im iy ik cmyk2gray /xt xdf currenttransfer {dup 1.0 exch sub xt mul add}concatprocs st image } ifelse }ndf fhnumcolors 1 ne {yt restore} if fhnumcolors 3 ne {/yt save def} if /customcolorimage{ aload pop (_vc_Registration) eq { pop pop pop pop separationimage } { /ik xdf /iy xdf /im xdf /ic xdf 1.0 dup ic ik add min sub 1.0 dup im ik add min sub 1.0 dup iy ik add min sub /ic xdf /iy xdf /im xdf currentcolortransfer 4 1 roll {dup 1.0 exch sub ic mul add}concatprocs 4 1 roll {dup 1.0 exch sub iy mul add}concatprocs 4 1 roll {dup 1.0 exch sub im mul add}concatprocs 4 1 roll setcolortransfer {/dummy xdf dummy}concatprocs{dummy}{dummy}true 3 colorimage } ifelse }ndf fhnumcolors 3 ne {yt restore} if fhnumcolors 4 ne {/yt save def} if /customcolorimage{ aload pop (_vc_Registration) eq { pop pop pop pop separationimage } { /ik xdf /iy xdf /im xdf /ic xdf currentcolortransfer {1.0 exch sub ik mul ik sub 1 add}concatprocs 4 1 roll {1.0 exch sub iy mul iy sub 1 add}concatprocs 4 1 roll {1.0 exch sub im mul im sub 1 add}concatprocs 4 1 roll {1.0 exch sub ic mul ic sub 1 add}concatprocs 4 1 roll setcolortransfer {/dummy xdf dummy}concatprocs{dummy}{dummy}{dummy} true 4 colorimage } ifelse }ndf fhnumcolors 4 ne {yt restore} if /separationimage{image}ndf /newcmykcustomcolor{6 packedarray}ndf /inkoverprint false ndf /setinkoverprint{pop}ndf /setspotcolor { spots exch get dup 4 get (_vc_Registration) eq {pop 1 exch sub setseparationgray} {0 5 getinterval exch setcustomcolor} ifelse }ndf /currentcolortransfer{currenttransfer dup dup dup}ndf /setcolortransfer{st pop pop pop}ndf /fas{}ndf /sas{}ndf /fhsetspreadsize{pop}ndf /filler{fill}bdf /F{gsave {filler}fp grestore}bdf /f{closepath F}bdf /S{gsave {stroke}fp grestore}bdf /s{closepath S}bdf /lfs{ gsave W n lfxform pop pop pop /xt xdf /lfbuf1 xdf 1 256 8 [1 0 0 -256 0 256] {lfbuf1} [spots xt get aload pop pop] customcolorimage grestore }ndf /lfp{ gsave W n lfxform 9 {pop} repeat _rci { /lfbuf4 xdf /lfbuf3 xdf /lfbuf2 xdf /lfbuf1 xdf pop 1 256 8 [1 0 0 -256 0 256] {lfbuf1}{lfbuf2}{lfbuf3}{lfbuf4} true 4 colorimage } { 4 {pop} repeat /lfbuf1 xdf 1 256 8 [1 0 0 -256 0 256] {lfbuf1} image } ifelse grestore }ndf /bcs [0 0] def /_rfs { /tint2 xdf /tint1 xdf bcs exch 1 exch put /radius xdf /yt xdf /xt xdf tint1 tint2 sub abs calcgraysteps mul abs round dup 2 lt {pop 2} if 1 sub /numsteps1 xdf currentflat mark currentflat clipflatness { { dup setflat W 0 1 numsteps1 { numsteps1 div /frac xdf bcs 0 tint2 tint1 sub frac mul tint1 add put bcs vc 1 index setflat { newpath mark xt yt radius 1 frac sub mul 0 360 {arc fill}stopped {cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if} {cleartomark exit}ifelse }loop }for } gsave stopped grestore {exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if} {exit}ifelse }loop cleartomark setflat }bdf /bc4 [0 0 0 0] def /_rfp { /k2 xdf /y2 xdf /m2 xdf /c2 xdf /k1 xdf /y1 xdf /m1 xdf /c1 xdf /radius xdf /yt xdf /xt xdf c1 c2 sub abs m1 m2 sub abs y1 y2 sub abs k1 k2 sub abs max max max calcgraysteps mul abs round dup 2 lt {pop 2} if 1 sub /numsteps1 xdf currentflat mark currentflat clipflatness { { dup setflat W 0 1 numsteps1 { numsteps1 div /frac xdf bc4 0 c2 c1 sub frac mul c1 add put bc4 1 m2 m1 sub frac mul m1 add put bc4 2 y2 y1 sub frac mul y1 add put bc4 3 k2 k1 sub frac mul k1 add put bc4 vc 1 index setflat { newpath mark xt yt radius 1 frac sub mul 0 360 {arc fill}stopped {cleartomark exch 1.3 mul dup setflat exch 2 copy gt{stop}if} {cleartomark exit}ifelse }loop }for } gsave stopped grestore {exch pop 2 index exch 1.3 mul dup 100 gt{cleartomark setflat stop}if} {exit}ifelse }loop cleartomark setflat }bdf /rfs{_rfs}ndf /rfp{_rfp}ndf /cvc [0 0 0 1] def /vc{ AltsysDict /cvc 2 index put aload length 4 eq {setcmykcolor} {setspotcolor} ifelse }bdf /origmtx matrix currentmatrix def /ImMatrix matrix currentmatrix def 0 setseparationgray /imgr {0 0 612 792 } def /bleed 0 def /clpr {0 0 612 792 } def /xs 1 def /ys 1 def /botx 0 def /overlap 0 def /wdist 18 def 0 2 mul fhsetspreadsize 0 0 ne {/df 0 def /clipflatness 0 def} if /maxsteps 256 def /currentpacking defed{false setpacking}if /spots[ 1 0 0 0 (Process Cyan) false newcmykcustomcolor 0 1 0 0 (Process Magenta) false newcmykcustomcolor 0 0 1 0 (Process Yellow) false newcmykcustomcolor 0 0 0 1 (Process Black) false newcmykcustomcolor ]def /textopf false def /curtextmtx{}def /otw .25 def /msf{dup/curtextmtx xdf makefont setfont}bdf /makesetfont/msf load def /curtextheight{.707104 .707104 curtextmtx dtransform dup mul exch dup mul add sqrt}bdf /ta{1 index {tempstr 0 2 index put tempstr 2 index gsave exec grestore tempstr stringwidth rmoveto 5 index eq{6 index 6 index rmoveto}if 3 index 3 index rmoveto }forall 7{pop}repeat}bdf /sts{/textopf currentoverprint def vc setoverprint /ts{awidthshow}def exec textopf setoverprint}bdf /stol{/xt currentlinewidth def setlinewidth vc newpath /ts{{false charpath stroke}ta}def exec xt setlinewidth}bdf /strk{/textopf currentoverprint def vc setoverprint /ts{{false charpath stroke}ta}def exec textopf setoverprint }bdf % mdd 3/11/93 highlight color hack for altsys virtuoso statusdict /highlightcolor known { mark spots 0 % search through the spot colors... spots { % ... for one called "HighlightColor" 4 get (HighlightColor) eq { % we found one; get the highlight color (in rgb) statusdict begin highlightcolor end % and convert to cmyk 3 { 1 exch sub 3 1 roll } repeat 0 % build a custom color object (HighlightColor) false newcmykcustomcolor % and install back in the spots array put exit } if 1 add } forall cleartomark } if clpr storerect left bottom width height rectclip [] 0 d 3.863708 M 1 w 0 j 0 J false setoverprint 0 i false eomode [0 0 0 1]vc vms 466 712.3514 m 151.6083 712.3514 L 151.6083 288 L 466 288 L 466 712.3514 L n q %%IncludeFont: Times-Italic { f2 [14 0 0 14 0 0] makesetfont 151.608276 344.697357 m 0 0 32 0 0 (I loathe people who k) ts -0.139923 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (eep do) ts -0.139923 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (gs. ) ts -0.251862 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (The) ts -0.419983 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (y ar) ts -0.517822 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (e cowar) ts -0.517822 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0 0 32 0 0 (ds who) ts } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 151.608276 327.697357 m 0 0 32 0 0 (have not got the guts to bite people themselves.) ts } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 331.608307 310.697357 m 0.699982 0 32 0 0 (\320 ) ts -0.251862 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0.699982 0 32 0 0 (A) ts -0.279846 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0.699982 0 32 0 0 (ugust Strindber) ts -0.517822 0 rmoveto } true [0 0 0 1]sts { f2 [14 0 0 14 0 0] makesetfont 0.699982 0 32 0 0 (g) ts } true [0 0 0 1]sts Q vmr end %%Trailer
From: amencke@panix.com (Andres Mencke) Newsgroups: comp.sys.next.bugs Subject: Printing envelopes under 3.0 Date: 3 Aug 1993 00:22:28 -0400 Organization: PANIX Public Access Internet and Unix, NYC Message-ID: <23kp64$hfm@panix.com> Summary: Envelopes printed off-center in 3.04 Keywords: printing, bug, WriteNow Printing on envelopes is off center, such that it is not possible to use the (centerering) enve- lope feed of the NeXT Laser Printer. I observed this in WriteNow (v2.0), Edit and MSWord 5.0 running under Executor. This bug appeared after upgrading from NS 2.2. Any know workarounds? Any help or suggestions will be appreciated. Andres Mencke amencke@panix.com
From: sanguish@digifix.com (Scott Anguish) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.marketplace,comp.sys.next.misc,comp.sys.next.programmer,comp.sys.next.software,comp.sys.next.sysadmin Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 3 Aug 1993 00:19:52 -0400 Organization: Next Announcements Distribution: world Message-ID: <23kp18$6e4@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.misc Subject: IMPORTANT: Problem with NEXTSTEP 3.1 fip CDs (please read and pass this info on!!) Date: 3 Aug 1993 15:25:53 GMT Organization: University of Houston Message-ID: <23m021$7l1@menudo.uh.edu> (Please alert your vendor of this potential problem!!! Also tell anyone you know who isn't on the net...) We have discovered a potentially serious problems with some shipments of NEXTSTEP 3.1/fip CDs that makes it IMPOSSIBLE to install NEXTSTEP on any hardware because the CD cannot be read: There seems to have been a defect in the packaging phase during the production of batch of NEXTSTEP 3.1 CDs. These CDs are "fogged." That is, they have a thin film over the back of the CD (side opposite of the label). At first we thought it was due to humidity, but now we are not sure what it is. However, we believe that the defect happened during the packaging phase because all of our 22 copies (from the same shipment) of NEXTSTEP 3.1/fip had this film. Copies from an earlier shipment were fine. We believe that this is not an isolated incident and that other shipments may also be affected. This problem can be fixed if you carefully clean the CD. We sucessfully used "computer screen cleaner" and Windex without any problems. Apply the cleaner to a lint-free cloth and wipe the film off the CD. After the CD is cleaned, installation and use of the CD should be problem free (that is if there aren't any other problems like hardware incompatiblity). We would like to know if you come across a CD with this "defect" so please send me email. You can send email if you have any questions too! -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.bugs From: darcy@solutions.ca (Darcy Brockbank) Subject: Bug in NeXT headers??? Message-ID: <1993Aug3.180513.695@sifon.cc.mcgill.ca> Sender: news@sifon.cc.mcgill.ca Organization: McGill University Date: Tue, 3 Aug 1993 18:05:13 GMT Anyone get things like this when trying to use #import <indexing/indexing.h>? QKWriter.h:2: warning: could not use precompiled header '/NextDeveloper/Headers/indexing/indexing.p', because: QKWriter.h:2: warning: macro 'index' defined by /NextDeveloper/Headers/ansi/ansi.h conflicts with precomp - db
Newsgroups: comp.sys.next.bugs From: steve@NETSYS.COM (Steve Eigsti) Subject: Printing in 3.1 Message-ID: <steve.744402365@netsys.com> Summary: Images get cut on printer in 3.1 Keywords: 3.1, bug Sender: news@netsys.com Organization: Netsys Inc. Date: Tue, 3 Aug 1993 18:26:05 GMT I found a puzzling bug which seemed to turn up after I installed 3.1 on my black mono box. I am trying to create a brochure with a scanned image, and I insert the image which is scaled down to fit on a portrait page. Everything looks ok on all the programs (like Preview, Draw, and Appsoft Draw (when it doesn't crash) but when I get a print the right side of the photo is chopped off, and the image is widened to fit the old size. I found an old 3.0 printout and everything seems ok, but now I can't get the full image to print. Also, in landscape mode the printing is ok -- problem is only in portrait. This is rendering 3.1 useless. Any ideas or fixes or anything similar. Thanks, Steve Eigsti
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: stefan@megatel.de (Stefan Runge) Subject: Sybase 3.1 Bug in DBROWS() Message-ID: <1993Aug3.151155.8330@megatel.de> Keywords: Sybase Sender: stefan@megatel.de Organization: megatel GmbH, Bremen, Germany Date: Tue, 3 Aug 93 15:11:55 GMT Adding my $1 to the Sybase-3.1 thread, I have found the following bug: The Sybase-function DBROWS(), which returns the number of rows in the current command seems not to work with the 3.1 libs (v.4.6). The value returned is always 0, regardless of how many rows are returned by the current command! Linking against the library which comes with 3.0 (v.4.0) works fine. In my sample-code my existence()-function checks for existence of a reord in a table. It uses DBROWS() to get a count of the existing records. It is called once before the data is inserted into the footab table and after the operation: Both times the existence()-func returns 0 (zero) !!!! This is not correct! Personally I won't rely on the 3.1 Sybase-library. The consequence is *NOT* to use the DBKit in 3.1 in conjunction with Sybase, and to link all other (not DBKit) programs against the 3.0 library which seems to work. If I have a couple of time I will send this information to bug-NeXT... -- Stefan Runge megatel GmbH, Wienerstr. 3, D-2800 Bremen 33, Germany NeXTMail: stefan@megatel.de ---
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1993Aug3.202907.3915@altsys.com> Keywords: DPS, bug, m68k, motorola, Font, corruption Organization: Altsys Corporation, Richardson, TX References: <1993Jul31.150445.9571@ToTSySSoft.com> <1993Aug2.180555.3160@altsys.com> <mdixon.744340726@thelonius> Date: Tue, 3 Aug 1993 20:29:07 GMT What I'm saying is, the eps in question does not do the Times-Italic thing to me. I have redtarted my window server and previewed the file and everything continues to work fine... Anyone got any clues? -- Lorin Rivers Lorin_Rivers@altsys.com NEXTSTEP Sales Manager 214.680.2518 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.bugs Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1296@rtbrain.rightbrain.com> Date: 3 Aug 93 23:22:13 GMT References: <1993Aug3.202907.3915@altsys.com> Sender: glenn@rightbrain.com Lorin Rivers III writes > What I'm saying is, the eps in question does not do the Times-Italic > thing to me. I have redtarted my window server and previewed the file > and everything continues to work fine... > > Anyone got any clues? I haven't seen the original post or any of the problem statements, other than a recollection that Mike Dixon said he had found a bad EPS file from Virtuoso that crashed things. I'm assuming this is the same problem. Here is what I would guess to be the problem/solution: If a particular font is killing you, particularly if it's Times Italic, a standard one, it's probably a corrupted bitmap file. Since bitmaps are in binary format, if the file got corrupted, it could easily hose the window server. Figure out what point size of Times-Italic is causing the problem. If it's small enough to correspond to a bitmap font (or, importantly, if scaling it up or down might happen to hit one of the bitmap sizes, such as 36-point Times-Italic zoomed to 50%), then that might explain the problem. There's an easy way to test this (assuming you can reproduce the crash, which I can imagine would not be easy unless you had the corrupted bitmaps). You can remove (or rename) the bitmap files in /NextLibrary/Fonts/ Times-Italic.font (remove everything but Times-Italic and Times-Italic.afm) and restart the window server. I hope this turns out to have been the problem. -- Glenn Reid NeXTmail: glenn@rightbrain.com RightBrain Software 415-326-2974 (NeXTfax 326-2977) Palo Alto, California Electronic Frontier Foundation, member #054
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Re: Bug in NeXT headers??? Message-ID: <1993Aug4.003735.27695@csus.edu> Sender: news@csus.edu Organization: San Francisco State University References: <1993Aug3.180513.695@sifon.cc.mcgill.ca> Date: Wed, 4 Aug 1993 00:37:35 GMT Precomps are just plain evil, and even more ill-behaved in 3.1 than they were in 3.0. For example, -bsd and <bsd/libc.h> conflict! The "fix" is to compile with cc -no-precomp Often you'll need to add -fno-builtin as well. (Not to say there aren't broken headers--there are--but you're far more likely to be bitten by compiler stupidity.) -=EPS=-
From: mdixon@parc.xerox.com (Mike Dixon) Newsgroups: comp.sys.next.bugs Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <mdixon.744425569@thelonius> Date: 4 Aug 93 00:52:49 GMT References: <1993Aug3.202907.3915@altsys.com> <1296@rtbrain.rightbrain.com> Sender: news@parc.xerox.com Organization: Xerox PARC [ in response to glenn's posting suggesting the problem results from corrupted bitmap fonts ] originally i too assumed that something like this was the problem; but after scrubbing the disk and installing 3.1 from scratch didn't fix things i began to suspect the problem was a little deeper... (also, the symptom is that ohlfs, in all point sizes, is replaced with times italic -- so it's clearly more than a single font file. logging out and restarting the window server made the problem temporarily go away, so it seemed likely that something was causing DPS's font cache to be corrupted.) i eventually determined that the problem would only occur after i started using one of my notebooks, so i sent it to jayson adams; he then further isolated the problem to an eps file that was a background on one of the notebook's pages. jayson had no problem reproducing the bug. i haven't found out yet whether he has minion-italic on his machine, but i'm beginning to suspect he does. (glenn: since you surely have minion (and every other adobe font known to man) on your machine, could you let us know if you get this bug too? the eps file is in my earlier posting; let me know if you'd like me to email it to you.) this is a seriously weird bug; i'd really be interested in hearing the post mortem when it's tracked down... .mike.
From: doug@foxtrot.ccmrc.ucsb.edu (Douglas Scott) Newsgroups: comp.sys.next.bugs Subject: Re: Bug in NeXT headers??? Date: 4 Aug 1993 02:04:08 GMT Organization: Center for Computer Music Research and Composition, U.C.S.B. Message-ID: <23n5eo$qo0@hub.ucsb.edu> References: <1993Aug3.180513.695@sifon.cc.mcgill.ca> In article <1993Aug3.180513.695@sifon.cc.mcgill.ca> darcy@solutions.ca writes: > > >Anyone get things like this when trying to use >#import <indexing/indexing.h>? > > >QKWriter.h:2: warning: could not use precompiled header >'/NextDeveloper/Headers/indexing/indexing.p', because: >QKWriter.h:2: warning: macro 'index' defined by >/NextDeveloper/Headers/ansi/ansi.h conflicts with precomp > FYI, This bug is listed in the release note suppliment that comes with the 3.1 Dev stuff. Any file using the 'index' macro cannot use the precomp headers. -- Douglas Scott (805)893-8352 Center for Computer Music Research and Composition University of California, Santa Barbara Internet: (NeXTMail ok) <doug@foxtrot.ccmrc.ucsb.edu>
Newsgroups: comp.sys.next.bugs From: stefan@initiera2 (Stefan Kruger) Subject: NSFIP - Problems w/ CirrusLogic Message-ID: <1993Aug4.081852.5514@sics.se> Sender: news@sics.se Organization: Swedish Institute of Computer Science, Kista Date: Wed, 4 Aug 1993 08:18:52 GMT Hi, My graphics card seems to start up in the wrong resolution. His configuration: 50Mhz 486 AMI bios CirrusLogic GD542 1Mb VRAM MicroScan 4G ADI Screen The screen goes all flickery just as if the card uses a much higher resolution than the screen. The system works fine running Windoze, but when NeXTSTEP is up the little display on the screen says that the card not properly tells the screen what resolution is being used. Any ideas ? /Stefan (stefan@initiera.upnet.se)
Newsgroups: comp.sys.next.bugs From: mikem@afs.com (Mike Matlack) Subject: PopUpList addItem: documentation Message-ID: <1993Aug4.132223.588@afs.com> Sender: mikem@afs.com Date: Wed, 4 Aug 1993 13:22:23 GMT There is an error in the documentation for the popuplist method addItem: The spec sheet for addItem: (- addItem:(const char *)title) says: Adds an item with the name title to the bottom of the PopUpList, and returns the MenuCell created for that item (so a key equivalent can be added, for example). If an item with the name title already exists in the PopUpList, this method does nothing and returns nil. It should say: If an item with the name title already exists in the PopUpList, the MenuCell for that item is returned. mikem -- Michael J. Matlack Anderson Financial Systems Mike_Matlack@afs.com (NeXTmail OK)
Newsgroups: comp.sys.next.bugs From: rob@lighthouse.com (Rob Kedoin) Subject: Re: Bug in NeXT headers??? Message-ID: <1993Aug4.150615.4156@lighthouse.com> Keywords: precomps, index Sender: rob@lighthouse.com Organization: Lighthouse Design, Ltd. References: <23n5eo$qo0@hub.ucsb.edu> Date: Wed, 4 Aug 1993 15:06:15 GMT To avoid the precomp problem, you can import <strings.h> *before* you import other precompiled headers. Things go faster this way than if you compile -no-precomp. Rob Kedoin Lighthouse Design, Ltd -- Robert Kedoin rob@lighthouse.com Lighthouse Design, Ltd NeXTmail accepted and encouraged! 2929 Campus Drive - Suite 250 San Mateo, CA 94403
Newsgroups: comp.sys.next.bugs From: shill@ccsi.com (Sean L. Hill) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1993Aug4.194619.3771@ccsi.com> Sender: shill@ccsi.com Organization: Crystal Computer Systems, Inc. References: <mdixon.744425569@thelonius> Date: Wed, 4 Aug 1993 19:46:19 GMT In article <mdixon.744425569@thelonius> mdixon@parc.xerox.com (Mike Dixon) writes: > [ in response to glenn's posting suggesting the problem results > from > corrupted bitmap fonts ] > > originally i too assumed that something like this was the problem; > but after scrubbing the disk and installing 3.1 from scratch > didn't fix things i began to suspect the problem was a little > deeper... this is a seriously weird bug; i'd really be interested > in hearing the post mortem when it's tracked down... > .mike. I had a similar problem when after using a palette from Target Development where the license panel came up. The license panel used Revue for it's font. I happen to own Revue, but then afterwards, everytime Ohlfs size 12 or 14 (I believe) and only two sizes was replaced by the corresponding Revue font. Way weird... After a reboot it was gone, never to return. -Sean -- Sean L. Hill Ergo Science Incorporated shill@ccsi.com Compuserve: 73667,3355
Newsgroups: comp.sys.next.bugs From: jayson@millennium.com (Jayson Adams) Subject: Re: Warning: DPS bug in 3.x (motorola) - Font corruption Message-ID: <1993Aug4.215637.212@millennium.com> Keywords: This article created by some version of Newsgrazer Sender: jayson@millennium.com Organization: Millennium Software Labs, Inc. References: <mdixon.744425569@thelonius> Date: Wed, 4 Aug 1993 21:56:37 GMT In article <mdixon.744425569@thelonius> mdixon@parc.xerox.com (Mike Dixon) writes: > [ in response to glenn's posting suggesting the problem results from > corrupted bitmap fonts ] > > ... > > jayson had no problem reproducing the bug. i haven't found out yet > whether he has minion-italic on his machine, but i'm beginning to > suspect he does. No, I don't. Here's an excerpt of the bug report I sent to NeXT, if anyone wants to try to make it happen on their machine (using the file Mike posted a few articles back). __jayson From: jayson (Jayson Adams) Date: Wed, 7 Jul 93 11:55:54 -0700 To: bug_next@next.com Subject: EPS file trashes Ohlfs font cache Cc: jayson When you view this eps file, Ohlfs font characters appear as Times Roman, and the character spacing's all wrong. Note: this is 100% reproducible on black hardware, but I don't think it occurs on Intel stuff, so you should try it on a black machine. Anyway, steps to reproducing: 1. Log out of your machine 2. Restart the window server 3. Log in and open the eps file using something like Preview 4. Now start Edit, create a new document, and type. The Ohlfs font comes out looking like Times-Roman Italic. My default Edit font is Ohlfs-10, so you may need to make the same setting or change the window's font.
From: sean@digaudio.byu.edu (Sean Luke) Newsgroups: comp.sys.next.bugs Subject: Re: Audio - Stereo input possible on NSI? Followup-To: comp.sys.next.bugs Date: 5 Aug 1993 02:34:41 GMT Organization: Brigham Young University Distribution: world Message-ID: <sean-040893203536@128.187.2.153> References: <CB5Bxp.B00@unix.portal.com> In article <CB5Bxp.B00@unix.portal.com>, raf@shell.portal.com (Man Wei Tam) wrote: > Not only this, but why doesn't Sound.app record stereoe sound when > it is passed through the LINE-IN socket on the ProAudio card? ONly > the left channel appears to be recorded. Has anybody had experience > of recording stereo sound on an INtel box, and if so - how? Harvard Toolworks is making a high-quality sound card (about $200?) for the PC that connects to an external ADC via the NeXT-standard DSP port, and they're also supplying an ADC ($400?) that does SMPTE, MIDI, digitial i/o and analog i/o. Impressive. At any rate, I'd take a look at this group. Sean Luke Brigham Young University sean@digaudio.byu.edu
From: therbert@umiami.ir.miami.edu Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.misc Subject: Re: IMPORTANT: Problem with NEXTSTEP 3.1 fip CDs (please read and pass this info on!!) Message-ID: <1993Aug4.225309.15578@umiami.ir.miami.edu> Date: 4 Aug 93 22:53:09 EDT References: <23m021$7l1@menudo.uh.edu> Organization: Univ of Miami IR In article <23m021$7l1@menudo.uh.edu>, sears@tree.egr.uh.edu (Paul S. Sears) writes: > > (Please alert your vendor of this potential problem!!! Also tell anyone you > know who isn't on the net...) > > We have discovered a potentially serious problems with some shipments of > NEXTSTEP 3.1/fip CDs that makes it IMPOSSIBLE to install NEXTSTEP on any > hardware because the CD cannot be read: > > There seems to have been a defect in the packaging phase during the > production of batch of NEXTSTEP 3.1 CDs. These CDs are "fogged." That is, > they have a thin film over the back of the CD (side opposite of the label). > At first we thought it was due to humidity, but now we are not sure what it > is. However, we believe that the defect happened during the packaging phase > because all of our 22 copies (from the same shipment) of NEXTSTEP 3.1/fip > had this film. Copies from an earlier shipment were fine. > > We believe that this is not an isolated incident and that other shipments > may also be affected. > > This problem can be fixed if you carefully clean the CD. We sucessfully > used "computer screen cleaner" and Windex without any problems. Apply the > cleaner to a lint-free cloth and wipe the film off the CD. After the CD is > cleaned, installation and use of the CD should be problem free (that is if > there aren't any other problems like hardware incompatiblity). > > We would like to know if you come across a CD with this "defect" so please > send me email. > > You can send email if you have any questions too! > > -- > Paul S. Sears * sears@uh.edu (NeXT Mail OK) > The University of Houston * suggestions@tree.egr.uh.edu (NeXT > Engineering Computing Center * comments, complaints, questions) > NeXT System Administration * DoD#1967 '83 NightHawk 650SC > >>> SSI Diving Certification #755020059 <<< > "Programming is like sex: One mistake and you support it a lifetime." Yes - We received 13 copies from NACSCorp - Academic packages. All 13 packages have both user and developer disks fogged. The coating seems slightly sticky, also. I used Windex also and a soft cloth and got the disks to read. I called NeXT and informed them of the problem - I am really disappointed in NeXT - We are not terribly inconvenienced but this incident seems to be one more tiny way in which NeXT is trying to kill its great software. A little more attention to details in manufacturing would really help NeXTstep! (Just letting off a bit of smoke - NeXT had not shown a lot of care in handling "details" with its hardware sales and support and seems to be right on its old track, here.) Thomas J. Herbert Department of Biology University of Miami therbert@umiami.ir.miami.edu
Newsgroups: comp.sys.next.bugs From: rfi@jeans.fokus.gmd.de (Robert Fischer) Subject: WSMgr: Windows on double-head Message-ID: <1993Aug5.062547.4886@fokus.gmd.de> Sender: news@fokus.gmd.de (News system) Organization: GMD-Fokus Date: Thu, 5 Aug 1993 06:25:47 GMT Hi, I'm sitting in front of a double-headed NeXT and do want to place my windows on the second screen too. That's possible, of course, but at new login time, the windows of the Workspace Manager doesn't care about my second screen: the position is correct, but on the wrong, the main (login) screen. Bug or feature? ------------------------------------------------------------------------ Robert Fischer @ GMD-Fokus -------- __o ------- _`\<,_ fischer@fokus.gmd.de ------- (*)/ (*) ## NeXT-Mail welcome ## ------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: uunet!lkba!lkb (Larry Blische) Subject: Re: IMPORTANT: Problem with NEXTSTEP 3.1 fip CDs (please read and pass this info on!!) Message-ID: <1993Aug5.115034.4929@lkba.uucp> Sender: lkb@lkba.uucp (Larry Blische) Organization: LKB Associates, Inc. References: <1993Aug4.225309.15578@umiami.ir.miami.edu> Date: Thu, 5 Aug 1993 11:50:34 GMT In article <1993Aug4.225309.15578@umiami.ir.miami.edu> therbert@umiami.ir.miami.edu writes: > > In article <23m021$7l1@menudo.uh.edu>, sears@tree.egr.uh.edu (Paul S. Sears) writes: > > > > [deleted description of fogged CD problem...] > > Yes - We received 13 copies from NACSCorp - Academic packages. All 13 > packages have both user and developer disks fogged. The coating seems > slightly sticky, also. I used Windex also and a soft cloth and got the > disks to read. > > I called NeXT and informed them of the problem - I am really disappointed > in NeXT - We are not terribly inconvenienced but this incident seems to > be one more tiny way in which NeXT is trying to kill its great software. > A little more attention to details in manufacturing would really help > NeXTstep! (Just letting off a bit of smoke - NeXT had not shown > a lot of care in handling "details" with its hardware sales and support > and seems to be right on its old track, here.) > > Thomas J. Herbert > Department of Biology > University of Miami I would find it difficult to lay blame with NeXT for a CD manufacturing problem. The 3.1 CDs, mine anyway, were manufactured by the 3M company. 3M, that name sounds pretty reputable to me. CDs are pressed, by the thousands, like old vinyl records. You only sample a small set to test quality. Mine aren't fogged, but it sounds like the fogging material could be excess mold release. This material is applied to the press mold to allow the CDs to pop off better. Remember, NeXT now only writes software, they don't make anything!
From: robert@steffi.demon.co.uk (Robert Nicholson) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: palette.make? (Build libs for NS3.1 palettes?) Date: 5 Aug 1993 13:36:41 +0100 Organization: me organized? That's a joke! Message-ID: <23qusp$4le@steffi.demon.co.uk> References: <23qirn$26c@steffi.demon.co.uk> LIBOFILES = $(PSWFILES:.psw=.o) $(PSWMFILES:.pswm=.o) $(CLASSES:.m=.o) \ $(CFILES:.c=.o) LIBDIR = ~/Developer/Palettes/lib OFILE_DIR = ./m68k_obj .linstall:: $(DSTROOT)$(LIBDIR) lib rm -f $(DSTROOT)$(LIBDIR)/lib$(NAME).a cp lib$(NAME).a $(DSTROOT)$(LIBDIR) ranlib $(DSTROOT)$(LIBDIR)/lib$(NAME).a @ echo > .linstall lib$(NAME).a : $(LIBOFILES) ar crvl lib$(NAME).a $? ranlib lib$(NAME).a installlib : .linstall lib : lib$(NAME).a This works, but it's ugly having to code OFILE_DIR like that. Why in 3.1 did OFILE_DIR resolve to ./obj????? This could happen is $(ARCH_LIST) didn't evaluate to anything. common.make has this OFILE_DIR = $(OBJROOT)/$(ARCH_LIST)obj However, ARCH_LIST isn't defined anywhere. And most targets use this to build obj_dir @(evaled_rc_archs="$(RC_ARCHS)"; \ obj_dir=`echo $$evaled_rc_archs | sed 's/ /_/g'`_obj ; \ $(MAKE) project \ "OFILE_DIR = $(OBJROOT)/$$obj_dir" \ My guess it's a bug? In fact if I change OFILE_DIR = $(OBJROOT)/$(ARCH_LIST)obj to OFILE_DIR = $(OBJROOT)/$(ARCH_LIST)robertobj And the make lib I get. cc -I./sym -arch `/usr/bin/arch` -I./sym -c DocumentIcon.m -o ./robertobj/DocumentIcon.o So that's where that comes from. I guess a fix is to define ARCH_LIST in my postamble or preferably patch common.make so that it resolves that properly. Hope I haven't wasted your time.
From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.sys.next.bugs Subject: Re: Printing envelopes under 3.0 Date: 6 Aug 1993 10:18:34 +0300 Organization: The Crimson Permanent Assurance Company Sender: otto@network.cc.jyu.fi Message-ID: <OTTO.93Aug6101832@tukki.jyu.fi> References: <23kp64$hfm@panix.com> In-reply-to: amencke@panix.com's message of 3 Aug 1993 00:22:28 -0400 In article <23kp64$hfm@panix.com> amencke@panix.com (Andres Mencke) writes: Printing on envelopes is off center, such that it is not possible to use the (centerering) enve- lope feed of the NeXT Laser Printer. I observed this in WriteNow (v2.0), Edit and MSWord 5.0 running under Executor. This bug appeared after upgrading from NS 2.2. Any know workarounds? Any help or suggestions will be appreciated. I noticed this problem also after upgrading from NS2.2 to NS3.0, and posted it here. No solutions surfaced. I'll let you know what happens when I install NS3.1 -- /* * * Otto J. Makela <otto@jyu.fi> * * * * * * * * * * * * * * * * * * */ /* Phone: +358 41 613 847, BBS: +358 41 211 562 (V.32bis/USR-HST,24h/d) */ /* Mail: Kauppakatu 1B18/SF-40100 Jyvaskyla/Finland, ICBM: 62.14N25.44E */ /* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.misc From: bill@bilver.uucp (Bill Vermillion) Subject: Re: IMPORTANT: Problem with NEXTSTEP 3.1 fip CDs (please read and pass this info on!!) Organization: W. J. Vermillion - Orlando / Winter Park, FL Date: Sun, 8 Aug 1993 03:10:30 GMT Message-ID: <1993Aug8.031030.28214@bilver.uucp> References: <23m021$7l1@menudo.uh.edu> <1993Aug4.225309.15578@umiami.ir.miami.edu> In article <1993Aug4.225309.15578@umiami.ir.miami.edu> therbert@umiami.ir.miami.edu writes: >In article <23m021$7l1@menudo.uh.edu>, sears@tree.egr.uh.edu (Paul S. Sears) writes: >> >> (Please alert your vendor of this potential problem!!! Also tell anyone you >> know who isn't on the net...) >> We have discovered a potentially serious problems with some shipments of >> NEXTSTEP 3.1/fip CDs that makes it IMPOSSIBLE to install NEXTSTEP on any >> hardware because the CD cannot be read: >> There seems to have been a defect in the packaging phase during the >> production of batch of NEXTSTEP 3.1 CDs. These CDs are "fogged." That is, >> they have a thin film over the back of the CD (side opposite of the label). >> At first we thought it was due to humidity, but now we are not sure what it >> is. However, we believe that the defect happened during the packaging phase >> because all of our 22 copies (from the same shipment) of NEXTSTEP 3.1/fip >> had this film. Copies from an earlier shipment were fine. ... >> This problem can be fixed if you carefully clean the CD. We sucessfully >> used "computer screen cleaner" and Windex without any problems. Apply the >> cleaner to a lint-free cloth and wipe the film off the CD. After the CD is >> cleaned, installation and use of the CD should be problem free (that is if >> there aren't any other problems like hardware incompatiblity). >> We would like to know if you come across a CD with this "defect" so please >> send me email. Just checked my copy, that I picked up earlier this week. The OS was that way, the development dis was not (see later). >Yes - We received 13 copies from NACSCorp - Academic packages. All 13 >packages have both user and developer disks fogged. The coating seems >slightly sticky, also. I used Windex also and a soft cloth and got the >disks to read. >I called NeXT and informed them of the problem - I am really disappointed >in NeXT - We are not terribly inconvenienced but this incident seems to >be one more tiny way in which NeXT is trying to kill its great software. >A little more attention to details in manufacturing would really help >NeXTstep! (Just letting off a bit of smoke - NeXT had not shown >a lot of care in handling "details" with its hardware sales and support >and seems to be right on its old track, here.) I wouldn't blame NeXT for a manufacturing problem like that. I've purchased commercial CDs with the same problem. What they could be blamed for is if they let it continue and don't inform their vendor. Plants to make these are most certainly shrink wrapping the whole package. Now - when I looked I saw an area that was not fogged. Sort of eliptical. Lo and behold, on the CD case itself there is a small serial number label. And the placement looks like it could be the same. And my developer disk was okay. The difference is the plastic in the OS was black while the developer was white. I suspect it may be out-gassing from the plastic cases, and the serial number limited the coating in that area. All it takes is a vendor who supplies a chemical to make an insignificant change (he thought) that causes problems with your formulation. I saw this happen when I worked in a recording studio and Ampex came an pulled all of our tape stock because it got sticky. A vendor had changes a component they used to make the binder, and reacted adversely to other chemicals in the binder. Don't blame NeXT, they didn't make the disk, but get them to fix them however. -- Bill Vermillion - bill@bilver.uucp OR bill@bilver.oau.org
From: treed@friday.bmt.gun.com (Timothy Reed) Newsgroups: comp.sys.next.bugs Subject: Subject: uuname does not correctly report hosts named 'xxxx' Date: 9 Aug 1993 10:30:26 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9308091457.AA01696@friday.bmt.gun.com> In 3.0 and 3.1, uuname does not list remote UUCP hosts named 'xxx' - any hostname with 3 'x' or more do not appear in the list of remote hosts configured in /etc/uucp/L.sys. Hosts you exchange mail with may not be named 'xxx' or the unsupported variations. Tim --- Timothy Reed, Black Market Technologies Voice: +1 718 522-5090 Fax: +1 718 852-4249 E-mail: treed@bmt.gun.com "Reading documentation is an admission of failure."
Newsgroups: comp.sys.next.bugs From: sfch@dmu.ac.uk (Simon F C Harwood) Subject: Re: WSMgr: Windows on double-head Message-ID: <1993Aug9.150948.19183@dmu.ac.uk> Organization: De Montfort University, Leicester, UK. References: <1993Aug5.062547.4886@fokus.gmd.de> Date: Mon, 9 Aug 1993 15:09:48 GMT In article <1993Aug5.062547.4886@fokus.gmd.de> rfi@jeans.fokus.gmd.de (Robert Fischer) writes: >Hi, > >I'm sitting in front of a double-headed NeXT and do want to >place my windows on the second screen too. That's possible, >of course, but at new login time, the windows of the Workspace >Manager doesn't care about my second screen: the position is >correct, but on the wrong, the main (login) screen. > >Bug or feature? This sounds like the system that I have got.. NeXT Cube with Dimension board and colour monitor added at a later date. What you probably need to do is to log in as root, then, using the "screens" section in the Preferences application, tell the NeXT that you want the second screen probably the mono one since installing the Dimension drivers sets the colour screen to be the only one on) that you want the mono screen to be on, and where it is relative to the colour screen. This makes it automatically sort out the boundarys on the screens for you. After that, log out and then "log in" (this doesn't really) as exit (no password) -- this re-starts your window server. Simon.. -- It meant that Crowley had been allowed to develop Manchester, while Aziraphale had a free hand in the whole of Shropshire. Crowley took Glasgow, Aziraphale had Edinburgh. (neither claimed any responsibility for Milton Keynes, but both reported it as a success). Terry Pratchett - Good Omens -- Simon Harwood, Research Technician, Phone: (+44)(0)533 551551 x7915 De Montfort University, The Gateway, Fax : (+44)(0)533 577574 LEICESTER, LE1 9BH UK. E-mail: sfch@uk.ac.dmu (JANET), sfch@dmu.ac.uk (Internet)
Newsgroups: comp.sys.next.bugs From: mw2630@albnyvms.bitnet Subject: Monitors from Hell Message-ID: <1993Aug9.172227.7764@sarah.albany.edu> Sender: news@sarah.albany.edu (News Administrator) Organization: University of Albany, SUNY Date: Mon, 9 Aug 93 17:22:27 GMT Heyas all, I thought I once saw a thread on this news-group about monitors that would sporadically just blank out. I never saw the resulotion to it though, which is depressing now that I have three monitors doing the same thing. They just see to blink off whenever they want to, real annoying to the users,... I was wondering if it might be a software bug, or a hardware problem. The monitors are E-Machine 1024x1024 16" 's. Real heavy. Well, I'm going to go switch the monitors and see if that does something. Thanx. Micah Wyenn Cellular One Paramus, NJ *---------////////////////////////////|\\\\\\\\\\\\\\\\\\\\\\\\\\\\----------* | Internet: Mw2630@thor.ALBANY.edu or Mw2630@albnyvms.albany.edu | | | | Qoute for the day: "The crown your honor, will show that the witness that| | now stands before you, was caught red-handed showing | | feeeeling, showing feeling of an almost human nature. | | This will not do." Pink Floyd, The Wall | *---------\\\\\\\\\\\\\\\\\\\\\\\\\\\\|////////////////////////////----------*
From: ambi@it-next2.bu.edu (Mike Amirault) Newsgroups: comp.sys.next.bugs Subject: Printer/Network problems (3.1) Date: 9 Aug 1993 18:28:47 GMT Organization: Boston University Message-ID: <24650v$daf@news.bu.edu> Setup: NeXTStation Color, 3.1, NeXT Laser printer, no ethernet connection, network connection via SLIP. Problem: The workspace thinks my printer is somehow on the network, or at least it does some network activity when using the printer. For example, if I bring up a print panel in any application, it generates some unknown traffic accross my SLIP link which can be a real nuisance if the SLIP wasn't up. Causes: 3.1? Could this be some bug? It used to work fine but doesn't anymore. I don't print enough things to be able to determine whether or not i had this problem before I did the 3.0 - 3.1 upgrade. I've checked all values in netinfo that I think might cause the problem, but everything seems ok. Anyone have any ideas? Mike Amirault ambi@world.std.com
From: sanguish@digifix.com (Scott Anguish) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.programmer,comp.sys.next.misc,comp.sys.next.advocacy,comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 10 Aug 1993 15:20:55 -0400 Organization: Digital Fix Development Distribution: world Message-ID: <248sen$3c4@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish -- - Scott Anguish - sanguish@digifix.com (NextMail) next-announce@digifix.com (comp.sys.next.announce submissions)
Newsgroups: comp.sys.next.bugs From: dkk@cbnewsl.cb.att.com (david.k.kallman) Subject: .ps icon mangled Organization: AT&T Bell Laboratories Date: Wed, 11 Aug 1993 21:38:34 GMT Message-ID: <CBM6sD.5K4@cbnewsl.cb.att.com> Folks, The icon for .ps files in WorkSpace Manager is mangled on my system. The file icon shows up in black and white (it used to be in color) and the title says "PS?". .eps files show up fine in color and saying "EPS". I'm running 3.1 on a NextStation Color. Anyone seen this? Thanks. Dave Kallman -- ---- Dave Kallman, AT&T, 480 Red Hill Rd., Middletown, NJ 07748 d_k_kallman@att.com, (908)615-2989, fax: (908)615-2507
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: .ps icon mangled Message-ID: <1993Aug13.025835.28257@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: Stanford University References: <CBM6sD.5K4@cbnewsl.cb.att.com> Date: Fri, 13 Aug 93 02:58:35 GMT david.k.kallman writes > Folks, > > The icon for .ps files in WorkSpace Manager is mangled on > my system. The file icon shows up in black and white (it > used to be in color) and the title says "PS?". .eps files > show up fine in color and saying "EPS". > > I'm running 3.1 on a NextStation Color. > > Anyone seen this? Yeah. I think its due to Opener 3.1. I wish it wouldn't do that. I know, I know, source is available and I can change it if I don't like it. Unfortunately, I don't program. -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@leland.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
Newsgroups: comp.sys.next.bugs From: gerben@rna.indiv.nluug.nl Subject: MoveWhenIdle in 3.1 not working?? Message-ID: <1993Aug13.072214.543@rna.indiv.nluug.nl> Sender: gerben@rna.indiv.nluug.nl (Gerben Wierda) Organization: G.R.O.S.S. Date: Fri, 13 Aug 1993 07:22:14 GMT I'd like to prevent a screen burn-in when I'm not logged in (the machine stays on). But instead of a moving loginwindow I get some NeXT logo in the middle which seems to be not moving at all. Is this a bug or has the way to save screen during logout changed? Thanks, -- Gerben Wierda [NeRD:7539] gerben@rna.indiv.nluug.nl "If you don't know where you are going, any road will take you there." From the Talmud(?), rephrased in Lewis Carroll, "Alice in Wonderland".
Newsgroups: comp.sys.next.bugs,comp.sys.next.software From: dkk@cbnewsl.cb.att.com (david.k.kallman) Subject: Re: .ps icon mangled Organization: AT&T Bell Laboratories Date: Thu, 12 Aug 1993 22:13:15 GMT Message-ID: <CBo324.F36@cbnewsl.cb.att.com> Followup-To: comp.sys.next.software References: <CBM6sD.5K4@cbnewsl.cb.att.com> In article <CBM6sD.5K4@cbnewsl.cb.att.com>, I wrote: > Folks, > > The icon for .ps files in WorkSpace Manager is mangled on > my system. The file icon shows up in black and white (it > used to be in color) and the title says "PS?". .eps files > show up fine in color and saying "EPS". > > I'm running 3.1 on a NextStation Color. > > Anyone seen this? Well, it seems that the 3.1 version of Opener also wants .ps files and that's what's causing the problem. Any suggestions? Thanks. Dave Kallman -- ---- Dave Kallman, AT&T, 480 Red Hill Rd., Middletown, NJ 07748 d_k_kallman@att.com, (908)615-2989, fax: (908)615-2507
Newsgroups: comp.sys.next.bugs Subject: Re: .ps icon mangled Message-ID: <1993Aug13.081817.16528@urz.unibas.ch> From: frank@ifi.unibas.ch (Robert Frank) Date: Fri, 13 Aug 1993 08:18:17 GMT Sender: news@urz.unibas.ch (USENET News System) References: <1993Aug13.025835.28257@leland.Stanford.EDU> Organization: Institut fuer Informatik In article <1993Aug13.025835.28257@leland.Stanford.EDU> writes: > david.k.kallman writes > > Folks, > > > > The icon for .ps files in WorkSpace Manager is mangled on > > my system. The file icon shows up in black and white (it > > used to be in color) and the title says "PS?". .eps files > > show up fine in color and saying "EPS". > > > > I'm running 3.1 on a NextStation Color. > > > > Anyone seen this? > > Yeah. I think its due to Opener 3.1. I wish it wouldn't do that. I > know, I know, source is available and I can change it if I don't like > it. Unfortunately, I don't program. > > -- > - > Stefano Pagiola > Food Research Institute, Stanford University > spagiola@leland.stanford.edu (NeXTMail encouraged) > spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged) How about clicking on such an icon, pressing control-3 (or whatever the tools panel now has) and just setting the preference to some other viewer? -Robert -- Robert Frank tel. + (061) 321 99 67 Institut fuer Informatik fax + (061) 321 99 15 University of Basel, Switzerland Mittlere Strasse 142 rfc822: frank@ifi.unibas.ch (NeXT mail accepted) CH-4056 Basel X400: S=frank;OU=ifi;O=unibas;P=switch;A=arcom;C=ch ( if all fails try frank@urz.unibas.ch )
From: anderson@macc.wisc.edu (Jess Anderson) Newsgroups: comp.sys.next.bugs Subject: Re: MoveWhenIdle in 3.1 not working?? Date: 13 Aug 1993 12:49:59 GMT Organization: Division of Information Technology, UW-Madison Message-ID: <24g2ln$gsu@news.doit.wisc.edu> References: <1993Aug13.072214.543@rna.indiv.nluug.nl> In article <1993Aug13.072214.543@rna.indiv.nluug.nl>, <gerben@rna.indiv.nluug.nl> wrote: >I'd like to prevent a screen burn-in when I'm not logged in >(the machine stays on). But instead of a moving loginwindow >I get some NeXT logo in the middle which seems to be not >moving at all. Is this a bug or has the way to save screen >during logout changed? Patience, my man, patience. The logo *does* move, just not very often. It jumps to a new place every now and then. Once again, NeXT seems to treat as valuable secrets the whole business of defaults and how certain things work. It really is *very* irritating. I can understand wanting to keep customers out of trouble, but with suitable caveats it should be easy to discover how to manipulate such things as the new-style login panel without turning a handspring. It wants for intelligence, which is not a quality one likes to associate with this particular vendor. -- [Jess Anderson <> Division of Information Technology, University of Wisconsin] [Internet: anderson@macc.wisc.edu {o"o} UUCP:{}!uwvax!macc.wisc.edu!anderson] [Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888] [-----> The way some people find fault, you'd think there was a reward. <-----]
Newsgroups: comp.sys.next.bugs From: dcode@netcom.com (Paul Marcos) Subject: Re: MoveWhenIdle in 3.1 not working?? Message-ID: <dcodeCBpFv6.MLt@netcom.com> Organization: Netcom - Online Communication Services (408 241-9760 guest) Date: Fri, 13 Aug 1993 15:47:30 GMT It is easy to figure it out. I put on some of the archives a thing called (cs.orst.edu at least) a thing called ScreenSaver.compressed. It's a replacement ScreenSaver.bundle that lives in /usr/lib/NextStep/loginWindow.app which will give you the moving login window back. I included the source to show how to create alternative screen savers. It was just a quick hack so it's not elegant in any way. Hopefully NeXT will open up this API for public consumption with 3.2. Paul -- -------------------------------------------------------------------------- dCode | Internet: dcode@netcom.com | (415) 960-3539 NeXT Mail Happily Accepted
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: MoveWhenIdle in 3.1 not working?? Message-ID: <1993Aug13.123426.7363@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Aug13.072214.543@rna.indiv.nluug.nl> Date: Fri, 13 Aug 1993 12:34:26 GMT In article <1993Aug13.072214.543@rna.indiv.nluug.nl> gerben@rna.indiv.nluug.nl writes: -> I'd like to prevent a screen burn-in when I'm not logged -> (the machine stays on). But instead of a moving -> loginwindow I get some NeXT logo in the middle -> which seems to be not moving at all. Is this a bug -> or has the way to save -> screen during logout changed? It's changed... If you leave it up for a while, you should see it reposition -- this is not a constantly moving display, but is a result of having a dwrite loginwindow ScreenSaverEnabled YES set. Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred, MIME-Mail ok
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: .ps icon mangled Message-ID: <1993Aug13.164244.13168@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: Stanford University References: <1993Aug13.081817.16528@urz.unibas.ch> Date: Fri, 13 Aug 93 16:42:44 GMT Robert Frank writes > > > The icon for .ps files in WorkSpace Manager is mangled on > > > my system. The file icon shows up in black and white (it > > > used to be in color) and the title says "PS?". .eps files > > > show up fine in color and saying "EPS". > > > > Yeah. I think its due to Opener 3.1. I wish it wouldn't do > > that. I know, I know, source is available and I can change it > > if I don't like it. Unfortunately, I don't program. > > How about clicking on such an icon, pressing control-3 (or whatever > the tools panel now has) and just setting the preference to some > other viewer? That fixes the autolaunching, but does _not_ change the icon back. I'm not sure how Workspace decides what icon to use when two different apps provide an icon for particular filetype, but changing the default app in the tools panel doesn't fix it. (the same problem occurs with Mesa, which provides a butt-ugly icon for Lotus .wk1 files; the much nicer icon that Improv provides no longer shows, even if Improv is made the default app for .wk1 files) -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@leland.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
From: jreiss@magnus.acs.ohio-state.edu (Joseph W Reiss) Newsgroups: comp.sys.next.bugs Subject: Re: .ps icon mangled Date: 13 Aug 1993 17:03:09 GMT Organization: The Ohio State University Message-ID: <24ghgd$7pm@charm.magnus.acs.ohio-state.edu> References: <1993Aug13.081817.16528@urz.unibas.ch> <1993Aug13.164244.13168@leland.Stanford.EDU> I've created my own set of color icons for Opener. I made them look like the NeXTSTEP icons for ".Z" and ".tar". The archives have the white background rectangle with a package in the lower right and the extension across the top. I put IBM and Apples on the left to show native computers. The compressed files (".z" and ".gz") have the white background with orange arrows pointing inward from the corners and the extension letters in the middle. I also stole the ".ps" icon from Preview and added the question mark to it. It's still color and it looks pretty good (better than Opener's mono version). I also colorized the app icon. (I hate mono icons!) I've been kinda meaning to archive all this stuff up and send it to the author(s) so that the icons could be made available in future releases. Is there enough interest in these icons for me to do this? Joe -- __________ | NeXTMail accepted, but not preferred | |___) | """""""""""""""""""""""""""""""""""""""""""""""""""""""" \_/OE | \EISS | Captain, it's too dangerous for you to lead the away `---- | team. Besides, it's my turn. You promised! Pleeease!
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: .ps icon mangled Message-ID: <1993Aug14.085729.8823@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <24ghgd$7pm@charm.magnus.acs.ohio-state.edu> Date: Sat, 14 Aug 1993 08:57:29 GMT I have not bothered, as I generally prefer secondary Icons to some of those distributed with NEXTSTEP -- as a reminder that the add-on app is available or ``apt'' to be used... A dwrite to override the standard search path for .apps or a manual hacking of ~/.NeXT/suffixes3_1.m68k.wmd is apt to solve the problem. Bruce Gingery bruce@TotSysSoft.com NeXT-mail preferred, MIME-Mail ok
Newsgroups: comp.sys.next.bugs From: phil@unitec.demon.co.uk (Phil Robinson) Subject: Allocating large amounts of memory:HOW WITHOUT CRASHING NEXT Distribution: world Organization: Unified Technology Date: Sat, 14 Aug 1993 12:52:55 +0000 Message-ID: <745358756snx@unitec.demon.co.uk> Sender: usenet@demon.co.uk We have written a NeXT driver (We're using release 3.0 on black hardware.) for an Agfa Arcus scanner (which scans colour photos and sends a 1200 dpi 24 bit colour bitmap over the SCSI). An A4 page at this resolution is about 12 * 8 * 1200 * 1200 * 24 bits = about 414 Mbytes. Of course, the user would usually select a smaller area to scan, but they have the option. We know how big the bitmap will be before we start the scan going, and we use vm_allocate to allocate a buffer of the required size. vm_allocate cheerfully says "yes" even if you only have 100Mb free on you disk and we've asked for 400Mb. Then we start filling the bitmap with data. The NeXT becomes very sluggish, disk space starts to disappear, and the machine dies. You have to use command-command-! to exit to monitor, and power off. When you reboot, your disk is corrupted with truncated INODEs etc, but it *usually* will recover. What we want to do is find out how much space is *really* available before allocating the buffer and if we find that there's not enough we can tell the user about it and refuse to perform the scan. The problem is: ????? HOW ?????; any answers greatly appreciated. (We also note that if you try to print seriously large colour EPS files to the NeXT color printer (from AI, PasteUp etc), the disk space can slowly disappear to a point when there isn't any, at which point your box is dead as described above, INodes and all. This makes us think that other people have the same problem, so it can't just be us being silly OR CAN IT?).
Newsgroups: comp.sys.next.bugs From: friendly@hotspur.psych.yorku.ca (Michael Friendly) Subject: Re: .ps icon mangled Message-ID: <CBtAys.6p0@newshub.ccs.yorku.ca> Sender: news@newshub.ccs.yorku.ca (USENET News System) Organization: York University References: <1993Aug14.085729.8823@ToTSySSoft.com> Date: Sun, 15 Aug 1993 17:52:04 GMT In article <1993Aug14.085729.8823@ToTSySSoft.com> bruce@TotSysSoft.com (Bruce Gingery) writes: ] ] I have not bothered, as I generally prefer secondary Icons to ] some of those distributed with NEXTSTEP -- as a reminder that ] the add-on app is available or ``apt'' to be used... ] ] A dwrite to override the standard search path for .apps or a ] manual hacking of ~/.NeXT/suffixes3_1.m68k.wmd is apt to solve ] the problem. ] ] Bruce Gingery bruce@TotSysSoft.com ] NeXT-mail preferred, MIME-Mail ok Enough people have been irked about this bug in Opener 3.1 that it would be real nice if someone could post exact instructions to squish it (while we wait for Opener 3.1.1). -- Michael Friendly Internet: friendly@vm1.yorku.ca Psychology Department NeXTmail: friendly@hotspur.psych.yorku.ca York University 4700 Keele Street Toronto, ONT M3J 1P3 CANADA
Newsgroups: comp.sys.next.bugs From: abell@netcom.com (Steven T. Abell) Subject: Methods and attributes Message-ID: <abellCBuHzp.MFD@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) Date: Mon, 16 Aug 1993 09:21:25 GMT Try this: #import <appkit/appkit.h> @interface Gronk:Object { id poGronk; } + gronk; @end @implementation Gronk + gronk { return poGronk; } @end This compiles without complaint. In case you didn't see the problem (neither did I after several minutes of staring at similar code), the method called "gronk" is a *class* method, but it refers to an attribute of an *instance* of the class. I expected a compiler error. Is this a bug, or an obscure feature of ObjC? Steve abell@netcom.com
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: ray@isrc.sandia.gov (Larry Ray) Subject: NS/FIP Problems with 3Com 3C509 and a Workaround Kluge Message-ID: <1993Aug13.210520.18728@isrc.sandia.gov> Organization: ISTG, Sandia National Labs, Albuquerque, NM Date: Fri, 13 Aug 1993 21:05:20 GMT Some of you may have seen my posting about installing NEXTSTEP on a Gateway, then a followup saying that things were working. To make a long story short, I find that networking fails at a very low level (ping doesn't work) *unless* I have previously booted OS/2, where I am using IBM TCP/IP package. Apparently, OS/2 is doing some necessary board setup function. Networking works through reboots as long as the reset switch is not pressed (and power is left on). I assume that the problem is with setup of the 3Com 3C509 Etherlink III card. I received E-mail from someone who couldn't get their 3Com working and reported that NeXT support said they needed another card. Switched to Intel and no problems. I'm unclear on whether this was a Gateway. Anyway, the 3Com remains on the list of compatible hardware. Is anyone using the 3C509 successfully? With a Gateway? The Twisted-Pair version? Booting OS/2 with TCP/IP first is hardly a general workaround, but it may let someone limp along ... Hardware configuration: Gateway 486/66 IDE Drives ATI Ultra Pro Adaptec 1542B NEC CDR-74 CDROM 3Com Etherlink III (TP version) [default addr (300) and interrupt(10)] -- Larry Ray <ray@isrc.sandia.gov> | Where did I come from? Why am I here? Intelligent Systems and Robotics | Where am I going? Sandia National Laboratories | Will I be there next week? *Not a statement for or by any organization. Opinions expressed are mine alone.
From: jreiss@magnus.acs.ohio-state.EDU (Joseph W Reiss) Newsgroups: comp.sys.next.software,comp.sys.next.bugs Subject: Removed Opener Icons from orst Date: 16 Aug 1993 09:28:15 -0400 Organization: The Ohio State University Sender: daemon@magnus.acs.ohio-state.edu Message-ID: <9308161327.AA01681@magnusug.magnus.acs.ohio-state.edu> Hello, all. Just wanted to let everyone know that I'm deleting the OpenerTiffs.tar.gz stuff from the submissions directory of orst. Now that Opener 3.1.1 is out and includes these icons, there's no more reason to keep them there as far as I can see. That's it. Joe -- __________ | NeXTMail accepted, but not preferred | |___) | """""""""""""""""""""""""""""""""""""""""""""""""""""""" \_/OE | \EISS | Real programmers don't like the "team programming" `---- | concept, unless they are the Chief Programmer.
From: blake015@mc.duke.edu (Denise Blakeley) Newsgroups: comp.sys.next.bugs Subject: Re: .ps icon mangled Message-ID: <19073@news.duke.edu> Date: 13 Aug 93 21:58:49 GMT References: <CBM6sD.5K4@cbnewsl.cb.att.com> Sender: news@news.duke.edu david.k.kallman writes > Folks, > > The icon for .ps files in WorkSpace Manager is mangled on > my system. The file icon shows up in black and white (it > used to be in color) and the title says "PS?". .eps files > show up fine in color and saying "EPS". > > I'm running 3.1 on a NextStation Color. > > Anyone seen this? Being the co-producer of Opener v3.1, I'll admit it! It's a bug in Opener, and it has me stymied right now. Perhaps someone can help me solve this, so I can make Opener v3.1.1 available! If you look at the Help panel, you'll see that Michael Hawley's original intent was for Opener to recognize .PS and .EPS (note the capital letters) files as its own and pass them to Preview, since Preview doesn't recognize the capitalized file extensions. As far as I can tell, even Opener v3.0 didn't pass them on correctly--it didn't translate the extensions from upper to lower case so that Preview could understand. Right now, Opener v3.1 compounds the old problem. It wants to recognize .ps, eps, .PS, and .EPS files, although .ps and .eps should be Preview's only. I have a fix in the works so that Opener v3.1 no longer recognizes .eps file and will transform the .PS and .EPS file extensions so that it can pass them to Preview. But what has me stymied is that it still wants to recognize .ps files, too, even though there's nothing in the iconheader about them. Does anyone know what else might control this urge of Opener's? Thanks-- Denise -- Denise Blakeley | PROGRAM, tr. v., An activity similar Duke Med Center Info Systems | to banging one's head against a wall, Durham, NC | but with fewer opportunities for (919) 282-6468 W | reward. blake015@mc.duke.edu |
From: jreiss@magnus.acs.ohio-state.edu (Joseph W Reiss) Newsgroups: comp.sys.next.bugs,comp.sys.next.software Subject: Re: .ps icon mangled Date: 14 Aug 1993 00:26:29 GMT Organization: The Ohio State University Message-ID: <24hbfl$8h2@charm.magnus.acs.ohio-state.edu> References: <CBM6sD.5K4@cbnewsl.cb.att.com> <19073@news.duke.edu> Since several people have expressed interest in my NeXT style, color/mono Opener icons, I've uploaded them to cs.orst.edu. The files are OpenerTiffs.tar.gz and OpenerTiffs.README. Speaking of the README, here it is... ----------------------------------------------------------------------- These icons were design to replace the icons used in Opener 3.1. I "borrowed" the .tar, .Z and .ps icons from the various NeXT apps and modified them to go along with the various formats that Opener supports. To use these icons, simply copy them into the Opener.app directory and recompile (you might want to back up the old icons first, just in case). For those without the developers version, I've sent email to the people responsible for Opener 3.1 about getting these icons included in the next official release. Hopefully that'll come through and this archive will be unnecessary. But in the meantime... Enjoy, Joe Reiss ----------------------------------------------------------------------- If/when the icons become "official", they'll also be added to the info panels and help files for Opener, the way I've got them on my system. This is really just a matter of a bit of drag and drop work, and anybody who is familiar with that kinda thing can do it without too much trouble. See ya round! -- __________ | NeXTMail accepted, but not preferred | |___) | """""""""""""""""""""""""""""""""""""""""""""""""""""""" \_/OE | \EISS | The Prime Directive forbids our interfering with a `---- | developing flame-war. But that's never stopped us.
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: Methods and attributes Message-ID: <Aug16.143636.35558@acs.ucalgary.ca> Date: Mon, 16 Aug 1993 14:36:36 GMT References: <abellCBuHzp.MFD@netcom.com> Organization: The University of Calgary, Alberta > ... [ Code sample removed ] ... > > This compiles without complaint. In case you didn't see the > problem (neither did I after several minutes of staring at > similar code), the method called "gronk" is a *class* method, > but it refers to an attribute of an *instance* of the class. I > expected a compiler error. Is this a bug, or an obscure > feature of ObjC? I've reported it as a bug, so we'll see... it's also annoying in the case where you define a local variable with the same name as an instance variable from within a class method. The compiler warns you "Local declaration hides an instance variable!"... when the instance variable should itself be hidden. I haven't check Cox's book to see if he has anything to say on the scope of instance variable. -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
From: dkk@cbnewsl.cb.att.com (david.k.kallman) Newsgroups: comp.sys.next.bugs,comp.sys.next.software Subject: Re: .ps icon mangled Message-ID: <CBuwDw.E2v@cbnewsl.cb.att.com> Date: 16 Aug 93 14:32:18 GMT References: <CBM6sD.5K4@cbnewsl.cb.att.com> Followup-To: comp.sys.next.bugs Organization: AT&T Bell Laboratories Folks, Thanks!! The resolution to my post last week was real quick (maybe it was in the works?). See the announcement of Opener_3.1.1 in comp.sys.next.announce. Thanks to the current authors of Opener.app, Denise Blakeley and Subrata Sircar, and Joseph Reiss for the new icons. Dave Kallman -- ---- Dave Kallman, AT&T, 480 Red Hill Rd., Middletown, NJ 07748 d_k_kallman@att.com, (908)615-2989, fax: (908)615-2507
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: Methods and attributes Message-ID: <Aug16.154113.33162@acs.ucalgary.ca> Date: Mon, 16 Aug 1993 15:41:13 GMT References: <abellCBuHzp.MFD@netcom.com> <Aug16.143636.35558@acs.ucalgary.ca> Organization: The University of Calgary, Alberta > > This compiles without complaint. In case you didn't see the > > problem (neither did I after several minutes of staring at > > similar code), the method called "gronk" is a *class* method, > > but it refers to an attribute of an *instance* of the class. > > I expected a compiler error. Is this a bug, or an obscure > > feature of ObjC? > I've reported it as a bug, so we'll see... Of course, I meant to actually answer the posed question originally :-) Yes, it seems to be an obscure feature the need for which passed some time ago. If you've been working in NeXTSTEP for a few years you'll probably remember code like: + new { self = [ super new ] ; ivar = 22 ; return self ; } This required a class method to turn into an instance method on the fly ... which was pretty ugly (reassigning "self" from within a method? Brrr...), and NeXT fixed by replacing most of the "new" class initializers with "alloc" and then an instance method called "init" in release 2.0. I wouldn't be too surprised if a few snippets of AppKit or application code shipped with NeXTSTEP required this obscure feature still. It's still a bug, and should be fixed. -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs From: gerald@kurt.in-berlin.de (Gerald Erdmann) Subject: Re: ?bug: ATC decompression aborted. Truncated input file? Message-ID: <1993Aug16.111523.332@kurt.in-berlin.de> Sender: gerald@kurt.in-berlin.de References: <231fsk$m1n@news.cs.tu-berlin.de> Date: Mon, 16 Aug 1993 11:15:23 GMT In article <231fsk$m1n@news.cs.tu-berlin.de> kiwi@cs.tu-berlin.de (Axel Habermann) writes: > Hello! > > After upgrading to NS3.1 (Moto), there are some sounds which can't be > played. Under 3.0 there's no problem to play those sounds. On the > console the following message appears: > ATC decompression aborted. Truncated input file? > I tried several tools to play the sound, but it doesn't work. > Sometimes the machine produces the message, sometimes it doesn't, > but no sound is heard anyway. > > I would like to ask everyone who has installed 3.1 to try it and report > the results to see if this is a bug in 3.1 or not! Try it with the sounds > of DarkForest.app, they didn't work with me. > > Thanks! > Axel > Hups, it's correct. It doesn't work at me, too! Does you report to bug to next_bug@next.com? -------------------------------------------------------------- | GERALD ERDMANN | email: gerald @ kurt.in-berlin.de (NeXTmail welcome) | voice: +49 30 372 43 10 (Germany - Berlin) |
Newsgroups: comp.sys.next.bugs From: frank@fnbc.com (Frank Mitchell) Subject: Re: Methods and attributes Message-ID: <1993Aug16.161844.25860@fnbc.com> Sender: news@fnbc.com Organization: First National Bank Of Chicago, Chicago IL, USA References: <Aug16.143636.35558@acs.ucalgary.ca> Date: Mon, 16 Aug 93 16:18:44 GMT I've also reported the "instance variable in class method compiles without error" bug, on April 8. It was given log #42166. I found it when *setting* said ivar stomped on the Class structure. Is this in 3.1/3.2 still? -- Frank Mitchell email(work): frank@fnbc.com (NeXTmail) (home): frank@gagme.chi.il.us Shop smart. Shop S-Mart.
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: ?bug: ATC decompression aborted. Truncated input file? Message-ID: <CBvDtz.Ftn@news.cis.umn.edu> Sender: news@news.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota Hospital and Clinic, Labratory Information Services References: <231fsk$m1n@news.cs.tu-berlin.de> <1993Aug16.111523.332@kurt.in-berlin.de> Date: Mon, 16 Aug 1993 20:47:28 GMT use 3.0's sndcompress to decompress the soundfiles. ATC on 3.1 is broke peter Gerald Erdmann (gerald@kurt.in-berlin.de) wrote: : In article <231fsk$m1n@news.cs.tu-berlin.de> kiwi@cs.tu-berlin.de (Axel : Habermann) writes: : > Hello! : > : > After upgrading to NS3.1 (Moto), there are some sounds which can't be : > played. Under 3.0 there's no problem to play those sounds. On the : > console the following message appears: : > ATC decompression aborted. Truncated input file? : > : > Thanks! : > Axel : > : Hups, it's correct. It doesn't work at me, too! Does you report to bug to : next_bug@next.com? -- Bureaucratically speaking, I am a subversive to obstructionists... peter@tahiti.umhc.umn.edu (Peter Eisch)
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 16 Aug 1993 17:36:46 -0400 Organization: Next Announcements Message-ID: <24oulc$gdi@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish
From: warren@cyberspace.com (Warren Victorian) Newsgroups: comp.sys.next.bugs Subject: What are these? Date: 16 Aug 1993 21:33:26 -0700 Organization: (CYBERSPACE) Public Internet 206.286.1600 Message-ID: <24pn2m$1jd@cyberspace.com> Cc: I found these wierd international phone sex lines in a magazine the otherday and I was just wondering how these people can offer a service like this for free. It makes no sence to me. Anyways it is pretty hardcore and anyone into that type of stuff should give it a shout. 011-239-129-2618 or 011-239-129-2620
Date: Tue, 17 Aug 1993 04:46:10 GMT From: jik@GZA.COM (Jonathan I. Kamens) Message-ID: <jik.cancel.930817044610.137.164@GZA.COM> Newsgroups: comp.sys.next.bugs,control Subject: cmsg cancel <24pn2m$1jd@cyberspace.com> Control: cancel <24pn2m$1jd@cyberspace.com> .
From: bajwa@ucs.ubc.ca (Bob Bajwa) Newsgroups: comp.sys.next.bugs Subject: MorningStar-PPP Date: 17 Aug 1993 20:24:41 GMT Organization: The University of British Columbia Distribution: world Message-ID: <24req9$hme@skeena.ucs.ubc.ca> Keywords: ppp, Morning Star Is there anyone running Morning Star PPP under NeXTSTEP3.1 on black hardware? I have the latest, dated July 30, 1993, MS-PPP software installed in on my NeXTcube running NEXTSTEP3.1. I have no problems connecting to remote site from my NeXTcube. However, the remote site can't connect to my NeXTcube. When the remote site calls my NeXTcube, the modem answers the call, allows remote to login, and then drop the line right after the successful login. It used to work fine in NeXTSTEP 3.0. Anyone else experiencing similar problem? -bob bajwa
From: jon@cbl.umd.edu (Jonathan Kruger) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: What sort of bug caused this panic message? Date: 18 Aug 1993 09:44:14 -0400 Organization: University of Maryland, Chesapeake Biological Laboratory Message-ID: <24tbneINNph0@cbl.umd.edu> I left my 486 running overnight with BackSpace running. When I came in to my office this morning I was greated by this cute little box in the middle of my screen which said: panic: (Cpu 0) new_posix_proc(): attempt to create posix proc struct for pid 6943, found existing struct; process exists. panic: NeXT Mach 3.1: Thu Apr 29 23:44:40 PDT 1993; root(rcbuilder): objects/mk-149.22.3.obj~2/RELEASE_I386 Raise RDP exception 6 code 3 subcode 0 Waiting for RDP connection (type 'c' to continue) Of course, when I type 'c' it just repeats the "type 'c'" message. Is this a bug in BackSpace, 3.1, the SMC ethernet driver or what? Is there any way to FIX it before 3.2 comes out? -- ------------------------------------------------------------------------------- Jonathan Kruger - jon@cbl.umd.edu - Computer and Network Systems Coordinator U of MD Center for Environmental and Estuarine Studies, Chesapeake Bio Lab
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: What sort of bug caused this panic message? Message-ID: <CBz4u6.1sz@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota Hospital and Clinic, Labratory Information Services References: <MS-C.745707094.1103527590.mrc@Ikkoku-Kan.Panda.COM> Date: Wed, 18 Aug 1993 21:17:51 GMT Mark Crispin (mrc@Ikkoku-Kan.Panda.COM) wrote: : You've encountered a kernel bug. It is extremely unlikely that you'll be able : to find any way to reproduce the problem. In fact, it seems that at least 50% : of all panics are discovered when the user comes into the office in the : morning. My host never panics. Perhaps because it's in my living room. <stupid grin> peter -- Bureaucratically speaking, I am a subversive to obstructionists... peter@tahiti.umhc.umn.edu (Peter Eisch)
Newsgroups: comp.sys.next.bugs From: pmfranc@afterlife.ncsc.mil. (Paul M. Franceus) Subject: Why doesn't my CD drive work with audio CD's Message-ID: <1993Aug19.132249.16213@afterlife.ncsc.mil> Keywords: CD audio scsi Sender: news@afterlife.ncsc.mil Organization: The Great Beyond Date: Thu, 19 Aug 1993 13:22:49 GMT Hello- Does anyone have any idea why my CD-ROM drive would work fine for data CD's, but when I try to play an audio CD (using CDPlayer.app) the program can't find the CD ROM? I have a color NeXTStation turbo running 3.0 Paul
From: bajwa@ucs.ubc.ca (Bob Bajwa) Newsgroups: comp.sys.next.bugs Subject: MorningStar-PPP Date: 17 Aug 1993 20:24:41 GMT Organization: The University of British Columbia Distribution: world Message-ID: <24req9$hme@skeena.ucs.ubc.ca> Keywords: ppp, Morning Star Is there anyone running Morning Star PPP under NeXTSTEP3.1 on black hardware? I have the latest, dated July 30, 1993, MS-PPP software installed in on my NeXTcube running NEXTSTEP3.1. I have no problems connecting to remote site from my NeXTcube. However, the remote site can't connect to my NeXTcube. When the remote site calls my NeXTcube, the modem answers the call, allows remote to login, and then drop the line right after the successful login. It used to work fine in NeXTSTEP 3.0. Anyone else experiencing similar problem? -bob bajwa
Newsgroups: comp.sys.next.bugs From: friendly@hotspur.psych.yorku.ca (Michael Friendly) Subject: .ps icon mangled - the saga continues Message-ID: <CC0K3n.LrM@newshub.ccs.yorku.ca> Sender: news@newshub.ccs.yorku.ca (USENET News System) Organization: York University Date: Thu, 19 Aug 1993 15:52:34 GMT Just when I thought it was safe to double click... Last week there was a flurry of posts related to the icon for .ps files getting unaccountedly changed in WMgr. The culprit was found to be Opener.app (3.1), which led to a timely fix to 3.1.1. After installing the new Opener, I downloaded BBFig1.3, which is designed to let you manipulate the bounding box for a .ps file. Now, even though Preview is my default tool for .ps files, the BBFig icon is displayed in the WMgr. So, perhaps Opener left some crumbs in my defaults somewhere. I tried dread -l |grep ps but nothing showed up. Anyone have any ideas? Pls reply direct. -- Michael Friendly Internet: friendly@vm1.yorku.ca Psychology Department NeXTmail: friendly@hotspur.psych.yorku.ca York University 4700 Keele Street Toronto, ONT M3J 1P3 CANADA
From: blake015@mc.duke.edu (Denise Blakeley) Newsgroups: comp.sys.next.bugs Subject: Re: .ps icon mangled - the saga continues Message-ID: <19357@news.duke.edu> Date: 20 Aug 93 00:06:07 GMT References: <CC0K3n.LrM@newshub.ccs.yorku.ca> Sender: news@news.duke.edu Michael Friendly writes > Just when I thought it was safe to double click... > Last week there was a flurry of posts related to the icon for .ps files > getting unaccountedly changed in WMgr. The culprit was found to be > Opener.app (3.1), which led to a timely fix to 3.1.1. > > After installing the new Opener, I downloaded BBFig1.3, which is designed to > let you manipulate the bounding box for a .ps file. Now, even though Preview > is my default tool for .ps files, the BBFig icon is displayed in the WMgr. > > So, perhaps Opener left some crumbs in my defaults somewhere. I tried > dread -l |grep ps > but nothing showed up. Sounds to me like BBFig (whatever that is--I haven't heard of it before) contains the same kind of bug that I fixed for Opener 3.1.1. It's definitely not an Opener bug you're experiencing, because Opener doesn't contain the BBFig icon (which it would have to to create this behavior). Denise -- Denise Blakeley | PROGRAM, tr. v., An activity similar Duke Med Center Info Systems | to banging one's head against a wall, Durham, NC | but with fewer opportunities for (919) 282-6468 W | reward. blake015@mc.duke.edu |
Newsgroups: comp.sys.next.bugs From: adrian@niagara.ucs.ualberta.ca (Adrian Smith) Subject: Re: MoveWhenIdle in 3.1 not working?? Message-ID: <1993Aug20.001528.19413@kakwa.ucs.ualberta.ca> Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <1993Aug13.123426.7363@ToTSySSoft.com> Date: Fri, 20 Aug 1993 00:15:28 GMT In article <1993Aug13.123426.7363@ToTSySSoft.com> bruce@TotSysSoft.com (Bruce Gingery) writes: > In article <1993Aug13.072214.543@rna.indiv.nluug.nl> > gerben@rna.indiv.nluug.nl writes: > -> I'd like to prevent a screen burn-in when I'm not logged > -> (the machine stays on). But instead of a moving > -> loginwindow I get some NeXT logo in the middle > -> which seems to be not moving at all. Is this a bug > -> or has the way to save > -> screen during logout changed? > > > It's changed... If you leave it up for a while, you should see > it reposition -- this is not a constantly moving display, but > is a result of having a > dwrite loginwindow ScreenSaverEnabled YES > set. Here's the explanation as given by NeXT. Due to some of the changes in NS 3.1, the dwrite for moving the screen (which used to be measured in something approaching ticks) is now measured in seconds. Thus, your old dwrite is no longer valid. Now if only I still had the message stating what the fix is (hard drive crashes that wipe out mail folders are SUCH a pain...) -- Adrian Smith --- University of Alberta Computing and Network Services Consultant NeXT Campus Consultant adrian@niagara.ucs.ualberta.ca
Newsgroups: comp.sys.next.bugs From: zaphod@ctrg.rri.uwo.ca (Lance R. Bailey) Subject: Re: .ps icon mangled - the saga continues Organization: University of Western Ontario Distribution: na Date: Fri, 20 Aug 1993 09:56:25 GMT Message-ID: <1993Aug20.095625.24591@julian.uwo.ca> References: <19357@news.duke.edu> Sender: news@julian.uwo.ca (USENET News System) >Michael Friendly writes >> After installing the new Opener, I downloaded BBFig1.3, which is designed to >> let you manipulate the bounding box for a .ps file. Now, even though Preview >> is my default tool for .ps files, the BBFig icon is displayed in the WMgr. >> i dunno, i think that the BBFig icon is pretty groovy :) -- Lance R. Bailey System/Network Manager Robarts Research Institute NeXT/email: zaphod@ctrg.rri.uwo.ca box: Clinical Trials Resources Group fax: +1 519 663 3789 P.O. Box 5015, 100 Perth Dr. vox: +1 519 663 3787 x4108 London, Canada N6A 5K8 Bus error. Passengers dumped.
Newsgroups: comp.sys.next.bugs From: friendly@hotspur.psych.yorku.ca (Michael Friendly) Subject: Re: .ps icon mangled - an answer Message-ID: <CC2D7K.6JE@newshub.ccs.yorku.ca> Sender: news@newshub.ccs.yorku.ca (USENET News System) Organization: York University References: <CC0K3n.LrM@newshub.ccs.yorku.ca> Date: Fri, 20 Aug 1993 15:18:55 GMT John Bartley <john@wpa.com> provided me with the situation under which this occurs and a workaround: -- begin quote -- Ah, my suspicion was correct. I've had strange problems like this before. I don't know whether NeXT considers this a bug or not, but I think you'll find that you will be able to do what you want to do if you move BBfig to /LocalApps (or vice versa.) The problem seems to be one of precedence but only under certain circumstances that I can't fully identify. I do know that having the "competing" apps in the same directory will solve the problem. -- end quote -- I've verified that having BBFig in the same directory as Opener cures the problem (even though Opener is now well-behaved). -- Michael Friendly Internet: friendly@vm1.yorku.ca Psychology Department NeXTmail: friendly@hotspur.psych.yorku.ca York University 4700 Keele Street Toronto, ONT M3J 1P3 CANADA
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: thomas@olorin.dark.sub.org (Thomas Fischer) Subject: Re: What sort of bug caused this panic message? Message-ID: <1993Aug21.092411.373@olorin.dark.sub.org> Organization: Olorin, NeXT Development & System Administration, FRG References: <24tbneINNph0@cbl.umd.edu> Date: Sat, 21 Aug 1993 09:24:11 GMT jon@cbl.umd.edu (Jonathan Kruger) wrote: >I left my 486 running overnight with BackSpace running. When I came >in to my office this morning I was greated by this cute little box in >the middle of my screen which said: > > panic: (Cpu 0) new_posix_proc(): attempt to create posix proc struct > for pid 6943, found existing struct; process exists. I had exactly the same error about 3 weeks back. And I have no idea what could have caused this, although I'm pretty sure it was not Backspace - I'm not running it... ;-) Actually (I think) there were no applications running on my machine so I guess NS3.1 has something to do with it. The worst thing was that I was on holiday and didn't come back for 14 days.:-( Thomas -- Although golf was originally restricted to wealthy, overweight Protestants, today it's open to anybody who owns hideous clothing. -- Dave Barry --- Thomas Fischer, thomas@olorin.dark.sub.org, +49 7191 23217 (fax & data)
Newsgroups: comp.sys.next.bugs From: nico@imani.cam.org (Nicolas Dore) Subject: Limit on # off apps WM can launch at once? Message-ID: <1993Aug19.234200.333@imani.cam.org> Sender: nico@imani.cam.org Date: Thu, 19 Aug 1993 23:42:00 GMT Hey folks. This is all on a Cube running 3.0. I was just showing the machine off to a friend, and tried to start all 17 Demos at once. WM started about 8, and then froze. All I could do was go in each app and quit it, and even took _MINUTES_ (between "Quit" and the actual disapearring of the icon from the screen). As the WM came back, after all apps had been "quitted", it printed this in the console: "Aug 19 19:28:19 Workspace: Extraneous launch reply message received" Does this mean there's a limit to the number of apps one can start from the WM? Didn't exist in pre-3.0 days, I know that, and I doubt it does, but that's what it gave me. And is giving me right now. BTW, ps tells me that the WM is using 0% of CPU time when it's frozen. WindowServer goes up (40-50%), thought. Any idea? Can you reproduce it? In 3.0, 3.1, FIP/Black? Ciao Nicolas Dore -- Nicolas Dore nico@imani.cam.org - - - - - - - - - CAREFUL! NERDIE TV SHOW QUOTE ZONE! - - - - - - - > "Just once I'd like to meet an alien nuisance < > that isn't immune to bullets" Policeman, in Dr Who <
Newsgroups: comp.sys.next.bugs From: gerben@rna.indiv.nluug.nl Subject: Upgrader_3.1.app bug (hangs) and fix Message-ID: <1993Aug21.175146.2236@rna.indiv.nluug.nl> Sender: gerben@rna.indiv.nluug.nl (Gerben Wierda) Organization: G.R.O.S.S. Date: Sat, 21 Aug 1993 17:51:46 GMT We encountered a bug in Upgrader_3.1.app. Cause: Upgrader_3.1.app PostProcess script calls ls. Our ls is aliased in /etc/cshrc.std as ls-CF. Result: PostProcess script will hang. Netinfo changes are not installed, and nor are the languages. Fix: Make sure ls is not aliased. Repairing if it has happened to you: Copy PostProcess to /tmp and apply the diff below and execute as: /tmp/PostProcess / /NEXTSTEP_3.1 The diff also fixes another typo where the string ">& /dev/null" is somewhere inside a netinfo argument instead of at the end of the command. We assume this is an error (safe assumption). DIFF: *** /tmp/PostProcess Sat Aug 21 17:44:47 1993 --- /NEXTSTEP_3.1/Upgrade_3.1.app/Default.upgrade/PostProcess Wed May 5 03:16:19 1993 *************** *** 13,19 **** set source = $argv[2] cd ${target}/etc/netinfo ! set databases = `/bin/ls ${target}/etc/netinfo` foreach database ($databases) --- 13,19 ---- set source = $argv[2] cd ${target}/etc/netinfo ! set databases = `ls ${target}/etc/netinfo` foreach database ($databases) *************** *** 52,58 **** niutil -t -createprop localhost/${usetag} /locations/renderers _writers '*' >& /dev/null niutil -t -create localhost/${usetag} /locations/renderers/localhost >& /dev/null niutil -t -createprop localhost/${usetag} /locations/renderers/localhost _writers '*' >& /dev/null ! niutil -t -createprop localhost/${usetag} /locations/renderers/localhost note "Local Renderer" >& /dev/null endif echo " Updating /rpcs..." --- 52,58 ---- niutil -t -createprop localhost/${usetag} /locations/renderers _writers '*' >& /dev/null niutil -t -create localhost/${usetag} /locations/renderers/localhost >& /dev/null niutil -t -createprop localhost/${usetag} /locations/renderers/localhost _writers '*' >& /dev/null ! niutil -t -createprop localhost/${usetag} /locations/renderers/localhost note "Local >& /dev/null Renderer" endif echo " Updating /rpcs..." -- Gerben Wierda [NeRD:7539] gerben@rna.indiv.nluug.nl "If you don't know where you are going, any road will take you there." From the Talmud(?), rephrased in Lewis Carroll, "Alice in Wonderland".
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: Limit on # off apps WM can launch at once? Message-ID: <Aug22.142824.31794@acs.ucalgary.ca> Date: Sun, 22 Aug 1993 14:28:24 GMT References: <1993Aug19.234200.333@imani.cam.org> Organization: The University of Calgary, Alberta > This is all on a Cube running 3.0. My response is from a cube running 3.1. > I was just showing the machine off to a friend, and tried to > start all 17 Demos at once. WM started about 8, and then froze. > All I could do was go in each app and quit it, and even took > _MINUTES_ (between "Quit" and the actual disapearring of the > icon from the screen). I just started all 18 apps while attempting to type this :-) The system definitely ground for about 1 minute but there was definite visible progress until all of the application came up. How much RAM do you have? > As the WM came back, after all apps had been "quitted", it > printed this in the console: > "Aug 19 19:28:19 Workspace: Extraneous launch reply message > received" > > Does this mean there's a limit to the number of apps one can > start from the WM? There certainly isn't such a limit, it sounds more like the message indicates that one of the applications reponded to being launched notified the WM twice. > Didn't exist in pre-3.0 days, I know that, and I doubt it does, > but that's what it gave me. And is giving me right now. BTW, ps > tells me that the WM is using 0% of CPU time when it's frozen. > WindowServer goes up (40-50%), thought. Any idea? Can you > reproduce it? In 3.0, 3.1, FIP/Black? How did you try to launch the apps? If you accidently did ANY icon dragging the WM may have become confused and waited to time out (it used to do this to me ALL the time if I was dragging an icon around when a disk auto-mounted). -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs From: paulz@olivetti.nl (Paul van der Zwan) Subject: bug in access(2) ?? Message-ID: <1993Aug22.212321.19033@olivetti.nl> Organization: Olivetti Nederland B.V. Date: Sun, 22 Aug 1993 21:23:21 GMT There appears to be a bug in access(2) in 3.1(black). The man page says the following: The real user ID and the group access list (including the real group ID) are used in verifying permission, so this call is useful to set-UID programs. But it looks like the effective uid is uses and not the real uid. I used the following program to test it. #include <stdio.h> #include <sys/file.h> #include <sys/errno.h> main(int argc, char **argv) { int retval ; extern int errno; if ( argc == 2 ) { retval=access(argv[1],R_OK); printf("retval=%d, errno=%d\n",retval,errno); printf("real uid=%d , effective uid=%d\n",getuid(),geteuid()); } } Can anyone confirm this behavior -- Paul van der Zwan paulz@olivetti.nl Olivetti Nederland B.V. paulzn@olivetti.nl (NeXT-mail)
Newsgroups: comp.sys.next.bugs From: dgursky@nextsrv1.andi.org (David Gursky) Subject: buildafmdir Message-ID: <dgursky.746042538@news.andi.org> Summary: Looking for a work-around for buildafmdir's font limit Organization: Association of NeXTSTEP Developers International Date: Sun, 22 Aug 1993 18:02:18 GMT I know that the version of buildafmdir that ships with NS versions 3.0 and beyond has a bug in it that will not let you install more than 255 typefaces, presumably in any one of ~Library/Fonts, /LocalLibrary/Fonts, or /NextLibrary/Fonts. If you don't have the version of buildafmdir that shipped with NS 2.1, are there any alternative work-arounds, without having to put fonts outside of /LocalLibrary/Fonts? David M. Gursky MIME and NEXTMAIL accepted Synex, Inc. e-mail: .. dgursky@nextsrv1.andi.org 5950 Symphony Woods Road voice: ............. (301) 621-5732 Columbia, MD 21044 fax: ............. (301) 621-6005 -- David M. Gursky MIME and NEXTMAIL accepted Synex, Inc. e-mail: .. dgursky@nextsrv1.andi.org 5950 Symphony Woods Road voice: ............. (301) 621-5732 Columbia, MD 21044 fax: ............. (301) 621-6005
Newsgroups: comp.sys.next.bugs From: schaik@cnplss5.cnps.philips.nl (Willem van Schaik) Subject: DOS floppies under NS 3.0 Message-ID: <1993Aug23.105447.28721@cnplss5.cnps.philips.nl> Keywords: DOS NEXT FLOPPY Sender: news@cnplss5.cnps.philips.nl (USENET News System) Organization: Philips Communications & Processing Services, Eindhoven Date: Mon, 23 Aug 1993 10:54:47 GMT Hi NeXT ones, I must say that using DOS floppies has in my opinion not much improved ;-) when you compare NS2.1 and NS3.0. My problems with it are: 1. in most cases the floppy is not mounted using the name of the label, but with something like /no_name, or /boeder (or something similar, I don't remember). Under 2.1 it was always /DOS, which is easy when you want to copy files to/from the floppy with scripts. 2. The date of files was under 2.1 set to something like the year 2099. Under 3.0 it is only 9 hours wrong. Has this something to do with the timezone ??? 3. When you copy a file from hard-disk to DOS-floppy the filename MUST be lowercase. While most filenames in NeXTstep are capitalized. Also automatic conversion to 8.3 format whould not have been that difficult. I don't remember how this case-sensitivity worked under 2.1, but I got much less pop-ups with warnings. If anyone has solutions for these problems, or if you can proove that I'm just stupid, please respond. If this is something we have to live with, maybe some NeXT person can tell us why they changed it and when they intend to change it back/again. Willem van Schaik schaik@cnplss5.cnps.philips.nl
Newsgroups: comp.sys.next.bugs From: gerben@rna.indiv.nluug.nl Subject: Someone with 3.1 black and PLI superfloppy: please check this: Message-ID: <1993Aug23.164358.1352@rna.indiv.nluug.nl> Sender: gerben@rna.indiv.nluug.nl (Gerben Wierda) Organization: G.R.O.S.S. Date: Mon, 23 Aug 1993 16:43:58 GMT Try formatting a 1.4MB disk in the PLI Superfloppy with a NeXT filesystem. Does it work? I have problems here. Look what happens when I try to format a DOS disk as NeXT disk: Aug 23 18:40:54 Workspace: Mounted floppy disk at /unlabeled probing for DOS probing for CDROM probing for cdaudio probing for mac unknown argument probing for HFS_XFer Aug 23 18:41:09 Workspace: Unmounted foreign disk at /unlabeled /usr/etc/disk -i -h mr_ed -l "transport" /dev/rsd3a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi device = /dev/rsd3a block size = 512 capacity = 1 MBytes Disk Format in progress... ***Format Complete*** writing disk label boot block extends beyond front porch What is going on here? Thanks, -- Gerben Wierda [NeRD:7539] gerben@rna.indiv.nluug.nl "If you don't know where you are going, any road will take you there." From the Talmud(?), rephrased in Lewis Carroll, "Alice in Wonderland".
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 23 Aug 1993 14:34:46 -0400 Organization: Next Announcements Message-ID: <25b2k4$sv5@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish
Newsgroups: comp.sys.next.bugs From: paulz@olivetti.nl (Paul van der Zwan) Subject: Re: bug in access(2) ?? Message-ID: <1993Aug24.101444.2083@olivetti.nl> Organization: Olivetti Nederland B.V. References: <1993Aug22.212321.19033@olivetti.nl> <1993Aug23.030614.10449@csus.edu> Date: Tue, 24 Aug 1993 10:14:44 GMT In article <1993Aug23.030614.10449@csus.edu> eps@cs.sfsu.edu writes: > >In article <1993Aug22.212321.19033@olivetti.nl> paulz@olivetti.nl > (Paul van der Zwan) writes: >>There appears to be a bug in access(2) in 3.1(black). The man page says the >[...] >>But it looks like the effective uid is uses and not the real uid. >>I used the following program to test it. >[...] >>Can anyone confirm this behavior > >I am unable to duplicate the problem you describe. Please >furnish additional details. > >+ Note that there was a problem with access(2) using the wrong > NFS credentials in 2.x; fixed in 3.0PR2 and later. > >+ /NextLibrary/Documentation/NextDev/ReleaseNotes/OperatingSystem.rtf > describes a situation in which access() may not function > correctly in a multithreaded application. > I did some more testing using the program in my original post. It looks like the problem occurs when you give an absolute path and the effective uid has no read permission for one the dirs in that path. Look at the following: [test:paulz]$ ls -ld /paulz drwx------ 12 paulz 2048 Aug 24 11:37 /paulz [test:paulz]$ ls -ld /paulz/src drwxr-xr-x 6 paulz 1024 Aug 23 21:27 /paulz/src [test:paulz]$ ls -ld /paulz/src/test drwxr-xr-x 2 paulz 1024 Aug 24 11:54 /paulz/src/test [test:paulz]$ ls -ld /paulz/src/test/testfile -rw------- 1 paulz 0 Aug 24 11:54 /paulz/src/test/testfile [test:paulz]$ [test:paulz]$ ls -lg acctest -rwsr-xr-x 1 nobody uucp 49712 Aug 22 23:10 acctest [test:paulz]$ ./acctest testfile retval=0, errno=0 real uid=544 , effective uid=-2 (This result is OK) [test:paulz]$ ./acctest /paulz/src/test/testfile retval=-1, errno=13 real uid=544 , effective uid=-2 [test:paulz]$ grep 13 /usr/include/sys/errno.h #define EACCES 13 /* Permission denied */ This result is incorrect, I HAVE read permission for /paulz/src/test/testfile. It looks like access is using the effective uid when checking the permissions for directories in its first argument. Paul -- Paul van der Zwan paulz@olivetti.nl Olivetti Nederland B.V. paulzn@olivetti.nl (NeXT-mail)
Newsgroups: comp.sys.next.bugs From: gerben@rna.indiv.nluug.nl Subject: /usr/etc/disk in 3.1 black broken. Workaround available. Message-ID: <1993Aug24.134011.616@rna.indiv.nluug.nl> Sender: gerben@rna.indiv.nluug.nl (Gerben Wierda) Organization: G.R.O.S.S. Date: Tue, 24 Aug 1993 13:40:11 GMT /usr/etc/disk in 3.1 is broken. So far it seems that formatting scsi disks does not work and that formatting the interbal floppy drive does work. If it does not work you get the error: boot block extends beyond front porch Replacing /usr/etc/disk with the 3.0 version is a workable alternative, but I do not know if maybe other initialisations (Mac?) or operations fail with the 3.0 version of /usr/etc/disk Bug has been seen also by John Bartley, who passed the 3.0 tip by Cal Thixton on to me. (Just to give everybody their credits, I didn't find this out myself :-). For completeness: BugNeXT 47776 (SCSI hard disk), 48829 (SCSCI floppy disk). -- Gerben Wierda [NeRD:7539] gerben@rna.indiv.nluug.nl "If you don't know where you are going, any road will take you there." From the Talmud(?), rephrased in Lewis Carroll, "Alice in Wonderland".
Newsgroups: comp.sys.next.bugs From: obrooks@worf.hssc.ksc.nasa.gov (Oscar Brooks) Subject: DMESG Problem Message-ID: <1993Aug25.131921.25809@dale.ksc.nasa.gov> Keywords: dmesg Sender: news@dale.ksc.nasa.gov Organization: NASA Date: Wed, 25 Aug 1993 13:19:21 GMT Everytime we try to run "dmesg" we get the following error: worf# dmesg Aug 25 09:03 Can't get kernel namelist worf# This being run on NeXTStation Color system (68030) running 3.1. Any hints ? Please!! O -- ------------------------------------------------ Oscar Brooks Mail Code: DL-DSD-24 Kennedy Space Center, Fla. 32899 Internet: obrooks@dale.ksc.nasa.gov
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: sholder@cse.uta.edu (Shane Andrew Holder) Subject: HELP: Problem with NeXT Header files, (all should read) Message-ID: <1993Aug26.040149.6094@news.uta.edu> Keywords: compiler, header, ingres Sender: news@news.uta.edu (USENET News System) Organization: Computer Science Engineering at the University of Texas at Arlington Date: Thu, 26 Aug 1993 04:01:49 GMT OK, The tools: NeXT 68040 NS v3.0 cc v 1.93 default compiler gcc 2.4.5 ingres 8.9 The task: I'm trying to compile Ingres on my NeXT. I'm going to try and port it, big task I know but I'm bored. The problem: (Those damn header files) Because of the way Ingres was written I am having to use a -traditional as one of the flags to cc (someone declared a variable with the name const). When using -traditional neither gcc nor cc will evaluate the #include macros that NeXT uses in some of their header files. ex: #include ARCH_INCLUDE(bsd/, machparam.h) in the file /NextDeveloper/Headers/bsd/machine/machparam.h I wasn't surprised to find out that gcc wouldn't make the translation. I mean, if your compiling with -traditional you should expect traditional stuff, but when cc didn't work (I know it's based on gcc) I was a little peeved. If NeXT is going to do so much untraditional stuff then they should support it fully. Now, I have been happy with my NeXT from the day I bought it. I understand their reasons for dinking with the headerfiles the way they have, and I don't want to start a debate on whether or not it's right or wrong, but damnit if it ain't frustrating to deal with in the real world. If anyone has any real suggestions on how I can get through my delima -- Thanks, Shane Holder sholder@cse.uta.edu
From: giddings@sadie.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs,comp.sys.sysadmin Subject: General disk read/initialize problems with NS/Intel Date: 26 Aug 1993 04:53:07 GMT Organization: Division of Information Technology Distribution: world Message-ID: <25hfjj$mbr@news.doit.wisc.edu> Keywords: disk format read We've been having problems with reading/writing using the floppy drives in both of our NS/I machines. General symptoms include: - Certain disks written to by a black system are simply unreadable - On readable disks, most files can be read, but at least 20% of reads fail - Macintosh disks seem less likely to be readable - Re-initializing one of these disks that is unreadable to the system results in initialization failure. - We've had problems with dos disks too (though I don't remember the details since it has been a while) Has anyone else noticed similar symptoms, or did we just get really unlucky with two bad floppy drives? A strange additional note is that today I inserted a Mac floppy that the the Workspace would not recognize (it wanted to initialize the disk), however, when I ran HFS_XFER under EXECUTOR, it WAS able to read the disk. This indicates to me this might be a software problem in the workspace . . . (ugh) Michael Giddings UW Madison Chemistry
From: gt8299c@prism.gatech.EDU (Badri Narasimhan) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: Sound on NextStep Keywords: sound, NextStep Message-ID: <110477@hydra.gatech.EDU> Date: 26 Aug 93 17:54:45 GMT Followup-To: comp.sys.next.misc Organization: Georgia Institute of Technology Dear Sir/Madam: I have installed NextStep on a DELL 450 DE/2. However, I am not able to hear any of the audio effects (I am told that there are many). Could anybody help me out? For example, even the demo sounds are not audible. I tried setting the volume level at full blast in the preferences window but of no avail. Hoping to get this fixed, Badri badri@gtsurya.gatech.edu -- Badri Narasimhan Georgia Institute of Technology, Atlanta Georgia, 30332 uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!gt8299c Internet: gt8299c@prism.gatech.edu
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: DO MEMORY LEAK in 3.0 and apparently still in 3.1 Message-ID: <1993Aug26.174907.9714@instep.wimsey.bc.ca> Keywords: do memory Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. Date: Thu, 26 Aug 1993 17:49:07 GMT DISTRIBUTED OBJECTS MEMORY LEAK in 3.0 ... still in 3.1! According to Next's documentation space for arguments passed to the server is allocated on the server side, and a pointer to the local data is received. The server's allocated copy of the data is local in scope and WILL BE FREED BY THE SYSTEM WHEN THE SERVER'S METHOD RETURNS. The capitals in the last statement is NOT the way DO has been implemented in 3.0 (and 3.1) I have written a small test program (shown below) to test/confirm this BLATANT memory leak in Distributed Objects. I see the 3.1 Release notes have fixed some bugs in DO, but failed to mention a fix for this bug. COMMENTS This Memory Leak has serious effects on the whole DO concept! It completely annihilates the concept of transparency of the DO paradigm. Without always passing sender, how is one to know if a method call originated locally or remotely? My patch to call free() explicitly would have very nasty effects if it were to be called on data passed locally on the stack. rfschtkt@banruc60.bitnet has added this to the Known Bugs in NEXTSTEP (KBNS.11.1.005_3.00): "Distributed Objects KBNS.11.1.005_3.0o Memory leak, reported by Bradley_Head on NeXT-prog@cpac.washington.edu on 1993-08-24, verified using his test program (available from him and included in the original report) by me IntroDistObjects.rtf says: In both the useAnIntByReference: and useAString: methods, a pointer is dereferenced on the client side, and the resulting data is sent to the server. On the server side, space for the data is allocated, and a pointer to the local data is received. The server's allocated copy of the data is local in scope and will be freed by the system when the server's method returns. This isn't true on 3.0 for strings: the string is leaked in the server. Bradley_Head said that the first string isn't leaked, but I found that it is." I sent this to bug_next. I can't believe NeXT has not fixed this for NS 3.1. TEST_CODE Here's the test code: I call it DOLeakTest_main.m. The instructions fo compiling and testing it are in the comments: /* * DOLeakTest_main.m * * * Distributed Objects memory leak test program. * * To use this program, first compile it like so: * * 1. Create a new project using Project Builder * 2. De-select "Generate Main file on save" option in Attributes. 3. Replace the _main.m file with this one. 4. Add libMallocDebug.a to the project's Libraries. 5. Compile as usual. * * * Alternatively: * * compile like so: * * cc -Wall -g DOLeakTest_main.m -lMallocDebug -o DOLeakTest * * To run the program, start the first one with the FULL path * name in a shell. This becomes the server. * * Select this "server" from the MallocDebug.app and check for * leaks, by clicking the "Leaks" button. It should say "No nodes" * at this point. * * Now, start another one these. It will become a client and ask * for text to send across to the server. Typing 'q' will quit. * This will be the client which will send the argument string over * to the server. At this point, no leaks should present themselves. * The next time you send a string, the previous string will become * the leaked memory. * * Somebody please test this code under NEXSTEP 3.0 and NEXTSTEP 3.1 * to see if this BUG has been fixed under 3.1. * * Thanks. */ #import <objc/objc.h> #import <objc/Object.h> #import <remote/NXProxy.h> #import <remote/NXConnection.h> #import <stdio.h> #import <string.h> #define RO_NAME "leak_test" @protocol ServerProtocol - receiveStr:(const char *)aStr; @end @interface MyServer:Object { } - receiveStr:(const char *)aStr; @end @implementation MyServer:Object - receiveStr:(const char *)aStr; { fprintf(stderr, "Received '%s'\nThis will not be freed when '%s'" "method returns.\nResults in a %lu octet leak the next time" " this method is called.\n\n", aStr, sel_getName(_cmd), (strlen(aStr) +1)); // According to NeXT Developer Docs, General Reference, Chapter 6 // Distributed Objects: // // "On the server side, space for the data is allocated, and a // pointer to the local data is received. The server's allocated // copy of the data is local in scope and will be freed by the system // when the server's method returns." // // As of NEXSTSTEP 3.0, this does NOT seem to be the case, so we will // explicitely free the data here: // // NOTE: Since this method does not receive sender, we have NO way // of knowing if the sender was a proxy. If it wasn't a proxy // the free() call to fix the memory leak will attempt to free // data passed on the stack, resulting in an exception. // This removes the transparancy of DO, since we must know in // advance that this method is called remotely. // // Note also, that if NeXT fixes this bug in a future release, // this code with the free() call will break, since it will // attempt to free data already freed. Watch out for this!!! // Uncomment the next line to fix the memory leak in 3.0 // free((char *)aStr); //??? This should NOT be required, but is... return self; } @end void main(int argc, char **argv) { MyServer *server; char buffer[2048]; id roserver = [NXConnection connectToName:RO_NAME]; char *str; if (roserver) { [roserver setProtocolForProxy:@protocol(ServerProtocol)]; fprintf(stderr, "Connected to server\n"); fprintf(stderr, "Enter text to send (q to quit):\n"); while (str = gets(buffer)) { if ((strlen(str) == 1) && (str[0] == 'q')) break; [roserver receiveStr:str]; fprintf(stderr, "Sent '%s' to server\n\n", str); fprintf(stderr, "Enter text to send:\n"); } } else { server = [[MyServer alloc] init]; roserver = [NXConnection registerRoot:server withName:RO_NAME]; fprintf(stderr, "Server waiting to receive strings...\n\n"); [roserver run]; } exit(0); } -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: ssircar@canon.com (Subrata Sircar) Newsgroups: comp.sys.next.bugs Subject: Re: DO MEMORY LEAK Date: 26 Aug 1993 15:50:11 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9308262048.AA18099@alychne-nc.canon.com> brad@instep.wimsey.bc.ca (Bradley Head) wrote: >According to Next's documentation space for arguments >passed to the server is allocated on the server side, and >a pointer to the local data is received. The server's >allocated copy of the data is local in scope and WILL BE >FREED BY THE SYSTEM WHEN THE SERVER'S METHOD RETURNS. The >capitals in the last statement is NOT the way DO has been >implemented in 3.0. I have confirmed the DO leak you posted about for both 3.0 and 3.1 (on my black hardware, anyway) and forwarded your bug report to NeXT. The reference number is 49040. --- Subrata Sircar|ssircar@canon.com (NextMail ok)|Prophet & SPAMIT Charter Member Canon Information Systems and I do not share the same views on everything. "I'm just mad that I missed the sexual revolution." - me "Yes, but you dress much better as a result." - Mike
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: General disk read/initialize problems with NS/Intel Message-ID: <1993Aug26.190028.13465@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <25hfjj$mbr@news.doit.wisc.edu> Date: Thu, 26 Aug 1993 19:00:28 GMT In article <25hfjj$mbr@news.doit.wisc.edu> giddings@sadie.chem.wisc.edu (Michael Giddings) writes: -> We've been having problems with reading/writing using -> the floppy drives in both of our NS/I machines. -> General symptoms include: -> -> - Certain disks written to by a black system are -> simply unreadable -> - On readable disks, most files can be read, but -> at least 20% of reads fail -> - Macintosh disks seem less likely to be readable -> - Re-initializing one of these disks that is -> unreadable to the system results in initialization -> failure. -> - We've had problems with dos disks too (though I -> don't remember the details since it has been a while) -> -> Has anyone else noticed similar symptoms, or did we -> just get really unlucky with two bad floppy drives? -> -> A strange additional note is that today I inserted a -> Mac floppy that the the Workspace would not recognize -> (it wanted to initialize the disk), however, when I -> ran HFS_XFER under EXECUTOR, it WAS able to read the disk. -> This indicates to me this might be a software problem -> in the workspace . . -> . (ugh) Michael, I've seen similar responses from the CD-ROM drive (unrecognized filesystem -- attempt to reinitialize...) and from Optical Disks on NEXTSTEP_3.1 (black), usually under heavy system loading. I'm beginning to suspect that there is an attempt to utilize a timeout parameter at too high a level, at least this is what the symptoms I've experienced seem to indicate. Do your cumulative experiences justify such a diagnosis? Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred MIME-Mail ok
From: otto@gandalf (Otto Lind) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: HELP: Problem with NeXT Header files, (all should read) Followup-To: comp.sys.next.programmer,comp.sys.next.bugs Date: 27 Aug 1993 05:58:09 GMT Organization: Coactive Aesthetics Inc. Message-ID: <25k7phINNjh4@disc.coactive.com> References: <1993Aug26.040149.6094@news.uta.edu> Shane Andrew Holder (sholder@cse.uta.edu) wrote: : When using -traditional neither gcc nor cc will : evaluate the #include macros that NeXT uses in some of their header : files. ex: : : #include ARCH_INCLUDE(bsd/, machparam.h) : : in the file /NextDeveloper/Headers/bsd/machine/machparam.h : If anyone has any real suggestions on how I can get through my delima Running the following script should make gcc happy: ----- cut here ----- #!/bin/sh # # Script to fix all references of ARCH_INCLUDE in NeXT header files # # # Set which machine type we want to convert to # ARCH=m68k # # Determine location of gcc installation # GCCSPEC=`gcc -v 2>&1 | egrep next | sed -e 's:Reading specs from \(.*\)/specs:\1:'` GCCINCLUDE=$GCCSPEC/include if test ! -d $GCCINCLUDE then echo "Cannot find gcc include directory" echo "dir = $GCCINCLUDE" exit 1 fi # # Find all ARCH_INCLUDE files and install them in gcc include subdirectory # cd /usr/include for i in `egrep -l ARCH_INCLUDE */*/*.h` do echo "Fixing $i" SUBDIR=`echo $i | sed -e 's:\(.*\)/.*:\1:'` mkdirs $GCCINCLUDE/$SUBDIR cat $i | egrep -v "architecture/ARCH_INCLUDE.h" | sed -e "s:ARCH_INCLUDE(\([a-z_][a-z_]*\)/,[ ][ ]*\(.*\)):<$ARCH/\2>:" \ > $GCCINCLUDE/$i done ----- cut here ----- Please note that I have not extensively tested this script (though it works with machine/machparam.h). Hope this helps, Otto -- Otto Lind Coactive Aesthetics otto@coactive.com P.O. Box 425967, San Francisco, CA 94142 netcom!coactive!otto voice:(415)626-5152 fax:(415)626-6320
From: work@dannug.dk (Michael Hallin) Newsgroups: comp.sys.next.bugs Subject: Re: buildafmdir Date: 26 Aug 1993 20:19:35 GMT Organization: Danish NeXT User Group Message-ID: <25j5sn$19s@localhost.dk> References: <dgursky.746042538@news.andi.org> In article <dgursky.746042538@news.andi.org> dgursky@nextsrv1.andi.org (David Gursky) writes: |>I know that the version of buildafmdir that ships with NS versions 3.0 and |>beyond has a bug in it that will not let you install more than 255 typefaces, |>presumably in any one of ~Library/Fonts, /LocalLibrary/Fonts, or |>/NextLibrary/Fonts. If you don't have the version of buildafmdir that shipped |>with NS 2.1, are there any alternative work-arounds, without having to put |>fonts outside of /LocalLibrary/Fonts? |> I don t know if there is another way to fix this, but I have several hundred fonts working on a 3.0 system, with the fonts spread evenly between the three ../Fonts directories. How, you ask? Well, I got a 2.2 version of buildafmdir, and that works. Mail me, if you want it. Best regards Michael --- _____________________________________________ Michael Hallin Copenhagen, Denmark NeXTMail: work@dannug.dk NonNeXTMail: mh.xeroxvang@rxdk.xerox.com Voice: Int + 45 43 53 34 33 Fax: Int + 45 43 53 34 33 _____________________________________________
Newsgroups: comp.sys.next.bugs From: dgursky@nextsrv1.andi.org (David Gursky) Subject: Re: buildafmdir Message-ID: <dgursky.746452560@news.andi.org> Organization: Association of NeXTSTEP Developers International References: <dgursky.746042538@news.andi.org> <25j5sn$19s@localhost.dk> Date: Fri, 27 Aug 1993 11:56:00 GMT work@dannug.dk (Michael Hallin) writes, in response to my original note: >I don t know if there is another way to fix this, but I have several >hundred fonts working on a 3.0 system, with the fonts spread evenly >between the three ../Fonts directories. How, you ask? Well, I got a 2.2 >version of buildafmdir, and that works. >Mail me, if you want it. I have been subsequently told this problem has been fixed in release 3.1 of NEXTSTEP. -- David M. Gursky MIME and NEXTMAIL accepted Synex, Inc. e-mail: .. dgursky@nextsrv1.andi.org 5950 Symphony Woods Road voice: ............. (301) 621-5732 Columbia, MD 21044 fax: ............. (301) 621-6005
From: Jacob Gore <jacob@blackbox.enmu.edu> Newsgroups: comp.sys.next.bugs Subject: Re: General disk read/initialize problems with NS/Intel Date: 27 Aug 1993 14:04:35 GMT Organization: Eastern New Mexico University, Department of Mathematical Sciences Distribution: world Message-ID: <25l49jINN2rb@almond.enmu.edu> References: <25hfjj$mbr@news.doit.wisc.edu> Michael Giddings writes > We've been having problems with reading/writing using the floppy drives in > both of our NS/I machines. We've seen it too. We don't use Mac floppies, but had the problem with NeXT and DOS file systems. The problem seems to be related to the floppy itself. 3M floppies exhibit the problem consistently, one Verbatim Bonus floppy we ran into did too. Verbatim DataLife have so far been consistently good. Jacob --- Jacob Gore, ToolCASE Computing Jacob@Gore.Com Member of the League for Programming Freedom (LPF)--lpf@uunet.uu.net
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: cleelacj@agedwards.com (Chris Cleeland) Subject: Re: HELP: Problem with NeXT Header files, (all should read) Message-ID: <CCF8q1.Grt@agedwards.com> Date: Fri, 27 Aug 1993 14:10:48 GMT References: <1993Aug26.040149.6094@news.uta.edu> Organization: A. G. Edwards & Sons, Inc. Followup-To: comp.sys.next.programmer,comp.sys.next.bugs Shane Andrew Holder (sholder@cse.uta.edu) wrote: : OK, : The tools: : NeXT 68040 : NS v3.0 : cc v 1.93 default compiler : gcc 2.4.5 : ingres 8.9 : The task: : I'm trying to compile Ingres on my NeXT. I'm going to try and port : it, big task I know but I'm bored. I know what you mean. I found myself hacking sendmail configuration files the other night. Must be a full moon soon... :-) : The problem: (Those damn header files) : Because of the way Ingres was written I am having to use a : -traditional as one of the flags to cc (someone declared a variable : with the name const). When using -traditional neither gcc nor cc will : evaluate the #include macros that NeXT uses in some of their header : files. ex: : #include ARCH_INCLUDE(bsd/, machparam.h) : in the file /NextDeveloper/Headers/bsd/machine/machparam.h : I wasn't surprised to find out that gcc wouldn't make the translation. : I mean, if your compiling with -traditional you should expect : traditional stuff, but when cc didn't work (I know it's based on gcc) : I was a little peeved. If NeXT is going to do so much untraditional : stuff then they should support it fully. Not to state the obvious, but perhaps sed(1) could be your friend today? If you're really going to port Ingres, then maybe you should change the name of the variable from "const" to something like "ANSItokenThatSignifiesUnchangableValues" :-) Seriously, though, that might be the easiest way to get around it. Perl, if you have it, could do an even better job. Seomthing like the following: % cd <ingres-body-top> % find . -name '*.[ch]' -print | xargs perl -pi.orig -e 's/\wconst\w/aConstant/og' should do the trick, replacing every occurrence of "const" surrounded by word boundaries with the string "aConstant". It will also keep the originals of anything it fixes in <name>.orig, so if you run into problems with the regexp, you can see what the old stuff was. Still, though, you'd think "-traditional" would parse the headers properly... -cj -- ============================================================================== Chris Cleeland | Internet: cleelacj@agedwards.com BOS Dev. Team | USnail: 3878 Connecticut St. Louis 63116 | BellNet: (314) 289-5372
Newsgroups: comp.sys.next.bugs From: friendly@hotspur.psych.yorku.ca (Michael Friendly) Subject: NewsGrazer / Workspace Mgr problems Message-ID: <CCFnFr.Ar7@newshub.ccs.yorku.ca> Sender: news@newshub.ccs.yorku.ca (USENET News System) Organization: York University, Psychology Department Date: Fri, 27 Aug 1993 19:28:39 GMT For the last two days I've been getting Workspace Manager Errors when I logout of my normal acct. This doesn't happen when I'm logged as root. Also, when I run NewsGrazer, it displays the Group and Article list, but as soon as I click on an item, NewsGrazer and all its windows just disaoppear - no longer in the process list. This happens too, but not for all newsgrous, when I'm logged as root. (Using NG 72.3) The only sysadmin stuff I did before this happened was to correct the spelling of my name in my UserManager user record. Can anyone suggest how I might diagnose the problem further ? Please reply direct: friendly@hotspur.psych.yorku.ca -- Michael Friendly Internet: friendly@vm1.yorku.ca Psychology Department NeXTmail: friendly@hotspur.psych.yorku.ca York University 4700 Keele Street
From: giddings@whitewater.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs Subject: Re: General disk read/initialize problems with NS/Intel Date: 27 Aug 1993 20:59:35 GMT Organization: Division of Information Technology Distribution: world Message-ID: <25lsjn$fdb@news.doit.wisc.edu> References: <25l49jINN2rb@almond.enmu.edu> In article <25l49jINN2rb@almond.enmu.edu> Jacob Gore <jacob@blackbox.enmu.edu> writes: > Michael Giddings writes > > We've been having problems with reading/writing using the floppy drives in > > both of our NS/I machines. > > We've seen it too. We don't use Mac floppies, but had the problem with NeXT > and DOS file systems. > > The problem seems to be related to the floppy itself. 3M floppies exhibit > the problem consistently, one Verbatim Bonus floppy we ran into did too. > Verbatim DataLife have so far been consistently good. > > Jacob > --- > Jacob Gore, ToolCASE Computing Jacob@Gore.Com > Member of the League for Programming Freedom (LPF)--lpf@uunet.uu.net Hmm... we've been using verbatim DataLife's, with which most of these problems have occured. Could it be a difference in the batches from which our disks were taken? Anyway, to add information to my earlier post, the problem has occured with the following hardware: Zenith Z-station XEN, built in floppy Toshiba 4400C (portable), built in floppy As mentioned Mac disks are the most problematic, however NeXT-formatted disks have also been problematic at times. Once a problem has occurred with reading a disk, the system generally won't allow it to be re-formatted (initialization failed messages), though other systems (e.g. Macintosh or NeXT hardware) can still format it. I also think it's strange that HFS_XFER can read Mac disks, but the Workspace can't. The Workspace thinks that they are unreadable . . .! -- Michael Giddings | DNA sequencing technologies giddings@whitewater.chem.wisc.edu | Artificial Intelligence giddings@cs.wisc.edu | Sciences NeXT User Group founder |---------\-----------/|\------------/---------|
Newsgroups: comp.sys.next.bugs From: joseph@daffy.tip.ameslab.gov (Joseph Reynolds) Subject: Re: DO MEMORY LEAK Message-ID: <CCFy6w.94q@news.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <9308262048.AA18099@alychne-nc.canon.com> Date: Fri, 27 Aug 1993 23:20:55 GMT Hi. #define DO DistributedObject In article <9308262048.AA18099@alychne-nc.canon.com> ssircar@canon.com (Subrata Sircar) writes: > brad@instep.wimsey.bc.ca (Bradley Head) wrote: [...] > >allocated copy of the data is local in scope and WILL BE > >FREED BY THE SYSTEM WHEN THE SERVER'S METHOD RETURNS. [...] > > I have confirmed the DO leak you posted about for both 3.0 and 3.1 > (on my black hardware, anyway) and forwarded your bug report to NeXT. > The reference number is 49040. [...] It sounds like there is a lot of confusion in people using DOs. I see three categories of DO users: 1. relying on DOs to keep the memory around forever, (as it does now) 2. copying what they need, relying on DOs to free the memory, (as it says in the documentation) 3. copying what they need, freeing the memory themselves, (as they have learned from experience) Maybe NeXT could try to fix this by adding new DO class methods: + tryToPlugLeaks:(BOOL)code; // initially NO + (BOOL) tryingToPlugLeaks; // initially NO DO users would then tell DO how they expect it to treat memory. Category 1 users wouldn't have to do anything and DO will behave as it does now (to maintain important backward compatability). Memory will continue to leak or not as it does now.... Category 2 users could enable the leak-plugger and DO would free the memory as it says in the documentation. This would plug all the leaks. (Unless the programmers forgot to copy some information they wanted to save.) Category 3 users wouldn't have to do anything. (Because they made their programs leak-proof and the system is backward compatable by default). Does anyone see any merits/problems with this approach? Joseph P.S. I'm a category 2 and 3 user, depending on my mood:-)
Newsgroups: comp.sys.next.bugs From: bnh@active.com (Brian Hess) Subject: Re: General disk read/initialize problems with NS/Intel Message-ID: <1993Aug28.021543.12255@nntpxfer.psi.com> Sender: news@nntpxfer.psi.com Organization: Performance Systems Int'l References: <1993Aug26.190028.13465@ToTSySSoft.com> Date: Sat, 28 Aug 1993 02:15:43 GMT Michael Giddings writes >We've been having problems with reading/writing using the floppy drives in >both of our NS/I machines. At the risk of adding spurious information, this sounds familiar -- Remember when DOS 720K floppies were supplanted by IBM's PS/2 1.44Mb format drives? The same thing would happen, usually the result of formatting the floppy on a 720K drive, then writing to it with the 1.44, then expecting to read it on the 720. Or, you could format it on the 1.44 drive (at 720K of course), then if you ever wrote to it with the 720 drive, subsequent writes by the 1.44 would not be readable. The only fix for this was that if you had *ever* written the disk in the higher-density drive, you had to bulk erase the disk before format/write in the low-density drive. This may not be your problem, but it's cheap to find out -- bulk-erase a 1.44HD disk, format and write it on the Intel box, make sure it can be read and written on both Intel boxes interchangeably, then take it and *read only* on the black hardware. If the whole disk reads, you win! Likewise, bulk-erase a 1.44 HD disk, format and write only on black hardware, then take it to an Intel box and see if you can *read* it. If that works too then it's the classic problem. If not, sorry to waste the bandwidth... Brian bnh@active.com (BTW, the PC problem was with DS-DD disks, 720K format on both drives (though the 1.44 drive was doing double-track writing of course) -- not the other problem with DS-HD disks, requiring higher bias than 720K drives could produce. You guys focusing on whether workspace can get files from the disk, what format it believes it is, auto-mounting, etc. may be correct. But if you start with a NeXT Unix file system on the disk and it can't be read, as was one of his problems, then it's more likely to be actual disk read errors. *Could* it just be your cheapo Intel drives? Nah -- *two* of them being out of tolerance is a bit unlikely. Personal opinion: *especially* if the QD 2.88 drive doing the original writing on the black hardware was a PLI external floppy rather than an internal one, and the media is standard HD 1.44, I would expect failure to be read even on another 2.88 drive! My PLI is known for producing junky tolerance 1.44 disks, that even other black hardware cannot read...)
Newsgroups: comp.sys.next.bugs From: mrothste@picard.acs.calpoly.edu (Rothstein) Subject: Re: buildafmdir Message-ID: <1993Aug28.061906.170049@zeus.calpoly.edu> Sender: news@zeus.calpoly.edu Organization: /usr/spool/news/organization References: <dgursky.746042538@news.andi.org> <25j5sn$19s@localhost.dk> <dgursky.746452560@news.andi.org> Date: Sat, 28 Aug 1993 06:19:06 GMT I'm not positive but I think the way to solve the 256 font limit problem is to go into Prefrences.app to the Unix panel and check large file systems. It seems that the default is to do some optimizations that only deal reliably when you are dealing with < 256 files. -Mont -- -Mont NeXTmail OK :-) President CP-NUG (Cal Poly NeXT User Group, SLO)
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: andy@research.canon.oz.au (Andy Newman) Subject: Re: multiple definitions of symbol.... Message-ID: <CCGoHF.9Ht@research.canon.oz.au> Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia References: <1993Aug25.051021.11950@frsvnsvn.cts.com> <1993Aug26.073716.22702@csus.edu> Date: Sat, 28 Aug 1993 08:48:50 GMT eps@cs.sfsu.edu writes: > HOWEVER, software that attempts to provide its own version of malloc() >for the hell of it is probably severely misguided. NeXT's malloc() is >not the traditional BSD malloc(), and if you think you're going to get >better performance with your own version, you're probably wrong. There is one good reason to override malloc(), NeXT's is broken. It doesn't guarantee that the memory is actually there. Do a malloc(1024 * 1024 * 1024 - 1) (you need the minus one to avoid another bug) and see what you get back. Suprised? I didn't think my disk could support that much VM! Now add a loop that touches each page, recompile, save anything you're working on and run it again. Watch your machine grind away. agree that it is often misguided to replace malloc() for performance reasons. -- Andy Newman (andy@research.canon.oz.au)
From: work@dannug.dk (Michael Hallin) Newsgroups: comp.sys.next.bugs Subject: Re: buildafmdir Date: 28 Aug 1993 05:32:26 GMT Organization: Danish NeXT User Group Message-ID: <25mqla$1b9@localhost.dk> References: <dgursky.746452560@news.andi.org> In article <dgursky.746452560@news.andi.org> dgursky@nextsrv1.andi.org (David Gursky) writes: |>work@dannug.dk (Michael Hallin) writes, in response to my original note: |> |>>I don t know if there is another way to fix this, but I have several |>>hundred fonts working on a 3.0 system, with the fonts spread evenly |>>between the three ../Fonts directories. How, you ask? Well, I got a 2.2 |>>version of buildafmdir, and that works. |>>Mail me, if you want it. |> |>I have been subsequently told this problem has been fixed in release |>3.1 of NEXTSTEP. |>-- From what I heard, it was supposed to be fixed, but wasn t. Not too sure about it, though, only hearsay...... Michael --- _____________________________________________ Michael Hallin Copenhagen, Denmark NeXTMail: work@dannug.dk NonNeXTMail: mh.xeroxvang@rxdk.xerox.com Voice: Int + 45 43 53 34 33 Fax: Int + 45 43 53 34 33 _____________________________________________
From: admin@bock.freiburg.sub.org (FreiNet Administrator) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.hardware,comp.sys.next.bugs Subject: how to mount a DOS-OD with NS-3.1 ? Date: 27 Aug 1993 12:32:44 GMT Organization: FreiNet, a VzF* InterNetNews site Message-ID: <25kutc$s9c@bock.freiburg.sub.org> Hi, i want to know if it is possible to mount a external OD which is DOS formatted ! Every time i put the OD into the drive (it's a sony :) the NeXT give me the choice to format the disk as an unix or mac disk. But he doesn't recognize that this disk is already formatted as a DOS disk :-( The NeXT is a "black" machine running NS 3.1. If anyone has managed this with success, please give me a hint !!! - Flo
Newsgroups: comp.sys.next.bugs From: netcom.com!kira!davidjohn (David John Burrowes) Subject: Re: Someone with 3.1 black and PLI superfloppy: please check this: Message-ID: <1993Aug28.202457.248@kira.net.netcom.com> Sender: davidjohn@kira.net.netcom.com Organization: No organization at this time. References: <1993Aug23.164358.1352@rna.indiv.nluug.nl> Date: Sat, 28 Aug 1993 20:24:57 GMT In article <1993Aug23.164358.1352@rna.indiv.nluug.nl> gerben@rna.indiv.nluug.nl writes: > Try formatting a 1.4MB disk in the PLI Superfloppy with a NeXT filesystem. > it work? > > I have problems here. Look what happens when I try to format a DOS disk > as NeXT disk: > ... > ***Format Complete*** > writing disk label > boot block extends beyond front porch > > What is going on here? I was just going to post this exact same question today! I'm seeing this, also on my NeXTcube running 3.1. It happens with all 1.44 and 2.88meg floppy disks that I've tried. Mac and DOS file systems format fine, NeXT ones extend beyond the front porch. (what does this `front porch' even mean?) \david john burrowes p.s. A month or so ago I learned that switching back to the 3.0 cd rom driver (from the 3.1 one) removed problems I was having the Big Green CD. Is there perhaps something wrong with the 3.1 floppy driver? Anyone know what 3.0 files would be needed if this would fix the problem?
From: pkron@corona.com (Peter Kron) Newsgroups: comp.sys.next.bugs Subject: New Serial Driver...PLEASE Message-ID: <118.UUL1.3#16216@corona.com> Date: Sun, 29 Aug 93 04:19:11 PDT Organization: Corona Design, Inc., Seattle, WA The new serial driver was rumored to be released at the end of July...it's now the end of August. Various folks on the net have alluded to it as being tested and problems solved. I don't much care if its perfect yet or not--it's got to be better than the 3.1 release. My machine crashes from 5 to 10 times a day trying to normal UUCP and remote login work. NeXT!! Please release something--ANYTHING--that doesn't crash! "FSCK" and tired. --------------- Peter Kron Please don't dominate the rap, Jack, Corona Design, Inc. If you've got nothing new to say... Peter_Kron@corona.com Grateful Dead
From: rcfa@andi.org (Ronald C.F. Antony) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: HELP: Problem with NeXT Header files, (all should read) Date: 29 Aug 1993 22:57:31 GMT Organization: IDS World Network Internet Access Service, (401) 884-9002 GUEST Distribution: world Message-ID: <25rc8r$25m@paperboy.ids.net> References: <CCF8q1.Grt@agedwards.com> Keywords: adding a local header file might fix the problem Many problems I had with the architecture macros could be solved by putting the following text into /LocalDeveloper/Headers/architecture/ARCH_INCLUDE.h -----8<------- cut here ------8<----- /* * ARCH_INCLUDE.h -- helper macro for including architecture specific * header files. * * Usage: * #import ARCH_INCLUDE(prefix_dir/, suffix.h) * Where: * ARCH_INCLUDE(prefix_dir/, suffix.h) * produces (for m68k architecture): * "prefix_dir/m68k/suffix.h" * * NOTE: prefix_dir, if non-null, must end with a '/' * * Current deficiency: can't specify <...>, only "...". * * __TARGET_ARCHITECTURE__ may be defined to specify a different * different architecture that the compiler is generating code for. * Define __TARGET_ARCHITECTURE__ as a string, e.g.: # #define __TARGET_ARCHITECTURE__ "m68k" */ #ifndef _ARCH_INCLUDE_H_ #define _ARCH_INCLUDE_H_ #ifndef __TARGET_ARCHITECTURE__ #define __TARGET_ARCHITECTURE__ __ARCHITECTURE__ #endif __TARGET_ARCHITECTURE__ #ifdef __STDC__ #define ARCH_INCLUDE(prefix, suffix) \ #prefix __TARGET_ARCHITECTURE__ "/" #suffix #else #define ARCH_INCLUDE(prefix, suffix) \ "prefix" __TARGET_ARCHITECTURE__ "/" "suffix" #endif #endif _ARCH_INCLUDE_H_ -----8<----- snipp snipp -----8<----- Since the local include file precede the standart include files in the include path, this file fixes and replaces the corresponding NeXT supplied file. I also sent this to NeXT as a bug report, so maybe it shows up sometime in the future... -- Ronald ============================================================================== "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." G.B. Shaw ------------------------------------------------------------------------------ HITECTURE__ "/" #suffix #else #d
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.bugs Subject: Installation of NS-3.1 includes about 30meg of useless files Date: 30 Aug 1993 02:33:18 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <25rote$g6v@usenet.rpi.edu> I finally got around to doing some of my "Snapshot_HD" tests on the NS-3.1 release for NeXT hardware. As others have noted, the installation of NS-3.1 takes up about 40meg more disk space than NS-3.0 did. A large chunk of that is due to the same installation oversight that NeXT had in NS-3.0, only it's even more noticable in NS-3.1. The first place to look is in /NextLibrary/Receipts. Do you notice any pkg-file receipts in there for languages that you did not install? Something about the installation process leaves around receipts for all the languages, including the ones that you haven't installed. To make matters worse, if you *don't* install the language then the pkg receipt includes the tar.Z file that could be used to install it. Due to this, the German.pkg receipt takes up over 8 meg of disk space. The French.pkg file takes up another 8 meg. Most of the other language files only take up about 1.5 meg each. Note that this tar file does you absolutely no good, since the installer won't let you install from these pkg files. To remidy this: logon as root, and click on each pkg file in /NextLibrary/Receipts that you do *not* want to have installed. When the Installer.app starts up, click on the button to delete the package. If you *do* want to have the package installed, then install it from pkg files on the CD-ROM disc and it will put in a new receipt which will be much smaller. Another file that might be wasting disk space on you is in /NextLibrary/References/Webster-Dictonary/CompactDictionary. This file is over 14 meg. If you have installed the Literature package, then you will see a file called Dictionary in the very same directory. *If* you have that Dictionary file, then the CompactDictionary file is not needed for anything (not that I can tell at least). You can destroy it. Note that if you don't have a Dictionary file in that directory, then Websters is using this CompactDictionary (which has less info) so you wouldn't want to delete it. For those that are curious about all these "snapshots", an assortment of these snapshots (as well as the script that I use to generate the snapshots) are available via anonymous FTP in the directory /NeXT/ls_output off the host eclipse.its.rpi.edu. The snapshots are just a bunch of "du -s" and "find -ls" commands done from root, so you get a picture of what files are where, and how much disk space is being taken up by various things. Each snapshot is a directory of files. I'm pretty sure I reported this to NeXT for release 3.0, but I haven't reported that the oversight is still there in release 3.1. It's more noticable in NS-3.1, as the German and French packages have grown by about 6 meg each. -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: cedman@princeton.edu (Carl Edman) Subject: Re: Installation of NS-3.1 includes about 30meg of useless files In-Reply-To: gad@eclipse.its.rpi.edu's message of 30 Aug 93 02:33:18 GMT To: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Message-ID: <CEDMAN.93Aug30094252@capitalist.princeton.edu> Originator: news@nimaster Sender: news@Princeton.EDU (USENET News System) Organization: Princeton University References: <25rote$g6v@usenet.rpi.edu> Date: Mon, 30 Aug 1993 13:42:51 GMT In article <25rote$g6v@usenet.rpi.edu> gad@eclipse.its.rpi.edu (Garance A. Drosehn) writes: [NS 3.1 installation wastes a lot of diskspace] To find such things automatically, I've run this perl script every night for a year or two. Maybe somebody else finds it useful too. It certainly has helped me find a lot of wasted space in places where I would never have looked without it. You should run this script as root every night (from cron or /usr/adm/daily) and mail yourself the results. Notice that you also need to have a /usr/local/lib directory and GNU du as /usr/local/bin/gdu. Carl Edman PS: Forgive the inappropriate name -- this is not really a daemon. It was just all I could think of on the spur of the moment. #!/usr/local/bin/perl # -*- Perl -*-
# # File: du-daemon # RCS: $Header: $ # Description: A program to keep track of disk usage over time # Author: Carl Edman # Created: Wed Jan 1 09:33:38 1992 # Modified: Tue Aug 24 09:55:19 1993 (Carl Edman) cedman@capitalist.princeton.edu # Language: Perl # Package: N/A # Status: Experimental (Do Not Distribute) # # (C) Copyright 1992, but otherwise this file is perfect freeware. # ############################################################################### require "getopts.pl"; do Getopts('d:m'); # -d file: filename for data files. Default: -d /usr/local/lib/du.data # -m : Specifiy minimum change to display. Default: 100 blocks if (!$opt_m) { $opt_m=100; } if (!$opt_d) { $opt_d="/usr/local/lib/du.data"; } open(OLD,"<$opt_d"); $otim=(stat(OLD))[9]; @o=<OLD>; close OLD; open(NEW,"/usr/local/bin/gdu --one-file-system $opt_a /|sort +1|"); #open(NEW,"</usr/local/lib/du.new"); @n=<NEW>; close(NEW); open(OLD,">$opt_d"); print OLD @n; $ntim=(stat(OLD))[9];; close(OLD); $ntot=shift(@n); $otot=shift(@o); @name=(); @olen=(); @nlen=(); while($#o!=-1 || $#n!=-1) { if ($o[0] eq $n[0]) { shift @o; shift @n; next; } $c=index($o[0],"\t"); $ol=substr($o[0],0,$c); $on=substr($o[0],$c+1,length($o[0])-$c-2); $c=index($n[0],"\t"); $nl=substr($n[0],0,$c); $nn=substr($n[0],$c+1,length($n[0])-$c-2); if ($on eq $nn) { push(@name,$on); push(@olen,$ol); push(@nlen,$nl); shift @o; shift @n; next; } if ($on lt $nn) { push(@name,$on); push(@olen,$ol); push(@nlen,0); shift @o; next; } if ($on gt $nn) { push(@name,$nn); push(@olen,0); push(@nlen,$nl); shift @n; next; } } while($#o!=-1) { $c=index($o[0],"\t"); push(@name,substr($o[0],$c+1,length($o[0])-$c-2)); push(@olen,substr($o[0],0,$c)); push(@nlen,0); shift @o; } while($#n!=-1) { $c=index($n[0],"\t"); push(@name,substr($n[0],$c+1,length($n[0])-$c-2)); push(@olen,0); push(@nlen,substr($n[0],0,$c)); shift @n; } for($i=0;$i<=$#name;$i++) { $nam=$name[$i] . "/"; $len=length($nam); for($j=$i+1;$j<=$#name&&((substr($name[$j],0,$len)) eq $nam);$j++) { if (index($name[$j],"/",$len)==-1) { $olen[$i] -= $olen[$j]; $nlen[$i] -= $nlen[$j]; } } } @grow=(); @shrink=(); @create=(); @delete=(); for($i=0;$i<=$#name;$i++) { if ($olen[$i]==0) { push(@create,sprintf("%6d %s",$nlen[$i],$name[$i])); } elsif ($nlen[$i]==0) { push(@delete,sprintf("%6d %s",$olen[$i],$name[$i])); } elsif ($olen[$i]<$nlen[$i]) { push(@grow,sprintf("%6d %s",$nlen[$i]-$olen[$i],$name[$i])); } elsif ($olen[$i]>$nlen[$i]) { push(@shrink,sprintf("%6d %s",$olen[$i]-$nlen[$i],$name[$i])); } } ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime($otim); printf("Between %d-%d-%d %d:%02d:%02d and ",$mon+1,$mday,$year,$hour,$min,$sec); ($sec,$min,$hour,$mday,$mon,$year,$wday,$yday,$isdst) = localtime($ntim); printf("%d-%d-%d %d:%02d:%02d:\n",$mon+1,$mday,$year,$hour,$min,$sec); if ($otot<$ntot) { printf("Disk usage grew by %d blocks from %d to %d blocks.\n",$ntot-$otot,$otot,$ntot); } elsif ($otot>$ntot) { printf("Disk usage shrunk by %d blocks from %d to %d blocks.\n",$otot-$ntot,$otot,$ntot); } else { printf("Disk usage remained constant at %d blocks.\n",$otot); } printf("%d directories changed.\n",$#create+$#delete+$#shrink+$#grow+4); if ($#create!=-1) { printf("\nCreation [%d directories]:\n",$#create+1); @create = sort {$b <=> $a;} @create; for($i=0;$i<=$#create && $create[$i]>=$opt_m;$i++) { print $create[$i] . "\n"; } } if ($#grow!=-1) { printf("\nGrowth [%d directories]:\n",$#grow+1); @grow = sort {$b <=> $a;} @grow; for($i=0;$i<=$#grow && $grow[$i]>=$opt_m;$i++) { print $grow[$i] . "\n"; } } if ($#delete!=-1) { printf("\nDeletion [%d directories]:\n",$#delete+1); @delete = sort {$b <=> $a;} @delete; for($i=0;$i<=$#delete && $delete[$i]>=$opt_m;$i++) { print $delete[$i] . "\n"; } } if ($#shrink!=-1) { printf("\nShrinkage [%d directories]:\n",$#shrink+1); @shrink = sort {$b <=> $a;} @shrink; for($i=0;$i<=$#shrink && $shrink[$i]>=$opt_m;$i++) { print $shrink[$i] . "\n"; } }
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Doc drag from NewsGrazer to folder kills WM Message-ID: <1993Aug30.113945.1400@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Mon, 30 Aug 1993 11:39:45 GMT On my most recent login, I was merely dragging a newsposting from the NewsGrazer document icon display to a folder in Workspace.app and (yet again) got a forced logout, evidently from some drag protocol error... Log-AUTH... Only the logout in response to the alert panel. Log-USER Aug 30 05:01:24 tssslab WM[232]: tossing badly formed message mach_init (to /usr/adm/messages...) Aug 30 05:01:26 tssslab mach_init[2]: Received destroyed notification for service Miniapp_boot_port on bootstrap port 111808 Aug 30 05:01:26 tssslab mach_init[2]: Service Miniapp_boot_port failed - deallocate Aug 30 05:04:46 tssslab mach_init[2]: Received destroyed notification for service FetchPort_bruce_032e5520 on bootstrap port 112800 Aug 30 05:04:46 tssslab mach_init[2]: Service FetchPort_bruce_032e5520 failed - deallocate Aug 30 05:05:49 tssslab mach_init[2]: Received destroyed notification for service DeviceInsertionNotifyPort on bootstrap port 111808 Aug 30 05:05:49 tssslab mach_init[2]: Service DeviceInsertionNotifyPort failed - deallocate Yet disks were not inserted until a minute later...! Anyone else with ODD Workspace kill-offs? in apparent response to successful drag operations? Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred, MIME-Mail ok
From: pierce@cantrell.tamu.edu (Pierce Cantrell) Newsgroups: comp.sys.next.bugs Subject: More resolv.conf problems 3.1 Date: 30 Aug 1993 15:42:42 GMT Organization: Texas A&M University, College Station, TX Distribution: world Message-ID: <25t75i$fbs@TAMUTS.TAMU.EDU> There still seems to be a problem in NEXTSTEP 3.1 (Black) with switching to the backup nameservers listed in resolv.conf when disconnected from the primary nameserver. I thought this problem was fixed, but there seems to be a least one case where the problem still exits. I submitted a bug report to NeXT. During a network reconfiguration, my subnet became disconnected from the backbone. I am running routed. The default gateway (brouter box) is also down, and does not appear in the routing table. The default nameserver in resolv.conf is in another subnet to which there is no route. Both of the secondary nameservers in resolv.conf are in my subnet, however. Under the conditions described above, telnet reports "Hostname lookup failure" in telneting to either a hostname or to a fully qualified domain name with a trailing period. In contrast, nslookup reports "*** Can't find server name for address 128.194.15.2: No response from server" and then immediately switches to the second nameserver in resolv.conf. This latter behavior verifies the syntax of the nameserver lines in the resolv.conf file. The failure of hostname lookup under these circumstances is not normal. If nslookup switches to the backup nameserver, so should the resolver. If I add back in the default route using a "route add default ..." command (the default router is still down and is not responding to a ping), hostname lookup starts to work again. Hard to see why this works since a packet is not actually sent in this case either because arp is unable to resolve the ethernet address because the brouter is down. -- Pierce E. Cantrell | cantrell@ee.tamu.edu Department of Electrical Engineering | Texas A&M University | tel: (409) 845-7441 College Station, Texas 77843-3128 | fax: (409) 845-6259
Newsgroups: comp.sys.next.bugs From: hugo@IRO.UMontreal.CA (Hugo Desrosiers) Subject: NFS ghost files when unlink'ing: is it NS 3.1 bug ? Message-ID: <1993Aug30.165939.2580@IRO.UMontreal.CA> Keywords: NFS, bugs, 3.1 Sender: news@IRO.UMontreal.CA Organization: Universite de Montreal Date: Mon, 30 Aug 1993 16:59:39 GMT I've got a clone PC running NS 3.1 linked on a MIPS 120 file system by a standard NFS link. In a application being developped, a directory of files must be deleted. So I dired the directory, then go through all the files in it and unlink() them. After that, I rmdir() the directory. Sometimes the rmdir() works, sometimes it doesn't. After a while, I noticed that some ghost files named ".nfs"<numeric id> where created in that directory, and they seem to be some kind of backup of the original files that were unlink'ed; rmdir() sees these files and refuses to delete the directory. Now are those files created by the NFS system of NS or by the MIPS one ? And how can they be dealed with ?? If anyone has an awnser, please reply through email... Thanks, Hugo DesRosiers.
From: giddings@sadie.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware Subject: A new twist to read/initialize problems with NS/I Date: 30 Aug 1993 19:26:59 GMT Organization: Division of Information Technology Distribution: world Message-ID: <25tka3$qlv@news.doit.wisc.edu> The latest in the problems I've been having with the floppy drive on an NS/Intel system: I formatted a Verbatim DataLife on PLI Cube Floppy to 1.44. It produced some read/write errors on the toshiba (4400c) NS/I disk drive when trying to copy to/from it. I initialized it on the Toshiba with NS/I, and initialization failed, giving the message: read I/O error block 2862 block_count 18 I booted up the same machine (Toshiba 4400C) in DOS and used the format command on the same floppy, with verify on. It formatted fine. So, I booted NS/Intel again and tried to format the same floppy, and initialization failed again. In summary, both DOS, and separate black harware running NS could format this floppy, but NS/I could not. This is seeming more and more like a software problem with NS/I. This leads me to believe it may be a timeout problem as someone mentioned priorly. Does anyone have any other ideas what may be causing this? Thanks Michael Giddings
Newsgroups: comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: Re: DO MEMORY LEAK Message-ID: <1993Aug30.185800.14553@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. References: <CCFy6w.94q@news.iastate.edu> Date: Mon, 30 Aug 1993 18:58:00 GMT In article <CCFy6w.94q@news.iastate.edu> joseph@daffy.tip.ameslab.gov (Joseph Reynolds) writes: > Hi. > > #define DO DistributedObject > > In article <9308262048.AA18099@alychne-nc.canon.com> ssircar@canon.com > (Subrata Sircar) writes: > > brad@instep.wimsey.bc.ca (Bradley Head) wrote: [...] > > >allocated copy of the data is local in scope and WILL BE > > >FREED BY THE SYSTEM WHEN THE SERVER'S METHOD RETURNS. [...] > > > > I have confirmed the DO leak you posted about for both 3.0 and 3.1 > > (on my black hardware, anyway) and forwarded your bug report to NeXT. > > The reference number is 49040. [...] > > It sounds like there is a lot of confusion in people using DOs. I see > three categories of DO users: > 1. relying on DOs to keep the memory around forever, > (as it does now) > 2. copying what they need, relying on DOs to free the memory, > (as it says in the documentation) > 3. copying what they need, freeing the memory themselves, > (as they have learned from experience) > > Maybe NeXT could try to fix this by adding new DO class methods: > + tryToPlugLeaks:(BOOL)code; // initially NO > + (BOOL) tryingToPlugLeaks; // initially NO > > DO users would then tell DO how they expect it to treat memory. > > Category 1 users wouldn't have to do anything and DO will behave as it > does now (to maintain important backward compatability). Memory will > continue to leak or not as it does now.... > > Category 2 users could enable the leak-plugger and DO would free the > memory as it says in the documentation. This would plug all the leaks. > (Unless the programmers forgot to copy some information they wanted to > save.) > > Category 3 users wouldn't have to do anything. (Because they made their > programs leak-proof and the system is backward compatable by default). > > Does anyone see any merits/problems with this approach? > > Joseph > > P.S. I'm a category 2 and 3 user, depending on my mood:-) You seem to be missing a VERY IMPORTANT feature which was intended to make DO a powerful concept! If I create an object that implements the following method (and protocol): - printString:(const char *)aStr; If this message is received normally (i.e. not through DO) then the argument aStr, passed as a constant, is not yours to modify (which includes freeing). You therefore should NOT attempt to free it. And when the call returns you should NOT rely on it to remain allocated (this is only guaranteed for the duration of the call) since YOU (the receiver) don't own it! Distributed Objects would like to mimic this way of passing const pointers since we should NOT care if this method is called remotely or locally. But, NeXT blew it and failed to implement the transparency that they (correctly) documented. The result is that, as a programmer, you must become aware that this method will be called remotely so that you can call free((char *)aStr) to clean up the memory leak. If you leave your call to free() in and call this method locally, you'll try to free memory on that you do not should not modify (including freeing), and then if the caller is relying on the string still being around, you'll have caused some very unwanted results. Imagine trying to make code like this work without implementing DO like NeXT intended: - someMethod; { char myString[100]; strcpy(myString, "Hello"); [someObject_possiblyAProxy printString:myString]; fprintf(stderr, "I asked to print '%s'\n", myString); return self; } /* some object that may or may not be a remote object */ @implementation PossibleRemoteObject - printString:(const char *)str; { fprintf(stderr, "%s\n", str); free((char *)str); // This fixes the memory leak when this is // Called remotely, but imagine the effect if // it was NOT called remotely? return self; } @end -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
Newsgroups: comp.sys.next.bugs From: ddj+@cs.cmu.edu (Doug DeJulio) Subject: ProAudioSpectrum problems. Message-ID: <CCL4vv.AnJ.2@cs.cmu.edu> Sender: news@cs.cmu.edu (Usenet News System) Organization: School of Computer Science, Carnegie Mellon Date: Mon, 30 Aug 1993 18:33:30 GMT I've got: 486DX2-66, 8M RAM (I know, I need more) Trident SVGA card Adaptec AHA-1542C SCSI card w/ gig drive & Texel CD-ROM SMC-Elite ethernet card Logitech bus mouse Pro Audio Spectrum 16 sound card 2 serial & 1 parallel card Whenever I tell NS to configure the soundcard with a configuration that works perfectly under DOS, the system panics every time it tries to boot up. When I tell NS to configure the soundcard with a configuation that should NOT work, the system boots up find, but the sound card indeed does not work (the infinite-audio-repeat symptom occurs). Any ideas? Anyone with similar hardware have something that works? -- Doug DeJulio ddj+@cmu.edu
Newsgroups: comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: BUG: netmsgserver doesn't care about case of ASCII characters Message-ID: <1993Aug30.211136.387@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. Date: Mon, 30 Aug 1993 21:11:36 GMT According to "Programming under Mach", by Boykin, et al, pp.72-73 : "A program wishing to pass send rights registers an ASCII name and the port with the netmsgserver (network message server)." Another program may obtain the send right to that port by querying the name server using the same ASCII name." The network name that is registered with the name server is of the netname_name_t. This is defined in servers/netname_defs.h as: typedef char netname_name_t[80]; So you can have 80 ASCII characters, including the null terminator, to register as. The bug I've noticed under NEXSTEP 3.0 is that the ASCII characters that have a toupper() complement are treated equally (i.e. 'a' and 'A' are equivalent). In other words, the netmsgserver doesn't care about the case of the characters when it checks the netname_name_t for pre-registered tasks. NOWHERE under NeXT's documentation or Mach's could I can find this SEVERE LIMITATION documented! Is this a known bug? Is it fixed under 3.1? I've sent it to bug_next. Here's a simple test program: /* * NetNameTest_main.m * * The test program tests and demonstrates a bug with * the Network Name Server (netmsgserver) * in which it doesn't care about the case of characters in a name to * register a port as or to look up. This case insensitivity is NOT * DOCUMENTED * * * To see for yourself, compile this test: * * cc -Wall -g NetNameTest_main.m -lNeXT_s -o NetNameTest * * * */ #import <objc/objc.h> #import <objc/Object.h> #import <appkit/Listener.h> #import <remote/NXProxy.h> #import <remote/NXConnection.h> #import <mach/mach.h> #import <stdlib.h> #import <libc.h> #import <stdio.h> #import <strings.h> #import <mach/mach_error.h> #import <mach/mig_errors.h> #import <servers/netname.h> #define RO_NAME1 "example_Port_name" #define RO_NAME2 "EXAMpLE_port_NAME" @protocol ServerProtocol - iConnectedToYouByName:(const char *)aName; @end @interface MyServer:Object { } - iConnectedToYouByName:(const char *)aName; @end @implementation MyServer - iConnectedToYouByName:(const char *)aName; { fprintf(stderr, "I'm the server registered as '%s'.\n", RO_NAME1); fprintf(stderr, "A client connected to me thru the NetNameServer using" " '%s'\nThis shouldn't work!\n\n", RO_NAME2); return self; } @end void main(int argc, char **argv) { MyServer *server = [[MyServer alloc] init]; id roserver, myServer; port_t port; kern_return_t ret; myServer = [NXConnection registerRoot:server withName:RO_NAME1]; [myServer runInNewThread]; roserver = [NXConnection connectToName:RO_NAME2]; // Let's attempt to connect to the server using a mixed // case name, that, if the case is ignored will succeed... if (roserver) { [roserver setProtocolForProxy:@protocol(ServerProtocol)]; [roserver iConnectedToYouByName:RO_NAME2]; } // Now let's try the NeXT function call... if (NXPortNameLookup(RO_NAME2, "") == PORT_NULL) fprintf(stderr, "NXPortNameLookup() failed to find '%s'\n", RO_NAME2); else fprintf(stderr, "NXPortNameLookup() of '%s' succeeded.\n", RO_NAME2); // Now let's try the mach way... ret = netname_look_up(name_server_port, "", RO_NAME2, &port); if (ret != KERN_SUCCESS) { /* Print the network name server's error message. */ mach_error("Lookup of server failed", ret); } else fprintf(stderr, "netname_look_up of '%s' succeeded.\n", RO_NAME2); exit(0); } Brad -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
Newsgroups: comp.sys.next.bugs From: joseph@daffy.tip.ameslab.gov (Joseph Reynolds) Subject: Re: DO Memory Leak Message-ID: <CCLIDF.I2w@news.iastate.edu> Keywords: distributed objects, memory leak Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <1993Aug30.185800.14553@instep.wimsey.bc.ca> Date: Mon, 30 Aug 1993 23:24:51 GMT In article <1993Aug30.185800.14553@instep.wimsey.bc.ca> brad@instep.wimsey.bc.ca writes: > In article <CCFy6w.94q@news.iastate.edu> joseph@daffy.tip.ameslab.gov > > [...] > > It sounds like there is a lot of confusion in people using DOs. I see > > three categories of DO users: [...] > > You seem to be missing a VERY IMPORTANT feature which was intended to > make DO a powerful concept! [...] I think it is too late to to get this feature [remote/local transparency] automatically. (See my reason below.) I think programmers should have to explicitly request it. > But, NeXT blew it and failed to implement the transparency that they > (correctly) documented. [...] Imagine trying to > make code like this work without implementing DO like NeXT intended: > [...] > Bradley Head Exactly. I'm not suggesting a fix or a workaround for DO programmers. (I guess my previous post should have been directed more to NeXT more than to the DO users.) Clearly NeXT should implement DO the way it is documented. But there is a problem with that: the code people now have to work around the memory leak will break; it would free the memory twice. So NeXT just fixing it would be a very bad thing. My suggested solution is to wait until the programmer explicitly tells DO that it should "conform to the documentation." This will avoid breaking old code if/when it is recompiled. And will let freshly written programs (or explicitly revamped ones) take advantage of the leak-free DO system. I don't see any other way to fix this mess (other than starting over and making something exactly like DO). Joseph
Newsgroups: comp.sys.next.bugs From: lloyd@world.std.com (Chris Lloyd) Subject: Re: BUG: netmsgserver doesn't care about case of ASCII characters Message-ID: <CCLnJD.416@world.std.com> Organization: The World Public Access UNIX, Brookline, MA References: <1993Aug30.211136.387@instep.wimsey.bc.ca> Date: Tue, 31 Aug 1993 01:16:24 GMT In article <1993Aug30.211136.387@instep.wimsey.bc.ca> brad@instep.wimsey.bc.ca writes: >The bug I've noticed under NEXSTEP 3.0 is that the ASCII characters >that have a toupper() complement are treated equally (i.e. 'a' and 'A' are >equivalent). In other words, the netmsgserver doesn't care about the case >of the characters when it checks the netname_name_t for pre-registered >tasks. > >NOWHERE under NeXT's documentation or Mach's could I can find this SEVERE >LIMITATION documented! > >Is this a known bug? Is it fixed under 3.1? I've sent it to bug_next. 2.1 & 3.1 are the same - I would imagine the real fix/bug to be in the documentation and not in the behaviour, for changing the behaviour may break a lot of existing stuff which in/advertantly relies on it. I wouldn't consider this a "SEVERE LIMITATION" - the namespace is still astronomically huge and there are lots of ways to permute a set of case sensitive names to fit into this behaviour. Undocumented, such is life, -- :: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: :: NEXTSTEP Monk ::
Newsgroups: comp.sys.next.bugs From: Neil Greene <neil@bMD.com> Subject: Re: New Serial Driver...PLEASE Message-ID: <1993Aug31.005418.5485@bmd.com> Sender: neil@bmd.com Organization: benchMark Developments, Inc. References: <118.UUL1.3#16216@corona.com> Date: Tue, 31 Aug 1993 00:54:18 GMT In article <118.UUL1.3#16216@corona.com> pkron@corona.com (Peter Kron) writes: > The new serial driver was rumored to be released at the end of July...it's > now the end of August. Various folks on the net have alluded to it as > being tested and problems solved. > > I don't much care if its perfect yet or not--it's got to be better than > the 3.1 release. My machine crashes from 5 to 10 times a day trying to > normal UUCP and remote login work. > > NeXT!! Please release something--ANYTHING--that doesn't crash! > > "FSCK" and tired. > --------------- > Peter Kron Please don't dominate the rap, Jack, > Corona Design, Inc. If you've got nothing new to say... > Peter_Kron@corona.com Grateful Dead > And please fix that damn new_posix_proc error, or whatever it is. Of course it causes our NetInfo server to crash the second you turn your back. What does this mean? It means new mail and no news and Oracle crashes. This pisses me off to no end. I would be happy if NeXT would even tell me what the status is regarding this error. Instead, some temporary mail clerk replies to my bug_report telling me that things are not that bad and upgrades work just as good as full installs. I can tell you that is not true!
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Re: BUG: netmsgserver doesn't care about case of ASCII characters Message-ID: <1993Aug31.114158.9090@csus.edu> Sender: news@csus.edu Organization: San Francisco State University References: <1993Aug30.211136.387@instep.wimsey.bc.ca> <CCLnJD.416@world.std.com> Date: Tue, 31 Aug 1993 11:41:58 GMT "It's not a bug, it's a feature." (Is this really undocumented? I've always known about it.) It's beyond a case-insensitive comparison--nmserver uppercases everything. -=EPS=-
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: Re: buildafmdir Message-ID: <1993Aug31.170951.303@altsys.com> Organization: Altsys Corporation, Richardson, TX References: <25j5sn$19s@localhost.dk> <dgursky.746452560@news.andi.org> <1993Aug28.061906.170049@zeus.calpoly.edu> Date: Tue, 31 Aug 1993 17:09:51 GMT In article <1993Aug28.061906.170049@zeus.calpoly.edu> mrothste@picard.acs.calpoly.edu (Rothstein) writes: >I'm not positive but I think the way to solve the 256 font limit problem is >to go into Prefrences.app to the Unix panel and check large file systems. It >seems that the default is to do some optimizations that only deal reliably >when you are dealing with < 256 files. > >-Mont > >-- >-Mont > > NeXTmail OK :-) > President CP-NUG (Cal Poly NeXT User Group, SLO) It's fixed in 3.1 and large file system has nothing to do with it. The buildafmdir from 2.1 or 3.1 will work fine. Drop me line if you need one. I'll NeXT mail it to you. -- Lorin Rivers Lorin_Rivers@altsys.com NEXTSTEP Sales Manager 214.680.2518 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
From: dennis.glatting@mccaw.com Newsgroups: comp.sys.next.bugs Subject: Re: More resolv.conf problems 3.1 Date: 31 Aug 1993 15:19:41 GMT Organization: McCaw Cellular Communications, Inc. Distribution: world Message-ID: <25vq6d$q9l@ftp-p.mccaw.com> References: <25t75i$fbs@TAMUTS.TAMU.EDU> In article <25t75i$fbs@TAMUTS.TAMU.EDU> pierce@cantrell.tamu.edu (Pierce Cantrell) writes: > There still seems to be a problem in NEXTSTEP 3.1 (Black) > with switching to the backup nameservers listed in > resolv.conf when disconnected from the primary > nameserver. I thought this problem was fixed, but there > seems to be a least one case where the problem still exits. > I submitted a bug report to NeXT. The NeXT version of BIND is 4.8.1. I have requested (twice) that they upgrade at least to 4.8.3 -- if not 4.9. The resolver libraries in 4.9 are effective in reducing network traffic and improving resolution efficiency -- they ignore servers in the name list who cannot be contacted. Trivia aside, the NeXT resolver works fine albeit they try the name servers in order. The resolver will go to the secondary. > During a network reconfiguration, my subnet became > disconnected from the backbone. I am running routed. The > default gateway (brouter box) is also down, and does not > appear in the routing table. The default nameserver in > resolv.conf is in another subnet to which there is no > route. Both of the secondary nameservers in resolv.conf > are in my subnet, however. ROUTED is nice because you don't have to tune /etc/hostconfig when a machine is moved to another subnet. I prefer specifying a default route however. Specifying a default route releases the host from relying on someone else to publish route information -- it lets the router route. Specifying a default route releases the host from running another process to collect the route information too. [ other stuff deleted ] -- Dennis P. Glatting / Technical Director / Paradigm Systems Corp. of WA
From: dennis.glatting@mccaw.com Newsgroups: comp.sys.next.bugs Subject: Re: More resolv.conf problems 3.1 Date: 31 Aug 1993 15:20:05 GMT Organization: McCaw Cellular Communications, Inc. Distribution: world Message-ID: <25vq75$q9m@ftp-p.mccaw.com> References: <25t75i$fbs@TAMUTS.TAMU.EDU> In article <25t75i$fbs@TAMUTS.TAMU.EDU> pierce@cantrell.tamu.edu (Pierce Cantrell) writes: > There still seems to be a problem in NEXTSTEP 3.1 (Black) > with switching to the backup nameservers listed in > resolv.conf when disconnected from the primary > nameserver. I thought this problem was fixed, but there > seems to be a least one case where the problem still exits. > I submitted a bug report to NeXT. The NeXT version of BIND is 4.8.1. I have requested (twice) that they upgrade at least to 4.8.3 -- if not 4.9. The resolver libraries in 4.9 are effective in reducing network traffic and improving resolution efficiency -- they ignore servers in the name list who cannot be contacted. Trivia aside, the NeXT resolver works fine albeit they try the name servers in order. The resolver will go to the secondary. > During a network reconfiguration, my subnet became > disconnected from the backbone. I am running routed. The > default gateway (brouter box) is also down, and does not > appear in the routing table. The default nameserver in > resolv.conf is in another subnet to which there is no > route. Both of the secondary nameservers in resolv.conf > are in my subnet, however. ROUTED is nice because you don't have to tune /etc/hostconfig when a machine is moved to another subnet. I prefer specifying a default route however. Specifying a default route releases the host from relying on someone else to publish route information -- it lets the router route. Specifying a default route releases the host from running another process to collect the route information too. [ other stuff deleted ] -- Dennis P. Glatting / Technical Director / Paradigm Systems Corp. of WA
From: dennis.glatting@mccaw.com Newsgroups: comp.sys.next.bugs Subject: Re: More resolv.conf problems 3.1 Date: 31 Aug 1993 15:20:19 GMT Organization: McCaw Cellular Communications, Inc. Distribution: world Message-ID: <25vq7j$q9n@ftp-p.mccaw.com> References: <25t75i$fbs@TAMUTS.TAMU.EDU> Keywords: keywords In article <25t75i$fbs@TAMUTS.TAMU.EDU> pierce@cantrell.tamu.edu (Pierce Cantrell) writes: > There still seems to be a problem in NEXTSTEP 3.1 (Black) > with switching to the backup nameservers listed in > resolv.conf when disconnected from the primary > nameserver. I thought this problem was fixed, but there > seems to be a least one case where the problem still exits. > I submitted a bug report to NeXT. The NeXT version of BIND is 4.8.1. I have requested (twice) that they upgrade at least to 4.8.3 -- if not 4.9. The resolver libraries in 4.9 are effective in reducing network traffic and improving resolution efficiency -- they ignore servers in the name list who cannot be contacted. Trivia aside, the NeXT resolver works fine albeit they try the name servers in order. The resolver will go to the secondary. > During a network reconfiguration, my subnet became > disconnected from the backbone. I am running routed. The > default gateway (brouter box) is also down, and does not > appear in the routing table. The default nameserver in > resolv.conf is in another subnet to which there is no > route. Both of the secondary nameservers in resolv.conf > are in my subnet, however. ROUTED is nice because you don't have to tune /etc/hostconfig when a machine is moved to another subnet. I prefer specifying a default route however. Specifying a default route releases the host from relying on someone else to publish route information -- it lets the router route. Specifying a default route releases the host from running another process to collect the route information too. [ other stuff deleted ] -- Dennis P. Glatting / Technical Director / Paradigm Systems Corp. of WA
From: dennis.glatting@mccaw.com Newsgroups: comp.sys.next.bugs Subject: Re: More resolv.conf problems 3.1 Date: 31 Aug 1993 15:20:38 GMT Organization: McCaw Cellular Communications, Inc. Distribution: world Message-ID: <25vq86$q9o@ftp-p.mccaw.com> References: <25t75i$fbs@TAMUTS.TAMU.EDU> Keywords: keywords In article <25t75i$fbs@TAMUTS.TAMU.EDU> pierce@cantrell.tamu.edu (Pierce Cantrell) writes: > There still seems to be a problem in NEXTSTEP 3.1 (Black) > with switching to the backup nameservers listed in > resolv.conf when disconnected from the primary > nameserver. I thought this problem was fixed, but there > seems to be a least one case where the problem still exits. > I submitted a bug report to NeXT. The NeXT version of BIND is 4.8.1. I have requested (twice) that they upgrade at least to 4.8.3 -- if not 4.9. The resolver libraries in 4.9 are effective in reducing network traffic and improving resolution efficiency -- they ignore servers in the name list who cannot be contacted. Trivia aside, the NeXT resolver works fine albeit they try the name servers in order. The resolver will go to the secondary. > During a network reconfiguration, my subnet became > disconnected from the backbone. I am running routed. The > default gateway (brouter box) is also down, and does not > appear in the routing table. The default nameserver in > resolv.conf is in another subnet to which there is no > route. Both of the secondary nameservers in resolv.conf > are in my subnet, however. ROUTED is nice because you don't have to tune /etc/hostconfig when a machine is moved to another subnet. I prefer specifying a default route however. Specifying a default route releases the host from relying on someone else to publish route information -- it lets the router route. Specifying a default route releases the host from running another process to collect the route information too. [ other stuff deleted ] -- Dennis P. Glatting / Technical Director / Paradigm Systems Corp. of WA
Newsgroups: comp.sys.next.bugs From: francisr@stupid.ucs.indiana.edu (Rob Francis) Subject: Exporting root access to groups Message-ID: <CCMy49.1sn@usenet.ucs.indiana.edu> Sender: news@usenet.ucs.indiana.edu (USENET News System) Organization: University Computing Services Date: Tue, 31 Aug 1993 18:02:32 GMT Can anyone confirm this for me? NextStep 3.0 on black hardware. I export user space to a group of machines which have a group name in netinfo, so that I can just export like this: /Users -access=group But if I want to have root too, /Users -access=group,root=group Doesn't work. I have to do: /Users -access=group,root=member1:member2:member3.... I've duplicated this on a couple of machines. -rob francisr@indiana.edu
From: bkr@silence.next.com (Brian Raymor) Newsgroups: comp.sys.next.bugs Subject: Re: Sound on NextStep Date: 27 Aug 1993 18:01:39 GMT Organization: NeXT, Inc. Message-ID: <25li63$24b@rosie.next.com> References: <110477@hydra.gatech.EDU> In article <110477@hydra.gatech.EDU> gt8299c@prism.gatech.EDU (Badri Narasimhan) writes: > Dear Sir/Madam: > > I have installed NextStep on a DELL 450 DE/2. However, I am not able to hear any of the audio effects (I am told that there are many). Could anybody help me out? > Sound cards are optional in PC configurations. Do you have a supported sound card in your system? ..brian
Newsgroups: comp.sys.next.bugs From: kwang@lore.acs.calpoly.edu (Kevin John Wang) Subject: NeXTMail: user pictures (NS3.0, Black) Message-ID: <1993Aug31.214318.158224@zeus.calpoly.edu> Sender: news@zeus.calpoly.edu Organization: Cal Poly State University, San Luis Obispo Date: Tue, 31 Aug 1993 21:43:18 GMT I have found that the mailDBupdate program that is supposed to run (according to librarian) only does an (nidump passwd /). This does not work for me, since I have users located in /, /acs, and /bus. Does anyone know of any way to make mailDBupdate point to these multiple domains? I also would like to know if mailDBupdate does anything MORE than (nidump passwd / >whateverthatfileis)? If it does nothing more, then I can probably just replace mailDBupdate with a script... - Kevin Wang
Newsgroups: comp.sys.next.bugs From: borris@boba.rhein-main.de (Borris Balzer) Subject: Re: buildafmdir Message-ID: <1993Aug31.184748.5769@boba.rhein-main.de> Sender: borris@boba.rhein-main.de Organization: Borris Balzer - DeskTopPublishing References: <25mqla$1b9@localhost.dk> Date: Tue, 31 Aug 1993 18:47:48 GMT work@dannug.dk (Michael Hallin) writes: > In article <dgursky.746452560@news.andi.org> dgursky@nextsrv1.andi.org > (David Gursky) writes: > |>work@dannug.dk (Michael Hallin) writes, in response to my original > |>note: > |> > |>>I don t know if there is another way to fix this, but I have several > |>>hundred fonts working on a 3.0 system, with the fonts spread evenly > |>>between the three ../Fonts directories. How, you ask? Well, I got a > |> 2.2 version of buildafmdir, and that works. > |>>Mail me, if you want it. > |> > |>I have been subsequently told this problem has been fixed in release > |>3.1 of NEXTSTEP. > |>-- > > From what I heard, it was supposed to be fixed, but wasn t. Not too sure > about it, though, only hearsay...... It IS fixed! I'm using 285 fonts (I've counted them at the moment!) with no troubles on my 3.1-Cube. O.k. - I didn't try to print them all since installing NS3.1 - but they all are represented in my font-panel. And the "Garamond-Bug" is fixed, too. Now I'm able to use 4 different Garamond families. NS3.0 just gave success to the three first-installed Garamonds. - Borris - -- borris@boba.rhein-main.de ist: Borris Balzer - Kennedyallee 34 D-60596 Frankfurt am Main - Tel +49-69-639266 - Fax +49-69-6312324
Newsgroups: comp.sys.next.bugs From: lloyd@world.std.com (Chris Lloyd) Subject: kill(2) with SIGCONT doesn't work on setuid programs ? Message-ID: <CCnJFC.898@world.std.com> Organization: The World Public Access UNIX, Brookline, MA Distribution: usa Date: Wed, 1 Sep 1993 01:42:47 GMT I get the feeling this is me being braindead, but anyways... From man 2 kill: For a process to have permission to send a signal to a pro- cess designated by pid, the real or effective user ID of the sending process must match the real or saved set-user-ID of the receiving process, unless the sending process has superuser privileges. *** The only exception is the signal SIGCONT, which may always be sent to any descendant of the current process. *** Problem: When fork/exec'ing a setuid program which suspends with SIGSTOP, the parent is unable to continue the process with a SIGCONT. kill() comes back with EPERM - Not owner. However: If the child does a setpgrp(0,getpid()), the parent IS able to SIGCONT it using killpg() or kill(-pid..). Example: (copy out parent.c and child.c from below) make parent child as root - chown root.wheel child as root - chmod u+s child parent And the error will pop out. If you uncomment the setpgrp and -, that works. Applies to 2.1 and 3.1. Is this a bug in documentation or the behaviour, and is this how it's supposed to work? File parent.c: #import <libc.h> #import <errno.h> #define $unix(r) $$unix(r,#r,__LINE__,__FILE__) void $$unix(int r,const char *t,int l,const char *file) { if(r<0) printf("%s from %s at %d in %s\n",strerror(errno),t,l,file); } void main() { int pid; union wait status; $unix(pid=fork()); if(pid==0){ /* setpgrp(0,getpid()); */ execl("./child","child",0); _exit(0); } $unix(wait4(pid,&status,WUNTRACED,NULL)); if(WIFSTOPPED(status)) $unix(kill(/* - */pid,SIGCONT)); } File child.c: #import <stdio.h> #import <libc.h> main() { printf("waiting...\n"); kill(getpid(),SIGSTOP); printf("awoke!\n"); } -- :: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: :: NEXTSTEP Monk ::
Newsgroups: comp.sys.next.bugs From: netcom.com!kira!davidjohn (David John Burrowes) Subject: Re: Someone with 3.1 black and PLI superfloppy: please check this: Message-ID: <1993Aug31.044902.296@kira.net.netcom.com> Sender: davidjohn@kira.net.netcom.com Organization: No organization at this time. References: <1993Aug23.164358.1352@rna.indiv.nluug.nl> Date: Tue, 31 Aug 1993 04:49:02 GMT In article <1993Aug23.164358.1352@rna.indiv.nluug.nl> gerben@rna.indiv.nluug.nl writes: > Try formatting a 1.4MB disk in the PLI Superfloppy with a NeXT filesystem. > Disk Format in progress... > ***Format Complete*** > writing disk label > boot block extends beyond front porch > I got an answer to this which I haven't had a chance to try out with yet. It suggested two possible solutions. The first is to use the /usr/etc/disk from 3.0 instead of the 3.1 one, or to run /usr/etc/disk manually and use the init command there (and to answer no when asked about putting /usr/standalone/boot on). Hope that helps anyone. \david john burrowes
Newsgroups: comp.sys.next.bugs From: Karl_Kraft@ensuing.com Subject: Re: NFS ghost files when unlink'ing: is it NS 3.1 bug ? Message-ID: <CCn82C.7CA@ensuing.com> Sender: karl@ensuing.com (Karl Kraft) Organization: Ensuing Technologies Inc. References: <1993Aug30.165939.2580@IRO.UMontreal.CA> Date: Tue, 31 Aug 1993 21:37:13 GMT In article <1993Aug30.165939.2580@IRO.UMontreal.CA> hugo@IRO.UMontreal.CA (Hugo Desrosiers) writes: > I've got a clone PC running NS 3.1 linked on a MIPS 120 file system > by a standard NFS link. In a application being developped, a directory > of files must be deleted. So I dired the directory, then go through all > the files in it and unlink() them. After that, I rmdir() the directory. > Sometimes the rmdir() works, sometimes it doesn't. After a while, I > noticed that some ghost files named ".nfs"<numeric id> where created in > that directory, and they seem to be some kind of backup of the original > files that were unlink'ed; rmdir() sees these files and refuses to delete > the directory. > No, it is not a bug. It's a feature of NFS. Read the documentation on NFS for more information. > Now are those files created by the NFS system of NS or by the MIPS one ? > And how can they be dealed with ?? > They are created by the NFS server, in this case the MIPS machine. Use unlink() to remove them. -- _________ Karl Kraft Karl_Kraft@ensuing.com (NeXT mail)
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: dav@well.sf.ca.us (Paul Davilon) Subject: New serial drivers in this century? Organization: The Whole Earth 'Lectronic Link, Sausalito, CA Date: Wed, 1 Sep 1993 12:19:21 GMT Message-ID: <CCoCw9.DLB@well.sf.ca.us> Summary: do you believe in santa claus? Sender: news@well.sf.ca.us The title says most of it. They were coming in mid-July, since this is now September I guess that SURPRISE, they are a little late. Since mid-July I have been actively dissuading people who have any interest in using a modem or ever hope to establish a SLIP link, from getting anywhere near NS/FIP. Come on NeXT, please, it isn't brain surgery, as much as I realize that NS is not Linux, this would have been fixed long ago under that "unsupported" and "non-commercial" environment.
From: jmd@cube.handheld.com (Jim De Arras) Newsgroups: comp.sys.next.bugs Subject: Re: ProAudioSpectrum problems. Date: 2 Sep 1993 00:05:16 GMT Organization: Hand Held Products, Inc. Distribution: world Message-ID: <263dbsINN8e3@clem.handheld.com> References: <CCL4vv.AnJ.2@cs.cmu.edu> In article <CCL4vv.AnJ.2@cs.cmu.edu> ddj+@cs.cmu.edu (Doug DeJulio) writes: > > I've got: > 486DX2-66, 8M RAM (I know, I need more) > Trident SVGA card > Adaptec AHA-1542C SCSI card w/ gig drive & Texel CD-ROM > SMC-Elite ethernet card > Logitech bus mouse > Pro Audio Spectrum 16 sound card > 2 serial & 1 parallel card > > Whenever I tell NS to configure the soundcard with a configuration > that works perfectly under DOS, the system panics every time it tries > to boot up. When I tell NS to configure the soundcard with a > configuation that should NOT work, the system boots up find, but the > sound card indeed does not work (the infinite-audio-repeat symptom > occurs). > > Any ideas? Anyone with similar hardware have something that works? > -- > Doug DeJulio > ddj+@cmu.edu It's my understanding that the Pro Audio Spectrum 16 sound card and the Adaptec AHA-1542C SCSI card are NOT compatible in the same bus, something about busmaster modes, I was not clear. But until I removed the Pro Audio Spectrum 16 driver from NS/FIP, my intel system would randomly lockup or panic when it made a sound. Most of the time it played sounds OK, but one in 10 times, it froze. Power switch time. Jim
From: npratt@madmax.modsys (Nevin Pratt) Newsgroups: comp.sys.next.bugs Subject: Re: ProAudioSpectrum problems. Date: 2 Sep 1993 15:40:54 GMT Organization: Sun Microsystems, Inc. Distribution: world Message-ID: <265466$no4@cnn.sim.es.com> References: <263dbsINN8e3@clem.handheld.com> In article 263dbsINN8e3@clem.handheld.com, jmd@cube.handheld.com (Jim De Arras) writes: > It's my understanding that the Pro Audio Spectrum 16 sound card and the Adaptec > AHA-1542C SCSI card are NOT compatible in the same bus, something about > busmaster modes, I was not clear. > > But until I removed the Pro Audio Spectrum 16 driver from NS/FIP, my intel > system would randomly lockup or panic when it made a sound. Most of the time > it played sounds OK, but one in 10 times, it froze. Power switch time. I have the PAS-16 and the AHA-1542B. They work fine together (using a SCSI hard drive-- *not* an IDE drive), and I suspect that the 1542C works fine with the PAS-16 also. However, initially I had the same symptoms you are describing. It was an IRA/DMA interaction between cards. It was hit-and-miss testing until I found a combination that worked. The specific settings you need will depend on the specific hardware you have. However, when I did this, I *do* remember thinking to myself that if I had an IDE hard drive instead of a SCSI drive, I could not have gotten it to work. With a little patience (OK, a *lot*), I think it will work, unless you have an IDE hard drive. Welcome to the world of PC's. Nevin
From: jmd@cube.handheld.com (Jim De Arras) Newsgroups: comp.sys.next.bugs Subject: Re: ProAudioSpectrum problems. Date: 3 Sep 1993 00:16:50 GMT Organization: Hand Held Products, Inc. Distribution: world Message-ID: <2662diINNb75@clem.handheld.com> References: <265466$no4@cnn.sim.es.com> In article <265466$no4@cnn.sim.es.com> npratt@madmax.modsys (Nevin Pratt) writes: > In article 263dbsINN8e3@clem.handheld.com, jmd@cube.handheld.com (Jim De Arras) writes: > > > It's my understanding that the Pro Audio Spectrum 16 sound card and the Adaptec > > AHA-1542C SCSI card are NOT compatible in the same bus, something about > > busmaster modes, I was not clear. > > > > But until I removed the Pro Audio Spectrum 16 driver from NS/FIP, my intel > > system would randomly lockup or panic when it made a sound. Most of the time > > it played sounds OK, but one in 10 times, it froze. Power switch time. > > I have the PAS-16 and the AHA-1542B. They work fine together (using a SCSI hard > drive-- *not* an IDE drive), and I suspect that the 1542C works fine with the > PAS-16 also. > > However, initially I had the same symptoms you are describing. It was an > IRA/DMA interaction between cards. It was hit-and-miss testing until I found > a combination that worked. > > The specific settings you need will depend on the specific hardware you have. > However, when I did this, I *do* remember thinking to myself that if I had an > IDE hard drive instead of a SCSI drive, I could not have gotten it to work. > PLEASE post your specific settings! > With a little patience (OK, a *lot*), I think it will work, unless you have > an IDE hard drive. > > Welcome to the world of PC's. > Welcome back, is more like it. I'd thought I'd left this nightmare behind when I was first Mac'ed, then NeXT'ed! > Nevin > -- ---------------------------------------------------------------------------- Jim De Arras - WA4ONG | "Government is not reason; it is not eloquence; NRA,ILA | it is a force. Like fire, it is a dangerous jmd@handheld.com | servant and a fearful master." -- George Washington
Newsgroups: comp.sys.next.bugs From: frank@dendrite.sps.mot.com (Mark Frank) Subject: SoundView display on NS/FIP Message-ID: <1993Sep2.180416.4294@newsgate.sps.mot.com> Sender: news@newsgate.sps.mot.com Organization: sps Distribution: usa Date: Thu, 2 Sep 1993 18:04:16 GMT Has anyone tried to display a sound in a SoundView on an Intel machine. The autoscaling doesn't appear to work properly. This used to work OK on black hardware. - Thanks, Mark -- Mark Frank frank@dendrite.sps.mot.com Motorola Inc. 2100 E. Elliot MD508 Tempe, AZ 85284
From: jmd@cube.handheld.com (Jim De Arras) Newsgroups: comp.sys.next.bugs Subject: Re: ProAudioSpectrum problems. Date: 3 Sep 1993 13:15:36 GMT Organization: Hand Held Products, Inc. Distribution: world Message-ID: <267g1oINNd37@clem.handheld.com> References: <2662diINNb75@clem.handheld.com> Posted for Steve: In article <2662diINNb75@clem.handheld.com> jmd@cube.handheld.com (Jim De >Arras): >In article <265466$no4@cnn.sim.es.com> npratt@madmax.modsys (Nevin Pratt) >writes: >> In article 263dbsINN8e3@clem.handheld.com, jmd@cube.handheld.com (Jim De >Arras) writes: >> >> > it played sounds OK, but one in 10 times, it froze. Power switch time. >> >> I have the PAS-16 and the AHA-1542B. They work fine together (using a SCSI >> [munch] >> The specific settings you need will depend on the specific hardware you have. >> However, when I did this, I *do* remember thinking to myself that if I had an >> IDE hard drive instead of a SCSI drive, I could not have gotten it to work. >> > >PLEASE post your specific settings! > >---------------------------------------------------------------------------- >Jim De Arras - WA4ONG | "Government is not reason; it is not eloquence; >NRA,ILA | it is a force. Like fire, it is a dangerous >jmd@handheld.com | servant and a fearful master." -- George Washington Jim, I can't post news, so I'm replying directly: The settings I use are: SCSI controller: IRQ 11 DMA 5 PAS-16 IRQ 15 DMA 7 Using IRQ 15 for the sound card lowers the priority of the sound card's interupts. Doing this seemed to remove the freeze up problems. I originally had this set up on an ISA bus PC and had tons of trouble - I eventually just removed the sound card altogether because the quality of sound (choppiness) was too distracting to make it worthwhile. I've since switched to an EISA (HP Vectra) and have had no problems. A warning: if you also have a Windows partition on the disk and want to use the sound card, use MediaVision's install program to get all the files & crap installed, then go in and *manually* edit autoexec/win.ini/system.ini to set the IRQ and DMA and remove the CD stuff. It's pretty obvious what to change. If you don't, the system will freeze - it seems that no matter what you tell the install program, it always uses DMA 5. MediaVision's software skills seem to be their weak point. You might want to post this, I know that everyone with one of these goes through this crap. Steve steveq@sitult.stevens-tech.edu
From: npratt@madmax.modsys (Nevin Pratt) Newsgroups: comp.sys.next.bugs Subject: Re: ProAudioSpectrum problems. Date: 3 Sep 1993 15:01:56 GMT Organization: Sun Microsystems, Inc. Distribution: world Message-ID: <267m94$no4@cnn.sim.es.com> References: <267g1oINNd37@clem.handheld.com> In article 267g1oINNd37@clem.handheld.com, jmd@cube.handheld.com (Jim De Arras) writes: > >PLEASE post your specific settings! > > > Jim, > > I can't post news, so I'm replying directly: > > The settings I use are: > SCSI controller: IRQ 11 DMA 5 > PAS-16 IRQ 15 DMA 7 > > Using IRQ 15 for the sound card lowers the priority of the sound card's > interupts. Doing this seemed to remove the freeze up problems. > > I originally had this set up on an ISA bus PC and had tons of trouble - > I eventually just removed the sound card altogether because the quality > of sound (choppiness) was too distracting to make it worthwhile. I've > since switched to an EISA (HP Vectra) and have had no problems. > > A warning: if you also have a Windows partition on the disk and want to > use the sound card, use MediaVision's install program to get all the > files & crap installed, then go in and *manually* edit > autoexec/win.ini/system.ini to set the IRQ and DMA and remove the CD > stuff. It's pretty obvious what to change. If you don't, the system > will freeze - it seems that no matter what you tell the install program, > it always uses DMA 5. MediaVision's software skills seem to be their > weak point. I am not having any trouble with my current setup. My specific settings are: (first the hardware being used) * DX66/2 ISA Motherboard, 32MB RAM (clone I picked up somewhere, don't have the specifics on it) * Adaptec 1542B SCSI Controller * Pro Audio Spectrum sound card * ATI Ultra Pro VLB video board * no-name clone multi-IO card * Logitech serial mouse (now *all* of the settings, as reported by "Configure.app") * ATI Ultra Pro -- port address 0x3B0, Mapped memory 2048K at 0x7E00000 * Serial Mouse -- Serial Port A * (no network) * Adaptec 1542B SCSI -- DMA 5, IRQ 11, port address 0x330 * ProAudioSpectrum 16 -- DMA 3, IRQ 15, port address 0x388 * Floppy Disk Driver -- DMA 2, IRQ 6, port address 0x3F2 * PS/2-Style Keyboard -- IRQ 1, port address 0x60 * On-Board Parallel Port -- IRQ 7, port address 0x378 * On-Board Serial Ports -- IRQ 3 & 4, port address 0x3F8 Nevin
Newsgroups: comp.sys.next.bugs From: alr2@quads.uchicago.edu (john alroy) Subject: system panic caused by /usr/lib/kern_loader/Audio?? Message-ID: <1993Sep3.162412.12589@midway.uchicago.edu> Sender: news@uchinews.uchicago.edu (News System) Organization: University of Chicago -- Academic & Public Computing Date: Fri, 3 Sep 1993 16:24:12 GMT I just purchased a 520 meg Fujitsu hard drive and loaded NS 3.1 on to it using a borrowed Color NeXT running with a 33 MHz '040 CPU and 32 meg RAM. There was no obvious problem booting with this configuration. However, when I tried to boot using my own 25 MHz Color, which has a measly 12 meg RAM, a system panic enused just after the "Reboot complete" message flashed on the ROM monitor and the screen cleared, as is usual as the boot is finishing up. Checking /usr/adm/messages, I found nothing terribly unusual except the following message, which came immediately after "Reboot complete": kern_loader: hashtable: count differs after rehashing; probably indicates a broken invariant (and so on) This led me to /usr/lib/kern_loader, where I found the directories /Audio, /Midi, and /nuc. Removing /Audio had the following effect: the system seems to boot properly but without audio output (of course), and executes common applications, but when floppy disks are put in the drive there is an immediate system panic. Not being a NeXT guru, I haven't the slightest idea how to proceed from this point. Help!
Newsgroups: comp.sys.next.bugs From: ddj+@cs.cmu.edu (Doug DeJulio) Subject: Re: ProAudioSpectrum problems. Message-ID: <CCsIn6.8Cr.2@cs.cmu.edu> Sender: news@cs.cmu.edu (Usenet News System) Organization: School of Computer Science, Carnegie Mellon References: <2662diINNb75@clem.handheld.com> <267g1oINNd37@clem.handheld.com> Date: Fri, 3 Sep 1993 18:13:53 GMT Okay. With the following settings: AHA-1542C : IRQ 11, DMA 5 Pro Audio SPectrum: IRQ 15, DMA 7 The panics and the freezes go away. However, any time any sound is played, all I get is an extremely short burst of static. Any idea what gives? I have an EISA motherboard (CAESAR chipset, HiNT corporation). With any of the DMA channels that are 8-bit under ISA motherboards, I get a pattern of sound-silence, BUT, the sound seems correct when it's playing. Perhaps the drivers under 3.2 will let me use an 8-bit DMA channel properly...? -- Doug DeJulio ddj+@cmu.edu
From: suckow@uropax.contrib.de (Ralf Suckow) Newsgroups: comp.sys.next.bugs Subject: Serial Ports Driver Bug Fix? Date: 4 Sep 1993 20:08:50 +0200 Organization: Contributed Software GbR Message-ID: <26alji$6o8@uropax.contrib.de> Does anybody know, when the serial ports driver problem will be fixed for NS/FIP 3.1? Will it be available for 3.1 Evaluation Kit users even after release of 3.2? Any information? Any rumors? Thanks, Ralf -- Ralf Suckow, Berlin | suckow@contrib.de | Do you think it's difficult to speak Russian? Contributed Software | Every Moscow kid aged 5 years speaks it perfectly. only delivers my mail.|
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs From: artek@mindvox.phantom.com (Ardal Technologies) Subject: Serial port drivers Message-ID: <mJye0B1w165w@mindvox.phantom.com> Originator: artek@mindvox Keywords: still broken Sender: news@mindvox.phantom.com Organization: [Phantom Access] / the MindVox system Date: Sun, 5 Sep 1993 17:02:57 GMT I posted a message describing my problems and extreme frustration at the constant system crashes associated with trying to use the serial ports on a Intel system running NeXTSTEP (at ANY speed, including 2400). I posted this message in the beginning of JULY. I subsequently received about 20 letters saying different things, most of which came down to "please be patient, a patch will be released mid-July." I in fact received these words from TWO SEPERATE people sending from next.com. It is now SEPTEMBER, I have been VERY PATIENT, I have controlled my anger and frustration and not given up on NS even if one of the primary things I need it for is to run SLIP and use a modem to connect to a company system from home. But it is now nearly 2 months after the promised fix date. I keep hearing that the drivers have been fixed and are now being tested. I put forth that NOTHING can possibly be worse than the drivers that exist right now, and I am getting very, VERY tired of being told that they are COMING REAL SOON NOW. I specifically purchased a Dell JAWS machine to evaluate NS after being told that NS Intel was primarily developed on the JAWS system because I wanted to be assured the maximum stability possible. This seems to have been a waste of time and money. NeXT, new serial port drivers are HIGHLY OVERDUE... Sincerely, Tired of the run-around
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: yoda@cis.uni-muenchen.de (Marc Guenther) Subject: rlogin as root ALWAYS asks for password Sender: news@informatik.uni-muenchen.de (News System) Message-ID: <CCwCE7.CFt@informatik.uni-muenchen.de> Date: Sun, 5 Sep 1993 19:49:19 GMT Organization: Institut fuer Informatik der Universitaet Muenchen Keywords: rlogin, root, passwort, rsh Hello, Assume you have two machines A,B in /.rhosts of A there is an entry for B, if you try to rlogin from B to A as root, rlogin always prompts for a password. It works for every other normal user. I think this is VERY annoying, does someone know, if there is a rlogind, that doesnt do this ? Thanx, Marc Guenther ------------------------------------------------------------------------- Centrum fuer Informations | Leopoldstrasse 139 | Phone: +49 89 364 072 und Sprachverarbeitung | D-8000 M"unchen 40 | Fax: +49 89 361 6199 University of Munich | Germany | yoda@cis.uni-muenchen.de -------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: yoda@cis.uni-muenchen.de (Marc Guenther) Subject: NextStep looses Events while playing long sounds Sender: news@informatik.uni-muenchen.de (News System) Message-ID: <CCwCyE.CKB@informatik.uni-muenchen.de> Date: Sun, 5 Sep 1993 20:01:26 GMT Organization: Institut fuer Informatik der Universitaet Muenchen Hello, has anyone else expierienced this ? I have several large soundfiles (4-20MB) and I play them via sndplay from the shell. While the sound is playing, the next sometimes looses key and mouse events, for xample the shift key, or the command key-down (very annoying if you have some text selected, and want to copy it with Command-C, the text is replaced by a c) or any other key and even mouse buttons. Sometimes up to every 10th key is lost (Try to write a mail with that !!). But all this happens only while a sound is playing. I have seen this happen on several Nexts, includeing a Cube, a TurboColor, and a normal Station and on 2.1 to 3.1. Any Ideas ? Marc Guenther ------------------------------------------------------------------------- Centrum fuer Informations | Leopoldstrasse 139 | Phone: +49 89 364 072 und Sprachverarbeitung | D-8000 M"unchen 40 | Fax: +49 89 361 6199 University of Munich | Germany | yoda@cis.uni-muenchen.de -------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: yoda@cis.uni-muenchen.de (Marc Guenther) Subject: resolver lib doesnt do hostaliases Sender: news@informatik.uni-muenchen.de (News System) Message-ID: <CCwF25.Cw3@informatik.uni-muenchen.de> Date: Sun, 5 Sep 1993 20:46:53 GMT Organization: Institut fuer Informatik der Universitaet Muenchen Keywords: resolver, resolv, alias, hostaliases Hello again, just another bug I already reported to Next since 3.0, of course with no response... hostaliasing in 3.1 still doesnt work. The following is from the hostname(7) manpage: If the name consists of a single component, i.e. contains no dot, and if the environment variable ``HOSTALIASES'' is set to the name of a file, that file is searched for an string matching the input hostname. The file should consist of lines made up of two white-space separated strings, the first of which is the hostname alias, and the second of which is the complete hostname to be substituted for that alias. If a case-sensitive match is found between the host- name to be resolved and the first field of a line in the file, the substituted name is looked up with no further pro- cessing. I have created a file .hostaliases in my homedirectory, set the env var HOSTALIASES to it, and it doesnt work. The only thing that does work is nslookup, and thats probably because it reads this file for itself, because it writes a message abuout this (which it couldnt do, if it would just call gethostbyname) Here is an example: ~:(1) 0> echo $HOSTALIASES /Users/admin/yoda/.hostaliases ~:(2) 0> more $HOSTALIASES hp8 hphalle8.informatik.tu-muenchen.de ~:(3) 0> nslookup hp8 Server: thecube.cis.uni-muenchen.de Address: 129.187.148.40 Aliased to "hphalle8.informatik.tu-muenchen.de" [debug info deleted] Name: hphalle8.informatik.tu-muenchen.de Address: 131.159.4.9 ~:(4) 0> ping hp8 ping: unknown host hp8 ~:(5) 1> telnet hp8 hp8: Unknown host ~:(6) 1> The same thing works on HPUX, which has the same manpage entry. It doesnt work on SUN, but SUNs resolver library sucks. Is this a known bug ??? I would like this to work, cause I have accounts on hosts in two totally different domains, and german domainnames are VERY long :) Marc Guenther ------------------------------------------------------------------------- Centrum fuer Informations | Leopoldstrasse 139 | Phone: +49 89 364 072 und Sprachverarbeitung | D-8000 M"unchen 40 | Fax: +49 89 361 6199 University of Munich | Germany | yoda@cis.uni-muenchen.de -------------------------------------------------------------------------
From: louie@sayshell.umd.edu (Louis A. Mamakos) Newsgroups: comp.sys.next.bugs Subject: Re: resolver lib doesnt do hostaliases Date: 6 Sep 1993 03:43:55 GMT Organization: University of Maryland, College Park Message-ID: <26eblr$p9j@ni.umd.edu> References: <CCwF25.Cw3@informatik.uni-muenchen.de> Keywords: resolver, resolv, alias, hostaliases In article <CCwF25.Cw3@informatik.uni-muenchen.de> yoda@cis.uni-muenchen.de (Marc Guenther) writes: >hostaliasing in 3.1 still doesnt work. [....] >I have created a file .hostaliases in my homedirectory, >set the env var HOSTALIASES to it, and it doesnt work. >The only thing that does work is nslookup, and thats >probably because it reads this file for itself, because >it writes a message abuout this (which it couldnt do, if it would >just call gethostbyname) nslookup works because it is performing DNS queries directly, rather than via the gethostbyname() library routine. The HOSTALIASES environment variable doesn't work on the NeXT because of the way that hostnames are looked up in the DNS. On most normal UNIX systems that use BIND, the resolver (the software component that generates DNS queries) is linked into the application. It is the resolver that looks for the HOSTALISES environment variable. On the NeXT, the resolver is *not* linked into your program. Rather, the lookupd process which normally looks up information in NetInfo will also look up a host names using the DNS (Domain Name System) queries if the /etc/resolv.conf file exists. But since it is a seperate process, it doesn't have access to the original process' environment variables. Not only that, but now DNS queries (along with all other NetInfo activity) become single threaded. >just another bug I already reported to Next since 3.0, of course >with no response... I reported this problem on Sat, 30 Nov 1991 16:08:12 EST as bug/log #20123 in release 2.something. We patched the shared C runtime library to invoke the DNS resolver directly, but never carried the patches forward to 3.0 or beyond. Lately, the lookupd process also incorrectly caches temporary failures are "host unknown" errors for a while. Louis Mamakos University of Maryland
Newsgroups: comp.sys.next.bugs From: joseph@daffy.tip.ameslab.gov (Joseph Reynolds) Subject: Re: rlogin as root ALWAYS asks for password Message-ID: <CCx7s9.96o@news.iastate.edu> Keywords: security, rlogin, rlogind, password Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA References: <CCwCE7.CFt@informatik.uni-muenchen.de> Date: Mon, 6 Sep 1993 07:07:20 GMT Hi. In article [...] Marc Guenther writes: > Assume you have two machines A,B in /.rhosts of A there is an entry > for B, if you try to rlogin from B to A as root, rlogin always prompts > for a password. And it's a GOOD THING that rlogin does this. Otherwise someone could pose as root at some machine in your .rhosts file and gain ROOT access to your machine! Can you imagine the damage they could do?!? In short, having a rhosts file is a BIG, WELL KNOWN, SECURITY RISK. It's bad. And it's even worse for root. > I think this is VERY annoying. Does someone know, if > there is a rlogind, that doesn't do this ? I hope there is not. It would be VERY ANNOYING to let anyone with a half an ounce (15 mL) of brains gain root access to your system. > Thanx, > Marc Guenther I apologize for the use of capitalization. Joseph
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: alibaba@mindvox.phantom.com (Nick Mordanzo) Subject: Re: New serial drivers in this century? Message-ID: <FH3F0B3w165w@mindvox.phantom.com> Originator: alibaba@mindvox Sender: news@mindvox.phantom.com Organization: [Phantom Access] / the MindVox system References: <CCoCw9.DLB@well.sf.ca.us> Date: Mon, 6 Sep 1993 07:25:38 GMT dav@well.sf.ca.us (Paul Davilon) writes: > The title says most of it. They were coming in mid-July, since this is > September I guess that SURPRISE, they are a little late. Since mid-July I > have been actively dissuading people who have any interest in using a > modem or ever hope to establish a SLIP link, from getting anywhere near > NS/FIP. > > Come on NeXT, please, it isn't brain surgery, as much as I realize that NS > is > not Linux, this would have been fixed long ago under that "unsupported" and > "non-commercial" environment. Yeah but does Linux have those pretty, shaded 3-d icons to look at? So you need to run fsck 10 times a day, its all a frustration threshold test, to see how much shit you can put up with before you say fuck this man and just stop booting the nexstep partition since the msdos one works just fine, sans artwork. $%$%$%$%$%$%$% ($) Ali Baba ($) %$%$%$%$%$%$%$
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: rlogin as root ALWAYS asks for password Message-ID: <1993Sep6.060850.1597@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <CCwCE7.CFt@informatik.uni-muenchen.de> Date: Mon, 6 Sep 1993 06:08:50 GMT In article <CCwCE7.CFt@informatik.uni-muenchen.de> yoda@cis.uni-muenchen.de (Marc Guenther) writes: -> -> Assume you have two machines A,B in /.rhosts of A there -> is an entry for B, if you try to rlogin from B to A as -> root, rlogin always prompts for a password. It works -> for every other normal user. -> -> I think this is VERY annoying, does someone know, if -> there is a rlogind, that doesnt do this ? -> -> Thanx, -> Marc Guenther I am not at all convinced that this is a ``bug'' rather than security enhancement, though it can interfere with both rlogin and rsh operations as root. It does not seem to matter if ~/.rhosts or /etc/hosts.equiv is used to establish the root-user equivalency -- it is ignored. It also does not seem to matter if the ``root'' user's home directory is left at the root directory of the filesystem, or if ``root'' is assigned a user directory elsewhere in order to clean-up the filesystem root directory. Bruce Gingery bruce@TotSysSoft.com Total System Software NeXT-Mail preferred, MIME-Mail ok
Newsgroups: comp.sys.next.bugs From: yoda@cis.uni-muenchen.de (Marc Guenther) Subject: Re: rlogin as root ALWAYS asks for password Sender: news@informatik.uni-muenchen.de (News System) Message-ID: <CCxKDr.JBG@informatik.uni-muenchen.de> Date: Mon, 6 Sep 1993 11:39:27 GMT References: <CCx7s9.96o@news.iastate.edu> Organization: Institut fuer Informatik der Universitaet Muenchen In article <CCx7s9.96o@news.iastate.edu> joseph@daffy.tip.ameslab.gov (Joseph Reynolds) writes: > In article [...] Marc Guenther writes: > > Assume you have two machines A,B in /.rhosts of A there is an entry > > for B, if you try to rlogin from B to A as root, rlogin always prompts > > for a password. > > And it's a GOOD THING that rlogin does this. Otherwise someone could pose > as root at some machine in your .rhosts file and gain ROOT access to your > machine! Can you imagine the damage they could do?!? In short, having a > rhosts file is a BIG, WELL KNOWN, SECURITY RISK. It's bad. And it's > even worse for root. Sorry, but im not going to discuss the advantages or disadvanteages of /.rhosts, I just want to use it. In article <1993Sep6.060850.1597@ToTSySSoft.com> bruce@TotSysSoft.com (Bruce Gingery) writes: > I am not at all convinced that this is a ``bug'' rather than > security enhancement, though it can interfere with both rlogin > and rsh operations as root. It does not seem to matter if > ~/.rhosts or /etc/hosts.equiv is used to establish the > root-user equivalency -- it is ignored. I forgot to mention it, rsh does work of course (or we couldnt perform our daily dumps), thats the strange thing. The only thing that doesnt work is rlogin. (rsh without an command just calls rlogin, so it doesnt work too) This is particulary useless, as anyone as root on machine B can get a root shell on machine A with rsh A /bin/sh. So I call this a BUG, or perhaps a misthought feature. In article <CCx7s9.96o@news.iastate.edu> joseph@daffy.tip.ameslab.gov (Joseph Reynolds) writes: > > I think this is VERY annoying. Does someone know, if > > there is a rlogind, that doesn't do this ? > > I hope there is not. It would be VERY ANNOYING to let anyone with a half > an ounce (15 mL) of brains gain root access to your system. As I said, to disable the rlogin capability completely, one had to modify the 'rsh host command' behaviour also. Of course I would be VERY ANNOYED, if I wouldnt be able to do rsh host dd of=/dev/nrxt0 anymore !!! But as its implemented now, it only forces me to retype the root password every time I want to rlogin from one server to the other, of course increasing the chances, that someone spots the passwort by looking over your shoulder... > > I apologize for the use of capitalization. me too... -- Marc Guenther ------------------------------------------------------------------------- Centrum fuer Informations | Leopoldstrasse 139 | Phone: +49 89 364 072 und Sprachverarbeitung | D-8000 M"unchen 40 | Fax: +49 89 361 6199 University of Munich | Germany | yoda@cis.uni-muenchen.de -------------------------------------------------------------------------
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs From: davida@guinness.huma.yorku.ca (David Aspinall) Subject: Re: Serial port drivers Message-ID: <CCyIEo.3G9@newshub.ccs.yorku.ca> Sender: news@newshub.ccs.yorku.ca (USENET News System) Organization: York University, Humanities Department References: <mJye0B1w165w@mindvox.phantom.com> Date: Mon, 6 Sep 1993 23:54:24 GMT I agree, even if an improved serial drive is "beta" it could not possibly be worse than the current driver. We had a heck of a time with the HP 4m printers until we figured out how to make the second parallel port active THE point is, there are many capable NEXT users who would happily test new driver code, and submit bug reports and be GRATEFUL for the new code (and the "effort" from NEXT), and all of this would cost NEXT .. nothing! All it would take is a "USE_AT_YOUR_OWN_RISK" directory on ftp.next.com. Is it really too much to ask? PS: if anyone from NEXT is reading this, I could use this serial driver ASAP, I'm tired of losing FAXes on my FAX Modem! artek@mindvox.phantom.com (Ardal Technologies) writes: : : I posted a message describing my problems and extreme frustration at the : constant system crashes associated with trying to use the serial ports on : a Intel system running NeXTSTEP (at ANY speed, including 2400). I posted : this message in the beginning of JULY. I subsequently received about 20 : letters saying different things, most of which came down to "please be : patient, a patch will be released mid-July." : : I in fact received these words from TWO SEPERATE people sending from : next.com. It is now SEPTEMBER, I have been VERY PATIENT, I have : controlled my anger and frustration and not given up on NS even if one of : the primary things I need it for is to run SLIP and use a modem to connect : to a company system from home. But it is now nearly 2 months after the : promised fix date. I keep hearing that the drivers have been fixed and : are now being tested. I put forth that NOTHING can possibly be worse than : the drivers that exist right now, and I am getting very, VERY tired of : being told that they are COMING REAL SOON NOW. : : I specifically purchased a Dell JAWS machine to evaluate NS after being : told that NS Intel was primarily developed on the JAWS system because I : wanted to be assured the maximum stability possible. This seems to have : been a waste of time and money. : : NeXT, new serial port drivers are HIGHLY OVERDUE... : : Sincerely, : Tired of the run-around -- David Aspinall ---------- Former-Former-NeXT Campus Consultant E-mail : cs911409@ariel.yorku.ca | I'd rather be NeXTMail: dave@ccs.yorku.ca | rich than stupid V-mail : (416) 663-4997 | -- Jack Handey
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 6 Sep 1993 21:14:59 -0400 Organization: Next Announcements Message-ID: <26gnag$1f2@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish Additions from: Greg Anderson (greg@afs.com) and Michael Pizolato (michael@afs.com)
Newsgroups: comp.sys.next.bugs From: alex@hal.rhein-main.de (Alexander Lehmann) Subject: Wrong time with DOS filesystem + fix (NS3.1 version) Message-ID: <CCxxxv.Ao@hal.rhein-main.de> Date: Mon, 6 Sep 1993 16:32:18 GMT I have posted the same article when I fixed this problemm in NS3.0, but since is in 3.1 also, here it is again. First of all, if you live on the westcoast and doen't care about DST, you can ignore this. I ran across a problem with the MSDOS filesystem in NS>=3.0. All files that are copied from a MSDOS disk onto the NeXT filesystems have a datestamp that is 9 hours newer that when read on a real (oh boy) MSDOS system. I checked into this problem an found out that the time are listed correctly, if PST is the current timezone. This could be considered a problem you have to live with rather than a bug, since the DOS driver is linked into the kernel and struct tm doesn't have a field for the timezone. On the other hand, it rather annoying to have the files suddenly beamed into the future. So I disassembled the dosfs_reloc program and found the functions that convert the MSDOS style times to UNIX times and vice versa. The problem is very simple to fix, since there only two addl # statements that add resp. subtract the second offset from GMT. I wrote a small perl program to do this automatically. (at the end of this post) If you want to apply this patch, first of all create a backup of /usr/filesystems/DOS.fs, since you might break something. (I don't think so, but who knows) You will have to change the $localtime variable at the start of the program to your timezone. e.g. GMT 0 PDT DST -7*3600 MET DST +2*3600 (that's where I live) then just execute 'patchmsd.pl' (this will not change anything, even if you are root). this will print the current time offset and complain, if it wants to change it. To actually change the offset, you have to become superuser and execute 'patchmsd.pl -p' If you have inserted a DOS disk since the last boot, you will have to reboot for the changes to become active (I think that dynamically loaded kernel programs are copied into memory and not paged readonly). After this procedure, DOS filetimes should be correct. If you are still using 3.0, you can apply the patch by doing 'patchmsd.pl -30' resp. 'patchmsd.pl -30 -p', but this in not tested, since I just moved to 3.1. To make life easy, the program will change the what string in the file to identify the timezone the driver is patched, this will look something like this PROGRAM:dosfs_reloc PROJECT:dos-32 DEVELOPER:root PATCHED: to GMT+2 Once again, I'd like to stress that it is important to create a backup copy of the filesystem driver and, of course, you should do this when nobody does any real work on the machine, since a kernel panic might occur, if something goes wrong. (It didn't happen with this fix, but you have to expect problems when dealing with the intestines of a system) And, of course, you're on your own, I feel not responsible when you screw up your box. O.K. here come the program: ------------------------------------------------------------------------------- #!/bin/sh # This is a shell archive (produced by shar 3.49) # To extract the files from this archive, save it to a file, remove # everything above the "!/bin/sh" line above, and type "sh file_name". # # made 09/06/1993 16:30 UTC by alex@hal # Source directory /alex/DOS.fs # # existing files will NOT be overwritten unless -c is specified # # This shar contains: # length mode name # ------ ---------- ------------------------------------------ # 2414 -rwxr-xr-x patchmsd.pl # # ============= patchmsd.pl ============== if test -f 'patchmsd.pl' -a X"$1" != X"-c"; then echo 'x - skipping patchmsd.pl (File already exists)' else echo 'x - extracting patchmsd.pl (Text)' sed 's/^X//' << 'SHAR_EOF' > 'patchmsd.pl' && #! /usr/local/bin/perl # # patchmsd.pl: patch the time offset for MSDOS disks # # $Id: patchmsd.pl,v 1.8 1993/09/06 16:30:13 alex Exp $ # # written by Alexander Lehmann <alex@hal.rhein-main.de> # # use this at your own risk # X if( $ARGV[0] eq "-30" ) { # offsets for NeXTStep 3.0 X shift; X $offset1=0x1e00+988; X $offset2=0x1b58+988; X $whatstr=0x6f94; } else { # offsets for NeXTStep 3.1 X $offset1=0x1e52+988; X $offset2=0x1bc0+988; X $whatstr=0x7114; } X $localtime=+2*3600; # CET DST (change this to suit your needs) X $fsfile="/usr/filesystems/DOS.fs/dosfs_reloc"; #$fsfile="dosfs_reloc"; X open(FILE,$fsfile) || die "Can't read $fsfile\n"; X seek(FILE,$offset1,0) || die "Can't seek to filepos\n"; read(FILE,$inp,6)==6 || die "Can't read data\n"; ($c,$v1)=unpack("Sl",$inp); X $c==0x0680 || die "not an addl # command\n"; X seek(FILE,$offset2,0) || die "Can't seek to filepos\n"; read(FILE,$inp,6)==6 || die "Can't read data\n"; ($c,$v2)=unpack("Sl",$inp); close FILE; X $c==0x0680 || die "not an addl # command\n"; X $v1==-$v2 || die "positive and negative time offsets don't aggree\n"; X print "time offset is set to GMT"; if($v2<0) { X print $v2/3600; } elsif($v2>0) { X print "+",$v2/3600; } X print "\n"; X if($v2==$localtime) { X print "MSDOS timeoffset agrees with local time\n"; X exit 0; } X if( int(@ARGV)!=1 || $ARGV[0] ne "-p" ) { X print "Use patchmsd.pl -p to patch the time offset\n"; X exit 0; } X open(FILE,"+>>$fsfile") || die "Can't write $fsfile\n"; X seek(FILE,$offset1+2,0) || die "Can't seek to filepos\n"; syswrite(FILE,pack("l",-$localtime),4) || die "Can't write data\n"; X seek(FILE,$offset2+2,0) || die "Can't seek to filepos\n"; syswrite(FILE,pack("l",$localtime),4) || die "Can't write data\n"; X seek(FILE,$whatstr,0) || die "Can't seek to filepos\n"; read(FILE,$str,1024)>0 || die "Can't read data\n"; X if(substr($str,0,4) ne "@(#)") { X die "Can't change what string\n"; } X if(($null=index($str,"\0"))!=$[) { X $str=substr($str,0,$null); } X if(($start=index($str,"BUILT"))!=$[-1 || ($start=index($str,"PATCHED"))!=$[-1) { X $len=length($str)-$built; X $pat="PATCHED: to GMT"; X if($localtime<0) { X $pat .= sprintf ("%d", $localtime/3600); X } elsif($localtime>0) { X $pat .= sprintf ("+%d", $localtime/3600); X } X X substr($str,$start,$len)="$pat\0"; X X seek(FILE,$whatstr,0) || die "Can't seek to filepos\n"; X print FILE $str; } X close FILE; X print "file successfully patched\n"; X SHAR_EOF chmod 0755 patchmsd.pl || echo 'restore of patchmsd.pl failed' Wc_c="`wc -c < 'patchmsd.pl'`" test 2414 -eq "$Wc_c" || echo 'patchmsd.pl: original size 2414, current size' "$Wc_c" fi exit 0 ------------------------------------------------------------------------------- You are free to distribute this program as you wish, but please leave my name in. One last thing, if someone can suggest a simple method for finding the current timezone in perl, I can change the program to automatically adjust to daylight saving time and other things, but the environment TZ is not always present and I didn't find any way to do it in perl (One could call localtime and gmtime and compare the results, but this seems rather complicated). That's about it, bye ... Alexander Lehmann -- Alexander Lehmann, alex@hal.rhein-main.de | "Wopp" or alexlehm@iti.informatik.th-darmstadt.de | - ( THHGTTG Pt.3 )
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs From: mark@cyantic.com (Mark T. Dornfeld) Subject: Re: Serial port drivers Organization: CYANTIC Systems Date: Tue, 07 Sep 1993 14:09:03 GMT Message-ID: <1993Sep07.140903.10205@cyantic.com> Keywords: still broken References: <mJye0B1w165w@mindvox.phantom.com> In article <mJye0B1w165w@mindvox.phantom.com> artek@mindvox.phantom.com (Ardal Technologies) writes: > >I posted a message describing my problems and extreme frustration at the >constant system crashes associated with trying to use the serial ports on >a Intel system running NeXTSTEP (at ANY speed, including 2400). I posted >this message in the beginning of JULY. I subsequently received about 20 >letters saying different things, most of which came down to "please be >patient, a patch will be released mid-July." It looks like the fix is long in coming, and when it does, there is no guarantee that it will be up to par. I have always avoided pushing PC serial ports too far under any operating system. They are too limited for high speed transfers. While this may avoid the real problem, I have tried to use outboard serial ports whenever possible, either with dedicated hardware such as Digiboard or Computone offer, or through terminal/communications servers. The least expensive communications box I have seen on the market recently is the Net Hopper from Sea Change. I know it handles PPP, but I don't think it does SLIP. The NetBlazer from Telebit handles both. I know this is an extra, large expense for the single user but small workgroups could profit from putting their serial connections on boxes like these. Xylogics, Xyplex, and quite a few other companies have really nice hardware that offloads the computer from communications duties and puts the equipment on the Ethernet where it can do the most good in a work group. Any hardware manufacturers want to take up the challenge for an under-$1000 comm server? -- Mark T. Dornfeld, CYANTIC Systems Voice: (416) 234-9048 101 Subway Crescent Suite 2103 Facsimile: (416) 234-0477 Etobicoke, Ontario, M9B 6K4 CANADA Email: mark@cyantic.com
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs From: ian@mindvox.phantom.com (Ian Bainbridge) Subject: Re: Serial port drivers Message-ID: <X3Li0B1w165w@mindvox.phantom.com> Originator: ian@mindvox Keywords: still broken Sender: news@mindvox.phantom.com Organization: [Phantom Access] / the MindVox system References: <1993Sep07.140903.10205@cyantic.com> Date: Tue, 7 Sep 1993 16:24:08 GMT mark@cyantic.com (Mark T. Dornfeld) writes: > >a Intel system running NeXTSTEP (at ANY speed, including 2400). I posted > >this message in the beginning of JULY. I subsequently received about 20 > >letters saying different things, most of which came down to "please be > >patient, a patch will be released mid-July." > > It looks like the fix is long in coming, and when it does, there is no > guarantee that it will be up to par. > > I have always avoided pushing PC serial ports too far under any operating > system. They are too limited for high speed transfers. While this may > avoid the real problem, I have tried to use outboard serial ports whenever > possible, either with dedicated hardware such as Digiboard or Computone > offer, or through terminal/communications servers. Yes, true, BUT ... there aren't any drivers to support any of these cards, unless I have somehow missed that option every single time. > The least expensive communications box I have seen on the market recently > is the Net Hopper from Sea Change. I know it handles PPP, but I don't > think it does SLIP. The NetBlazer from Telebit handles both. > > I know this is an extra, large expense for the single user but small > workgroups could profit from putting their serial connections on boxes like > these. Xylogics is quite good, Digicom is all right, there are many excellent terminal servers on the market. However, to suggest that in order to use a temrinal program or run a SLIP on a personal NeXT system, one should have to buy an ethernet card AND a terminal server, is nice, but of little practical use in that place called "the real world" where most people would like to just plug in a modem and not have the system grind to a halt. ian ################# @ #Ian Bainbridge # mindvox. # ############################################### phantom. # I am not responsible for my opinons, I don't know or care! # com ###############################################################
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: ian@mindvox.phantom.com (Ian Bainbridge) Subject: Re: New serial drivers in this century? Message-ID: <69Li0B2w165w@mindvox.phantom.com> Originator: ian@mindvox Sender: news@mindvox.phantom.com Organization: [Phantom Access] / the MindVox system References: <sean-060993161441@128.187.73.66> Date: Tue, 7 Sep 1993 16:27:52 GMT sean@digaudio.byu.edu (Sean Luke) writes: > In article <FH3F0B3w165w@mindvox.phantom.com>, alibaba@mindvox.phantom.com > (Nick Mordanzo) wrote: > > > > Yeah but does Linux have those pretty, shaded 3-d icons to look at? > > > > So you need to run fsck 10 times a day, its all a frustration threshold > > test, to see how much [----] you can put up with before you say [----] this > > man and just stop booting the nexstep partition since the msdos one works > > just fine, sans artwork. > > Ah. Another person who doesn't know what he's talking about when it comes > to NeXTSTEP. Sad that with the move to Intel (and bigger markets) we now > have to come face to face with huge numbers of ignorant people. A veritable madman, all high-end, haute cuisine (to borrow a term from PC World) workstations crash every hour when a modem is plugged into them. Obviously this ignorant fool doesn't understand that. All that junk like uucp, tip and cu should be deleted from the distribution media and kermit and slip crippled to make sure nobody using white hardware will ever be able to run them. ian ################# @ #Ian Bainbridge # mindvox. # ############################################### phantom. # I am not responsible for my opinons, I don't know or care! # com ###############################################################
Newsgroups: comp.sys.next.bugs From: raf@shell.portal.com (Man Wei Tam) Subject: 3.1 feels a little 'stiff' Message-ID: <CCztp8.EBx@unix.portal.com> Sender: news@unix.portal.com Organization: Portal Communications Company -- 408/973-9111 (voice) 408/973-8091 (data) Date: Tue, 7 Sep 1993 16:55:53 GMT Has anybody felt that 3.1 on black hardwar feels a little 'stiff' - much like a new pair of shoes. It definately seems to respond quite differently from 3.0. Sometimes quite sluggish in fact, other times it suddendly zips along. Strange. Maybe I'm just going insane. Brian Leake, Fox River Financial Resources, Inc.
From: u288869@uebung3.rz.fh-reutlingen.de (Frank Martin Siegert) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: Re: New serial drivers in this century? Date: 7 Sep 1993 17:00:20 GMT Organization: Fachhochschule fuer Technik und Wirtschaft, Reutlingen, Germany Message-ID: <26ien4$h6b@infoserv.zdv.uni-tuebingen.de> References: <sean-060993161441@128.187.73.66> <69Li0B2w165w@mindvox.phantom.com> Keywords: SERIAL DRIVER CRASH BURN Maybe someone from NeXT could give us the *REAL* release date for the serial drivers. C'mon NeXT, it cannot be so hard to write this stuff. I really like NeXTSTEP but how should I recommend an OS that crash-and burn on serial transfer and sound. If your software people cannot get it right, maybe releasing the driver source to public could be a way? Even UNSUPPORTED beta drivers are better than the current crap. Frank Siegert
From: madler@cco.caltech.edu (Mark Adler) Newsgroups: comp.sys.next.bugs Subject: Re: 3.1 feels a little 'stiff' Date: 7 Sep 1993 21:02:20 GMT Organization: California Institute of Technology, Pasadena Message-ID: <26isssINN91e@gap.caltech.edu> References: <CCztp8.EBx@unix.portal.com> I noticed an odd thing perhaps related to that. There is a Solitaire 1.01 recompiled fat on 3.1, which is "stiff" when running on 3.0! The old Solitaire would move the cards smoothly, whereas the new fat Solitaire moves them jerklily. It is claimed that it is a simple recompile of the old source, so something has changed in 3.1 that reaches all the way into 3.1 executables that run on 3.0. Mark Adler madler@cco.caltech.edu
From: lee@daruma.zoo.duke.edu (Lee Altenberg) Newsgroups: comp.sys.next.bugs Subject: EtherExpress16 driver: only 8 bit? Message-ID: <20118@news.duke.edu> Date: 8 Sep 93 00:23:17 GMT Sender: news@news.duke.edu Organization: Duke University Zoology Dept.; Durham, N.C. I just installed an Intel EtherExpress16 twisted pair network card in a Gateway2000 4DX2 66-V. Using Configure.app I set the network driver to say: Port Addresses 16 bytes at 0x300 and IRQ Levels 10 But when NS/I 3.1 boots up, it says a couple of times in the startup messages: EtherExpress16 8 bit only Is this proper? Has anyone else had (or NOT had) this experience with the EtherExpress16 and NS/I 3.1? Would there be some problem with the card or the expansion slot that is causing it to come up as 8 bit and not 16 bit? Is the NS/I driver for the Intel EtherExpress16 only capable of running it as 8 bit? Thanks for any help. Lee Altenberg altenber@acpub.duke.edu
From: david@jaffe.com Newsgroups: comp.sys.next.bugs Subject: 3.1 problems accessing NeXT bus Date: 8 Sep 1993 00:58:27 GMT Organization: University of California, Berkeley Message-ID: <26janj$p5f@agate.berkeley.edu> I'm having problems with my program's detecting the presence of a NeXTbus card under NeXTstep 3.1 (pre-release for black hardware (obviously)). The problem is intermittent. It worked fine under 3.0 and 2.0. If anyone has had this problem and found a work-around, please contact me. I can provide more details if necessary, including sample code that fails. Please send your reply to david@jaffe.com, as I don't read the net regularly. David Jaffe
Newsgroups: comp.sys.next.bugs From: preuss@netcom.com (Peter Preuss) Subject: Re: EtherExpress16 driver: only 8 bit? Message-ID: <preussCD0sM0.Azt@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) References: <20118@news.duke.edu> Date: Wed, 8 Sep 1993 05:29:59 GMT Lee Altenberg (lee@daruma.zoo.duke.edu) wrote: : I just installed an Intel EtherExpress16 twisted pair network : card in a Gateway2000 4DX2 66-V. Using Configure.app I set : the network driver to say: [...] : But when NS/I 3.1 boots up, it says a couple of times in the : startup messages: : EtherExpress16 8 bit only : Is this proper? [...] NeXT posted an improved driver (performance, support of later revisions of the board) to ftp.next.com (NextAnwers). * EtherExpressDriver.41190.1 93-08-26 1286 EtherExpressDriver.pkg 93-08-26 1285 EtherExpressDriver.ReadMe 93-08-26 Go get it! Peter. -- preuss@futon.sfsu.edu San Francisco State University
From: jmm@king.econ.lsa.umich.edu (Jeffrey K. MacKie-Mason) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: NeXT OS (3.1) doesn't get Norwegian time zone right Date: 8 Sep 1993 07:25:24 GMT Organization: University of Oslo Distribution: world Message-ID: <26k1d4$44d@hermod.uio.no> Keywords: clock, time zone I have just moved to Norway. I find that when I set my clock to local time (using the Preferences panel), it puts me in time zone GMT+1, but during daylight savings time it should be GMT+2. This has prevented me from being authenticated to an afs cell in another time zone that thinks my clock is off by an hour. Anyone know a fix? -- Prof. Jeff MacKie-Mason internet: jmm@umich.edu Dept. of Economics bitnet: usergc76@umichum Univ. of Michigan phone: 313-764-7438 Ann Arbor, MI 48109-1220 fax: 313-763-9181
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: rtbrunne@iiic.ethz.ch (Ralf Thomas Brunner) Subject: Re: New serial drivers in this century? Message-ID: <1993Sep8.100947.24944@neptune.inf.ethz.ch> Summary: Serial port driver Keywords: serial port Sender: rtbrunne@iiic.ethz.ch Organization: Dept. Informatik, Swiss Federal Institute of Technology (ETH), Zurich, CH References: <CCoCw9.DLB@well.sf.ca.us> <FH3F0B3w165w@mindvox.phantom.com> Date: Wed, 8 Sep 1993 10:09:47 GMT > The title says most of it. They were coming in mid-July, since this is > September I guess that SURPRISE, they are a little late. Since mid-July I > have been actively dissuading people who have any interest in using a > modem or ever hope to establish a SLIP link, from getting anywhere near > NS/FIP. The new serial driver is on ftp.next.com. --------------------------------------------------------------------------- Irrationality is the square root of all evil. Ralf T. Brunner - Douglas Hofstadter rtbrunne@iiic.ethz.ch ---------------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware From: ed@cubx.com (Erik Dasque) Subject: Re: EtherExpress16 driver: only 8 bit? Message-ID: <1993Sep8.113036.18037@cubx.com> Sender: news@cubx.com Organization: Cub'x Systemes - Rueil Malmaison, France. References: <20118@news.duke.edu> Date: Wed, 8 Sep 1993 11:30:36 GMT In article <20118@news.duke.edu> lee@daruma.zoo.duke.edu (Lee Altenberg) writes: > I just installed an Intel EtherExpress16 twisted pair network > card in a Gateway2000 4DX2 66-V. Using Configure.app I set > the network driver to say: > > Port Addresses > 16 bytes at 0x300 > > and > > IRQ Levels > 10 > > But when NS/I 3.1 boots up, it says a couple of times in the > startup messages: > > EtherExpress16 8 bit only > > Is this proper? > Has anyone else had (or NOT had) this experience with the EtherExpress16 > and NS/I 3.1? > Would there be some problem with the card or the expansion slot that is > causing it to come up as 8 bit and not 16 bit? > Is the NS/I driver for the Intel EtherExpress16 only capable of running > it as 8 bit? > > Thanks for any help. > > Lee Altenberg > altenber@acpub.duke.edu Using your SoftSet program under DOS, you'll need to re-map the cache RAM to an un-used space. The Intel card seems to have 32 Kb of RAM which is wrongly mapped by default (your mileage may vary, mine did). Booting with 16 bit ethernet seems to speed things up, a little bit. Ed -- Erik Dasque "The French Guy" Cub'x Systemes only SMALL NeXTMAIL pleeeeease... ed@cubx.com It all started 2 full back-up ago...
Newsgroups: comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs From: jmbreuer@trek.nbg.sub.org Subject: Re: NeXSTEP Intel and SERIAL PORT DRIVER == JOKE Message-ID: <1993Sep7.134921.1503@trek.nbg.sub.org> Organization: private References: <LTo46B3w165w@mindvox.phantom.com> Date: Tue, 7 Sep 1993 13:49:21 GMT chrisl@mindvox.phantom.com (Chris Lesher) writes: >Having spent more hours than I care to count exposed to the Windows >environment at work, and through an extended patronage of MindVox which >seems to be something of a NeXT mecca full of converts and true believers, >when the time came for me to purchase a new machine this fall for in-house >evaluation and future planning, I was quite excited by the prospects of >NeXTSTEP technology. > After arranging to view some of the NeXT's at Vox I came away with >a strange feeling that perhaps I should have listened to. I was stunned >by the user environment and in an office full of machinery the only only >ones that seemed to have any active use as workstations were two NeXT's, >and a Super NES ;-). But for the life of me, other than the obvious >observation that a lot of people smoke pot in a closed room, I was unable >to figure out what anybody there used the NeXT's for other than $10,000 >paper weights which served as terminals to be hooked through an ethernet >to the servers, all of which were dull, dreary, with the monitors turned >off, but every single machine was some kind of Sun. In fact MindVox which >started on the NeXT had moved away from using them for anything except >fancy terminals as quickly as they could. > > But no..... I listened to the advice of the people hanging around, >read and re-read the evangelists postings and sunk nearly $10,000 of my >company's money into a NeXTSTEP eval machine from Dell. > > And what I now proudly possess is my very own $10,000 paperweight. > I plug it into the ethernet, RDP exception #6, the machine hangs every >time within a matter of hours. I plug in a modem, guess what, oh SORRY, >the serial port drivers have a few problems. I NEEDED A MACHINE THAT CAN >COMMUNICATE WITH OTHER MACHINES. A STAND-ALONE SYSTEM IS NEARLY WORTHLESS >TO ME AND RIGHT NOW, THAT'S WHAT I HAVE, BECAUSE ANY TIME I TRY TO PLUG IT >INTO A NETWORK OR CONNECT A MODEM, IT HANGS. *EVERY SINGLE TIME* To >suggest that the solution is waiting for NS3.2 to arrive in the 3rd >quarter, or 4th quarter, or whenever it gets here, is absolutely >preposterous. I have paid for something which does NOT work. For all its >garbage, Windows DOES work and rarely crashes and right now I'm using a What exactly does "rarely" for you? Once every half an hour? :-| I once TRIED to do some "amateur" DTP using Windows (and the two thousand utilities you need to run it). Oh, no... >486dx/33 to get my work done, while I look at the NeXT and realize what I >should have known in the first place. The NeXT is a beautiful >paper-weight, which is championed by the sort of people who have SGI >Indigo^2's sitting in their houses because "they're so cool man", have >wardrobes from Armani, cars from Porsche, and make a living selling ATTITUDE. > > In a word, that's the NeXT, because it certainly doesn't do >anything like FUNCTION as expected. When I brought these problems back to >the true believers I came away with the tremendous wisdom of "well, I >dunno, right now I just use kermit on the SGI or tip out" followed by >"NeXTSTEP is pretty to look at, but ya know, its like whatever, the Apple >][+ pretty much did everything I wanted a computer to do. It had a >terminal program called AE pro, and a word processor. Everything else are >neat toys to play with." > > BINGO. So now I'm using Windows. And looking at OS/2. > > NeXT, this is RIDICULOUS. Kindly assign one or two persons to >take the 3 hours needed to fix your serial port and ethernet drivers and >allow those of us who have invested into what you and your evangelists are >espousing, to at least make use of what we have purchased. There is no >way I could ever recommend NeXTSTEP to our purchasing department, I have >this sinking feeling I'd be left holding the bag, a feeling many people >who purchased black hardware in 1993 must be very familiar with. > > chrisl@phantom.com Hmmm... maybe those people [NeXT Inc.] should have kept on making the real thing. I was quite upset with DOS/Windoze, and finally replaced my I-Blame-Myself-compatible equipment with a NeXTcube w/ dimension. And, whoa!, the machine stayed up for one week, two weeks, three weeks, a month, half a year... and, in fact, is still running and doing anything I need and want to do. I do not experience any strange problems with connecting the cube to about any Ethernet Network or modem, (how else could I write this letter), and I still have not seen any GUI comparable to NS. The problem mentioned above comes down to the basic philosophy of buying computers: Either you try to stay "in fashion" (good luck to your bank account or wherever you get your money from), or you try and find a computer that does anything you want it to do with the speed you need it being done, and do not really need to keep up to date. I, personally, chose the second option, and I cannot imagine replacing the Cube with anything else. It does what I want it to do, and it does not need hours of personal care. Have you tried to configure, say, an IBM-Comp. to run one of these wonderful memory managers (like QEMM, which is not bad at all) and something weird like a CD-ROM driver to have more than 450 KB of base memory free (which Windoze desperatly needs to run)? Yes, it works, but good luck, take your time, and don't ever dare to add some more peripherals which need drivers... or take the time again. If DOS/Windows does everything you want your computer to do, fine! I don't try to persuade anyone to turn away from a working equipment. I just want to tell those people who do want to work with their computers (instead of doing a full-time-job configuring them) that I found a solution which works fine for me. I am not pro-NeXT (well, at least not in the extreme), I just don't like equipment that does not work, imagine a car sold with the following instructions: Yes, the new engine can be put in "enhanced mode", which gives you some hundred percent more performance, but it also uses a different kind of fuel, which is very difficult to get (although it really is not); and the other parts of the car were not really built to facilitate the engine being run in enhanced mode. Therefore we recommend you to run your engine in "compatibility mode". ... that is about the reason why I am "anti-IBM". Again, this is not meant to be a flame, I would just like to put things a bit differently: NeXT did make a mistake, that's right, they moved to unsuitable hardware for NS and are now (apparently) not able to handle it. IBM somehow managed to sell its "it-just-might-work...perhaps"- Computers to about everyone... and now you blame NeXT for not being able to cope with old-fashioned architecture restrictions. Just wanted to say that, Joe -- | Joachim Breuer | Usenet: | | Weichselgartenstrasse 34a | jmbreuer@trek.nbg.sub.org | | 91301 Forchheim +---------------------------+ | Germany | Data: +49 9191 33915 |
Newsgroups: comp.sys.next.bugs From: mmanning@agent99 (Michael Manning) Subject: Re: Memory leak in DO... still in 3.1? Message-ID: <1993Sep8.210723.26378@il.us.swissbank.com> Sender: root@il.us.swissbank.com (Operator) Organization: Swiss Bank Corporation CM&T Division References: <1993Aug24.231432.5503@instep.wimsey.bc.ca> Date: Wed, 8 Sep 1993 21:07:23 GMT brad@instep.wimsey.bc.ca writes > > DISTRIBUTED OBJECTS MEMORY LEAK in 3.0 ... still in 3.1? > Yes it is. - Michael mmanning@its.com
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: New serial drivers in this century? Message-ID: <Sep8.215437.19753@acs.ucalgary.ca> Date: Wed, 8 Sep 1993 21:54:37 GMT References: <sean-060993161441@128.187.73.66> <69Li0B2w165w@mindvox.phantom.com> <26ien4$h6b@infoserv.zdv.uni-tuebingen.de> Organization: The University of Calgary, Alberta Keywords: SERIAL DRIVER CRASH BURN > Maybe someone from NeXT could give us the *REAL* release date > for the serial drivers. C'mon NeXT, it cannot be so hard to > write this stuff. Maybe you could check before writing? You posted this message AFTER the new drivers became available on ftp.next.com. Can we just end this thread now? (... or at least start a new one describing quirks of the new driver, should that be necessary). > I really like NeXTSTEP but how should I recommend an OS that > crash-and burn on serial transfer and sound. If your software > people cannot get it right, maybe releasing the driver source > to public could be a way? The problems associated with sound are hardware conflicts with other devices and problems with the ISA bus. They are NOT NeXT's fault. Many customers (me included) can get a ton of useful work done without either serial or sound support while waiting for the final drivers. Would I recommend NeXTSTEP to people who need the support NOW? No, although with the new serial drivers I should be able to reverse that decision. Most organizations are already committed to NeXTSTEP and have black hardware to support UUCP links and such, or are just beginning to evaluate NeXTSTEP as a development platform and can do without the drivers until they became available. NeXTSTEP is not yet being advertised as the ideal hobbyist / home user / desktop environment, but should be up to the task by the time it is being pushed into those markets. > Even UNSUPPORTED beta drivers are better than the current crap. ... and customers who expressed a need for the beta drivers should have been able to get them from NeXT. We were able to do so, as were a number of NeXT's larger customers to whom it was an issue. I can definitely understand NeXT not wanting to let beta drivers out on the internet, as they'd discover people using them years later (don't scoff, it happens... we ran into one fellow running version 0.97 of the Mac operating system a while back). -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs Subject: Re: New serial drivers i From: damon.cooper@canrem.com (Damon Cooper) Distribution: world Message-ID: <60.690.4901.0N1834FF@canrem.com> References: <Sep8.215437.19753@acs.ucalgary.ca> Date: Wed, 8 Sep 93 22:36:00 -0400 Organization: CRS Online (Toronto, Ontario) For those of you awaiting new drivers... >Hello, > >The NEXTSTEP 3.1 Intel Serial Port Driver is now available from >NeXTanswers. The serial driver is available via anonymous ftp from >ftp.next.com under the file names: > >/pub/NeXTanswers/CompressedFiles/Drivers/ > 1326_SerialPortDriver.ReadMe.compressed > and 1327_SerialPortDriver.pkg.compressed > >To retrieve the files via email, send an email message to >"nextanswers@next.com" with the subject of "1326 1327". > >Conrad Geiger >NeXT Damon F. Cooper EDS Canada --- * UniQWK v2.1 * The Solution for Multilingual Messages
Newsgroups: comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs From: dav@well.sf.ca.us (Paul Davilon) Subject: Re: NeXSTEP Intel and SERIAL PORT DRIVER == JOKE Organization: The Whole Earth 'Lectronic Link, Sausalito, CA Date: Thu, 9 Sep 1993 05:59:13 GMT Message-ID: <CD2oMq.8o5@well.sf.ca.us> Followup-To: comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs References: <LTo46B3w165w@mindvox.phantom.com> <1993Sep7.134921.1503@trek.nbg.sub.org> Sender: news@well.sf.ca.us jmbreuer@trek.nbg.sub.org wrote: : chrisl@mindvox.phantom.com (Chris Lesher) writes: : >Having spent more hours than I care to count exposed to the Windows : >environment at work, and through an extended patronage of MindVox which : >seems to be something of a NeXT mecca full of converts and true believers, : >when the time came for me to purchase a new machine this fall for in-house : >evaluation and future planning, I was quite excited by the prospects of : >NeXTSTEP technology. : > After arranging to view some of the NeXT's at Vox I came away with : >a strange feeling that perhaps I should have listened to. I was stunned : >by the user environment and in an office full of machinery the only only : >ones that seemed to have any active use as workstations were two NeXT's, : >and a Super NES ;-). But for the life of me, other than the obvious : >observation that a lot of people smoke pot in a closed room, I was unable : >to figure out what anybody there used the NeXT's for other than $10,000 : >paper weights which served as terminals to be hooked through an ethernet : >to the servers, all of which were dull, dreary, with the monitors turned : >off, but every single machine was some kind of Sun. In fact MindVox which : >started on the NeXT had moved away from using them for anything except : >fancy terminals as quickly as they could. : > : > But no..... I listened to the advice of the people hanging around, : >read and re-read the evangelists postings and sunk nearly $10,000 of my : >company's money into a NeXTSTEP eval machine from Dell. : > : > And what I now proudly possess is my very own $10,000 paperweight. : > I plug it into the ethernet, RDP exception #6, the machine hangs every : >time within a matter of hours. I plug in a modem, guess what, oh SORRY, : >the serial port drivers have a few problems. I NEEDED A MACHINE THAT CAN : >COMMUNICATE WITH OTHER MACHINES. A STAND-ALONE SYSTEM IS NEARLY WORTHLESS : >TO ME AND RIGHT NOW, THAT'S WHAT I HAVE, BECAUSE ANY TIME I TRY TO PLUG IT : >INTO A NETWORK OR CONNECT A MODEM, IT HANGS. *EVERY SINGLE TIME* To : >suggest that the solution is waiting for NS3.2 to arrive in the 3rd : >quarter, or 4th quarter, or whenever it gets here, is absolutely : >preposterous. I have paid for something which does NOT work. For all its : >garbage, Windows DOES work and rarely crashes and right now I'm using a : What exactly does "rarely" for you? Once every half an hour? :-| : I once TRIED to do some "amateur" DTP using Windows (and the two : thousand utilities you need to run it). Oh, no... : >486dx/33 to get my work done, while I look at the NeXT and realize what I : >should have known in the first place. The NeXT is a beautiful : >paper-weight, which is championed by the sort of people who have SGI : >Indigo^2's sitting in their houses because "they're so cool man", have : >wardrobes from Armani, cars from Porsche, and make a living selling ATTITUDE. : > : > In a word, that's the NeXT, because it certainly doesn't do : >anything like FUNCTION as expected. When I brought these problems back to : >the true believers I came away with the tremendous wisdom of "well, I : >dunno, right now I just use kermit on the SGI or tip out" followed by : >"NeXTSTEP is pretty to look at, but ya know, its like whatever, the Apple : >][+ pretty much did everything I wanted a computer to do. It had a : >terminal program called AE pro, and a word processor. Everything else are : >neat toys to play with." : > : > BINGO. So now I'm using Windows. And looking at OS/2. : > : > NeXT, this is RIDICULOUS. Kindly assign one or two persons to : >take the 3 hours needed to fix your serial port and ethernet drivers and : >allow those of us who have invested into what you and your evangelists are : >espousing, to at least make use of what we have purchased. There is no : >way I could ever recommend NeXTSTEP to our purchasing department, I have : >this sinking feeling I'd be left holding the bag, a feeling many people : >who purchased black hardware in 1993 must be very familiar with. : > : > chrisl@phantom.com : Hmmm... maybe those people [NeXT Inc.] should have kept on making the : real thing. : I was quite upset with DOS/Windoze, and finally replaced my : I-Blame-Myself-compatible equipment with a NeXTcube w/ dimension. : And, whoa!, the machine stayed up for one week, two weeks, three : weeks, a month, half a year... and, in fact, is still running and : doing anything I need and want to do. : I do not experience any strange problems with connecting the cube to : about any Ethernet Network or modem, (how else could I write this : letter), and I still have not seen any GUI comparable to NS. : The problem mentioned above comes down to the basic philosophy of : buying computers: Either you try to stay "in fashion" (good luck to : your bank account or wherever you get your money from), or you try and : find a computer that does anything you want it to do with the speed : you need it being done, and do not really need to keep up to date. I, : personally, chose the second option, and I cannot imagine replacing : the Cube with anything else. It does what I want it to do, and it does : not need hours of personal care. Have you tried to configure, say, an : IBM-Comp. to run one of these wonderful memory managers (like QEMM, : which is not bad at all) and something weird like a CD-ROM driver to : have more than 450 KB of base memory free (which Windoze desperatly : needs to run)? Yes, it works, but good luck, take your time, and don't : ever dare to add some more peripherals which need drivers... or take : the time again. : If DOS/Windows does everything you want your computer to do, fine! : I don't try to persuade anyone to turn away from a working equipment. : I just want to tell those people who do want to work with their : computers (instead of doing a full-time-job configuring them) that I : found a solution which works fine for me. : I am not pro-NeXT (well, at least not in the extreme), I just don't like : equipment that does not work, imagine a car sold with the following : instructions: : Yes, the new engine can be put in "enhanced mode", which : gives you some hundred percent more performance, but it : also uses a different kind of fuel, which is very difficult : to get (although it really is not); and the other parts of : the car were not really built to facilitate the engine being : run in enhanced mode. Therefore we recommend you to run your : engine in "compatibility mode". : ... that is about the reason why I am "anti-IBM". : Again, this is not meant to be a flame, I would just like to put : things a bit differently: : NeXT did make a mistake, that's right, they moved to unsuitable : hardware for NS and are now (apparently) not able to handle it. : IBM somehow managed to sell its "it-just-might-work...perhaps"- : Computers to about everyone... and now you blame NeXT for not : being able to cope with old-fashioned architecture restrictions. : Just wanted to say that, : Joe : -- : | Joachim Breuer | Usenet: | : | Weichselgartenstrasse 34a | jmbreuer@trek.nbg.sub.org | : | 91301 Forchheim +---------------------------+ : | Germany | Data: +49 9191 33915 |
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Message-ID: <1993Sep08.3@corona.com> Date: Mon, 08 Sep 1993 23:11:00 PDT Newsgroups: comp.sys.next.bugs Subject: Edit/Gdb loses double precision When the variable browser in Edit/Gdb displays the value for a double, it loses precision. It appears to convert the value to a float before displaying. PRINT will display the correct value in the gdb terminal window. So if you have more than 6 digits of precision in a double, don't trust what you see in the browser...PRINT it if you need to see full precision. ________________________________________________________ NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: 3.1 feels a little 'stiff' Message-ID: <Sep9.140516.58665@acs.ucalgary.ca> Date: Thu, 9 Sep 1993 14:05:16 GMT References: <CCztp8.EBx@unix.portal.com> <26isssINN91e@gap.caltech.edu> Organization: The University of Calgary, Alberta > I noticed an odd thing perhaps related to that. There is a > Solitaire 1.01 recompiled fat on 3.1, which is "stiff" when > running on 3.0! The old Solitaire would move the cards > smoothly, whereas the new fat Solitaire moves them jerklily. Sigh. Sorry to hear that. It doesn't seem to be the case on a mono system, but it DOES seem to be on color systems. > It is claimed that it is a simple recompile of the old source, > so something has changed in 3.1 that reaches all the way into > 3.1 executables that run on 3.0. It actually wasn't a "simple recompile". The Intel version was a simple recompile of the motorola version, but the motorola version had one change from version 1.0: I now use NeXTSTEP's drag-and-drop support rather than rolling my own. The net effect: It makes better demo code, and you can drag cards outside of the Solitaire window (heck, with changes to the code you can drag cards from one Solitaire game to another and cheat!). It also appears to have a performance impact. I'd argue, though, that the drag-and-drop mechanism was the right thing to do. -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs From: ian_stewart@pyrian.com (Ian H. Stewart) Subject: Re: Serial Ports Driver Bug Fix? Message-ID: <CD0zLH.11v@pyrian.com> Sender: ian@pyrian.com (Ian H. Stewart) Organization: ABC Company. We specialize in classic chewing gum! References: <26alji$6o8@uropax.contrib.de> Date: Wed, 8 Sep 1993 08:00:52 GMT You should see it on the ftp/mail site at NeXT in the a day or so. It is done! ian In article <26alji$6o8@uropax.contrib.de> suckow@uropax.contrib.de (Ralf Suckow) writes: > Does anybody know, when the serial ports > driver problem will be fixed for NS/FIP 3.1? > > Will it be available for 3.1 Evaluation Kit users > even after release of 3.2? > > Any information? > Any rumors? > > Thanks, > Ralf > -- > Ralf Suckow, Berlin | > suckow@contrib.de | Do you think it's difficult to speak Russian? > Contributed Software | Every Moscow kid aged 5 years speaks it perfectly. > only delivers my mail.|
Newsgroups: comp.sys.next.bugs From: Klaus@ideal.muc.de (Klaus Bscheid) Subject: Re: NeXT OS (3.1) doesn't get Norwegian time zone right Message-ID: <1993Sep8.174005.4028@ideal.muc.de> Sender: me@ideal.muc.de (Klaus Bscheid) Organization: Eversmile References: <26k1d4$44d@hermod.uio.no> Date: Wed, 8 Sep 1993 17:40:05 GMT In article <26k1d4$44d@hermod.uio.no> jmm@king.econ.lsa.umich.edu (Jeffrey K. MacKie-Mason) writes: > > I have just moved to Norway. I find that when I set my clock to local time > (using the Preferences panel), it puts me in time zone GMT+1, but during > daylight savings time it should be GMT+2. This has prevented me from > being authenticated to an afs cell in another time zone that thinks my clock is > off by an hour. > > Anyone know a fix? > > -- > Prof. Jeff MacKie-Mason internet: jmm@umich.edu > Dept. of Economics bitnet: usergc76@umichum > Univ. of Michigan phone: 313-764-7438 > Ann Arbor, MI 48109-1220 fax: 313-763-9181 If Norway is MET (GMT+1). Try MET in Preferences and you will automatically get into DST. If you won't find MET in Preferences then ask if the patch which is available for NS 3.0 will work with NS 3.1. If you need it,I have the 3.0 patch somewhere on my HD. klaus -- ____________________________________________________________ Klaus Bscheid, klaus@ideal.muc.de, voice/fax: +49 89 3103829 Germany, 85716 Unterschleissheim, Sportplatzstrasse 7
Newsgroups: comp.sys.next.bugs From: alibaba@mindvox.phantom.com (Nick Mordanzo) Subject: Serial Ports we're backkkkkk! Message-ID: <TDFm0B1w165w@mindvox.phantom.com> Originator: alibaba@mindvox Sender: news@mindvox.phantom.com Organization: [Phantom Access] / the MindVox system Date: Thu, 9 Sep 1993 17:49:52 GMT Dudes at NeXT, first off thanks for the new serial drivers, I understand that you guys probably have angry-crazy-tired StevenGodJobs chasing you around with a whip and screaming FASTER FASTER!!!!!! and using them for 3 days has made life mucho eaisier. Maybe its just me and maybe it was just two coincidences, but......... when I used kermit (which is what I'm running), the logs get littered up with streams of these: Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace last message repeated 2 times Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) Hundreds and hundreds of times and then THE BAD THING happens and I get system Panic, rdp exception 6 and can only restart with a cold boot and waiting 5 minutes for the hard disk to fsck. Which is what used to happen with the old serial drivers. I'm running the serial port (a) on a 486/66 at 38400, which works ok under windoze, os/2 and Linux, but I remember when I had a 486/33 windoze and os/2 would both drop data, only Linux worked as it does now. Is it a bad idea to run the serial ports at 38.4? I can live with 19.2 if I need to, even if the machine does crash every 2 days I can live with that too its the once every hour that used to get to me, so whatever you did thanks for listening to us bitch, whine and complain and at least releasing an interim release. I just wanted to let you all know that some quirks still exist, at least when you run the port at 38.4 and connect to a v32.bis modem at the other end. $%$%$%$%$%$%$% ($) Ali Baba ($) %$%$%$%$%$%$%$
From: giddings@sadie.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Cube boots thinking HD is CD-ROM! Date: 9 Sep 1993 19:03:40 GMT Organization: Division of Information Technology Distribution: world Message-ID: <26numc$9bm@news.doit.wisc.edu> Keywords: help Hello, We have a Cube with an internal seagate SCSI drive that was just upgraded to 3.1. After the upgrade, the cube booted fine and everything seemed to work. Then, someone added the CD-ROM drive to the exports list using NFS Manager, and rebooted with the NEXTSTEP developer in the drive. Now, the computer thinks the hard drive (/dev/rsd0a) is a CD-ROM (i.e. we can't write to it at all), even when the CD-ROM is completely disconnected as well as when rootdev is specified to be the Hard Drive at boot. If the CD-ROM is connected, it boots into install mode from the CD. This happens for boots into single user mode as well. No matter what is done, the computer things the boot device is a CD-ROM, even when it is not (and no CD-ROM connected) The only thing that we have noticed as a bit strange is that when /usr/etc/disk was run to retrieve the label info on the HD, there was a line something to the effect of (not verbatim): read/write partition: b We never initialized the disk to have a second partition - a is the one listed as the root partition, and it should be the only one. We cannot change this, and I have no idea whether it is related. Any help would be appreciated. Michael Giddings UW Madison Chemistry
Newsgroups: comp.sys.next.bugs From: Ralph_Jung@radical.com (Ralph Jung) Subject: Does Object's performv:: method forward messages? Message-ID: <1993Sep9.205520.18272@radical2.radical.com> Sender: ralph@radical2.radical.com Organization: Radical System Solutions, Inc. Distribution: usa Date: Thu, 9 Sep 1993 20:55:20 GMT Does Object's performv:: method forward messages or have I found a bug? The basic setup: ObjectA has ObjectB has its delegate and ObjectB has ObjectC as its delegate. Each object has a respondsTo: method that first checks its super class and then its delegate to see if anyone responds to a message. Each object also has a forward:: method that sends respondsTo: first to its super class and then to its delegate and then sends the message with performv:: to whoever responds YES. (See methods below.) - forward: (SEL) aSelector : (marg_list) argFrame { if ( [delegate respondsTo: aSelector] ) { return [delegate performv: aSelector : argFrame]; } else { return [self doesNotRecognize: aSelector]; } } - (BOOL) respondsTo: (SEL) aSelector { BOOL result; if ( ! (result = [super respondsTo: aSelector]) ) { result = [delegate respondsTo: aSelector]; } return result; } The bug/feature: ObjectA is sent MessageC. ObjectA doesn't respond to it and so it asks its delegate ObjectB. ObjectB doesn't respond to it either and so asks its delegate ObjectC. ObjectC does respond and YES is passed back up the food chain. Since someone down the food chain can respond, ObjectA sends MessageC using performv:: to its delegate. Booom!!! The performv:: fails with a "delegate does not respond to MessageC" error. I would have thought that performv:: should have caused the delegate's forward:: method to be invoked which would have forwarded MessageC to ObjectC. Anyone know if this is a bug or a feature? Anyone have any thoughts on how to get around this bug/feature? Thanks. -- Ralph Jung ( Ralph_Jung@Radical.Com ) Radical System Solutions, Inc. NeXTmail accepted rad~i~cal \'rad-i-kel\ adj. - marked by a considerable departure from the usual or traditional: EXTREME
Newsgroups: comp.sys.next.bugs From: bchin@nextsrv1.andi.org (Bill Chin) Subject: Re: Serial Ports we're backkkkkk! Message-ID: <bchin.747630494@news.andi.org> Organization: Association of NeXTSTEP Developers International References: <TDFm0B1w165w@mindvox.phantom.com> Date: Fri, 10 Sep 1993 03:08:14 GMT alibaba@mindvox.phantom.com (Nick Mordanzo) writes: >Maybe its just me and maybe it was just two coincidences, but......... when >I used kermit (which is what I'm running), the logs get littered up with >streams of these: >Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-902) >Sep 9 00:51:36 horace mach: ttyscc0: receive error 2 (-901) [lots of messages deleted] >I'm running the serial port (a) on a 486/66 at 38400, which works ok under >windoze, os/2 and Linux, but I remember when I had a 486/33 windoze and os/2 >would both drop data, only Linux worked as it does now. >Is it a bad idea to run the serial ports at 38.4? I can live with 19.2 if I >need to, even if the machine does crash every 2 days I can live with that too >its the once every hour that used to get to me, so whatever you did thanks for >listening to us bitch, whine and complain and at least releasing an interim >release. As soon as the drivers came out, I tested them on a Toshiba 6400C portable 486/33 at 38.4k running kermit (189) and uucp. I did get a few of those messages, but only when I loaded the system with something else while downloading. I did notice that kermit transfers would freeze every once in a while, but the system never crashed. Lowering the DTE rate down to 19.2 helped some. I don't think the serial ports on PC's in general are up to it, and esp. not these. I'm sure a newer 16550 UART would help the situation some. Maybe you have a UART problem? Ugh! PCs... Good luck! -- Bill Chin, NeXTSTEP Developer, PRC Inc. VP Communications, Washington Area NeXT Users Group Association of NeXTSTEP Developers International Technical Staff bchin@nextsrv1.andi.org - NeXTmail welcomed
Newsgroups: comp.sys.next.bugs From: rahner@zuni.litc.lockheed.com (Mark Rahner) Subject: 3.1 Terminal Keypad Bug? Message-ID: <1993Sep10.055507.27970@butch.lmsc.lockheed.com> Sender: news@butch.lmsc.lockheed.com Organization: Lockheed Date: Fri, 10 Sep 93 05:55:07 GMT Hello everyone, Please pardon me if this is a well known bug and I'm just out of the loop. Also, please go easy if this isn't a real bug and I'm just being boneheaded. I just installed 3.1 on my monochome non-Turbo NeXTstation (which has the evil 2nd generation keyboard with |, \, etc. on the keypad) and I am using the NextUSA key mapping. The release notes for the Terminal application state that "There have been no major changes since the 3.0 release." But, as far as I can tell, the top row of the keypad keys are no longer capable of generating VT100 keypad sequences as they were under 3.0. If memory serves, the top row of keys on a VT100 keypad are labeled PF1, PF2, PF3, and PF4. The other keypad keys appear to work correctly as before so I am baffled. If this is a bug, I need a patch. If this is not a bug, I need instruction. Any pointers? Thanks in advance, Mark -- Mark V. Rahner rahner@lmsc.lockheed.com
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: preuss@netcom.com (Peter Preuss) Subject: Re: Cube boots thinking HD is CD-ROM! Message-ID: <preussCD4Js9.I03@netcom.com> Followup-To: comp.sys.next.bugs,comp.sys.next.sysadmin Organization: NETCOM On-line Communication Services (408 241-9760 guest) References: <26numc$9bm@news.doit.wisc.edu> Date: Fri, 10 Sep 1993 06:09:44 GMT Michael Giddings (giddings@sadie.chem.wisc.edu) wrote: : Hello, : We have a Cube with an internal seagate SCSI drive that was just upgraded : to 3.1. After the upgrade, the cube booted fine and everything seemed to : work. Then, someone added the CD-ROM drive to the exports list using NFS : Manager, and rebooted with the NEXTSTEP developer in the drive. : Now, the computer thinks the hard drive (/dev/rsd0a) is a CD-ROM (i.e. we : can't write to it at all), even when the CD-ROM is completely disconnected : as well as when rootdev is specified to be the Hard Drive at boot. If the : CD-ROM is connected, it boots into install mode from the CD. [...] : Michael Giddings : UW Madison Chemistry I had the same thing happening after copying too much stuff from the CD (yet uninstalled packages for nfs access). /etc/rc checks for a magic directory name /NextCD to decide its further lifestyle... excerpt from /etc/rc: # Are we booting from a CD-ROM? If so, switch over to /etc/rc.cdrom. if [ -d /NextCD -a -f /etc/rc.cdrom.`/usr/bin/arch` ]; then sh /etc/rc.cdrom.`/usr/bin/arch` $1 (echo "CD-ROM boot procedure complete.") >/dev/console /etc/halt -e exit 0 fi Peter. -- preuss@futon.sfsu.edu San Francisco State University
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: is fstat() broken? Message-ID: <1993Sep10.085011.1678@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Sep8.195221.5810@news.media.mit.edu> Date: Fri, 10 Sep 1993 08:50:11 GMT In article <1993Sep8.195221.5810@news.media.mit.edu> wave@media.mit.edu (Michael B. Johnson) writes: [snip] -> 121 if (fileId < 0) { -> 126 if (fstat(fileId, &statBuf) == -1) { I've only had occasion to use fstat in conjunction with fileno() on an open stream, so can't say for sure, but is the line-126 above in the ELSE clause???? As it appears in your posting it seems that you're attempting to fstat a closed file. Bruce Gingery NeXT-mail preferred, MIME-Mail ok
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: Edit/Gdb loses double precision -- not limited to gdb Message-ID: <1993Sep10.090602.1753@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Sep08.3@corona.com> Date: Fri, 10 Sep 1993 09:06:02 GMT In article <1993Sep08.3@corona.com> pkron@corona.com (Peter Kron) writes: -> When the variable browser in Edit/Gdb displays the -> value for a double, it loses precision. It appears -> to convert the value to a float before displaying. -> PRINT will display the correct value in the gdb -> terminal window. -> -> So if you have more than 6 digits of precision in a -> double, don't trust what you see in the browser... -> PRINT it if you need to see full precision. Peter, I'm not sure that this is at the gdb level, rather than in the shlib supporting code! I noticed just last week that using %g & %G does not seem to use long displays UNLESS the override field widths are specified. I believe that %f is the same and that the code is somewhat combined in the shlib. Can anyone quote what the STANDARDS call for in double precision displays versus simple float? The man-page for printf seems to avoid covering the subject completely. Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred, MIME-Mail ok
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: mihe@gordon.enea.se (Mike Henry) Subject: Re: NeXT OS (3.1) doesn't get Norwegian time zone right Message-ID: <1993Sep10.125832.11114@enea.se> Keywords: clock, time zone Sender: usenet@enea.se Organization: ENEA DATA AB, Stockholm, Sweden References: <26k1d4$44d@hermod.uio.no> Date: Fri, 10 Sep 1993 12:58:32 GMT In article <26k1d4$44d@hermod.uio.no> jmm@king.econ.lsa.umich.edu writes: > >I have just moved to Norway. I find that when I set my clock to local time >(using the Preferences panel), it puts me in time zone GMT+1, but during >daylight savings time it should be GMT+2. This has prevented me from >being authenticated to an afs cell in another time zone that thinks my clock is >off by an hour. > >Anyone know a fix? Yup, in Preferences pick the correct time-zone on the map and then choose "Poland" off the pull-down menu. This will enable MET with daylight savings time. Cant beleive the named it "Poland" though... Anyways, Welcome to Europe! >Prof. Jeff MacKie-Mason internet: jmm@umich.edu -Mike -- Mike Henry /// ENEA DATA AB TEL : +46 8 638-5000 /// Box 232 TFX : +46 8 638-5050 \\\/// S-183 23, SWEDEN INET : mihe@enea.se (NeXTmail OK) \XX/
Newsgroups: comp.sys.next.bugs From: Klaus@ideal.muc.de (Klaus Bscheid) Subject: a patch to get into MET DST Message-ID: <1993Sep10.164800.789@ideal.muc.de> Sender: me@ideal.muc.de (Klaus Bscheid) Organization: Eversmile Date: Fri, 10 Sep 1993 16:48:00 GMT Hallo I got a lot of requests for that Preferences patch. I guess it won't hurt if I post it. The thing is that all the zoneinfo files are on the disk. Only Preferences won't offer it. So put the __INFO.labes file to /tmp an hit the next few lines into Terminal/Stuart: cd /NextApps/Preferences.app cp -p Preferences Preferences.orig segedit Preferences.orig -replace __INFO labels /tmp/__INFO.labels -o Preferences __INFO.labels: But I really don't know if this will work with NS3.1. I mean it should. After this you will find MET in Preferences and it will automatically flip into MET DST. klaus -- NewsGrazer, a NeXTstep(tm) news reader, posting -- M>UQR=&8P7&%N<VE[7&9O;G1T8FQ<9C!<9FUO9&5R;B!#;W5R:65R.WT*7&UA M<F=L,3(P"EQM87)G<C$R,`I<<&%R9%QT>#$Q-3)<='@R,S`T7'1X,S0U-EQT M>#0V,#A<='@U-S8P7'1X-CDQ,EQT>#@P-C1<='@Y,C$V7'1X,3`S-CA<='@Q M,34R,%QF,%QB,%QI,%QU;&YO;F5<9G,R-%QF8S!<8V8P($AA;&QO7`I<"DD@ M9V]T(&$@;&]T(&]F(')E<75E<W1S(&9O<B!T:&%T(%!R969E<F5N8V5S('!A M=&-H+B!)(&=U97-S(&ET('=O;B=T(&AU<G0@:68@22!P;W-T(&ET+EP*7`I4 M:&4@=&AI;F<@:7,@=&AA="!A;&P@=&AE('IO;F5I;F9O(&9I;&5S(&%R92!O M;B!T:&4@9&ES:RY<"D]N;'D@4')E9F5R96YC97,@=V]N)W0@;V9F97(@:70N M7`I3;R!P=70@=&AE(%]?24Y&3RYL86)E<R!F:6QE('1O("]T;7`@86X@:&ET M('1H92!N97AT(&9E=R!L:6YE<R!I;G1O(%1E<FUI;F%L+U-T=6%R=#I<"EP* M8V0@+TYE>'1!<'!S+U!R969E<F5N8V5S+F%P<%P*8W`@+7`@4')E9F5R96YC M97,@4')E9F5R96YC97,N;W)I9UP*<V5G961I="!0<F5F97)E;F-E<RYO<FEG M("UR97!L86-E(%]?24Y&3R!L86)E;',@+W1M<"]?7TE.1D\N;&%B96QS("UO M(%!R969E<F5N8V5S7`I<"E]?24Y&3RYL86)E;',Z(`I[>UQ.1T1O8W5M96YT M-#,U(%]?24Y&3RYL86)E;',*,C8Q,B!-)UE6,#=;6$0\-BM$0C!,5C@\,C0X M,RPG0"PN)R0B+2I')$)12$PV*R8B3B)6)D(C(4!4,&`C.BI!8"4R"DU9)#HR M*#153DLE)R,Q2%8U+28[)$HB)D-10%0Y+$0S.D0D)2,Q3$(L,"@L*B<T2E1* M+29#,BDL2C<\2E0*34HU+D<V25A8*C`H0D%`*B0B34=(+BTJ)#)(3#@L+"A* M+"DN)C,Q1#TK7$LP)C\M(E-13%<Y/2I8+#\O1@I-(34^3S@J7$8W*D)#4DDP M-S(L*SPB.2Q&4SU"4CE=+DX[/TQ66TU26C]`)"LI1E!86D4P,"Q/,497/4I5 M"DTA.%`\.$Q&.C$Z3C9+-4Y8/$Y'.ELY42,L75\H-CY*3#XW35A-)BLS0S4M M(U]!35M-04\W-D@^)#PQ+B8*33,I0#=/-D8K,T52.BP^2R<K6#`S+5A9/"U& M5RLU)CQ@65Y0-2%(6S!")$1/+TY5.%T]5#8N*SDG04$I1@I-,R%*4CA62%,G M65P[7D]+5EM=+R117TM:*U=/5UPK-T`Q(4574B(\/CM,7DD]05Y@7D!%*%@G M.S(E-S\\"DT_7T<E35U2(5-)-3<U6#,T-#!"/V!-0B$P+"U665PE4&!70E8M M-#X^.TI-63TX+5H_4S=1,4%53E0D)S@*33M1/SY%0B8K1#Q%*$A855)0/T$B M)"<J1#PU2#@A3DI82$=57R0V1T0V5$-2)5U14"1+6T`X6%17*4I%0@I-/SI) M43XM4C4P+U@V.$!41#U`.B,C,D,N05HB)BL[.4!`62$C124F0R<F)E!(,C5= M(CY8-D<Y4514)D9'"DU%(TE83CX^/#T]6EDI2$XB441'2$=732TN/551,3@P M42%15$TS(B=))D8F3$$P.B%0449:*%<R(C%#24D*34DY/48N3#I&0%A$224U M-4]@14E"(S9%0DXJ,5E'.20I.B8R0E1%)B8G(T(F25(R-SY..EI:5EY77TDU M2PI-(E1&6#`T.#HU)TA:.ELB,C1)2TQ,3%0B)D9*5%!32"L[)S$T-$(\3$M2 M(DXB3"HK2TE)*3!:4E]934=&"DU"+3E6/E50,#TB(31(5ULZ2D),2$\O*S(P M-EXH6CDW.U<P4T@[2D=./CU*55Y>0"M@75DA)5A51%(D328*34\V4"I&3R,B M4D-(/%M&-DU>/DXY(V`G0U(^.5E&.#8X15PX4$!@-"-1(E(^.5DW*#5/1EM4 M,25212(G1PI-)S]*04`S*50L+$],(4Q61SM'/24D-3,\2RU++S`[3#H\6CA` M(B4E1$8B5#1$-#LL,$T]54$A(2TO55<F"DT]1$8L3#TA4"->/$@L*4TY.UI7 M3%$U,R5$*49?*EDS/%PZ)%@]6S4B4EA72E1@,S`T-4TI35LU5#Y>5%$*34A' M/R<C/#0[)4Y/+4U&25\V4E%24#<G/T4S.R<I4$]>*CI5-$LG(597)#,W-SM' M*%LB.TXM0%!@+5Y;2PI-55)&6T,_048U+3!!45%)15DE)5=:.CY',T<Y-3DH M2SQ*3CHQ4%<B3EE21TY7-SM$*%A)+"M.54E06$I;"DU&2%TK6S<[3%A,.C!' M3$`Y8%=?1E9,-E=.+"H[*#<I/#E.5$<C0E]+34A*7S8C5SQ&4D=.)S\S+S)- M74\*35<E+R@]-#@X/"M0(4T^+T5)7E\F7DY5(R,V0#`]-%-**5LL3S<E)R9) M)S<C1U];2E$C7U]@.R%:1%!//PI-640B0T\W,5U3)E<M5EA0,E8M/$E>)E5+ M0$<C2#4O-29143PA74A&8%%7)B)>7D%`+%!.2E)8+ULB7B0H"DT[-SI?7R=6 M,",_4CM02%$H)B1@-TE/8"4L2E`C(SI.-RXP-2931C`M(2U73E='.E(E0%@P M04P^04!*,SH*32PA4495/R(H7R4O0B<I0T@A0CPZ7#@W7$)4*#T](SHG4"=5 M+CU:22$H,$$_2"0T3C9.4BHM6S(B/TY#0`I-+T(^.D0D54(Q+B@K52-`)BU! M.$DR1R8K*%]>/"PH-$LO(28K*#Y30UI625)/.SXY2R9:*D)<)RI1(C8C"DU6 M/T=0.SA1(TDM3RQ-051'.B@D*#4F(B$I.CPP32,^4E(I*B-?+51#.%U@63(_ M63`N5%TI23))-U(\238*34Y/*C5,*%)%*R8]*5)52SI<23I84RHT3CU<1RLW M3TM215Q@+$E#(3TJ.RM+/S(T3#`P,D-</R$R42M!)0I-*4,B(RHT4SU'0T0Y M.C4[+T8I7$$G7STX*%HS1%TB25=`72XS+5(G1$M.2UA)1EHB)D8^*"XJ0C4D M1U1'"DU&/B5,5%]$5DQ:8"HS/2Q?7B]%,$PU6T!(,#A%6RE;7%,J/%\G5C)0 M*D\W,S!%7BQ)6F`N7DM(/EQ*-20*358S+44B5#,Y)U)/+2(D32%<0C(S*R]* M0RLN5S,R-#PB*B1"03$L6B-`,D4K)DY5,BXT7#I)(R5!)%174`I-0RU962<E M13$Q.U0P2",[53141DM%+2TB23<Q(UD^4$E(4SE32S4E.3I`6CA403)'3T1& M7%Q!-C4T1#TM"DU:2D8V7D-*.DU-+2Q022Y(2SE122LF4B%:6CQ/4"DU-T(\ M-S4E45%+-DQ00B-$(R]*2E)46$DF2%D_4#8*331;/4=+6T(N73<T-$\V25<[ M0CTQ05-*2C)/0#I#2U@P(DQ;2%<R33Y`358W3BX[630C+C4D2E`D5E)%50I- M*4<[,4%')"U'/C9$*RPL+"E:6"@M2SA;1#@Q3#E4*C9/)CM:5",N)R4B53XW M2C\H6EM43#E#+DLF,BE!"DU.4R\Y8$I)4C@J5CQ4/$I@+2HV14`V12X^55TB M.31*55@E6"TT)B=3.$8G*T5=4RM"0E(A1U15.SI(/3L*34]$,4XY5EH]22Y: M5DQ@3D%/)D<W-T=7.S,N)$XB73M10TY54$$X,2$Z*U];4"Q!(3523E@Y,EXK M*TD\7`I-3U<H1SLX7C5;42,Y2C`O-D@T654X+S9/6E0R)D\L3R10*DM733E4 M5B%>.E970C1/2U!'+DI&23<T+B)2"DTK,EU91TTU2U9&(4I23D0M5$LS,2T] M)B)66TPB6U,D,C\B)5XY6#PY2E$W650\75TU4"Y+0EU$)UA>5T@*35PS0"9) M+"P_.UE#0S`[6%=0,%-,/"@Y54`L)"I:13Q5,34[-3DV,V!744Q#.R@T6R=* M+"A9-"$C+2A840I-05,P)$I9+E$[(RP^)4$J*"<Q63DG1E18,4)%,E0X52=+ M2$XS4SU3)$U7.C!3)RA,2%E26C(M6%0C4$<N"DTV/5-"1RQ<6#E"0#Y!6%E6 M,2\M4DU>-40P*S\Q4S5)42Q!7UU*)C1<(5TJ+U4]3THJ*CQ;.F`[7SPI)2L* M33%'8$)554U))$4L,C0I.R1)(CI54"Q&6D`[*5HD)%E$/T-,/4Y%+$HX*4)0 M0TLV3#E45TLV34]:54M#7@HA*3=@0@I@"GT*K'U<<&%R9%QT>#$Q-3)<='@R M,S`T7'1X,S0U-EQT>#0V,#A<='@U-S8P7'1X-CDQ,EQT>#@P-C1<='@Y,C$V M7'1X,3`S-CA<='@Q,34R,%QF,%QB,%QI,%QU;&YO;F5<9G,R-%QF8S!<8V8P M(%P*7`I"=70@22!R96%L;'D@9&]N)W0@:VYO=R!I9B!T:&ES('=I;&P@=V]R M:R!W:71H($Y3,RXQ+B!)(&UE86X@:70@<VAO=6QD+EP*7`I!9G1E<B!T:&ES M('EO=2!W:6QL(&9I;F0@3454(&EN(`I0<F5F97)E;F-E<R!A;F0@:70@=VEL M;"!A=71O;6%T:6-A;&QY(&9L:7`@:6YT;R!-150@1%-4+EP*7`IK;&%U<UP* %7`H*?0IO ` -- ____________________________________________________________ Klaus Bscheid, klaus@ideal.muc.de, voice/fax: +49 89 3103829 Germany, 85716 Unterschleissheim, Sportplatzstrasse 7
Newsgroups: comp.sys.next.bugs From: rahner@zuni.litc.lockheed.com (Mark Rahner) Subject: Re: 3.1 Terminal Keypad Bug? Message-ID: <1993Sep10.194452.27094@butch.lmsc.lockheed.com> Sender: news@butch.lmsc.lockheed.com Organization: Lockheed References: <1993Sep10.055507.27970@butch.lmsc.lockheed.com> Date: Fri, 10 Sep 93 19:44:52 GMT Hello again, In a previous post I indicated that, after upgrading to 3.1, Terminal's VT100 PF key emulation was no longer working for me (see other post for details). By reverting to the version of Terminal that shipped with 3.0, I was able to workaround the problem. Since the version of Terminal was the only difference, I am relatively certain that this is an actual Terminal bug. As I am new to the world of NeXT bug reporting, I am compelled to ask what should be done to make sure that NeXT knows about this? Are they listening? Do they already know about this? Etc. -- Mark V. Rahner rahner@lmsc.lockheed.com
Newsgroups: comp.sys.next.bugs From: dabbah@tron.bwi.wec.com (Albert Dabbah) Subject: Re: 3.1 Terminal Keypad Bug? Message-ID: <1993Sep10.232656.8065@tron.bwi.wec.com> Organization: Westinghouse Electric Corporation, Baltimore MD. References: <1993Sep10.055507.27970@butch.lmsc.lockheed.com> Date: Fri, 10 Sep 1993 23:26:56 GMT In article <1993Sep10.055507.27970@butch.lmsc.lockheed.com> rahner@zuni.litc.lockheed.com (Mark Rahner) writes: > >Hello everyone, > >Please pardon me if this is a well known bug and I'm just out of the >loop. Also, please go easy if this isn't a real bug and I'm just >being boneheaded. > >I just installed 3.1 on my monochome non-Turbo NeXTstation (which >has the evil 2nd generation keyboard with |, \, etc. on the keypad) >and I am using the NextUSA key mapping. > >The release notes for the Terminal application state that "There >have been no major changes since the 3.0 release." But, as far as >I can tell, the top row of the keypad keys are no longer capable of >generating VT100 keypad sequences as they were under 3.0. If memory >serves, the top row of keys on a VT100 keypad are labeled PF1, PF2, >PF3, and PF4. The other keypad keys appear to work correctly as >before so I am baffled. > >If this is a bug, I need a patch. If this is not a bug, I need >instruction. Any pointers? > >Thanks in advance, >Mark > > >-- >Mark V. Rahner rahner@lmsc.lockheed.com Yes, I have the same problem. I reported to bug_next@next.com and was assigned problem number 47334. I have a "good" (ie non-evil) keyboard. The PF keys don't generate the right codes but it appears that KP1, KP2, KP3, and KP4 generate the codes for PF1, PF2 etc. Workaround is use terminal from 3.0. Albert -- dabbah@tron.wec.com ! <include standard_disclaimer>
Newsgroups: comp.sys.next.bugs From: uli@zoodle.robin.de (Ulrich Grepel) Subject: Re: NeXT OS (3.1) doesn't get Norwegian time zone right Message-ID: <CD61DE.38D@zoodle.robin.de> Sender: uli@zoodle.robin.de (Ulrich Grepel) Organization: meow!!! References: <26k1d4$44d@hermod.uio.no> Date: Sat, 11 Sep 1993 01:27:13 GMT In article <26k1d4$44d@hermod.uio.no> jmm@king.econ.lsa.umich.edu (Jeffrey K. MacKie-Mason) writes: > > I have just moved to Norway. I find that when I set my clock to local time > (using the Preferences panel), it puts me in time zone GMT+1, but during > daylight savings time it should be GMT+2. This has prevented me from > being authenticated to an afs cell in another time zone that thinks my clock is > off by an hour. There's a menu above the map in preferences. Set it to the Polish time zone and you'll get GMT+2 during summer time, GMT+1 during winter time, just as you need it. It might be off about one or two hours on the day switching between summer and winter and/or vice versa, but that's about all. Bye, Uli
Newsgroups: comp.sys.next.bugs From: paul@np.com (Paul Nordstrom) Subject: Re: Serial Ports we're backkkkkk! Message-ID: <CD59Av.IzM@np.com> Organization: NP Consulting, San Francisco References: <TDFm0B1w165w@mindvox.phantom.com> Date: Fri, 10 Sep 1993 15:20:54 GMT In article <TDFm0B1w165w@mindvox.phantom.com> alibaba@mindvox.phantom.com (Nick Mordanzo) writes: > > Dudes at NeXT, first off thanks for the new serial drivers, I understand that > you guys probably have angry-crazy-tired StevenGodJobs chasing you around with > a whip and screaming FASTER FASTER!!!!!! and using them for 3 days has made > life mucho eaisier. ditto!!! > > Maybe its just me and maybe it was just two coincidences, but......... when > I used kermit (which is what I'm running), the logs get littered up with > streams of these: > > Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-901) > Sep 9 00:51:31 horace mach: ttyscc0: receive error 2 (-902) It is not just you, at least; I am getting this too. > > Hundreds and hundreds of times and then THE BAD THING happens and I > get system Panic, rdp exception 6 and can only restart with a cold boot > and waiting 5 minutes for the hard disk to fsck. Which is what used to > happen with the old serial drivers. Fortunately (for me that is) I have yet to get the panic. Maybe it is coming... ):-( > > I'm running the serial port (a) on a 486/66 at 38400, which works ok under ditto. Anyone else with something to contribute here? I have not bugged Next with this yet. -- Paul Nordstrom NP Consulting paul@np.com (NeXTMail Appreciated)
Newsgroups: comp.sys.next.bugs From: paulk@mindvox.phantom.com (Paul Kerrios) Subject: How to crash the new serial drivers Message-ID: <X48q0B1w165w@mindvox.phantom.com> Originator: paulk@mindvox Sender: news@mindvox.phantom.com Organization: [MindVox] / Phantom Access Technologies / (+1 800-MindVox) Date: Sun, 12 Sep 1993 08:00:44 GMT I just did this 3 times in a row with the same results. I also have a 486/66 with the /etc/remote file set to 38400. I am on MindVox which is a internet site with a T1 link to the internet, when I enter IRC I found that by typing /names Which lists all channels and all names, usually coming up with about 15 screens of output at 14.4k speed to my screen, it will ALWAYS crash 1-3 screens into the list. To test my theory, I got rid of the page breaks MindVox usually inserts to scroll one screen at a time and viewed a long file. 5 screenfulls and it will crash. It always gives this same error: <4>tty480 raw input overrun <4>tty480 raw input overrun <4>tty480 raw input overrun panic: (Cpu 0) ns_abstimeout overflow panic: NeXT Mach 4.1, etc Raise RDP exception 6, Code 3, subcode 0 And its impossible to reboot without using the on/off switch. Same as before. The important difference is that it doesn't crash uucp, transfers, or any activity that doesn't make the screen continously scroll output at the same time as its receiving data at 14.4k with the serial port locked at 38.4k //=======================================\\ Paul Kerrios /=/ Society has made me what I am today. \=\ \=\ Ok so maybe I just watch too much TV! /=/ \\=======paulk@mindvox.phantom.com=======//
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: Re: New serial drivers in this century? Date: 11 Sep 1993 12:18:39 -0000 Organization: Palumbian Research Labs Message-ID: <26sfmv$1ac@marsu.tynet.sub.org> References: <sean-060993161441@128.187.73.66> <69Li0B2w165w@mindvox.phantom.com> <26ien4$h6b@infoserv.zdv.uni-tuebingen.de> <Sep8.215437.19753@acs.ucalgary.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Keywords: SERIAL DRIVER CRASH BURN bstone@acs.ucalgary.ca (Blake Stone) writes: >> Maybe someone from NeXT could give us the *REAL* release date >> for the serial drivers. C'mon NeXT, it cannot be so hard to >> write this stuff. >Maybe you could check before writing? You posted this message >AFTER the new drivers became available on ftp.next.com. Can we >just end this thread now? If you have no host directly connected to Internet, it is impossible to peep into ftp.next.com every day. >> I really like NeXTSTEP but how should I recommend an OS that >> crash-and burn on serial transfer and sound. If your software >> people cannot get it right, maybe releasing the driver source >> to public could be a way? >The problems associated with sound are hardware conflicts with >other devices and problems with the ISA bus. They are NOT NeXT's >fault. NeXT's fault is that the Adaptec controller is the only supported ISA SCSI controller, and the ProAudio Spectrum is the only supported sound card. Both cards don't like each other, so all trouble was known from the very beginning. Why didn't NeXT write a driver for a different ISA SCSI controller or maybe a Galaxy VesaLB board? Sometimes I wonder why NeXT supports non-EISA boards at all... >> Even UNSUPPORTED beta drivers are better than the current crap. >... and customers who expressed a need for the beta drivers >should have been able to get them from NeXT. We were able to do >so, as were a number of NeXT's larger customers to whom it was an >issue. I can definitely understand NeXT not wanting to let beta >drivers out on the internet, as they'd discover people using them >years later (don't scoff, it happens... we ran into one fellow >running version 0.97 of the Mac operating system a while back). Maybe they still released a beta. I shot the new drivers twice using 38400 bps DTE speed. At least the error messages became much more verbose before entering the famous "RDP exception". However, the new drivers seem to be stable at 19200. -- /dev Markus Wenzel, University of Stuttgart /usr/spool/mail mow@marsu.tynet.sub.org ~/.ircrc/nick Marsu /etc/motd NeXTSTEP for Cray computers? Where? When?? How???
Newsgroups: comp.sys.next.bugs From: willers@itp.unibe.ch (Moritz Willers) Subject: Re: NeXT OS (3.1) doesn't get Norwegian time zone right Message-ID: <1993Sep13.155611.13571@aragorn.unibe.ch> Sender: news@aragorn.unibe.ch Organization: University of Berne, Switzerland References: <26k1d4$44d@hermod.uio.no> Date: Mon, 13 Sep 1993 15:56:11 GMT As I told someone about the problem that we NeXT users in the MET zone have all to live in Poland he pointed out to me the following: What Greenwich is to the GMT zone, is Goerbitsch on 15 Degree east in Poland to us in the MET zone. So the fact that the timezone is called Poland seems to be a historical question and therefore handled perfectly alright by NeXT. Don'task me how they knew about it. I never heard of it before. Hope this helps to live with it -- Moritz Willers Institute for Theoretical Physics, Berne Switzerland willers@itp.unibe.ch
From: jblevins@uniwa.uwa.edu.au (Jim Blevins) Newsgroups: comp.sys.next.bugs Subject: Re: 3.1 Terminal Keypad Bug? Date: 14 Sep 93 12:23:28 Organization: University of Western Australia Distribution: world Message-ID: <JBLEVINS.93Sep14122328@uniwa.uwa.edu.au> References: <1993Sep10.055507.27970@butch.lmsc.lockheed.com> <1993Sep10.232656.8065@tron.bwi.wec.com> In-reply-to: dabbah@tron.bwi.wec.com's message of Fri, 10 Sep 1993 23:26:56 GMT One peculiar consequence of this bug on my machine is that the code generated by the bar `|' confounds the cursor in Emacs and Edit, so that it starts to straddle pairs of adjacent characters. /jim -- ---- Jim Blevins jblevins@uniwa.uwa.edu.au Centre for Linguistics phone: +61-9-380-1882 University of Western Australia fax: +61-9-380-1154 Nedlands, W.A. 6009
From: mandel@romulus.ehs.uiuc.edu (Hector Mandel) Newsgroups: comp.sys.next.bugs Subject: Re: Serial Ports we're backkkkkk! Date: 14 Sep 1993 15:16:36 GMT Organization: University of Illinois at Urbana Message-ID: <274n8k$dji@vixen.cso.uiuc.edu> References: <CD59Av.IzM@np.com> Paul Nordstrom (paul@np.com) wrote: : Anyone else with something to contribute here? I have not bugged Next with : this yet. Oh yeah ... you bet. I am running my serial port at only 9600 baud with a 14.4K HST on it. So far everything works EXCEPT that I can get the system to PANIC by generating an incoming uucico transfer from another machine. As soon as the transfer is complete and uucico on the calling end drops carrier, I get the RDP exception 6 code 3 subcode 0 message. I have to do a cold boot, wait for fsck, each time. This is not good and I'm not a happy camper although I appreciate the work that NeXT is doing and definitely appreciated this new driver which at least PANICS the system in a more or less predictable manner. However, I don't think there's going to be much of a future in NeXTStep Intel unless they get this stuff fixed soon. These kinds of bugs should not appear in an OS that sells for more than $99. I invested a lot of cash in a fully loaded i486 system and now I find that I should have stuck with Linux. The NSi GUI is pretty elegant, but it's next to worthless if I have to hit the red button every couple of hours.
Newsgroups: comp.sys.next.bugs From: alibaba@mindvox.phantom.com (Nick Mordanzo) Subject: Re: How to report kernel panics properly Message-ID: <68Hw0B1w165w@mindvox.phantom.com> Originator: alibaba@mindvox Sender: news@mindvox.phantom.com Organization: [MindVox] / Phantom Access Technologies / (+1 800-MindVox) References: <2754p3$qvi@rosie.next.com> Date: Wed, 15 Sep 1993 04:27:16 GMT erikkay@next.com (Erik Kay) writes: > lately, I've seen a number of bugs dropped in here about the new serial > drivers that talk about system panics. Both of the recent messages I read > said something to the effect of: "the system panics with a RDP exception 6 > code 3 subcode 0". Unfortunately, while this is useful information, it's > not the information we need more often than not. When the system panics, > it will print something like: > > System Panic > <system panic error message> > RDP exception 6 code 3 subcode 0 > > The RDP message means that the remote kernel debugging facility has been > enabled with the exception code message and that it is waiting for a > remote debugger to attach to it (we use this in house to debug kernel > crashes). What we're really looking for is the error message that > precedes this message. That will (usually) tell us where the panic > occurred. Its the same thing that Paul posted a couple of days ago, to recap: > <4>tty480 raw input overrun > <4>tty480 raw input overrun > <4>tty480 raw input overrun > panic: (Cpu 0) ns_abstimeout overflow > panic: NeXT Mach 3.1, etc > > Raise RDP exception 6, Code 3, subcode 0 > > And its impossible to reboot without using the on/off switch. Same as > before. The important difference is that it doesn't crash uucp, transfers, > or any activity that doesn't make the screen continously scroll output at > the same time as its receiving data at 14.4k with the serial port locked > at 38.4k There ya go $%$%$%$%$%$%$% ($) Ali Baba ($) %$%$%$%$%$%$%$
Newsgroups: comp.sys.next.bugs From: strebel1@gwdu03.gwdg.de (Stephan Trebels ) Subject: Re: NeXT OS (3.1) doesn't get Norwegian time zone right Message-ID: <ATAHB5HG@gwdu03.gwdg.de> Sender: news@gwdu03.gwdg.de (USENET News System) Organization: GWDG, Goettingen References: <1993Sep13.155611.13571@aragorn.unibe.ch> Date: Wed, 15 Sep 1993 09:45:43 GMT Moritz Willers (willers@itp.unibe.ch) wrote: : As I told someone about the problem that we NeXT users in the MET zone : have all to live in Poland he pointed out to me the following: : What Greenwich is to the GMT zone, is Goerbitsch on 15 Degree east in : Poland to us in the MET zone. : So the fact that the timezone is called Poland seems to be a historical : question and therefore handled perfectly alright by NeXT. Don'task me how : they knew about it. I never heard of it before. I just want to correct that, because so many people seem to think Poland is MET. IT IS NOT! The correct timezone file for MET/CET WET EET are shipped with 3.*, but there is no way to select them from preferences :-(. Poland and MET have the same offset to GMT but use different rules! Poland switches between DST/non-DST at 1:00, while MET switches at 2:00. If you don't believe me, check the sources (any BSD that's not NeXTSTEP :-). Rule W-Eur 1986 max - Mar lastSun 1:00s 1:00 " DST" Rule W-Eur 1986 max - Sep lastSun 1:00s 0 - Rule M-Eur 1986 max - Mar lastSun 2:00s 1:00 " DST" Rule M-Eur 1986 max - Mar lastSun 2:00s 0 - -------------------------------------------------------/|\-------------------- # Zone NAME GMTOFF RULES FORMAT Zone Poland 1:00 W-Eur MET%s Zone MET 1:00 M-Eur MET%s -----------------------/|\------------ NeXT just forgot any standard timezone for Europe! The following timezone files are shipped, but are NOT SELECTABLE: MET/CET WET EET Canada/Newfoundland W-SU Solutions: 1) Live with Poland, if you don't care for two hours of correct time. 2) Any sysadmin can manually link /etc/zoneinfo/localtime to the correct timezone, but has to disable any date/time setting from preferences. One still has to dwrite the correct timezone, so Preferences will show it. 3) What NeXT should have done / and many people did... Backup Preferences.app/Preferences to Preferences.app/Preferences.orig use segedit to extract the Mach-O section __INFO.labels from Preferences. This is just plain ASCII text. Change it, to suit your needs, and replace it. Now Preferences works as nice as it should! If you need the correct __INFO.labels, send me an email. But if you look at __INFO.labels, you will understand the structure anyway, so you can change it yourself, just give it a try :-) Ciao, Stephan -- Stephan Trebels, Institut fuer Theorethische Physik, Universitaet Goettingen email: trebels@theo-phys.gwdg.de phone +49 551 44690
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Message-ID: <1993Sep15.1@corona.com> Date: Wed, 15 Sep 1993 07:58:05 PDT Newsgroups: comp.sys.next.bugs Subject: RE: How to report kernel panics properly Referneces: <2754p3$qvi@rosie.next.com> erikkay@next.com (Erik Kay) writes: > The RDP message means that the remote kernel debugging > facility has been enabled with the exception code > message and that it is waiting for a remote debugger to > attach to it (we use this in house to debug kernel > crashes). What we're really looking for is the error > message that precedes this message. That will (usually) > tell us where the panic occurred. Is there a way to disable this facility? It's pretty useless outside of NeXT and forces manual intervention to bring the system back up. ________________________________________________________ NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: alex@mecati.mecasoft.ch (Alessandro MAGNETTI) Subject: Rdp_poll_error Message-ID: <CDEJuA.20L@mecati.mecasoft.ch> Date: Wed, 15 Sep 1993 15:46:57 GMT Organization: Mecasoft s.a. Muralto, Switzerland -------------------- My machine (an Intel GX) is at the same time an uucp client and server. If I use uucp as a client (polling) I have no problem at all. Instead when a client of my machine polls my machine, exactly after the uucp connection is closed, my machine crashes with a rdp connection error (system panic). I©am already using the new serial driver of NeXT and I am running it at 38400 and I have no problem using it with other communication software like kermit or tip. Did someone else on the net experience the same problem ? Thank you very much in advance. - Massimo _____________________________________________________________________ ARNOLDI Massimo Phone: +4191 595539 Via Vignascia Fax: +411 2842210 CH - 6982 Agno E-mail: massimo@cslife.ch (NeXT mail) _____________________________________________________________________
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Edit breaks hard links Organization: Primitive Software Ltd. Date: Fri, 10 Sep 1993 12:18:50 +0000 Message-ID: <1993Sep10.121850.363@prim.demon.co.uk> Sender: usenet@demon.co.uk This was apparantly noticed a couple of years ago, but it's worth repeating because it's a daft thing for a unix application to do: Edit breaks hard links by creating a new inode each time a file is saved. Dave Griffiths
From: mandel@romulus.ehs.uiuc.edu (Hector Mandel) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: Re: Rdp_poll_error Followup-To: comp.sys.next.misc,comp.sys.next.bugs Date: 16 Sep 1993 02:49:36 GMT Organization: University of Illinois at Urbana Message-ID: <278k80$5g7@vixen.cso.uiuc.edu> References: <CDEJuA.20L@mecati.mecasoft.ch> : I)am already using the new serial driver of NeXT and I am running it : at 38400 and I have no problem using it with other communication : software like kermit or tip. : Did someone else on the net experience the same problem ? : Thank you very much in advance. I am experiencing that very same problem. I have no idea what is causing it, have reported it to Eric at NeXT.com and have yet to hear anything -- it's only been a couple of days. Very disconcerting behavior for an O.S. that NeXT, Inc is banking on almost entirely ... * sigh. -- =============================================================================== Hector Mandel, CHP (217) 244-7237 |E-mail: h-mandel@uiuc.edu Head, Health Physics Section |Snail mail: 101 S. Gregory St. Division of Environmental Health and Safety | Urbana, IL 61801 ===============================================================================
Newsgroups: comp.sys.next.bugs From: bdiller@sfsuvax1.sfsu.edu (Brad Diller) Subject: Copying a large file on to multiple floppies Message-ID: <1993Sep16.044348.19922@csus.edu> Sender: news@csus.edu Organization: California State University, Sacramento Date: Thu, 16 Sep 1993 04:43:48 GMT Anyone else have this problem? I am unable to copy a large file on to multiple floppies. After successfully copying the first chunk, I eject the floppy and reinsert another NeXT formatted floppy, as instructed. When I press proceed in the Processes window, nothing happens, even after I manually mount the the disk by executing the "Check Disks" menu option in the Disk submenu of the WorkSpace Manager. I am still prompted to insert another floppy by the Processes window. I have tried every possible permutation with no success. My suspicion is that the problem lies with my Adaptec 1542C SCSI Host Adapter which is not officially supported in release 3.1. However, the hardware/software configuration for the 1542 conforms to the specifications listed in NeXTAnswers. Incidentally, the temporary file created in the /tmp directory is not deleted when the copy process is aborted. My hardware configuration is as follows: Hardware Configuration: Processor: I386 (Intel 486) AMI 486DX2 66Mhz Primary memory: 32.00 MB Boot Drivers PS2Keyboard PS2Mouse Adaptec1542C Floppy Drivers: PS2Keyboard at IRQ 1; ports 0x60-0x65 Adaptec 1542C at IRQ 11; DMA 5; ports 0x330-0x333 Floppy at IRQ 6; DMA 2; ports 0x3f2-0x3f7 System Serial at IRQ 4 3; ports 0x3f8-0x3ff 0x2f8-0x2ff Serial Mouse ProAudioSpectrum 16 at IRQ 5; DMA 7; ports 0x388-0x388 ATI Ultra Pro ports 0x3b0-0x3e0 map 0x7e00000-0x7ffffff 0xa0000-0xbffff 0xc0000 -0xcffff;
Newsgroups: comp.sys.next.bugs From: Karl_Kraft@ensuing.com Subject: Re: Graphic placement bug in Draw? Message-ID: <CDEHBI.55A@ensuing.com> Sender: karl@ensuing.com (Karl Kraft) Organization: Ensuing Technologies Inc. References: <OTTO.93Sep14132848@tukki.jyu.fi> Distribution: comp Date: Wed, 15 Sep 1993 14:52:26 GMT In article <OTTO.93Sep14132848@tukki.jyu.fi> otto@tukki.jyu.fi (Otto J. Makela) writes: > I've noticed a couple of times when placing TIFF graphics into a Draw > document (under NeXTstep 3.1) that it seems to size the image wrong. > It is shown on the screen correctly, but when printed on the NeXT laser, > the right edge of the graphic gets sligthly cropped. I've been using > LZW-compressed 68040 byte order TIFFs generated on a Macintosh with a > HP DeskScan IIc and retouched with PhotoShop 2.5. > > Anyone else notice this? Only with 8 bit TIFFS, and only when printed to the NLP. It works fine when I go onto Lino. I 've also noticed this behaviour in a number of applications. I seem to recall NeXT posted a note about it. It can be cured by putting an imperceivable rotation on the image (like 0.001 degrees) -- _________ Karl Kraft Karl_Kraft@ensuing.com (NeXT mail)
From: slv0y@cc.usu.edu Newsgroups: comp.sys.next.bugs Subject: Re: Copying a large file on to multiple floppies Message-ID: <1993Sep16.083321.605@cc.usu.edu> Date: 16 Sep 93 08:33:21 MDT References: <1993Sep16.044348.19922@csus.edu> Organization: Utah State University > I am unable to copy a large file on to multiple floppies. > After successfully copying the first chunk, I eject the > floppy and reinsert another NeXT formatted floppy, > as instructed. When I press proceed in the Processes > window, nothing happens, even after I manually mount > the the disk by executing the "Check Disks" menu option > in the Disk submenu of the WorkSpace Manager. > I am still prompted to insert another floppy by the > Processes window. I have tried every possible permutation > with no success. I also had some problems with this. With the intel machines YOU MUST insert the next disk, hit the CHECK DISK button so that the machine knows about it, wait for it to show up (so you know its mounted), THEN hit proceed. Is anyone making a floppy drive that can auto sense when you put one in? I never knew how irritating that could be. ;-) [Hardware outline] The above procedure worked for me... Z.
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: How to report kernel panics properly Message-ID: <1993Sep15.215752.2783@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <2754p3$qvi@rosie.next.com> Date: Wed, 15 Sep 1993 21:57:52 GMT In article <2754p3$qvi@rosie.next.com> erikkay@next.com (Erik Kay) writes: -> Hi all... -> -> First off, reporting panics here isn't really guaranteed -> to do anything. If you have bugs to report with our -> software, you should email them to bug_next@next.com. -> Bugs that only show up here aren't necessarily going -> to be noticed. -> -> Next... -> -> lately, I've seen a number of bugs dropped in here about -> the new serial drivers that talk about system panics. -> Both of the recent messages I read said something to -> the effect of: "the system panics with a RDP exception 6 -> code 3 subcode 0". Unfortunately, while this is useful -> information, it's not the information we need more often -> than not. When the system panics, -> it will print something like: -> -> System Panic -> <system panic error message> -> RDP exception 6 code 3 subcode 0 -> [translation of RDP line omitted -> later, -> Erik -> NeXT software engineer Now, the REAL question, is how to access the ``past xxx messages'' after a panic and reboot --- Are these lines saved? i.e. in RAM/EPROM/SWAP??? If so, is there no utility to fetch them with the system up? I've been unable to locate one so far. I've had TWO today which scrolled past the dinky panic window too fast to get more than it was something about invalid mmu data. The ``big'' command was ignored. ==== syslog.kern Sep 15 11:28:33 tssslab mach: "%&())*******+-./2679:;;;=>>??@ABCEFIMRYabefhijknnnnoopqrz{{|} ~~~12cba Sep 15 11:28:33 tssslab mach: t On the second panic, the system immediately rebooted with NO manual intervention.... ==== syslog.kern Sep 15 14:57:47 tssslab mach: Killing all processes <159>dutclose line xbe1 Sep 15 14:57:47 tssslab mach: Sep 15 14:57:47 tssslab mach: continuing Sep 15 14:57:47 tssslab mach: unmounting NEXTSTEP_3.1 ... done Sep 15 14:57:47 tssslab mach: unmounting NEXTSTEP_Dev_3.1 ... done Sep 15 14:57:47 tssslab mach: unmounting swapfile.front ... done Sep 15 14:57:47 tssslab mach: rebo Both on 68040-25 cube. There was a heck of a lot more than that that cycled through the mini-panic window. IF it can still be gotten to from the NMI monitor, surely there is a way to get at it programmatically, for copy-paste, accumulation and diagnosis. Bruce Gingery bruce@TotSysSoft.com NeXT-Mail preferred, MIME-Mail ok
From: shukin@jester.usask.ca (Geoff Shukin) Newsgroups: comp.sys.next.bugs Subject: Clock in NeXTSTEP FIP Date: 16 Sep 1993 21:34:02 GMT Organization: University of Saskatchewan Message-ID: <27am4a$f45@tribune.usask.ca> I am wondering if anyone else has seen the time and date been reset to May 5, 1993 and some time (other thsan the present)? My system will (after a reboot) reset the date to May5 and the time will also get changed. I have called NeXT and they have told me to log a bug report, so I did. Any Suggestions? Thanks in advance, Geo
Newsgroups: comp.sys.next.bugs From: brad@shunda.srv.ualberta.ca (Brad Nelson) Subject: Re: Edit breaks hard links Message-ID: <1993Sep16.214952.1852@kakwa.ucs.ualberta.ca> Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <1993Sep10.121850.363@prim.demon.co.uk> Date: Thu, 16 Sep 1993 21:49:52 GMT In article <1993Sep10.121850.363@prim.demon.co.uk> dave@prim.demon.co.uk (Dave Griffiths) writes: > This was apparantly noticed a couple of years ago, but it's worth repeating > because it's a daft thing for a unix application to do: Edit breaks hard > links by creating a new inode each time a file is saved. > > Dave Griffiths Edit also changes the ownership of an already existing file to that of the user editing it. Drives me nuts when trying to do uucp admin stuff.
Newsgroups: comp.sys.next.bugs From: CCGREG@mizzou1.missouri.edu (Greg Johnson) Subject: Re: Edit breaks hard links Message-ID: <16C4B101F8.CCGREG@mizzou1.missouri.edu> Sender: news@mont.cs.missouri.edu Organization: University of Missouri References: <1993Sep10.121850.363@prim.demon.co.uk> <1993Sep16.214952.1852@kakwa.ucs.ualberta.ca> Date: Thu, 16 Sep 93 18:20:37 CDT brad@shunda.srv.ualberta.ca (Brad Nelson) writes: >(Dave Griffiths) writes: >> This was apparantly noticed a couple of years ago, but it's worth repeating >> because it's a daft thing for a unix application to do: Edit breaks hard >> links by creating a new inode each time a file is saved. > >Edit also changes the ownership of an already existing file to that >of the user editing it. Drives me nuts when trying to do uucp admin stuff. Feature, not bug. Edit.app practices "safe saves" by insuring that all edited data has been written before removing the original. vi and some other editors don't do this but leave you vulnerable to losing the original if the system crashes while you are writing to disk. A "safe save" is not 100% invulnerable since Unix buffers I/O so cleverly but at least the Murphy window is much smaller than vi's. Another sometimes bothersome effect of this method of saving is that you need space for both the original and the edited version, unless you delete the original before saving. I 'spose this business could be made made a Preferences option, there's one to retain the original file. If you regularly want to do a "hard save" from Edit.app you can set up a User Command or User Pipe entry. Here's one I put in .commanddict: Hard Save H echo -n "$selection" > "$file" There's a tab on each side of the isolated H. Press Command-a then Command-H to do the "hard save".
Newsgroups: comp.sys.next.bugs From: rab@cs.cmu.edu (Robert Brennan) Subject: 2.88 floppy trouble Message-ID: <CDI4xB.GpF.2@cs.cmu.edu> Keywords: floppy 2.88 Sender: news@cs.cmu.edu (Usenet News System) Organization: School of Computer Science, Carnegie Mellon Date: Fri, 17 Sep 1993 14:15:10 GMT Has anyone else experienced difficulty trying to initialize a new 2.88 (ED) floppy in a PLI SuperFloppy 2.8 running NeXTStep 3.1 on a 040 NeXTCube. If I put in a new uninitialized disk into the drive, the system comes back in couple of minutes saying the disk is uninitialized and asks if I want to initialize it. Then it wants to know the format and I leave the default UNIX. At this point I get MEDIA ERROR; block OH retry # a number of times and the disk is ejected. If I simply try a low level format (Instead of selecting the file system as UNIX, I select None), the disk will format. Or at least appear to. If I then reinsert the disk, I again get the format disk panel and tell it to format the disk with the Unix File System. The trouble is that the system has now automatically detected the capacity as 2M instead of 4M as it should be. It merrily goes on and completes the format and ejects. However when I reinsert the disk again I get a message that the disk is damaged. If I select initialize here, I get yet a different Initialize panel. Here I select Next as the system and tell it to erase. Finally I get a cannot initialize disk message and an error message on the console that says: boot block extends beyond front porch. At this point I am convinced that there is a bug. This has occurred for more than one disk, so I believe the disks are not the trouble. Does anyone have a solution? Bob -- +----------------------------------------------------------------+ | Robert Brennan | | Carnegie Mellon University email: Robert_Brennan@cmu.edu | | School of Computer Science phone: 412-268-3806 | | 5000 Forbes Avenue fax: 412-452-6763 | | Pittsburgh, PA 15213-3891 |
From: max@fml.tuwien.ac.at (Maximilian Hantsch) Newsgroups: comp.sys.next.bugs Subject: Re: New serial drivers in this century? Date: 17 Sep 1993 15:11:27 GMT Organization: Technical University Vienna, Austria Message-ID: <27ck2v$7l4@email.tuwien.ac.at> References: <26sfmv$1ac@marsu.tynet.sub.org> In article <26sfmv$1ac@marsu.tynet.sub.org> mow@marsu.tynet.sub.org (Markus Wenzel) writes: > Maybe they still released a beta. I shot the new drivers twice using > 38400 bps DTE speed. At least the error messages became much more > verbose before entering the famous "RDP exception". However, the > new drivers seem to be stable at 19200. Well, I'm afraid I had exactly the same problems with the new driver and 19200 baud when I happened to switch the modem off and on again. I have put the modem back to a Motorola machine for now. Max
Newsgroups: comp.sys.next.bugs From: robert@ictv.com (Robert Patrick Thille) Subject: Project Builder won't tell Edit the correct file to open. Message-ID: <1993Sep17.214633.5729@ictv.com> Sender: usenet@ictv.com Organization: ICTV, Santa Clara, CA (408) 562-9200 Distribution: usa Date: Fri, 17 Sep 1993 21:46:33 GMT When I compile on another system (slopoke: my 030 board in the same cu be as my 040 board) Project builder tells Edit to open the file, but omits the leading slash on the file name, so unless I have a window open in Edit that resides in /, the open fails. Is there any way to fix this/ work around it? Thanks, robert -- Robert Thille NeXTMail robert@ictv.com OK At All 1548 Maple Ave. RWC CA 94063 Addresses he file name, so unless I have a window open in Edit that resides in /, the open fails. Is there any way to fix this/ work around it? Thanks, robert -- Robert Thille
Newsgroups: comp.sys.next.bugs From: phyd@interaccess.com (Brian Leake) Subject: Re: Project Builder won't tell Edit the correct file to open. References: <1993Sep17.214633.5729@ictv.com> Sender: news@interaccess.com (Usenet News) Organization: InterAccess, Chicago's best Internet service provider. Date: Sat, 18 Sep 1993 15:09:42 GMT Message-ID: <1993Sep18.150942.198@interaccess.com> Distribution: usa In article <1993Sep17.214633.5729@ictv.com>, Robert Patrick Thille <robert@ictv.com> wrote: > >When I compile on another system (slopoke: my 030 board in the same cu > >be as my 040 board) Project builder tells Edit to open the file, but omits the leading slash on the file name, so unless I have a window open in Edit that resides in /, the open fails. Is there any way to fix this/ work around it? > Hmm, this sounds strange. I've had no trouble with my cube and project builder. Check your NetInfo NFS mounts to make sure it's not getting confused about your root directory. Brian Leake. -- _____________________________________________________________________ Image Art "No problems... Only Solutions" Brian Leake phyd@interaccess.com _____________________________________________________________________
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.hardware,comp.sys.next.bugs From: jmbreuer@trek.nbg.sub.org Subject: Re: how to mount a DOS-OD with NS-3.1 ? Message-ID: <1993Sep19.123747.3540@trek.nbg.sub.org> Organization: private References: <25kutc$s9c@bock.freiburg.sub.org> Date: Sun, 19 Sep 1993 12:37:47 GMT admin@bock.freiburg.sub.org (FreiNet Administrator) writes: >Hi, >i want to know if it is possible to mount a external OD which is DOS >formatted ! >Every time i put the OD into the drive (it's a sony :) the NeXT give me >the choice to format the disk as an unix or mac disk. But he doesn't >recognize that this disk is already formatted as a DOS disk :-( >The NeXT is a "black" machine running NS 3.1. Well, I don't know about NS 3.1 (yet :-), but under 3.0 it is not possible to format disks larger than 1.44 MB with a DOS filesystem, nor is it possible to mount DOS-Harddisk-Filesystems (probably too FAT ;-). >If anyone has managed this with success, please give me a hint !!! >- Flo So long, Joe -- | Joachim Breuer | Usenet: | | Weichselgartenstrasse 34a | jmbreuer@trek.nbg.sub.org | | 91301 Forchheim +-----------------------------+ | Germany | Data: +49 9191 33915 (24h) |
Newsgroups: comp.sys.next.bugs From: dinse@catatac.niehs.nih.gov (Gregg E. Dinse) Subject: System Panic on NextDimension Message-ID: <1993Sep20.192608.5669@alw.nih.gov> Keywords: panic, nextdimension, kernel Sender: postman@alw.nih.gov (AMDS Postmaster) Organization: National Institutes of Health Date: Mon, 20 Sep 1993 19:26:08 GMT Hello, I just upgraded to 3.1 and have had a couple of panics on my cube. My setup is a NextDimension with 52 mb on the motherboard, 32 mb on the ND board, and lots of room on the hard drives. I have run 3.0 for a long time and don't remember a similar problem. Less than 2 weeks ago I installed 3.1 and twice have had a system panic. There are various messages in the /usr/adm/messages file, but the one that looks the most serious to me (though I do not know much about mach and UNIX and so on) is the following: mach: panic: (Cpu 0) No more room in kernel map The first time it happened (about 10 days ago), a panic window appeared and lots and lots of stuff flew by, and then the system rebooted itself. The second time (today), I came back from lunch and the screen was black and the machine would not respond, so I forced a reboot. The only other person at our site with a NextDimension upgraded to 3.1 a couple of months ago. He also had problems like this. He said that the situation got progressively worse, with each new panic occurring sooner after the last. When his ND started doing this at least once a day, he gave up and reinstalled 3.0. Does anyone have a clue? Is this a known problem? Is there a solution? Is there a workaround? Will 3.2 solve this? I'd hate to go back and reinstall 3.0 now. I'd be glad to e-mail my messages file to anyone who might be able to help me diagnosis the problem. Many thanks in advance. Gregg Dinse 919-541-4931 dinse@catatac.niehs.nih.gov
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 20 Sep 1993 23:04:59 -0400 Organization: Next Announcements Message-ID: <27lr0p$khb@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs From: dimitri@dutiws.twi.tudelft.nl (Dimitri Tischenko) Subject: Re: Edit breaks hard links Message-ID: <CDHr0o.M9L@dutiws.twi.tudelft.nl> Organization: Delft University of Technology References: <1993Sep10.121850.363@prim.demon.co.uk> Date: Fri, 17 Sep 1993 09:14:47 GMT In article <1993Sep10.121850.363@prim.demon.co.uk>, Dave Griffiths <dave@prim.demon.co.uk> wrote: >This was apparantly noticed a couple of years ago, but it's worth repeating >because it's a daft thing for a unix application to do: Edit breaks hard >links by creating a new inode each time a file is saved. > >Dave Griffiths O, right!!! That's why when I save a file with Edit on a DOS file system (but not on floppy) under NEXTSTEP the kernel panics with: Kernel Trap Raise RDP exception 2 code d subcode 55540000 Waiting for RDP connection (type 'c' top continue) and the only way to recover is cold boot... Is this a registered bug? Dimitri +----------------------------------------------------------------------------+ | Dimitri Tischenko | D.B.Tischenko@TWI.TUDelft.NL | NeXTmail preferred! | +---------------------------------------+------------------------------------+ | Delft University of Technology | Technische Universiteit Delft | | Fac Applied Math & Computer Science | Fac. Techn. Wiskunde & Informatica | | The Netherlands | Nederland | +---------------------------------------+------------------------------------+
Newsgroups: comp.sys.next.bugs From: sdavenpo@vaxc.stevens-tech.edu Subject: CD ROM Drive Not Found?? Message-ID: <1993Sep21.100531.1@vaxc.stevens-tech.edu> Sender: news@dmi.stevens-tech.edu (USENET News System) Organization: Stevens Institute Of Technology Date: Tue, 21 Sep 1993 15:05:31 GMT I'm new to NeXT so forgive me if this question has been asked before: I'm running NSi and am receiving a CD ROM Drive Not Found error (or something to that effect) when I try to run CDPlayer. I've got a NEC Multisync SCSI CD ROM at SCSI ID 0 and an Adaptec 1542C controller at SCSI ID 7. NS loaded and installed without problems and all other CDs I put in the drive are found by Workspace Manager. Can anybody help?? Scott Davenport sdavenpo@vaxc.stevens-tech.edu (NeXT mail coming soon....)
From: rogata@is-next.umd.edu (Richard Scott Ogata) Newsgroups: comp.sys.next.bugs Subject: Re: System Panic on NextDimension Date: 21 Sep 1993 15:47:10 GMT Organization: University Of Maryland, College Park, MD Message-ID: <27n7lu$g95@umd5.umd.edu> References: <1993Sep20.192608.5669@alw.nih.gov> Keywords: panic, nextdimension, kernel < Gregg Dinse's descriptions of problems with 3.1 and NeXT Dimensions deleted> Yes, we have about 30 Dimension equipped units here, and have experienced similar problems with 3.1. Any machine upgraded from 3.0 to 3.1 using the Upgrade App started panicking within a few days of the upgrade. We also experienced numerous other problems, such as NeXTMail crashing when you pressed the compose button (observed on two machines), NeXTMail being missing (1 machine), Workspace hanging (many machines), etc. This made me suspicious, so I did diffs of the disks of the problem machines against a Dimension machine I had built from scratch. Sure enough, there were many very strange inconsistencies between the two. Apparently, the Upgrade App is unreliable, at best, on these systems. I have been slowly rebuilding each of these machines with BuildDisk off a cleanly built system. It is worth noting that I have not had a single panic from a machine that was installed from the ground up off of CD, or built using BuildDisk from a cleanly built system. I am keeping my fingers crossed. Rich Ogata rogata@arpa.mil
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.hardware,comp.sys.next.bugs From: phyd@interaccess.com (Brian Leake) Subject: Re: how to mount a DOS-OD with NS-3.1 ? References: <25kutc$s9c@bock.freiburg.sub.org> <1993Sep19.123747.3540@trek.nbg.sub.org> Sender: news@interaccess.com (Usenet News) Organization: InterAccess, Chicago's best Internet service provider. Date: Tue, 21 Sep 1993 12:47:57 GMT Message-ID: <1993Sep21.124757.728@interaccess.com> In article <1993Sep19.123747.3540@trek.nbg.sub.org>, <jmbreuer@trek.nbg.sub.org> wrote: >admin@bock.freiburg.sub.org (FreiNet Administrator) writes: > >>Hi, > >>i want to know if it is possible to mount a external OD which is DOS >>formatted ! >>Every time i put the OD into the drive (it's a sony :) the NeXT give me >>the choice to format the disk as an unix or mac disk. But he doesn't >>recognize that this disk is already formatted as a DOS disk :-( >>The NeXT is a "black" machine running NS 3.1. > >Well, I don't know about NS 3.1 (yet :-), but under 3.0 it is not possible >to format disks larger than 1.44 MB with a DOS filesystem, nor is it >possible to mount DOS-Harddisk-Filesystems (probably too FAT ;-). > >>If anyone has managed this with success, please give me a hint !!! > You'll need 3.1, shouldn't be any problem unless it is Doublespaced, Stackered, or NT HPFS. By the way, did you know NT can't read DOS 6 Doublespace disks! I've had no problem with 3.1 reading DOS drives up to 340Mb. Brian. -- _____________________________________________________________________ Image Art "No problems... Only Solutions" Brian Leake phyd@interaccess.com _____________________________________________________________________
From: giddings@whitewater.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs,comp.sys.next.software Subject: Watch for NS/I viruses! Date: 21 Sep 1993 19:35:31 GMT Organization: Division of Information Technology Distribution: world Message-ID: <27nl23$k17@news.doit.wisc.edu> Last week I had my Toshiba 4400C portable at a service center for some work. A few days later they called me and told me it had a virus that had infected their disks. I did not beleive them as it is soleley configured as a NeXTSTEP machine, with no DOS partition. However, the symptoms they described as occuring with this virus have been happening on the machine, so today I scanned the hard drive using the McAffee associates virus scan utility (with the /maint option). It found the "Joshi" virus within the partition table. This virus has infected other disks (this is the one that the service people told me infected their disks from my machine). I do not know yet whether it was responsible for the strange floppy/mouse problems I've been having, but it is supposed to cause those types of problems in DOS/Windows. It seems I was able to remove the virus with the "clean" program also by Mcaffee. I hope that this is the only way DOS viruses can affect NeXTSTEP (through the partition table). However, people should be on the lookout. Another "bonus" of the Intel computer world revealed . . . -- Michael Giddings | DNA sequencing technologies giddings@whitewater.chem.wisc.edu | Artificial Intelligence giddings@cs.wisc.edu | Sciences NeXT User Group founder |---------\-----------/|\------------/---------|
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Date: Wed, 22 Sep 1993 06:30:28 PDT Message-ID: <1993Sep22.133028.1887@corona.com> Newsgroups: comp.sys.next.bugs Subject: Watch for NS/I viruses! References: <27nl23$k17@news.doit.wisc.edu> > Last week I had my Toshiba 4400C portable at a service center > for some work. A few days later they called me and told me > it had a virus that had infected their disks. I did not > beleive them as it is soleley configured as a NeXTSTEP > machine, with no DOS partition. > ... > Another "bonus" of the Intel computer world revealed . . . > -- > Michael Giddings | DNA sequencing technologies ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ...and perhaps a bonus of gene-splicing? :^) --- NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
From: samurai@amber.hasc.ca (Darcy Brockbank) Newsgroups: comp.sys.next.bugs Subject: gdb 4.7 / NS3.1 Date: 22 Sep 1993 18:32:56 GMT Organization: The Hutchison Avenue Software Corp. Message-ID: <27q5oo$p12@hasc.ca> Is it just me or is gdb suddenly most non-robust? Stupid gdb tricks like this seem to happen 50% of the time I use it: Breakpoint 1, -[FixedFields_in allocVars] (self=0x93070, _cmd=0xd5078) at input.m:55 55 for(length=0,lastp=desc,p=strchr(desc,':');lastp;lastp=p,p=(p)?strchr(p,':'):0) (gdb) view Segmentation fault .. gdb crashed here. Or this one (length is an int): (gdb) display length 2: (???(???(???((???(((-((?????????(???(???((((???((???(???VAL,(???(((((???((???(( ???(???(???(???((((???(???(???(???(???CHR((???(???(???(???(???(???(???(???(???( ???(???(???(???(???((???(???(???((???((???(???(???(???(???(???(???(???(???(???( ???(???(???(???(???(???(???(???(???(???(???(???(((???((???(???(???((???(???((?? ?(???(???(???(???(???(???(???(???(???(???(???((???(???(???((???(???(???(???((?? ?(???(???(???(???(???(???(???(???(???(???(???(???(???(???((((((((???(???(???(?? ?((???(???(???(???(???(???(???(???(???(???((???(???(???(???(???(???(???(???(??? (???((???(???(???(???(???(???(???((???(???(???(???(???(???(???(???(???(???(???( print_subexp: Not implemented. Disabling display 2 to avoid infinite recursion. (gdb) print length $1 = 20 These are some of the few nice things showing up over the last 10 minutes... to tired to show them all. Does anyone know if we can run newer versions of gdb with NS 3.1? - darcy -- "No man should be discouraged from entering business through fear of taxation." -- N. Machiavelli
From: kent@infoserv.com Newsgroups: comp.sys.next.bugs Subject: Re:Watch for NS/I viruses Message-ID: <CDsFMA.24o@infoserv.com> Date: 23 Sep 93 03:42:10 GMT References: <1993Sep22.133028.1887@corona.com> Sender: kent@infoserv.com (Kent L. Shephard) Distribution: na Organization: K. L. Shephard Consulting In article <1993Sep22.133028.1887@corona.com> pkron@corona.com (Peter Kron) writes: #> Last week I had my Toshiba 4400C portable at a service center #> for some work. A few days later they called me and told me #> it had a virus that had infected their disks. I did not #> beleive them as it is soleley configured as a NeXTSTEP #> machine, with no DOS partition. They do not know what they are talking about. If it only has UNIX, it could not infect their diskettes with a DOS virus. Kent -- /* K.L. Shephard Consulting is my company. Infoserv only delivers my mail. */ /* Please direct mail to kent@infoserv.com other adresses may not work. */
Newsgroups: comp.sys.next.bugs From: phyd@interaccess.com (Brian Leake) Subject: Re: System Panic on NextDimension Keywords: panic, nextdimension, kernel References: <1993Sep20.192608.5669@alw.nih.gov> <27n7lu$g95@umd5.umd.edu> Sender: news@interaccess.com (Usenet News) Organization: InterAccess, Chicago's best Internet service provider. Date: Thu, 23 Sep 1993 14:55:36 GMT Message-ID: <1993Sep23.145536.97@interaccess.com> In article <27n7lu$g95@umd5.umd.edu>, Richard Scott Ogata <rogata@is-next.umd.edu> wrote: >< Gregg Dinse's descriptions of problems with 3.1 and NeXT Dimensions deleted> > > Yes, we have about 30 Dimension equipped units here, and have >experienced similar problems with 3.1. Any machine upgraded from 3.0 to 3.1 >using the Upgrade App started panicking within a few days of the upgrade. We I upgraded from 3.0 to 3.1 with a dimension cube at work, and nothing in particular went wrong with the machine. Strange. Brian Leake. -- _____________________________________________________________________ Image Art "No problems... Only Solutions" Brian Leake phyd@interaccess.com _____________________________________________________________________
From: john@klein.Mines.Colorado.EDU (John Stockwell) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: NeXT Printer bug in 3.1 Message-ID: <1993Sep23.173044.37210@slate.mines.colorado.edu> Date: 23 Sep 93 17:30:44 GMT Sender: news@slate.mines.colorado.edu Organization: Colorado School of Mines I have found a bug in the printer driver for NeXT Printers under NeXTSTEP_3.1 (NeXT Machines) version. The problem that you see is that bitmapped graphics are stretched and truncated on the right edge, or have discontinuities running the length of the long axis of the plot. The problem appears when the long axis of the plot, as measured in pixels, is oriented in same direction as the long axis direction of the paper. Thus the problem can be seen either in landscape mode or portrait mode, depending on the plot. I have confirmed with NeXT that this is a bona fide bug. They say that it is fixed in OS 3.2. Their suggestion: 1) downgrade printer servers to 3.0 2) wait for 3.2, which is due to be released sometime between now and December. They don't have a workaround. :-( Hope this helps. John Stockwell Center for Wave Phenomena Colorado School of Mines Golden, CO 80401 john@dix.mines.colorado.edu
From: giddings@sadie.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs Subject: Re:Watch for NS/I viruses Date: 24 Sep 1993 01:03:19 GMT Organization: Division of Information Technology Distribution: na Message-ID: <27th0n$r17@news.doit.wisc.edu> References: <CDsFMA.24o@infoserv.com> Keywords: virus nextstep In article <CDsFMA.24o@infoserv.com> kent@infoserv.com writes: > In article <1993Sep22.133028.1887@corona.com> pkron@corona.com (Peter Kron) > writes: > #> Last week I had my Toshiba 4400C portable at a service center > #> for some work. A few days later they called me and told me > #> it had a virus that had infected their disks. I did not > #> beleive them as it is soleley configured as a NeXTSTEP > #> machine, with no DOS partition. > > They do not know what they are talking about. > > If it only has UNIX, it could not infect their > diskettes with a DOS virus. > > Kent > -- > /* K.L. Shephard Consulting is my company. Infoserv only delivers my mail. */ > /* Please direct mail to kent@infoserv.com other adresses may not work. */ This virus (joshi) is one that infects the partition table. NeXTSTEP utilizes the same partition table that DOS does so that it can allow the dual boot capability. Therefore, a virus that infects the partition table can "infect" a UNIX system, which is exactly what happened. Not only did it affect my hard drive, but it spread to one of their disks. I did not believe it, but it happened, and I did the virus scan myself to find exactly the virus on my hard disk that they claimed had infected their disks. What I am NOT claiming is that this virus is active under NeXTSTEP. I doubt that it could be active under UNIX, though I am still slightly suspicious due to strange behavior of the system. However, the virus is definately activated when the computer is booted from a DOS floppy, and it was able to remain present on a non-DOS drive (no DOS partition whatsoever). Anyway, how would they have known that it was the Joshi virus, which is exactly what the scanning program found and removed from my disk when I ran it myself? I doubt it was guesswork. Michael Giddings P.S. I have not seen many concerned responses, maybe due to disbelief. Personally, I was very shocked to find that my pureley NS/I system COULD get a virus infection, whether or not it is and active one under NS/I. And, since there are no virus tools under NS/I, it was complicated to detect and remove. I think it warrants more attention than people seem to be giving it.
From: marcel@cs.tu-berlin.de (Marcel Weiher) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: NeXT Printer bug in 3.1 Date: 24 Sep 1993 06:34:36 GMT Organization: Technical University of Berlin, Germany Message-ID: <27u4ds$g2h@news.cs.tu-berlin.de> References: <1993Sep23.173044.37210@slate.mines.colorado.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit john@klein.Mines.Colorado.EDU (John Stockwell) writes: >I have found a bug in the printer driver for NeXT Printers >under NeXTSTEP_3.1 (NeXT Machines) version. >The problem that you see is that bitmapped graphics >are stretched and truncated on the right edge, or >have discontinuities running the length of the long >axis of the plot. >The problem appears when the long axis of the plot, >as measured in pixels, is oriented in same direction >as the long axis direction of the paper. Thus the problem >can be seen either in landscape mode or portrait mode, >depending on the plot. This bug is actually described in the release notes, which also describe a workaround: "...put an invisible rotation on the image..." This is fine if you have a document to work with, but no help for finished layouts. So here's a workaround: In the directory "/usr/lib/NextPrinter/Drivers/NXNLPDriver" create the file "image_bugfix.ps" with the following contents: /image { gsave .1 rotate image grestore } bind def The, using NetInfoManager, add the property "InitFiles" with the value "/usr/lib/NextPrinter/Drivers/NXNLPDriver/image_bugfix.ps" to the "Admin" subdirectory of any NeXT Laserprinter entry. I just tried it, it works. Marcel
Newsgroups: comp.sys.next.bugs,comp.unix.programmer,comp.sys.next.programmer From: esky@marathon.cs.ucla.edu (Eskandar Ensafi) Subject: tgetstr() problems & incomplete curses library Message-ID: <1993Sep24.174130.16968@cs.ucla.edu> Sender: usenet@cs.ucla.edu (Mr Usenet) Organization: UCLA CS Department, Los Angeles, CA Date: Fri, 24 Sep 93 17:41:30 GMT Hello, I have noticed that using 'tgetstr( char *id, char **area)' results in my programs exiting with either code 012 or 0360. After some debugging, I realized that it was [partly?] due to memory allocation problems -- the program cannot successfully 'free( area)', where 'area' is a 'char *' pointer declared as follows: char *area = (char *)malloc( 252); I successfully read the termcap entry under vt100 emulation: char buffer[ 1024]; tgetent( buffer, "vt100"); I then attempted to: tgetstr( "me", &area); /* the code for all attributes off */ As expected, 'area' was incremented by the number of bytes contained in the termcap entry for "me", plus an additional byte for the null character which terminates the entry. The string returned was correct: "ESC-[-m". Then, when the program terminated (running under gdb), it exited with an error code (012 _without_ explicitly calling 'free( area)' and 0360 when I attempted to 'free( area)' myself before exiting.) What could the problem be? And to top this off, my curses library lacks attron(), attroff(), etc..., so I can't even give up and use those functions instead -- I *REALLY* need help! Thanks in advance! - Eskandar P.S. Why doesn't NeXT update its libcurses.a (not to mention a whole bunch of other UNIXish C libraries) ??? -- "Dance with the dead in my dreams Listen to their hollowed screams The dead have taken my soul Temptation's lost all control" -- Slayer (Dead Skin Mask)
Newsgroups: comp.sys.next.advocacy,comp.sys.next.software,comp.sys.next.bugs From: chris@iastate.edu (Chris Wong) Subject: Better color in Windooze than in NS? Message-ID: <chris.748897239@vincent1.iastate.edu> Sender: news@news.iastate.edu (USENET News System) Organization: Iowa State University, Ames IA Date: Fri, 24 Sep 1993 19:00:39 GMT It's amazing that viewing GIF files under Windooze or OS/2 is much much much better than viewing them under NS/FIP. Those images (GIFs) are copied from my DOS floppy and viewed under NS/FIP 3.1 with Dell 450DE/2 DGX. The difference between viewing these images under Windooze and NS/FIP is that.... the images seems to be "whitened" for a certain degree by DPS. Anything wrong with my hardware or NS? Those NS TIFFs icons are pretty. BTW, postscript images (not in EPS format) has the same problem as GIF's. (I created the postscript file under xv for X from an GIF file.) Any help would be appreciated. -- Chris Wong | "Hardware is supposed to serve Software." chris@iastate.edu | Computer Engineering & Computer Science twba8@isuvax.iastate.edu | Iowa State University of Science and Technology
Newsgroups: comp.sys.next.bugs From: phyd@interaccess.com (Brian Leake) Subject: Re: Watch for NS/I viruses References: <1993Sep22.133028.1887@corona.com> <CDsFMA.24o@infoserv.com> Sender: news@interaccess.com (Usenet News) Organization: InterAccess, Chicago's best Internet service provider. Date: Fri, 24 Sep 1993 14:43:22 GMT Message-ID: <1993Sep24.144322.3280@interaccess.com> Distribution: na In article <CDsFMA.24o@infoserv.com>, <kent@infoserv.com> wrote: >In article <1993Sep22.133028.1887@corona.com> pkron@corona.com (Peter Kron) >writes: >#> Last week I had my Toshiba 4400C portable at a service center >#> for some work. A few days later they called me and told me >#> it had a virus that had infected their disks. I did not >#> beleive them as it is soleley configured as a NeXTSTEP >#> machine, with no DOS partition. > >They do not know what they are talking about. > >If it only has UNIX, it could not infect their >diskettes with a DOS virus. > Definately, these people sound like total idiots. This just goes to show the rot and general ignorance that DOS and Windows is causing throughout the industry. Like Lennin said, "If it ain't communism, it's wrong." (or words to that effect!). Brian. -- _____________________________________________________________________ Image Art "No problems... Only Solutions" Brian Leake phyd@interaccess.com _____________________________________________________________________
From: Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: Watch for NS/I viruses Date: Fri, 24 Sep 1993 15:14:31 -0700 Organization: University of Washington Message-ID: <MS-C.748908871.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII To: Brian Leake <phyd@interaccess.com> In-Reply-To: <1993Sep24.144322.3280@interaccess.com> You are misinformed. You are quite correct that NS/I would be immune to a DOS virus, particularly if there is no DOS partition on the disk. However, some PC viri are BIOS viri, and NS/I is as vulnerable to one of these as any other PC operating system. Apparently, the virus that this particular fellow acquired infected the partition map.
From: john@klein.Mines.Colorado.EDU (John Stockwell) Newsgroups: comp.sys.next.bugs Subject: Re: NeXT Printer bug in 3.1 Message-ID: <1993Sep24.205349.23961@slate.mines.colorado.edu> Date: 24 Sep 93 20:53:49 GMT References: <27u4ds$g2h@news.cs.tu-berlin.de> Sender: news@slate.mines.colorado.edu Organization: Colorado School of Mines In article <27u4ds$g2h@news.cs.tu-berlin.de> marcel@cs.tu-berlin.de (Marcel Weiher) writes: > john@klein.Mines.Colorado.EDU (John Stockwell) writes: > > >I have found a bug in the printer driver for NeXT Printers > >under NeXTSTEP_3.1 (NeXT Machines) version. > > >The problem that you see is that bitmapped graphics > >are stretched and truncated on the right edge, or > >have discontinuities running the length of the long > >axis of the plot. > > >The problem appears when the long axis of the plot, > >as measured in pixels, is oriented in same direction > >as the long axis direction of the paper. Thus the problem > >can be seen either in landscape mode or portrait mode, > >depending on the plot. > > This bug is actually described in the release notes, which > also describe a workaround: > > "...put an invisible rotation on the image..." > > This is fine if you have a document to work with, but no > help for finished layouts. So here's a workaround: > > In the directory "/usr/lib/NextPrinter/Drivers/NXNLPDriver" > create the file "image_bugfix.ps" > with the following contents: > > /image { gsave .1 rotate image grestore } bind def > > The, using NetInfoManager, add the property "InitFiles" > with the value "/usr/lib/NextPrinter/Drivers/NXNLPDriver/image_bugfix.ps" > to the "Admin" subdirectory of any NeXT Laserprinter entry. > > I just tried it, it works. > > Marcel Nope. I'm seeing a different bug. I still see 2 horizontal dicontinuities running the length of the plot. In addition, the rotation introduced by your "fix" causes a smearing effect on the plot that makes it look worse than before. However, you may have put me on the trail of a method of solution, so thanks for the info, anyway. -John
From: mycroft@monolith.utexas.edu (Alex Currier) Newsgroups: comp.sys.next.bugs Subject: Re: Watch for NS/I viruses Date: 25 Sep 1993 02:21:24 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <2809v4$7n1@geraldo.cc.utexas.edu> References: <MS-C.748908871.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> In article <MS-C.748908871.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU> writes: > You are misinformed. > > You are quite correct that NS/I would be immune to a DOS virus, particularly > if there is no DOS partition on the disk. However, some PC viri are BIOS > viri, and NS/I is as vulnerable to one of these as any other PC operating > system. Apparently, the virus that this particular fellow acquired infected > the partition map. However, since (I think I recall him saying) he had no DOS disks and never formatted his drive with a DOS partition how can we suppose he actually got the virus? Maybe his friendly neighborhood PC repair shop gave him the virus? I find if difficult to believe he could have gotten a bios virus through the use of any NS floppy or CD so at some point his machine came into contact with a PC disk carrying the virus. (all of this assuming of course that he didn't use PC disks and the virus was in fact a BIOS virus. -- ======================================================================== Alex Currier | History is made at night... mycroft@ccwf.cc.utexas.edu | Character is what you are in the dark. ========================================================================
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.bugs,comp.sys.next.software Subject: Re: Better color in Windooze than in NS? Date: 25 Sep 1993 07:36:49 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <280seh$dsl@usenet.rpi.edu> References: <chris.748897239@vincent1.iastate.edu> chris@iastate.edu (Chris Wong) writes: > It's amazing that viewing GIF files under Windooze or OS/2 is much > much much better than viewing them under NS/FIP. > > Those images (GIFs) are copied from my DOS floppy and viewed under > NS/FIP 3.1 with Dell 450DE/2 DGX. The difference between viewing > these images under Windooze and NS/FIP is that.... the images seems > to be "whitened" for a certain degree by DPS. Most images, such as GIF images, are stored with a gamma (brightness) correction in them. As I understand it, the reason for this is historical, it is an artifact of the way that monitors work (or to be more specific, the away the original TV sets worked). For some discussion on this, check the help information in the PhotoAlbum.app which comes with NeXTSTEP-3.1. Under the "Preferences" part of the help information, there is a paragraph on gamma correction. The difference in how DPS on a color NeXT handles brightness and the way most other OS's handle brightness is quite noticable. Assuming you have on your NeXT the same programs I have on mine, you can see this difference by: open up a GIF image (in PixelMagician, in my case) & save it as TIFF open up the TIFF file (in TIFFany, in my case) & use a Brightness Control panel (in the Color Control inspector) to apply a gamma of 0.4545 (or maybe a little higher, 0.5 or 0.6). Compare the result of that with the original image. If the original was created for some other platform, the above transformation will result in a much more realistic looking picture. The funny thing is that many pictures won't seem to look all that bad until you have the corrected version of the picture to compare it against. Things get a little tricker than even that, as people with greyscale NeXTstations do not get the type of brightness processing that a user gets when using NeXTSTEP on a Color machine. Thus, a picture which looks too bright on a color NeXT will probably look about right on a greyscale machine. And if you correct the brightness so things look right on the color machine, it will look much too dark on the greyscale machine. As I understand it, there is good reason for the way NeXTSTEP handles brightness on a color display. However, the consequence of that is that "generic viewers" (such as GIF viewers) need to have some way to adjust the brightness level of images that they display. Note that this has to be an *option* - it can't be automatically done all the time - if for no other reason than images on greyscale NeXT's would come out wrong. I do believe that there are some GIF viewers for NeXTSTEP which have that ability, but I don't know which ones those would be. I really can't imagine the rationale behind the brightness being handled differently between color and greyscale NeXT's. I find this rather irritating, in fact. It means that any image (such as face-tiffs for mail) really have to be setup as two images, one for color and one for greyscale, in order to get the brightness level right on all NeXTSTEP machines. Arrrrggggggg!! (note that I don't know if NS/Intel running on greyscale PC's works like greyscale NeXTstations or like color NeXTstations. It's clear from your comment that NS/Intel on color PC's works like color NeXTstations). Disclaimer: I make no pretensions of being an expert in this area. I'm sure that someone who understands the issues more would do a better job at explaining it. Added rambling: People have complained that NS-3.0 icons look "muddy" (or something) on greyscale machines. I wonder if this might be partially due to this brightness mismatch between color and greyscale machines? -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Newsgroups: comp.sys.next.bugs From: yanik@planon.qc.ca (Yanik Crepeau) Subject: Re: Watch for NS/I viruses Message-ID: <1993Sep24.184005.1546@CAM.ORG!planon> Sender: yanik@CAM.ORG!planon References: <CDsFMA.24o@infoserv.com> Distribution: na Date: Fri, 24 Sep 1993 18:40:05 GMT In article <CDsFMA.24o@infoserv.com> kent@infoserv.com writes: | In article <1993Sep22.133028.1887@corona.com> pkron@corona.com (Peter Kron) | writes: | #> Last week I had my Toshiba 4400C portable at a service center | #> for some work. A few days later they called me and told me | #> it had a virus that had infected their disks. I did not | #> beleive them as it is soleley configured as a NeXTSTEP | #> machine, with no DOS partition. | | They do not know what they are talking about. | | If it only has UNIX, it could not infect their | diskettes with a DOS virus. | | Kent | -- | /* K.L. Shephard Consulting is my company. Infoserv only delivers my mail. */ | /* Please direct mail to kent@infoserv.com other adresses may not work. */ For DOS people, NeXTSTEP IS the ultimate virus. NeXTSTEP mania is a very contagious disease. -- Yanik Crepeau Programmer Planon Telexpertise E-Mail: yanik@planon.qc.ca (NeXT)
Newsgroups: comp.sys.next.bugs,comp.sys.next.software From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Re: Better color in Windooze than in NS? Message-ID: <1993Sep25.105734.4031@prim.demon.co.uk> Organization: Primitive Software Ltd. References: <chris.748897239@vincent1.iastate.edu> <280seh$dsl@usenet.rpi.edu> Date: Sat, 25 Sep 1993 10:57:34 GMT In article <280seh$dsl@usenet.rpi.edu> gad@eclipse.its.rpi.edu (Garance A. Drosehn) writes: > >As I understand it, there is good reason for the way NeXTSTEP handles >brightness on a color display. However, the consequence of that >is that "generic viewers" (such as GIF viewers) need to have some >way to adjust the brightness level of images that they display. Note >that this has to be an *option* - it can't be automatically done all >the time - if for no other reason than images on greyscale NeXT's >would come out wrong. I do believe that there are some GIF viewers >for NeXTSTEP which have that ability, but I don't know which ones >those would be. I've just compared a monalisa.gif under ViewGif3 and ImageViewer 0.7 on my monochrome display and the results are strikingly different. The ImageViewer version looks over-exposed, while the ViewGif3 one is darker and richer. Dave Griffiths PS: Does anyone know of a Filter Service for GIFs?
Newsgroups: comp.sys.next.bugs From: hellgate.utah.edu!uplherc!cusa!magnusson!kris (Kristopher Magnusson) Subject: Try this one.... Message-ID: <1993Sep25.044413.240@magnusson.uucp> Sender: kris@magnusson.uucp Organization: Salt Lake area NeXT Group Date: Sat, 25 Sep 1993 04:44:13 GMT I found an interesting bug. When I use NewsGrazer to uudecode GIFs, I display them with Graphics Workshop. Sometimes GW spins into hyperspace, so I keep open the Processes panel in the workspace and push "Kill" and let the modal panel "Do you really want to kill Graphics Workshop?" hang open. If I double-click on the GW icon on the dock when this modal panel is open, the Workspace hides itself as expected--but when I double-click on the NeXT icon at the top of the dock the Workspace doesn't reappear. I'm able to repeat this bug at will, but I don't like to as I have to open a Terminal window and sync the file system and warm boot the machine. Oh well.... Kris Magnusson Alpine Computing NeXT salesdroid -- Kris Magnusson <hellgate!uplherc!cusa!neb!magnusson!kris> Alpine Computing ------------------------------------------------------------------------------- #import <salespitchforcloneEpsonIntelDECALRASTCompaqNECHPandwrittenguarantee.h> ------------------------------------------------------------------------------- "I'd give my right arm to be ambidextrous." --Marvin Gardner
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.bugs Subject: Re: New serial drivers in this century? Date: 23 Sep 1993 09:19:51 +0100 Organization: Palumbian Research Labs Message-ID: <27rm77$1jf@marsu.tynet.sub.org> References: <26sfmv$1ac@marsu.tynet.sub.org> <27ck2v$7l4@email.tuwien.ac.at> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit max@fml.tuwien.ac.at (Maximilian Hantsch) writes: >In article <26sfmv$1ac@marsu.tynet.sub.org> mow@marsu.tynet.sub.org (Markus >Wenzel) writes: >> Maybe they still released a beta. I shot the new drivers twice using >> 38400 bps DTE speed. At least the error messages became much more >> verbose before entering the famous "RDP exception". However, the >> new drivers seem to be stable at 19200. >Well, I'm afraid I had exactly the same problems with the new driver and 19200 >baud when I happened to switch the modem off and on again. >I have put the modem back to a Motorola machine for now. Hmm... I just checked switching off the modem - my machine is still alive. But I usually leave my modem on-line 24 hours a day. I'm glad about the new drivers. At 19200 DTE speed and 16800 Zyxel connection, Taylor-uucp i-protocol makes up to 2000 cps. That's it! Regards, Markus. -- /dev Markus Wenzel, University of Stuttgart /usr/spool/mail mow@marsu.tynet.sub.org ~/.ircrc/nick Marsu /etc/motd Yesterday MS-DOS reformatted my NeXTSTEP partiton.
Newsgroups: comp.sys.next.bugs From: uunet!lkba!lkb (Larry Blische) Subject: Re: Watch for NS/I viruses Message-ID: <1993Sep25.204405.827@lkba.uucp> Sender: lkb@lkba.uucp (Larry Blische) Organization: LKB Associates, Inc. References: <2809v4$7n1@geraldo.cc.utexas.edu> Date: Sat, 25 Sep 1993 20:44:05 GMT A couple of questions about this virus stuff: What is a BIOS virus? A ROM cannot be contaminated so is this really caused by code that has infected the boot block? Which boot block (I assume that there is a boot block for each OS partition)? How can a partition table be infected by a virus? Does the partition table contain executable code? How can a virus propagate without executing code? --- Larry Blische lkba!lkb@uunet.UU.NET LKB Associates, Inc. NeXTmail Welcome! 3118 Dunglow Road 410 285 2262 Dundalk, Maryland 21222-5304 USA
Newsgroups: comp.sys.next.bugs From: andrew@stone.com (Andrew Stone) Subject: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep26.042215.415@stone.com> Keywords: shift tab Sender: andrew@stone.com Organization: Stone Design Corp Date: Sun, 26 Sep 1993 04:22:15 GMT Stick something on your pasteboard, say an image from Create. In Mail.app, Compose, tab, tab, tab, down into the body text. Hit shift-tab. Do you go back to CC: field? Nope. Weird eh? andrew Mach kernel version: NeXT Mach 3.1: Fri Apr 30 08:31:15 PDT 1993; root(rcbuilder):mk-149.22.3.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 33 MHz Processor active: 0 System type: 5 Board revision: 0xf Primary memory available: 64.00 megabytes. Default processor set: 51 tasks, 81 threads, 1 processors Load average: 1.18, Mach factor: 0.70 -- ||<<->>||<<==>>||<<++>>||<<?>>||<<+>>||<<-->>||<<==>>||<<+>>|| !! Andrew Stone !! (505) 345-4800 !! !! andrew@stone.com <> Stone Design Corp !! ||<<->>||<<==>>||<<++>>||<<?>>||<<+>>||<<-->>||<<==>>||<<+>>||
Newsgroups: comp.sys.next.bugs From: alex@cs.umd.edu (Alex Blakemore) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <CDyrHL.1J1@genoa.com> Sender: alex@genoa.com (Alex Blakemore) Organization: Genoa Software Systems References: <1993Sep26.042215.415@stone.com> Date: Sun, 26 Sep 1993 13:44:09 GMT In article <1993Sep26.042215.415@stone.com> andrew@stone.com (Andrew Stone) writes: > Stick something on your pasteboard, say an image from Create. > In Mail.app, Compose, tab, tab, tab, down into the body text. > Hit shift-tab. Do you go back to CC: field? > Nope. on my system, it behaves the same way even if there is not an image on the pasteboard (running on a black mono turbo with NS 3.1) -- Alex Blakemore alex@cs.umd.edu NeXT mail accepted
From: mycroft@monolith.utexas.edu (Alex Currier) Newsgroups: comp.sys.next.bugs Subject: Re: Cool "bug/feature" in Mail.app... Date: 26 Sep 1993 18:44:29 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <284nud$9ac@geraldo.cc.utexas.edu> References: <CDyrHL.1J1@genoa.com> In article <CDyrHL.1J1@genoa.com> alex@cs.umd.edu (Alex Blakemore) writes: > > Stick something on your pasteboard, say an image from Create. > > In Mail.app, Compose, tab, tab, tab, down into the body text. > > Hit shift-tab. Do you go back to CC: field? > > Nope. > > on my system, it behaves the same way even if there > is not an image on the pasteboard Same here. Is there some significance to this? NeXTdimension '040. NS v3.0 -- ======================================================================== Alex Currier | History is made at night... mycroft@ccwf.cc.utexas.edu | Character is what you are in the dark. ========================================================================
Newsgroups: comp.sys.next.bugs From: mross@antigone.com Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep26.233027.2333@antigone.com> Organization: Antigone Press gateway, San Francisco References: <CDyrHL.1J1@genoa.com> <284nud$9ac@geraldo.cc.utexas.edu> Date: Sun, 26 Sep 1993 23:30:27 GMT Alex Currier (mycroft@monolith.utexas.edu) wrote: : In article <CDyrHL.1J1@genoa.com> alex@cs.umd.edu (Alex Blakemore) writes: : > > Stick something on your pasteboard, say an image from Create. : > > In Mail.app, Compose, tab, tab, tab, down into the body text. : > > Hit shift-tab. Do you go back to CC: field? : > > Nope. : > on my system, it behaves the same way even if there : > is not an image on the pasteboard : Same here. Is there some significance to this? It's been this way throughout NS1.0, NS2.0, NS3.0. With or without pasteboard objects. It's a feature, not a bug. :) -- Michael Ross Antigone Press, San Francisco, California e-mail: mross@antigone.com FAX: +1 415 431 3650
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Message-ID: <CDzu18.9IH@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI Date: Mon, 27 Sep 1993 03:36:45 GMT Hi Folks, No. I'm not using dblspace, never have, and don't intend to. We've been using NEXTSTEP with an 80Mb DOS partition ever since NS/Intel shipped. We've always experienced weird behaviour, but have just put up with it until now. Some of the problems we see are: Files on the DOS partition appear to be filled with zeros when accessed from NEXTSTEP Copying files to the DOS partition from NEXTSTEP corrupts other unrelated DOS files. Example: chkdsk under DOS shows no trouble, run NEXTSTEP, add a file to the DOS partition, boot DOS and chkdsk has trouble. NOTE: We use this machine under DOS not nearly as much as we do under NEXTSTEP, but still enough to be sure that as long as we're totally in DOS there's no trouble. df and the workspace report that the disk is completely full when it is not. Under DOS, chkdsk and Norton both say that there is 10Mb free. One thing that I noticed that Norton Disk Doctor says in its report is "Large Partition: yes". I've scanned the Norton manual for just what this means, but to no avail. What's going on? I love NEXTSTEP, but the trouble we've had with the filesystem has been a constant source of pain. Yesterday Command.com was fried enough so that DOS would start to boot, but hang after autoexec.bat was hit. Fun Fun. I haven't sent this to NeXT because there's some chance that I've missed something trivial, like a statement that partitions can only be so large or whatnot. I tried looking through the documentation for anything that might be relevant, but Digital Librarian appears to be broken. If I ask to see anything with "DOS" in it, nothing shows up, even in the man pages, but when I ask "fdisk", the entry for fdisk, which has "DOS" in it appears. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs Subject: Printing DBTableviews From: David_Boyle@kcbbs.gen.nz (David Boyle) Date: 27 Sep 93 02:48:01 GMT Message-ID: <5993269.10081.22404@kcbbs.gen.nz> Organization: Kappa Crucis Unix BBS, Auckland, New Zealand We appear to be seeing a bug in the DBTableView postscript generator. When a window containing a DBTableView is printed, data is not displayed until a cell with a formatter is drawn, then all subsequent cells are drawn correctly. This is a little puzzling because the postscript generated for the screen should be similar to that generated for the printer, and it works on the screen. The error is that font information is not being prepared prior to drawing the cells themselves. i.e.: - draw the tableview background, borders, scrollbar etc - save context - ERROR: should set up font info here - print each cell, working top to bottom, left to right. I have printed to a file, and inserted the following lines just after the save context: /Helvetica findfont 12 scalefont [1 0 0 -1 0 0] makefont 1001 exch defineuserobject 1001 execuserobject setfont and everything prints just fine. It is not just our printer that is complaining, the previewer is unable to display the windows properly as well. We are running 3.1 on NextStation turbos. Are there any workarounds, or are we doing something stupid. I guess a solution is to attach a formatter to the first column of every tableview and set the font on the first cell - ick. ADVthanksANCE david
Newsgroups: comp.sys.next.bugs From: dimitri@dutiws.twi.tudelft.nl (Dimitri Tischenko) Subject: Booting, Edit and Project Builder Message-ID: <CE0D1F.Kpn@dutiws.twi.tudelft.nl> Organization: Delft University of Technology Date: Mon, 27 Sep 1993 10:27:15 GMT This is my last posting before I submit the bug reports to NeXT. 1. When booting a 486 clone with an UN-1072 IDE controller and WD Caviar 200MB drive with a 80 MB DOS partition, the system pauses at "registering hc0" and continues with the following error message: ide:Read error: status=0x50 error=0x0 cyl=0x0 sec=0x1 drhd=0x00 The hd device is registered normally and the drive functions properly, except for 2. When saving a file with Edit _in certain directories_ the system panics with a KerneTrap Raise RDP exception 2 code d subcode 55540000 Waiting for RDP connection (type 'c' to continue) Typing 'c' does not do much, the only way to recover is a cold boot. NB: when saving the same file with vi, everything is ok. Possible connection between 1 and 2? 3. When remotely building projects with Project Builder, PB does not find files correctly when the user clicks on an compiler error message. Workaround: make a link to /Net called Net in the project directory (and as needed). Is there a better work-around or a solution? Dimitri -- +----------------------------------------------------------------------------+ | Dimitri Tischenko | D.B.Tischenko@TWI.TUDelft.NL | NeXTmail preferred! | +---------------------------------------+------------------------------------+ | Delft University of Technology | Technische Universiteit Delft | | Fac Applied Math & Computer Science | Fac. Techn. Wiskunde & Informatica | | The Netherlands | Nederland | +---------------------------------------+------------------------------------+
Newsgroups: comp.sys.next.bugs From: Michael_Pizolato@afs.com (Michael Pizolato) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep27.144400.430@afs.com> Sender: Michael_Pizolato@afs.com References: <1993Sep26.042215.415@stone.com> Date: Mon, 27 Sep 1993 14:44:00 GMT Andrew Stone writes >Stick something on your pasteboard, say an image from Create. > >In Mail.app, Compose, tab, tab, tab, down into the body text. > >Hit shift-tab. Do you go back to CC: field? > >Nope. > >Weird eh? Alex Blakemore writes >on my system, it behaves the same way even if there is not an >image on the pasteboard > >(running on a black mono turbo with NS 3.1) Alex Currier writes >Same here. Is there some significance to this? Michael Ross >It's been this way throughout NS1.0, NS2.0, NS3.0. With or without >pasteboard objects. It's a feature, not a bug. :) Guys, that last big field in a Compose window is a Scrollview. Scrollviews don't have a nextText ivar. You can't tab out of them in any direction, never could. Program much? ;-) Thanx, Michael -- Michael_Pizolato@afs.com NeXTMail accepted
From: jweiss@casbah.acns.nwu.edu (Jerry Weiss) Newsgroups: comp.sys.next.bugs Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Date: 27 Sep 1993 17:35:14 GMT Organization: Northwestern University, Evanston IL USA Message-ID: <28788i$505@news.acns.nwu.edu> References: <CDzu18.9IH@cobra.cs.unm.edu> In article <CDzu18.9IH@cobra.cs.unm.edu>, <ctm@ardi.com> wrote: >Hi Folks, > >No. I'm not using dblspace, never have, and don't intend to. > >We've been using NEXTSTEP with an 80Mb DOS partition ever since NS/Intel >shipped. We've always experienced weird behaviour, but have just put up >with it until now. Some of the problems we see are: > > Files on the DOS partition appear to be filled with zeros > when accessed from NEXTSTEP > Well, I have 100Mb Partition and I have see this from time to time. The data is there but the unused bytes in some blocks show up as nulls. > Copying files to the DOS partition from NEXTSTEP corrupts > other unrelated DOS files. Example: chkdsk under DOS shows > no trouble, run NEXTSTEP, add a file to the DOS partition, > boot DOS and chkdsk has trouble. NOTE: We use this machine > under DOS not nearly as much as we do under NEXTSTEP, but > still enough to be sure that as long as we're totally in > DOS there's no trouble. > I haven't seen this. > df and the workspace report that the disk is completely full > when it is not. Under DOS, chkdsk and Norton both say that > there is 10Mb free. > The unix/Next way of file systems is to "reserve" 20% for root access only. This makes sense on a real Unix partition, not so much sense on the DOS partition. It's very annoying. You can use tunefs (I think) to change the Unix partition. I have and it works. I have not found a way to change the DOS paritition. The usual unix tools don't work, sigh. The Dos partition is a little weak, possibly buggy. Some of this has to do with DOS and all the evil that implies. -- Jerry S. Weiss j-weiss@nwu.edu Dept. Medicine, Northwestern Univ. Medical School, Chicago, Illinois %SYSTEM-S-PHALOKTARG, Phasers Locked on Target, Ready to Fire
Newsgroups: comp.sys.next.bugs From: bstone@acs.ucalgary.ca (Blake Stone) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <Sep27.194905.51374@acs.ucalgary.ca> Date: Mon, 27 Sep 1993 19:49:05 GMT References: <CDyrHL.1J1@genoa.com> <284nud$9ac@geraldo.cc.utexas.edu> <1993Sep26.233027.2333@antigone.com> Organization: The University of Calgary, Alberta > > > Stick something on your pasteboard, say an image from > > > Create. In Mail.app, Compose, tab, tab, tab, down into the > > > body text. > > > Hit shift-tab. > > on my system, it behaves the same way even if there is not an > > image on the pasteboard > It's been this way throughout NS1.0, NS2.0, NS3.0. With or > without pasteboard objects. It's a feature, not a bug. :) Errr.... am I missing out totally? What Andrew was referring to was that shift-tab in the body of a mail message acts just like selecting paste from the edit menu. How can that possibly work "with or without pasteboard objects"? Or "the same way even if there is not an image on the pasteboard"? While I thought the behaviour of Mail.app was strange, the behaviour of people in comp.sys.next.* may be stranger yet... -- Blake W. Stone | DKW Systems Corporation Chief Technical Officer | A N[EXTSTEP,eXT[STEP,step,Step]] VAR bstone@acs.ucalgary.ca | | ... couldn't have been ME
Newsgroups: comp.sys.next.bugs From: alex@data.acs.calpoly.edu (Alex Raftis) Subject: Re: Better color in Windooze than in NS? Message-ID: <1993Sep27.194448.23914@rat.csc.calpoly.edu> Date: Mon, 27 Sep 93 19:44:48 GMT Organization: Cal Poly, SLO References: <chris.748897239@vincent1.iastate.edu> In article <chris.748897239@vincent1.iastate.edu> chris@iastate.edu (Chris Wong) writes: > It's amazing that viewing GIF files under Windooze or OS/2 is much > much much better than viewing them under NS/FIP. > > Those images (GIFs) are copied from my DOS floppy and viewed under > NS/FIP 3.1 with Dell 450DE/2 DGX. The difference between viewing > these images under Windooze and NS/FIP is that.... the images seems to > be "whitened" for a certain degree by DPS. > > Anything wrong with my hardware or NS? > > Those NS TIFFs icons are pretty. > > BTW, postscript images (not in EPS format) has the same problem as > GIF's. (I created the postscript file under xv for X from an GIF > file.) > As I understand it, NS/Intel uses a 12 bit color model, while most Dos gif viewers will use a 256 color color model. That this means to you is that under the 12 bit display, colors will be dithered to try and approximate 24 bit color. The end result of this is to produce colors that are slightly washed out. As someone in a previous post stated, the easiest fix is adjust the gamma through some program that supports it. Alex -- ______________________________________________________ Internet: alex@data.acs.calpoly.edu (NeXT mail) alex@cosmos.acs.calpoly.edu
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: NXZoneFromPtr() not thread-safe? Message-ID: <1993Sep27.180044.9395@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. Date: Mon, 27 Sep 1993 18:00:44 GMT We have a problem in which it appears that an Object's zone method intermittently returns an invalid pointer. It is hard to get a handle on because the problem occurs inside of Next's distributed object code. We are working in a multi-threaded environment using only the default zone (the zone returned by NXDefaultMallocZone()). We have specified objc_setMultithreaded(YES), and we are using thread-safe memory allocation. We disassembled [Object zone] and NXZoneFromPtr() in gdb. NXZoneFromPtr() is called from within -zone method to find the (NXZone *) zone. It seems they are not thread-safe in the way that the malloc/free functions are. (ie. they don't seem to use the nxzonemalloc mutex lock. The NXZoneFromPtr() branches to subroutine findregionnolock to do the work of getting the zone - the "nolock" portion is consistent with the nxzonemalloc routine in that once it acquires a mutex lock, it branches to subroutine nxzonemallocnolock - but NXZoneFromPtr() does NOT attempt to acquire any locks prior to branching to subroutine findregionnolock. We are speculating that NXZoneFromPtr() can examine the zone data structure while it the zone is in an inconsistent state during modification by the malloc/free functions in another thread. Two questions: Has anyone else seen similar problems with [Object zone] and/or NXZoneFromPtr() in a multi-threaded environment? What work arounds can you suggest? brad... -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Date: Mon, 27 Sep 1993 16:08:42 -0400 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Message-ID: <4gdoV_600WB3Qle4xX@andrew.cmu.edu> In-Reply-To: <28788i$505@news.acns.nwu.edu> Excerpts from netnews.comp.sys.next.bugs: 27-Sep-93 Re: Anyone using an 80Mb DO.. by Jerry Weiss@casbah.acns. > The unix/Next way of file systems is to "reserve" 20% for root access > only. This makes sense on a real Unix partition, not so much sense > on the DOS partition. It's very annoying. You can use tunefs (I think) to > change the Unix partition. I have and it works. I have not found > a way to change the DOS paritition. The usual unix tools don't work, sigh. The percentage typically reserved is actually 10%. The reason this is done is because NeXT uses the "Berkeley Fast File System" (FFS), which tries to do disk activity in such a way as to avoid fragmenting the disk. This automatic defragging requires some spare space to work. My drive is nearly two years old, and it has about .5% fragmentation, without ever having been defragmented. BTW, using tunefs can give you additional space, but you will suffer a performance penalty for doing so. It's a tradeoff that you'll have to decide upon yourself.... -Chuck Charles William Swiger -- CMU...*crunch*! | 1. You can't fly. ------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@mon.slip.andrew.cmu.edu | 4. Fire burns.
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 27 Sep 1993 16:26:40 -0400 Organization: Next Announcements Message-ID: <287i9t$dof@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs,comp.unix.programmer,comp.sys.next.programmer From: ross@utopia.druid.com (Ross Ridge) Subject: Re: tgetstr() problems & incomplete curses library References: <1993Sep24.174130.16968@cs.ucla.edu> Organization: (none) Date: Mon, 27 Sep 1993 08:56:36 GMT Message-ID: <1993Sep27.085636.1905@utopia.druid.com> esky@marathon.cs.ucla.edu (Eskandar Ensafi) writes: > char *area = (char *)malloc( 252); ... > tgetstr( "me", &area); /* the code for all attributes off */ > >As expected, 'area' was incremented by the number of bytes contained in the >termcap entry for "me"... >Then, when the program terminated (running under gdb), it exited with an >error code (012 _without_ explicitly calling 'free( area)' and 0360 when I >attempted to 'free( area)' myself before exiting.) How does your programme exit? Are you returning from main() without a value? You can't call "free(area)", because "area" doesn't point to the start of memory you allocated with malloc. Ross Ridge
Newsgroups: comp.sys.next.bugs From: johnc@object.com (John Coppinger) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep27.232850.743@object.com> Sender: johnc@object.com Organization: Objective Technologies,Inc. References: <1993Sep26.042215.415@stone.com> Date: Mon, 27 Sep 93 23:28:50 GMT In article <1993Sep26.042215.415@stone.com> andrew@stone.com (Andrew Stone) writes: > Stick something on your pasteboard, say an image from Create. > In Mail.app, Compose, tab, tab, tab, down into the body text. > Hit shift-tab. Do you go back to CC: field? Turns out that shift-tab maps to the same charCode as ctrl-y (that's the strange part). In emacs, ctrl-y is yank. I guess NeXT's emacs keybindings code does a paste: when asked to yank. So, shift-tab does a paste. John Coppinger Objective Technologies, Inc. johnc@object.com
Newsgroups: comp.sys.next.bugs From: gjudd@hackatg.demon.co.uk (Graham Judd) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep28.111353.731@hackatg.demon.co.uk> Sender: gjudd@hackatg.demon.co.uk Organization: Hackwood Service Company References: <1993Sep28.004204.6016@stone.com> Date: Tue, 28 Sep 1993 11:13:53 GMT In article <1993Sep28.004204.6016@stone.com> andrew@stone.com (Andrew Stone) writes: [munch] > > How many of you who tried this has Emacs mode on in Mail? > > andrew Not me, don't use emacs mode so shift-tab seems to do nothing... Graham
Newsgroups: comp.sys.next.bugs From: Michael_Pizolato@afs.com (Michael Pizolato) Subject: Re: Cool "bug/feature" in Mail.app... Message-ID: <1993Sep28.144240.735@afs.com> Sender: michael_pizolato@afs.com References: <1993Sep27.144400.430@afs.com> Date: Tue, 28 Sep 1993 14:42:40 GMT Michael Pizolato (that's me) writes >Andrew Stone writes >>Stick something on your pasteboard, say an image from Create. >> >>In Mail.app, Compose, tab, tab, tab, down into the body text. >> >>Hit shift-tab. Do you go back to CC: field? >> >>Nope. >> >>Weird eh? > >Alex Blakemore writes >>on my system, it behaves the same way even if there is not an >>image on the pasteboard >> >>(running on a black mono turbo with NS 3.1) > >Alex Currier writes >>Same here. Is there some significance to this? > >Michael Ross >>It's been this way throughout NS1.0, NS2.0, NS3.0. With or without >>pasteboard objects. It's a feature, not a bug. :) > >Guys, that last big field in a Compose window is a Scrollview. >Scrollviews don't have a nextText ivar. You can't tab out of them >in any direction, never could. > >Program much? ;-) Once again, I leap before I look. As others have asked, could this "interesting" behavior be due to emacs key bindings? I don't think that whatever this key binding is is advertized as one of the ones turned on when you set emacs key bindings on in Mail preferences. Thanx, Michael P.S. I'm right about ScrollViews, though ;-). You'd have to override their normal behavior to tab out of them back to the other fields, and that's no good, especially if you're constructing carefully formated NeXTMail with rulers and all. -- Michael_Pizolato@afs.com NeXTMail accepted
From: ling@earl (Robert Ling) Newsgroups: comp.sys.next.bugs Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Date: 28 Sep 1993 18:58:30 GMT Organization: Los Alamos National Laboratory, NM Message-ID: <28a1gm$3ci@news.u.washington.edu> References: <4gdoV_600WB3Qle4xX@andrew.cmu.edu> I have a 100Mb DOS 5.0 partition on my main disk which also has NS/I and another 120Mb DOS 5.0 disk. With 30Mb free in the 100Mb DOS partition and 58Mb free on the 120Mb DOS disk, NS/I reports only 0.1Mb and 2Mb available, respectively. I don't think the "lost" space can be accounted for by the "reserve" if NS/I uses that for the DOS partition at all. - Robert Ling <rling@u.washington.edu> In article <4gdoV_600WB3Qle4xX@andrew.cmu.edu> Charles William Swiger <infidel+@CMU.EDU> writes: >Excerpts from netnews.comp.sys.next.bugs: 27-Sep-93 Re: Anyone using an >80Mb DO.. by Jerry Weiss@casbah.acns. >> The unix/Next way of file systems is to "reserve" 20% for root access >> only. This makes sense on a real Unix partition, not so much sense >> on the DOS partition. It's very annoying. You can use tunefs (I think) to >> change the Unix partition. I have and it works. I have not found >> a way to change the DOS paritition. The usual unix tools don't work, sigh. > >The percentage typically reserved is actually 10%. The reason this is >done is because NeXT uses the "Berkeley Fast File System" (FFS), which >tries to do disk activity in such a way as to avoid fragmenting the >disk. This automatic defragging requires some spare space to work. >
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: Re: NXZoneFromPtr() not thread-safe? Message-ID: <1993Sep28.184920.384@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. References: <1993Sep27.180044.9395@instep.wimsey.bc.ca> Date: Tue, 28 Sep 1993 18:49:20 GMT In article <1993Sep27.180044.9395@instep.wimsey.bc.ca> brad@instep.wimsey.bc.ca writes: > > We have a problem in which it appears that an Object's zone method > intermittently returns an invalid pointer. It is hard to > get a handle on because the problem occurs inside of Next's > distributed object code. [stuff deleted] > NXZoneFromPtr() does NOT attempt to acquire any locks prior to branching > to subroutine findregionnolock. > > We are speculating that NXZoneFromPtr() can examine the zone > data structure while it the zone is in an inconsistent state during > modification by the malloc/free functions in another thread. I forgot to mention that this problem is using NS 3.0. Here's the code from NS 3.0 for NXZoneFromPtr() contrasted to NeXT's bug fix for NS 3.1's NXZoneFromPtr(): NEXTSTEP RELEASE 3.0 NXZoneFromPtr(): (gdb) disass NXZoneFromPtr Dump of assembler code for function NXZoneFromPtr: 0x5009de8 <NXZoneFromPtr>: linkw fp,#0 0x5009dec <NXZoneFromPtr+4>: movel fp@(8),sp@- 0x5009df0 <NXZoneFromPtr+8>: bsr 0x507202a <findregionnolock> 0x5009df6 <NXZoneFromPtr+14>: moveal d0,a0 0x5009df8 <NXZoneFromPtr+16>: tstl a0 0x5009dfa <NXZoneFromPtr+18>: beq 0x5009e00 <NXZoneFromPtr+24> 0x5009dfc <NXZoneFromPtr+20>: movel a0@(8),d0 0x5009e00 <NXZoneFromPtr+24>: unlk fp 0x5009e02 <NXZoneFromPtr+26>: rts End of assembler dump. NEXTSTEP RELEASE 3.1 NXZoneFromPtr(): (gdb) disass NXZoneFromPtr Dump of assembler code for function NXZoneFromPtr: to 0x5009e46: 0x5009dfc <NXZoneFromPtr>: linkw fp,#0 0x5009e00 <NXZoneFromPtr+4>: movel a2,sp@- 0x5009e02 <NXZoneFromPtr+6>: lea @#0x4011504 <rld_env+692>,a2 0x5009e08 <NXZoneFromPtr+12>: movel a2@,sp@- 0x5009e0a <NXZoneFromPtr+14>: bsrl 0x5008a8c <mutex_try_lock> 0x5009e10 <NXZoneFromPtr+20>: addqw #4,sp 0x5009e12 <NXZoneFromPtr+22>: tstl d0 0x5009e14 <NXZoneFromPtr+24>: bne 0x5009e20 <NXZoneFromPtr+36> 0x5009e16 <NXZoneFromPtr+26>: movel a2@,sp@- 0x5009e18 <NXZoneFromPtr+28>: bsrl 0x5024660 <mutex_wait_lock> 0x5009e1e <NXZoneFromPtr+34>: addqw #4,sp 0x5009e20 <NXZoneFromPtr+36>: movel fp@(8),sp@- 0x5009e24 <NXZoneFromPtr+40>: bsrl 0x5072ebe <findregionnolock> 0x5009e2a <NXZoneFromPtr+46>: moveal d0,a0 0x5009e2c <NXZoneFromPtr+48>: clrl d0 0x5009e2e <NXZoneFromPtr+50>: tstl a0 0x5009e30 <NXZoneFromPtr+52>: beq 0x5009e36 <NXZoneFromPtr+58> 0x5009e32 <NXZoneFromPtr+54>: movel a0@(8),d0 0x5009e36 <NXZoneFromPtr+58>: moveal @#0x4011504 <rld_env+692>,a0 0x5009e3c <NXZoneFromPtr+64>: clrl a0@ 0x5009e3e <NXZoneFromPtr+66>: moveal fp@(-4),a2 0x5009e42 <NXZoneFromPtr+70>: unlk fp 0x5009e44 <NXZoneFromPtr+72>: rts End of assembler dump. (gdb) To my knowledge, NeXT QUIETLY fixed this BUG (lack of mutex locking) in NEXTSTEP 3.1. We've been frustrated by this bug for several weeks now with our multithreaded server at a customer site crashing about once a day due to this 3.0 BUG. I'm appalled by the poor developer relations NeXT has when it comes to revealing bugs in their code. This bug has cost our company time and money (and an ear full of customer complaints). We made the mistake of thinking it was a bug in our code - refusing to believe our eyes when debugging the core files since it seemed to indicate a bug in NeXT's fundamental NXZoneFromPtr() function. If we'd known that the bug in NS 3.0 existed when NeXT first discovered it (or more correctly, when some unfortunate registered developer reported it), we would have saved ourselves a lot of time and money. I vote NeXT release timely development kit BUG reports to registered developers (with workarounds if possible). Brad. -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: jweiss@casbah.acns.nwu.edu (Jerry Weiss) Newsgroups: comp.sys.next.bugs Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Date: 28 Sep 1993 20:00:17 GMT Organization: Northwestern University, Evanston IL USA Message-ID: <28a54h$a1g@news.acns.nwu.edu> References: <4gdoV_600WB3Qle4xX@andrew.cmu.edu> <28a1gm$3ci@news.u.washington.edu> In article <28a1gm$3ci@news.u.washington.edu>, Robert Ling <ling@earl> wrote: >I have a 100Mb DOS 5.0 partition on my main disk which also has >NS/I and another 120Mb DOS 5.0 disk. With 30Mb free in the 100Mb >DOS partition and 58Mb free on the 120Mb DOS disk, NS/I reports >only 0.1Mb and 2Mb available, respectively. I don't think the >"lost" space can be accounted for by the "reserve" if NS/I uses >that for the DOS partition at all. > Are you running Windows or some disk compression stuff? I think if you have Windows swap files, they can eat up some space. With disk compression, the actual and real sizes will differ. NS cannot access compressed files on such a disk anyway. -- Jerry S. Weiss j-weiss@nwu.edu Dept. Medicine, Northwestern Univ. Medical School, Chicago, Illinois %SYSTEM-S-PHALOKTARG, Phasers Locked on Target, Ready to Fire
Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin From: agnus@amylnd.stgt.sub.org (Matthias Zepf) Subject: Re: NeXT Printer bug in 3.1 Content-Type: text/plain; charset=ISO-8859-1 Message-ID: <1993Sep28.082947.3577@amylnd.stgt.sub.org> Followup-To: comp.sys.next.bugs,comp.sys.next.sysadmin Content-Transfer-Encoding: 8bit Organization: Agnus' Home, Leonberg/Warmbronn, Germany References: <27u4ds$g2h@news.cs.tu-berlin.de> Mime-Version: 1.0 Date: Tue, 28 Sep 1993 08:29:47 GMT Marcel Weiher (marcel@cs.tu-berlin.de) wrote: > "...put an invisible rotation on the image..." > /image { gsave .1 rotate image grestore } bind def This rotation is NOT invisible. You should use .01 or .001!! Then this fix works great! Matthias -- ** Matthias Zepf, Riegelaeckerstrasse 27, 71 229 Leonberg, Germany ** ** +49 7152 41917 Email: agnus@amylnd.stgt.sub.org (use NeXTmail!) **
Newsgroups: comp.sys.next.bugs,comp.unix.programmer,comp.sys.next.programmer From: int145w@aurora.cc.monash.edu.au (Tobias Sargeant) Subject: Re: tgetstr() problems & incomplete curses library Message-ID: <1993Sep28.191728.9239@monu6.cc.monash.edu.au> Sender: news@monu6.cc.monash.edu.au (Usenet system) Organization: Monash University References: <1993Sep24.174130.16968@cs.ucla.edu> Date: Tue, 28 Sep 1993 19:17:28 GMT Eskandar Ensafi (esky@marathon.cs.ucla.edu) wrote: : : I have noticed that using 'tgetstr( char *id, char **area)' results in : my programs exiting with either code 012 or 0360. I'm probably stupid, but the man page here says tgetstr(char *id,char *area). ---- Tobias Sargeant. -------- Man cares for all: to birds he gives his woods, ---------------------. | To beasts his pastures, and to fish his floods; | | For some his Int'rest prompts him to provide, | | For more his pleasure, yet for more his pride: | | All feed on one vain Patron, and enjoy | `-------- Th' extensive blessing of his luxury. -------------- Alexander Pope -'
Newsgroups: comp.sys.next.bugs From: thf@zelator.in-berlin.de (Thomas Funke) Subject: Re: tgetstr() problems & incomplete curses library Message-ID: <1993Sep27.131038.939@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization References: <1993Sep24.174130.16968@cs.ucla.edu> Date: Mon, 27 Sep 1993 13:10:38 GMT In article <1993Sep24.174130.16968@cs.ucla.edu> esky@marathon.cs.ucla.edu (Eskandar Ensafi) writes: > > And to top this off, my curses library lacks attron(), attroff(), > etc..., so I can't even give up and use those functions instead > -- I *REALLY* need help! > > > P.S. Why doesn't NeXT update its libcurses.a (not to mention a > whole bunch of > other UNIXish C libraries) ??? > NeXT curses is the really old version from BSD4.3. Quite a junk actually. Does anybody know of a Sys-V compatible FREE version of curses ? -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brook's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
From: lee@daruma.zoo.duke.edu (Lee Altenberg) Newsgroups: comp.sys.next.bugs Subject: NeXT Printer gone under 3.0! Help. Message-ID: <21148@news.duke.edu> Date: 28 Sep 93 22:12:49 GMT Sender: news@news.duke.edu Organization: Duke University Zoology Dept.; Durham, N.C. I just upgraded a 68040 Cube from NEXTSTEP 2.1 to 3.0 , and the NeXT Printer disappeared as a configured printer under the Print window and PrintManager, and is no longer an option for configuring new printers under PrintManager. There is a mysterious entry under "Type" for Create New Printer option of PrintManager, "NeXT 400 dpi Level II Printer", but in grey font that you can't select. How do I get the Next Printer back? Thanks, Lee Altenberg altenber@acpub.duke.edu
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Message-ID: <CE32Bv.3Mt@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI References: <4gdoV_600WB3Qle4xX@andrew.cmu.edu> <28a1gm$3ci@news.u.washington.edu> Date: Tue, 28 Sep 1993 21:28:46 GMT In article <28a1gm$3ci@news.u.washington.edu> ling@earl (Robert Ling) writes: >I have a 100Mb DOS 5.0 partition on my main disk which also has >NS/I and another 120Mb DOS 5.0 disk. With 30Mb free in the 100Mb >DOS partition and 58Mb free on the 120Mb DOS disk, NS/I reports >only 0.1Mb and 2Mb available, respectively. I don't think the >"lost" space can be accounted for by the "reserve" if NS/I uses >that for the DOS partition at all. > >- Robert Ling <rling@u.washington.edu> T H A N K Y O U That's definitely one of the symptoms I'm seeing. I am really curious as to how many people have DOS partitions >= 80Mb and how much chkdsk under DOS disagrees with df under NEXTSTEP. I'm aware of the FFS stuff; I remember when Kirk made his infamous ~oh, that's when we start using the ECC bits for data~ at a FFS tutorial at Usenix during 4.1c BSD days. That's not relevant because the DOS filesystem isn't FFS. Something fishy is going on and if it's only affecting a few people, that may mean that NeXT doesn't know about it which may mean that it won't be fixed in 3.2. This is real bad. I'm not griping on my own behalf here (we now just sneakernet our data back and forth using a floppy disk). I'm seriously worried that there are esoteric, but nonetheless major, problems with the DOS filesystem support under NEXTSTEP/Intel. Interestingly enough, when I defragged my disk (using the 6.0 defrag utility), it went from some small amount of free space, to no free space at all. Could it be that NeXT's DOS filesystem implementation figures out how many free blocks there are by examining only the first N clusters (or whatever you call them)? If this is the case, then that would mean that as long as you had sufficient free space in the beginning of your filesystem, you wouldn't necessarily notice a difference. I'd love to know who is having problems and who isn't and whether or not defragging changes the amount of free space for other people as well. I'd also feel more comfortable if I got e-mail from someone at NeXT saying that this thread is being followed. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? Message-ID: <CE32Fz.3pD@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI References: <4gdoV_600WB3Qle4xX@andrew.cmu.edu> <28a1gm$3ci@news.u.washington.edu> <28a54h$a1g@news.acns.nwu.edu> Date: Tue, 28 Sep 1993 21:31:13 GMT In article <28a54h$a1g@news.acns.nwu.edu> jweiss@casbah.acns.nwu.edu (Jerry Weiss) writes: >In article <28a1gm$3ci@news.u.washington.edu>, Robert Ling <ling@earl> wrote: >>I have a 100Mb DOS 5.0 partition on my main disk which also has >>NS/I and another 120Mb DOS 5.0 disk. With 30Mb free in the 100Mb >>DOS partition and 58Mb free on the 120Mb DOS disk, NS/I reports >>only 0.1Mb and 2Mb available, respectively. I don't think the >>"lost" space can be accounted for by the "reserve" if NS/I uses >>that for the DOS partition at all. >> > >Are you running Windows or some disk compression stuff? > >I think if you have Windows swap files, they can eat up some space. > >With disk compression, the actual and real sizes will differ. >NS cannot access compressed files on such a disk anyway. I'm the person who started this thread and I have the same trouble Robert has and I am not running Windows, and I am not using compression. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: More fun with DOS partitions Message-ID: <CE3sHL.8zD@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI Date: Wed, 29 Sep 1993 06:53:47 GMT DOS-sters, Earlier I mentioned troubles that I've had with our DOS partition. I asked how many other people were doing similar things to what I'm doing and got back a couple replies that might have been matches, but the replier wasn't explicit and one person who confirmed the bad behaviour. I've since taken some time out to futz with my DOS partition and I strongly suspect that NeXT is at least in some cases not looking at the entire filesystem. If I use "defrag" from DOS 6.0 and "optimize" the partition, then by definition, all the blocks at the beginning of the disk will be used and all the free space will be coalesced into one lump at the end of the disk. When I do this, and then boot NEXTSTEP I am told that my DOS partition has 0 free blocks left. If I deliberately make a whole, say by copying a file, and deleting the original, NEXTSTEP sees some space. So, is there anyone out there who has a DOS partition that is larger than 64Mb (i'm guessing that the 64Mb is where NEXT drops the ball) who also has defrag or some other optimizer that can be used to move all the used disk blocks to the head of the partition? Can you do that and let me know what you find? My suspicion is that df will only list the free blocks that it finds before some magic cutoff (probably 64Mb), or perhaps will work fine, unless you have more blocks used than some magic cutoff. I want to report this to NeXT later today (Wednesday), but I want as much info as possible, especially if the majority of you *can't* reproduce the strange behaviour I'm seeing. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: Watch for NS/I viruses Message-ID: <1993Sep28.134907.3511@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Sep25.204405.827@lkba.uucp> Date: Tue, 28 Sep 1993 13:49:07 GMT In article <1993Sep25.204405.827@lkba.uucp> uunet!lkba!lkb (Larry Blische) writes: -> A couple of questions about this virus stuff: -> -> What is a BIOS virus? A ROM cannot be contaminated so is this really caused -> by code that has infected the boot block? Which boot block (I assume that -> there is a boot block for each OS partition)? -> -> How can a partition table be infected by a virus? -> Does the partition table contain executable code? -> How can a virus propagate without executing code? -> -> --- -> Larry Blische lkba!lkb@uunet.UU.NET -> LKB Associates, Inc. NeXTmail Welcome! -> 3118 Dunglow Road 410 285 2262 -> Dundalk, Maryland 21222-5304 USA -> Does the partition table contain executable code? That's the ticket. It can easily be disassembled with quite a number of utilities (most of which are on the DOS side). Essentially it's a boot-strap's bootstrap, in addition to tabular information. Bruce Gingery bruce@TotSysSoft.com NeXT-mail preferred, Mime-mail ok
From: blake015@mc.duke.edu (Denise Blakeley) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: TIFFs not showing up in NeXTMail messages under NSFIP Message-ID: <21190@news.duke.edu> Date: 29 Sep 93 18:37:07 GMT Sender: news@news.duke.edu Followup-To: comp.sys.next.misc Yesterday I composed a NeXTMail message to one of my colleagues on a Turbo Color 32/400 running NS 3.1. I drag-and-dropped several icons into the message to show him what I've been up to. They are all 48x48, 2, 8, and 12-bit TIFFs. When he views the message in NeXTMail on his machine, the icons do not appear! The rest of the message is intact. His machine is a Dell 466/ME 32/400 running NSFIP. When he views the message on black hardware, the icons show up just fine. Is this a new NeXTMail NSFIP bug? Denise -- Denise Blakeley | PROGRAM, tr. v., An activity similar Duke Med Center Info Systems | to banging one's head against a wall, Durham, NC | but with fewer opportunities for (919) 282-6468 W | reward. blake015@mc.duke.edu |
Newsgroups: comp.sys.next.bugs From: df@watershed.com (Dirk P. Fromhein) Subject: New ATI Driver not working Message-ID: <CE3LJw.6KA@ripple.uunet> Sender: jaeger@ripple.uunet (Dirk P. Fromhein) Organization: Watershed Technologies, Inc. Date: Wed, 29 Sep 1993 04:23:56 GMT I just got the new ATI driver from NeXT and I am having quite a few problems with it. I'm using it with an Intel GX/Pro with 2MB VRAM. If I use it at 1120x832x16bit color my monitor (a MAG 17") has lines at the far right of the display, and when I drag a window the whole screen distorts badly (very). Multi-color Lines flash across the screen. When I use it in 1120x832x8bit mono it is much better, but still has lines on the far left of the display. When I use it at 1280x1024 it totally freaks out, the screen blanks, then nearly fills with while lines, then blanks... It will not work at all. So, now is it my monitor ? (it works just fine at 1280x1024 under NT) It seems to not be able to synch correctly. I would like to hear other people's experience. Thanks, --- Dirk Fromhein df@watershed.com Watershed Technologies, Inc. (508)-460-9612 Voice (508)-481-3955 Fax -- Dirk Fromhein df@watershed.com Watershed Technologies, Inc. (508)-460-9612 Voice
From: jweiss@casbah.acns.nwu.edu (Jerry Weiss) Newsgroups: comp.sys.next.bugs Subject: Re: New ATI Driver not working Date: 29 Sep 1993 21:37:36 GMT Organization: Northwestern University, Evanston IL USA Message-ID: <28cv70$e33@news.acns.nwu.edu> References: <CE3LJw.6KA@ripple.uunet> In article <CE3LJw.6KA@ripple.uunet>, Dirk P. Fromhein <df@watershed.com> wrote: > >I just got the new ATI driver from NeXT and I am having quite a few problems >with it. I'm using it with an Intel GX/Pro with 2MB VRAM. > >If I use it at 1120x832x16bit color my monitor (a MAG 17") has lines at the far >right of the display, and when I drag a window the whole screen distorts badly >(very). Multi-color Lines flash across the screen. > I tried it this morning with the Gateway version of that monitor and computer. I could not get the MAG to handle 1120x832x16 color at anything but 60hz. I did have to tweek the controls on the mag to get things centered right. At 68Hz I could see distortion and I figure the the ATI board (and XLR in mine whatever the heck that is) cannot handle it. >When I use it in 1120x832x8bit mono it is much better, but still has lines on >the far left of the display. > >When I use it at 1280x1024 it totally freaks out, the screen blanks, then >nearly fills with while lines, then blanks... It will not work at all. I didn't see a problem with this, but again I was set to 60hz. Things look kinda small on a 17" monitor anyway. > >So, now is it my monitor ? (it works just fine at 1280x1024 under NT) >It seems to not be able to synch correctly. >I would like to hear other people's experience. > I supposedly have one of the newer Mach32 chips in my board, but I do not know enough about things to do anything more than speculate that this may also be a factor. BTW, Thanks to NeXT for the newer drivers. 1120x832 Looks great on 17". I only wish I could get up to 64Hz or so. One thing I don't like is the fact that the grey color used for disk spaced size is always fuzzy looking (at any resolution) on Mag 15 and 17" monitors (or gateway equivalents). Anyone know a quick hack to change the size/color to something more reasonable. -- Jerry S. Weiss j-weiss@nwu.edu Dept. Medicine, Northwestern Univ. Medical School, Chicago, Illinois %SYSTEM-S-PHALOKTARG, Phasers Locked on Target, Ready to Fire
From: jon@starburst.umd.edu (Jonathan Kruger) Newsgroups: comp.sys.next.bugs Subject: Re: New ATI Driver not working Date: 29 Sep 1993 21:55:02 GMT Organization: Chesapeake Biological Laboratory Message-ID: <28d07m$gdq@gamera.umd.edu> References: <CE3LJw.6KA@ripple.uunet> df@watershed.com (Dirk P. Fromhein) writes: > I just got the new ATI driver from NeXT and I am having quite a few > problems with it. I'm using it with an Intel GX/Pro with 2MB VRAM. > > If I use it at 1120x832x16bit color my monitor (a MAG 17") has lines > at the far right of the display, and when I drag a window the whole > screen distorts badly (very). Multi-color Lines flash across the > screen. > > When I use it in 1120x832x8bit mono it is much better, but still has > lines on the far left of the display. I had the exact same experience on my Mag MX17F. The README file did *not* say that it would work at 1120x832x16, even though the resolution select panel in Configure allows you to select it. It did say that it works at 1120x832x8, which it does not (almost, but not quite). At 1024x768x16 there is a definite speed improvement (like, "half as slow?") which makes installing the new driver worthwhile regardless, but video performance on my 486/66DX2 is still well below that of a -- ------------------------------------------------------------------------------- Jonathan Kruger - jon@cbl.umd.edu - Computer and Network Systems Coordinator UMCEES/CBL, PO Box 38, Solomons, MD 20688 Phone: 410-326-7306 Fax: 410-326-7341
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Date: Thu, 30 Sep 1993 06:58:10 PDT Message-ID: <1993Sep30.135810.183@corona.com> Newsgroups: comp.sys.next.bugs Subject: Re: Anyone using an 80Mb DOS 6.0 partition and NEXTSTEP? References: <CE32Bv.3Mt@cobra.cs.unm.edu> ctm@ardi.com writes: > In article <28a1gm$3ci@news.u.washington.edu> ling@earl (Robert Ling) writes: > >I have a 100Mb DOS 5.0 partition on my main disk which also has > >NS/I and another 120Mb DOS 5.0 disk. With 30Mb free in the 100Mb > >DOS partition and 58Mb free on the 120Mb DOS disk, NS/I reports > >only 0.1Mb and 2Mb available, respectively. I don't think the > >"lost" space can be accounted for by the "reserve" if NS/I uses > >that for the DOS partition at all. > > > >- Robert Ling <rling@u.washington.edu> > > T H A N K Y O U > > That's definitely one of the symptoms I'm seeing. I am > really curious as to how many people have DOS partitions >= > 80Mb and how much chkdsk under DOS disagrees with df under > NEXTSTEP. I'm aware of the FFS stuff; I remember when Kirk > made his infamous ~oh, that's when we start using the ECC bits > for data~ at a FFS tutorial at Usenix during 4.1c BSD days. > That's not relevant because the DOS filesystem isn't FFS. > Something fishy is going on and if it's only affecting a few > people, that may mean that NeXT doesn't know about it which > may mean that it won't be fixed in 3.2. I show the same situation: DOS reports more space free than NEXTSTEP, although in my case it may be due to the reserve. This is on the boot IDE drive, which has a 112Mb DOS partition and a 120Mb NS partition. From df: Filesystem kbytes used avail capacity Mounted on /dev/hd0a 122232 103825 12295 89% / /dev/rhd0h 112450 106874 5576 95% /disk_ide230 From chkdsk: Volume DISK_IDE230 created 06-01-1993 7:28a Volume Serial Number is 0543-1DD8 115146752 bytes total disk space 73728 bytes in 2 hidden files 362496 bytes in 163 directories 91789312 bytes in 2860 user files 22921216 bytes available on disk 2048 bytes in each allocation unit 56224 total allocation units on disk 11192 available allocation units on disk 655360 total bytes memory 540000 bytes free I haven't had any problems with moving files to and from dos via the disk. --- NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
From: npratt@glacier.sim.es.com (Nevin Pratt) Newsgroups: comp.sys.next.bugs Subject: Re: New ATI Driver not working Date: 30 Sep 1993 15:57:53 GMT Organization: E&S Distribution: world Message-ID: <28evm1$m2e@cnn.sim.es.com> References: <28d07m$gdq@gamera.umd.edu> In article gdq@gamera.umd.edu, jon@starburst.umd.edu (Jonathan Kruger) writes: > df@watershed.com (Dirk P. Fromhein) writes: > > > I just got the new ATI driver from NeXT and I am having quite a few > > problems with it. I'm using it with an Intel GX/Pro with 2MB VRAM. > > > > If I use it at 1120x832x16bit color my monitor (a MAG 17") has lines > > at the far right of the display, and when I drag a window the whole > > screen distorts badly (very). Multi-color Lines flash across the > > screen. > > > > When I use it in 1120x832x8bit mono it is much better, but still has > > lines on the far left of the display. > > I had the exact same experience on my Mag MX17F. The README file did > *not* say that it would work at 1120x832x16, even though the > resolution select panel in Configure allows you to select it. It did > say that it works at 1120x832x8, which it does not (almost, but not > quite). 1120x832x8bit @ 68 hz on my Sony CPD-1730 is rock solid. 1120x832x16bit @ 60/68 hz produces the symptoms you describe. I suspect these anomolies are due to monitor differences. Nevin
Newsgroups: comp.sys.next.bugs From: souksam@next.nb.rockwell.com (Tommy Souksamlane) Subject: NS Terminal bug Message-ID: <1993Sep30.180753.18524@nb.rockwell.com> Sender: news@nb.rockwell.com Organization: Rockwell International Date: Thu, 30 Sep 1993 18:07:53 GMT The VT100 emulation on the NS 3.1 Terminal program does not translate the top row keypads at all. Does anybody have a fix that can be used? Also, when I tried using the previous version in NS 3.0 of Terminal program the /dev/ttyp files are not set correctly. The following error is displayed: /dev/ttyp6: Not owner mesg: cannot change mode Please help!! ----------------- Tommy Souksamlane _______ Rockwell International Corporation /##|||##\ Telecommunication Division /###|||###\ 4311 Jamboree Road |####/|\####| Newport Beach, Calif. 92660 USA |###/ | \###| Email: souksam@next.nb.rockwell.com \#/ /#\ \#/ ___________________________________________\_/###\_/______________ >> All opinions are my own, not Rockwell's. "Choose Life"
Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware From: alastair@farli.otago.ac.nz (Alastair Thomson) Subject: Re: New ATI Driver not working Message-ID: <CE6snu.9En@news.otago.ac.nz> Sender: usenet@news.otago.ac.nz (News stuff) Organization: University of Otago References: <28evm1$m2e@cnn.sim.es.com> Date: Thu, 30 Sep 1993 21:50:18 GMT In article <28evm1$m2e@cnn.sim.es.com> npratt@glacier.sim.es.com (Nevin Pratt) writes: > > 1120x832x8bit @ 68 hz on my Sony CPD-1730 is rock solid. > > 1120x832x16bit @ 60/68 hz produces the symptoms you describe. > > I suspect these anomolies are due to monitor differences. > > Nevin We have a Sony CPD-1730S (Southern Hemisphere) with ATI LocalBuThe pic is fine at 1120x832, either 8 or 16-bit, we can even manage to lock it at 1280x1024 8-bit. Things are fine until we move a window/dock/menu, then shimmering lines appear. It looks like scan linea are randomly shifted to the right by about 30 odd pixels. I would suggest it is a bus timing problem, conflicting with retrace or some such, as when I stop moving the window all is happy again. We are using a DECpc 466d2 MTE and VL-Bus ATI GUP. We have one of the new ATI cards arriving in the next couple of days, it will be interesting to see what that does. By the way, welcome to the wonderful world of the PC, trying to get drivers to work with all configurations is hell, keep at it NeXT, we really do appreciate your work! -- Alastair Thomson, | Phone +64-3-479-8347 Black Albatross Chief Programmer, | Fax +64-3-479-8529 Department of Computer Science, | University of Otago, | alastair@farli.otago.ac.nz Dunedin, New Zealand | NeXTmail Welcome
Newsgroups: comp.sys.next.bugs From: df@watershed.com (Dirk P. Fromhein) Subject: Re: New ATI Driver not working Message-ID: <CE6v9B.C0@ripple.uunet> Sender: jaeger@ripple.uunet (Dirk P. Fromhein) Organization: Watershed Technologies, Inc. References: <28evm1$m2e@cnn.sim.es.com> Date: Thu, 30 Sep 1993 22:46:22 GMT In article <28evm1$m2e@cnn.sim.es.com> npratt@glacier.sim.es.com (Nevin Pratt) writes: > In article gdq@gamera.umd.edu, jon@starburst.umd.edu (Jonathan Kruger) writes: > > df@watershed.com (Dirk P. Fromhein) writes: > > > > > I just got the new ATI driver from NeXT and I am having quite a few > > > problems with it. I'm using it with an Intel GX/Pro with 2MB VRAM. > > > [munch munch] > > 1120x832x8bit @ 68 hz on my Sony CPD-1730 is rock solid. > > 1120x832x16bit @ 60/68 hz produces the symptoms you describe. > > I suspect these anomolies are due to monitor differences. > > Nevin > Wait a sec, I thought the Sony CPD-1730 only did 1024x768? That was the one reason I did not buy it. -- Dirk Fromhein df@watershed.com Watershed Technologies, Inc. (508)-460-9612 Voice
From: ellis@nova.gmi.edu (R. Stewart Ellis) Newsgroups: comp.sys.next.bugs,comp.unix.questions Subject: Apps and utils can't access /dev/tty on NeXT 68K, OS version 3,HELP Date: 1 Oct 93 14:14:25 GMT Organization: GMI Engineering&Management Institute, Flint, MI Message-ID: <ellis.749484865@nova> I am helping someone with net sourceware software installation on a NeXT 68K, OS version 3. A number of the utils are unable to access /dev/tty and I am at a loss to understand what is wrong. About the only things I can see are that the ownership may be wrong on /dev/tty, or there may be an improper link. I can't find a MKDEV file or anything to examine, so I am asking for your help. Here is the output of everything I can think of that might have some relevance. I have been using and programming and admin'ing UNIX for 8 or so years, and this one is a little different. While we are at it, where is libc? I do not have physical access to the machine and the owner is not a C programmer or UNIX expert. csf /Editors/ellis> cat >/dev/tty /dev/tty: No such device or address. csf /Editors/ellis> l /dev/tty crw-rw-rw- 1 root wheel 2, 0 Apr 8 08:13 /dev/tty csf /Editors/ellis> eval `resize` resize: can't open terminal /dev/tty csf /Editors/ellis> kermit Error opening /dev/tty congm: No such device or address C-Kermit 5A(170) ALPHA, 23 Apr 91, NeXT Type ? or 'help' for help csf /Editors/ellis> l /dev lrwxrwxrwx 1 root wheel 11 Jan 5 1993 /dev -> private/dev@ csf /Editors/ellis> l `which kermit` -rwxr-xr-x 1 root wheel 266816 Aug 25 22:47 /usr/local/bin/kermit* csf /Editors/ellis> l `which resize` -rwxr-xr-x 1 2018 218 16384 Oct 30 1992 /usr/bin/X11/resize* csf /Editors/ellis> Can someone please offer me any insight? Thanks for any suggestions. -- R.Stewart(Stew) Ellis, Assoc.Prof., (Off)313-762-9765 ___________________ Humanities & Social Science, GMI Eng.& Mgmt. Inst. / _____ ______ Flint, MI 48504 ellis@nova.gmi.edu / / / / / / Gopher,News and sendmail maintainer, all around hack /________/ / / / /
Newsgroups: comp.sys.next.bugs From: scott@henson.cc.wwu.edu (J. Scott Williams) Subject: Problem Using rsh from NeXT to Ultrix Message-ID: <1993Oct1.215113.25252@henson.cc.wwu.edu> Summary: Can't rsh from NeXT to Ultrix Keywords: rsh NeXT Ultrix rlogin Organization: Western Washington University Date: Fri, 1 Oct 1993 21:51:13 GMT I have a users with NeXTStep 2.x and 3.0 and 3.1. None of these users can successfully use the "rsh" command to execute a command on our Ultrix hosts. The rlogin command for the NeXT works fine so I know the Ultrix .rhosts file/entry are OK. Other users on other platforms can rsh successfully to this particular Ultrix host. And the NeXT can sucessfully rsh to a Sun. Does anyone have any wisdom about this problem that they are willing to share with me? -jscott- -- |J. Scott Williams Ph: (206) 650-2868 FAX: (206) 650-6548 | |Academic Tech. User Services Internet: scott@henson.cc.wwu.edu | |Western Washington Univ. "Internet--Talking across the electronic| |Bellingham, WA 98225-9094 back fence of the world."-JSW|
Newsgroups: comp.sys.next.bugs From: twasko@cuug.ab.ca (Tim Wasko 403-266-0900) Subject: Re: New ATI Driver not working Sender: usenet@cuug.ab.ca Message-ID: <CE89ut.78I@cuug.ab.ca> Date: Fri, 1 Oct 1993 16:59:17 GMT Organization: Calgary UNIX User's Group I too have some of the same problems that you experience. I get the sparkling dashed lines on the left of the screen when I move a window around. I do get a faint vertical distortion (unevenness in color) on the left. This problem only occurs in 1120x832x16-bits, the 8 bit gray work fine. The 1280x1024x8 works fine for my monitor (Seiko CM1706-LR 17" Trinitron). The 800x600x16 mode hasn't been tested yet (who want that low res.). Tim
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: thf@zelator.in-berlin.de (Thomas Funke) Subject: No more processes (NS3.1) Message-ID: <1993Oct2.010642.2832@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization Date: Sat, 2 Oct 1993 01:06:42 GMT I just noticed that you get this bug not only when dragging files around, as NeXT has admitted recently, but also when doing a command-u, Update Viewers. Strange: with 'ps aux' you cannot see those "too many processes". *** Problem forking /usr/lib/NextStep/Workspace.app/WM.app/AppFinder.tool (errno = 11) Really annoying, seems we have to keep on using shells. -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brook's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Re: Problem Using rsh from NeXT to Ultrix Message-ID: <1993Oct2.205902.6097@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software References: <1993Oct1.215113.25252@henson.cc.wwu.edu> Date: Sat, 2 Oct 1993 20:59:02 GMT In article <1993Oct1.215113.25252@henson.cc.wwu.edu> scott@henson.cc.wwu.edu (J. Scott Williams) writes: -> I have a users with NeXTStep 2.x and 3.0 and 3.1. -> -> None of these users can successfully use the "rsh" -> command to execute a command on our Ultrix hosts. -> -> The rlogin command for the NeXT works fine so I know -> the Ultrix .rhosts file/entry are OK. Other users -> on other platforms can rsh successfully to this -> particular Ultrix host. And the NeXT can sucessfully -> rsh to a Sun. -> -> Does anyone have any wisdom about this problem that they -> are willing to share with me? -> -> -jscott- Does the Ultrix system have the "classed as experimental" user "auth"orization protocol installed -- Hmmm was that kerberos? -- which is not being confirmed by the NeXTs, yet required on the Ultrix box? Bruce Gingery bruce@TotSysSoft.com
From: samurai@amber.hasc.ca (Darcy Brockbank) Newsgroups: comp.sys.next.bugs Subject: Re: Cool "bug/feature" in Mail.app... (and Edit.app) Message-ID: <28mv76$6lu@amber.hasc.ca> Date: 3 Oct 93 16:39:02 GMT References: <1993Sep28.004204.6016@stone.com> Organization: The Hutchison Avenue Software Corp. In article <1993Sep28.004204.6016@stone.com> andrew@stone.com (Andrew Stone) writes: > "Turns out that shift-tab maps to the same charCode as ctrl-y (that's the > strange part). In emacs, ctrl-y is yank. I guess NeXT's emacs > keybindings code does a paste: when asked to yank. So, shift-tab does a > paste. Our emacs bindings did the same thing until I patched it." > How many of you who tried this has Emacs mode on in Mail? If nobody else has made the leap yet... the same behaviour is in Edit.app as well, but not NewsGrazer.app. This seems to be because the EmacsText code does use the pasteboard when you do a Control-K. So either Control-Y or paste will bring the text back... wierd that Control-Y is a backtab character though... I didn't know that. - db -- "No man should be discouraged from entering business through fear of taxation." -- N. Machiavelli "Oh God, I've got to catch Matlock at the courthouse and let him know that we've been tricked!" -- Me, (very confused) on awakening, Sep 24, 1993 ----- Opionions expressed by me, are not necessarily those of HASC -------
From: mcquill@keen.ccit.duq.edu (Tod McQuillin) Newsgroups: comp.sys.next.bugs,comp.unix.questions Subject: Re: Apps and utils can't access /dev/tty on NeXT 68K, OS version 3,HELP Message-ID: <28naqb$27q@noether.mathcs.duq.edu> Date: 3 Oct 93 19:56:58 GMT References: <ellis.749484865@nova> Followup-To: comp.sys.next.bugs,comp.unix.questions Organization: Duquesne University R. Stewart Ellis (ellis@nova.gmi.edu) wrote: : I am helping someone with net sourceware software installation on a NeXT : 68K, OS version 3. A number of the utils are unable to access /dev/tty and : I am at a loss to understand what is wrong. : csf /Editors/ellis> cat >/dev/tty : /dev/tty: No such device or address. I've encountered this a number of times, and just recently found a partial fix for it. The NeXT rlogind program does this as part of its startup (because it was erroneously compiled with DEBUG defined): int tt = open("/dev/tty", O_RDWR); if (tt > 0) { (void)ioctl(tt, TIOCNOTTY, 0); (void)close(tt); } Here is the only fix I've been able to find: I did kind of a gross thing. I wrote and ran this program: #include <sys/ioctl.h> main() { union { long l; char c[4]; } w; int i; w.l = TIOCNOTTY; for (i = 0; i < 4; i++) printf("%o\n", w.c[i]); } And then I loaded up /usr/etc/rlogind in emacs and found those bytes (they only occured once). I patched them to NUL's, and now I have a controlling tty when I log in with rlogin. Is that sick or what?
From: bestor@caracal.cs.wisc.edu (Gareth Bestor) Newsgroups: comp.sys.next.bugs Subject: Q: "ls -lR" bug with CD-ROMS? Message-ID: <1993Oct4.021344.2353@cs.wisc.edu> Date: 4 Oct 93 02:13:44 GMT Sender: news@cs.wisc.edu (The News) Organization: University of Wisconsin, Madison -- Computer Sciences Dept. I'm trying to get an ls -lR listing of some of my CD-ROMs and keep getting a weird "XXX not found" error on a few of them. For example: > jabberwocky:39# pwd <--- here's where I am > /CDROM_NEWS/NeXT/Games/xtank > > jabberwocky:40# ls -l <--- show me what's here. OK. > total 14 > -r--r--r-- 1 root 2449 Feb 9 1992 BETA-README > drwxr-xr-x 2 root 2048 Mar 7 1993 Bin/ > -r--r--r-- 1 root 638 Feb 9 1992 COPYRIGHT > drwxr-xr-x 3 root 2048 Mar 7 1993 Doc/ > drwxr-xr-x 2 root 2048 Mar 7 1993 Help/ > -rw-r--r-- 1 root 842 Feb 13 1992 Imakefile > -rw-r--r-- 1 root 11713 Mar 31 1992 Imakefile.Config > -rw-r--r-- 1 root 20895 Mar 31 1992 Makefile > drwxr-xr-x 2 root 18432 Mar 7 1993 Mazes/ > drwxr-xr-x 3 root 2048 Mar 7 1993 Programs/ > -r--r--r-- 1 root 1908 Feb 9 1992 README > drwxr-xr-x 7 root 10240 Mar 7 1993 Src/ > drwxr-xr-x 2 root 2048 Mar 7 1993 Todo/ > drwxr-xr-x 4 root 4096 Mar 7 1993 Util/ > drwxr-xr-x 2 root 61440 Mar 7 1993 Vehicles/ > > jabberwocky:41# ls -l /CDROM_NEWS/NeXT/Games/xtank <--- show me again. NO! > /CDROM_NEWS/NeXT/Games/xtank/Makefile not found > /CDROM_NEWS/NeXT/Games/xtank/Programs not found > /CDROM_NEWS/NeXT/Games/xtank/Util not found > total 12 > -r--r--r-- 1 root 2449 Feb 9 1992 BETA-README > drwxr-xr-x 2 root 2048 Mar 7 1993 Bin/ > -r--r--r-- 1 root 638 Feb 9 1992 COPYRIGHT > drwxr-xr-x 3 root 2048 Mar 7 1993 Doc/ > drwxr-xr-x 2 root 2048 Mar 7 1993 Help/ > -rw-r--r-- 1 root 842 Feb 13 1992 Imakefile > -rw-r--r-- 1 root 11713 Mar 31 1992 Imakefile.Config > drwxr-xr-x 2 root 18432 Mar 7 1993 Mazes/ > -r--r--r-- 1 root 1908 Feb 9 1992 README > drwxr-xr-x 7 root 10240 Mar 7 1993 Src/ > drwxr-xr-x 2 root 2048 Mar 7 1993 Todo/ > drwxr-xr-x 2 root 61440 Mar 7 1993 Vehicles/ > jabberwocky:42# > Why should command #40 work but not command #41 !!! This bug (?) means I can't get a full ls -lR listing from the root directory without getting a ton of the "XXX not found" errors. In fact, if I even try it takes forever and the computer eventually locks up and I have to pull the plug (no, I can't even get into the NMI monitor!). This happens on all my JANA CD-ROMs and the first issue of EAW, but not on any of my other CD-ROMs. Any ideas? - Gareth
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 5 Oct 1993 00:01:26 -0400 Organization: Next Announcements Message-ID: <28qrik$2q5@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Source links and 3.1's Edit.app Message-ID: <1993Oct5.060004.8445@csus.edu> Sender: news@csus.edu Organization: San Francisco State University Date: Tue, 5 Oct 1993 06:00:04 GMT + Name: Eric P. Scott + Organization or company: San Francisco State University + E-mail address: eps@CS.SFSU.EDU + Please check one that applies: x_Bug __Suggestion + Application where bug was found: Edit + NeXT system release: 3.1 + Application release: 3.0(v78) + Detailed description of the problem. Please include the minimum steps to reproduce this problem. If you cannot reproduce this problem, please indicate that in your report. Applications that support object linking are expected to create a DataLink manager for each of their documents. Edit contains all of the code necessary to serve as a source [for entire documents], but DataLink manager creation seems to be deliberately prevented except for a new document-- if the user preferences chose RTF for an existing document-- if it is RTFD (even RTF isn't good enough!) This bizarre restriction prevents software, such as a source code revision control system, from obtaining "when-source-saved" notifications through NXDataLinkManager. (Note that for such an application, NXSelection support isn't needed.) The following procedure creates a decrippled version of Edit on 3.1/m68k systems: 1) This patch is only for the Lightning4H Edit! % sum /NextApps/Edit.app/Edit 55340 356 2) Copy the app wrapper and the executable proper to your personal Apps subdirectory. % mkdir ~/Apps/Edit.app % cd ~/Apps/Edit.app % ln -s /NextApps/Edit.app/* . % rm Edit % cp -p /NextApps/Edit.app/Edit . 3) Using one of the publicly available binary patchers, nop out the RTF/RTFD tests; verify: % cmp -l /NextApps/Edit.app/Edit Edit 28251 147 116 28252 14 161 31989 147 116 31990 76 161 4) If the original Edit.app is in your dock, remove it. Drag the new Edit.app to your dock. Edit should now supply DataLink source information for plain ASCII text documents. "NO WARRANTY" This patch is not approved or supported by NeXT. Do not modify your original copy of Edit. If you don't understand what this patch accomplishes, you probably don't need it. User assumes full responsibility for consequences, including possible data loss or corruption, resulting from use of such modified software. Please do not redistribute modified versions unless they are clearly identified as such. No inference of the existence or operation of unannounced products should be made from this posting. Usual disclaimers apply. -=EPS=-
From: michaell@swdev.research.otc.com.au (Michael) Newsgroups: comp.sys.next.bugs Subject: Why entry still in services menu ?? Date: 5 Oct 1993 06:29:03 GMT Organization: Technical Development Group, Telstra International Sender: michaell@swdev.research.otc.com.au (Michael Lofquist) Distribution: world Message-ID: <28r47f$dq2@turin.research.otc.com.au> I down loaded sometime ago a copy of DataBag ! I tried it out and then removed from my machine. Still my applications ( Workspace manager, edit etc ) have a Services menu entry for the removed DataBag application !! Why is it still there. I thought that the Workspace manager investigates when it starts up what applications are availabe ? How can I get rid of it ?? Running NS 3.1 on motorola ! Michael
Newsgroups: comp.sys.next.bugs From: thf@zelator.in-berlin.de (Thomas Funke) Subject: Re: Q: "ls -lR" bug with CD-ROMS? Message-ID: <1993Oct5.120751.1185@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization References: <1993Oct4.021344.2353@cs.wisc.edu> Date: Tue, 5 Oct 1993 12:07:51 GMT In article <1993Oct4.021344.2353@cs.wisc.edu> bestor@caracal.cs.wisc.edu (Gareth Bestor) writes: > I'm trying to get an ls -lR listing of some of my CD-ROMs and keep > getting a weird "XXX not found" error on a few of them. For example: > Yes, this is a feature of the 3.1 'downgrade': You have to get the CDROM.fs from a 3.0 system.: It should look like this: ls -l /usr/filesystems/CDROM.fs/ total 80 -r--r--r-- 1 root 3546 Mar 26 1992 CDROM.fs.tiff -rw-r--r-- 1 root 5 Sep 28 12:07 CDROM.label -rw-r--r-- 1 root 16 Sep 28 12:07 CDROM.name -r--r--r-- 1 root 3546 Mar 26 1992 CDROM.openfs.tiff -rwsr-xr-x 1 root 24576 Jul 22 1992 CDROM.util* -rw-r--r-- 1 root 46224 Jul 22 1992 CDROM_reloc BTW: The filesystem which is delivered with 3.1 is not only buggy, it also has full debugging info inside. NeXT has to improve its beta-testing definitely, such hacks are really not acceptable for a commercial system. -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brook's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: scott@henson.cc.wwu.edu (J. Scott Williams) Subject: Re: Problem Using rsh from NeXT to Ultrix Message-ID: <1993Oct6.184912.20516@henson.cc.wwu.edu> Keywords: rsh NeXT Ultrix rlogin Organization: Western Washington University References: <1993Oct1.215113.25252@henson.cc.wwu.edu> Date: Wed, 6 Oct 1993 18:49:12 GMT scott@henson.cc.wwu.edu (J. Scott Williams) writes: >I have a users with NeXTStep 2.x and 3.0 and 3.1. >None of these users can successfully use the "rsh" command >to execute a command on our Ultrix hosts. >The rlogin command for the NeXT works fine so I know the Ultrix .rhosts >file/entry are OK. Other users on other platforms can rsh successfully >to this particular Ultrix host. And the NeXT can sucessfully rsh to a >Sun. > stuff deleted ..... I received the following via email that solved my problem. I put the NeXT host in the Ultrix /etc/hosts table and now rsh from the NeXT to the Ultrix machine works. ---------------- Cut Here ------------------- Date: Sat, 2 Oct 93 12:25:31 -0700 From: Magnus Nordborg <magnus@fisher.Stanford.EDU> To: scott@henson.cc.wwu.edu (J. Scott Williams) Subject: Re: Problem Using rsh from NeXT to Ultrix <stuff deleted> I believe this could be due to a classical Ultrix bug and unrelated to NeXTstep: You can only use rsh if the (calling) machines are in /etc/hosts on the Ultrix machine. I could remember this incorrectly, but check it. -- Magnus Nordborg magnus@fisher.stanford.edu (NeXT mail preferred) Department of Biological Sciences Stanford University Stanford, CA 94305-5020 +1 (415) 723-4952 (office) ------------------- Cut Here --------------- Thank you Magnus! -jscott- -- |J. Scott Williams, MH 354 Ph: (206) 650-2868 FAX: (206) 650-6548 | |Academic Tech. User Services Internet: scott@henson.cc.wwu.edu | |Western Washington Univ. "Internet--Talking across the electronic| |Bellingham, WA 98225-9094 back fence of the world."-JSW|
From: root@anton.music.washington.edu (Operator) Newsgroups: comp.sys.next.bugs Subject: Need help with screen problem Date: 6 Oct 1993 19:53:02 GMT Organization: University of Washington Message-ID: <28v7mu$f7v@news.u.washington.edu> The screen on our network server began going dark at random time intervals of about a minute two days ago. Now it goes dark every few seconds, and the problem seems to be spreading to other machines on the network. Can anyone offer some advice? Ron Averill School of Music Computer Center, University of Washington raverill@u.washington.edu
From: robert@amo.mit.edu(Robert Lutwak) Newsgroups: comp.sys.next.bugs Subject: NS3.1 telnetd Date: 6 Oct 1993 20:07:08 GMT Organization: Massachvsetts Institvte of Technology Message-ID: <28v8hc$sli@senator-bedfellow.MIT.EDU> O.K. This one has appeared scattered throughout CSN.misc for long enough to present it here: The telnet daemon just doesn't work if you try to connect to it from a PC running DOS or OS/2, or from a Macintosh. My personal experience is only with an OS/2 system, others have complained about similar experiences on the other platforms listed above. The OS/2 system (Gateway DX2/66 - 3COM Etherlink III) connects (no problems) with a NeXT running 3.0. When connecting to a NeXTcube running 3.1 it hangs after the connect message (no login prompt). When connecting to a NSI machine (Gateway DX2/66 - 3COM Etherlink III), you get a login prompt but then no password request. Both of the NS 3.1 machines connect just fine to each other or to the NS 3.0 machines. Usually, one fixes problems of this sort by re-installing the 3.0 version of the defective program. I haven't tried this, but I noticed that the file size of the (Black) telnetd is identical under 3.0 and 3.1. I notice also that /usr/etc/inetd has changed size, but I'm a little scared to go replacing that one. Is NeXT aware of this problem? Is there a fix available? -- Robert Lutwak robert@amo.mit.edu MIT Atomic Resonance and Spectroscopy Laboratory ---- NeXTmail always welcome ----
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Re: NS3.1 telnetd Message-ID: <1993Oct7.011126.15195@csus.edu> Sender: news@csus.edu Organization: San Francisco State University References: <28v8hc$sli@senator-bedfellow.MIT.EDU> Date: Thu, 7 Oct 1993 01:11:26 GMT In article <28v8hc$sli@senator-bedfellow.MIT.EDU> robert@amo.mit.edu (Robert Lutwak) writes: >The telnet daemon just doesn't work if you try to connect to it >from a PC running DOS or OS/2, or from a Macintosh. Actually, it just doesn't work. NeXT has been shipping the same *known to be defective* version of telnetd since 2.0--even though the problem was fixed in Berkeley sources over two years ago. >Usually, one fixes problems of this sort by re-installing the 3.0 >version of the defective program. I haven't tried this, but I >noticed that the file size of the (Black) telnetd is identical >under 3.0 and 3.1. I notice also that /usr/etc/inetd has >changed size, but I'm a little scared to go replacing that one. inetd is fine, leave it alone. >Is NeXT aware of this problem? Yes. Does NeXT care? Apparently not. >Is there a fix available? Not officially. -=EPS=-
From: anderson@macc.wisc.edu (Jess Anderson) Newsgroups: comp.sys.next.bugs Subject: Re: NS3.1 telnetd Date: 7 Oct 1993 09:56:57 GMT Organization: Division of Information Technology, UW-Madison Message-ID: <290p59$1te@news.doit.wisc.edu> References: <28v8hc$sli@senator-bedfellow.MIT.EDU> <1993Oct7.011126.15195@csus.edu> In article <1993Oct7.011126.15195@csus.edu>, Eric P. Scott <eps@cs.sfsu.edu> wrote: >In article <28v8hc$sli@senator-bedfellow.MIT.EDU> > robert@amo.mit.edu (Robert Lutwak) writes: >>The telnet daemon just doesn't work if you try to connect to it >>from a PC running DOS or OS/2, or from a Macintosh. >Actually, it just doesn't work. NeXT has been shipping the same >*known to be defective* version of telnetd since 2.0--even though >the problem was fixed in Berkeley sources over two years ago. Am I doing something wrong? It works just fine for me, if we're talking about running NCSA or Clarkson/Rutgers telnet on a DOS box. Do it all the time, never had a problem with it. -- [Jess Anderson <> Division of Information Technology, University of Wisconsin] [Internet: anderson@macc.wisc.edu {o"o} UUCP:{}!uwvax!macc.wisc.edu!anderson] [Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888] [--------------> What we do not understand we do not possess. <---------------]
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: jwdb@dutnak2.tn.tudelft.nl (Jan-Willem de Bruijn) Subject: Preferences(.app) corrupted by Cub'X ??? Message-ID: <jwdb.749989533@dutnak2> Summary: after installing Cub'X mouse no longer has menu button Keywords: mouse preferences Cub'X Sender: news@news.tudelft.nl (UseNet News System) Organization: Delft University of Technology Date: Thu, 7 Oct 1993 10:25:33 GMT I've seen strange things, but this one beats me. After I had installed the Cub'X-Window software, although I must say I don't know if this is the real cause, the mouse no longer had a menu button. Trying to change this back again with the Preferences.app, causes the latter program to crash. There is no way to configure the mouse with a menu button anymore. Also the Volume and Brightness sliders keep on moving back to their minimum and maximum positions respectively, no matter what you do. The Key Repeat Rate is reset to its slowest position, and although you can click on the buttons in the Keyboard Preferences panel, this has no effect. Does anyone have an explanation, or even better a remedy for this? Thanks in advance, Jan-Willem -- Jan-Willem de Bruijn jwdb@dutnak2.tn.tudelft.nl Lab. of Seismics and Acoustics NeXT-mail: jwdb@delphi.tn.tudelft.nl Dep. of Applied Physics Discipline is never an end in itself, Delft University of Technology only a means to an end.
From: eoliver@ralph.cs.haverford.edu (Erik Oliver) Newsgroups: comp.sys.next.bugs Subject: Re: NS3.1 telnetd Date: 7 Oct 1993 13:09:02 GMT Organization: Haverford College Computer Science Department Message-ID: <2914de$aos@saturn.haverford.edu> References: <28v8hc$sli@senator-bedfellow.MIT.EDU> <1993Oct7.011126.15195@csus.edu> <290p59$1te@news.doit.wisc.edu> Same here, we use NCSA telnet on our Appletalk and Ethertalk macs to copnnect to our NextStation Color running 3.0 and previously 2.X without any trouble. Additionally, we use telnet from any number of other uix platforms, Vax, and also occasionally PC' s running DOS without problems... So, I would really love to know what the problem is!!! -Erik In article <290p59$1te@news.doit.wisc.edu>, Jess Anderson <anderson@macc.wisc.edu> wrote: >In article <1993Oct7.011126.15195@csus.edu>, >Eric P. Scott <eps@cs.sfsu.edu> wrote: > >>In article <28v8hc$sli@senator-bedfellow.MIT.EDU> > >> robert@amo.mit.edu (Robert Lutwak) writes: >>>The telnet daemon just doesn't work if you try to connect to it >>>from a PC running DOS or OS/2, or from a Macintosh. > >>Actually, it just doesn't work. NeXT has been shipping the same >>*known to be defective* version of telnetd since 2.0--even though >>the problem was fixed in Berkeley sources over two years ago. > >Am I doing something wrong? It works just fine for me, if >we're talking about running NCSA or Clarkson/Rutgers telnet >on a DOS box. Do it all the time, never had a problem with >it. > >-- >[Jess Anderson <> Division of Information Technology, University of Wisconsin] >[Internet: anderson@macc.wisc.edu {o"o} UUCP:{}!uwvax!macc.wisc.edu!anderson] >[Room 3130 <> 1210 West Dayton Street / Madison WI 53706 <> Phone 608/262-5888] >[--------------> What we do not understand we do not possess. <---------------] -- Erik Oliver eoliver@haverford.edu (DISCLAIMER: Opinions expressed are mine and not the college's.)
From: statman@stat.ufl.edu (Charles D. Kincaid) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.misc,comp.sys.next.bugs Subject: 3.1 Librarian Questions Date: 7 Oct 1993 14:52:06 GMT Organization: University of Florida Message-ID: <291aemINN1ba@no-names.nerdc.ufl.edu> Hello, Alright, I'm stumped. There are a few of things in Librarian in NS3.1 that seem to be screwed up. The first and most important is that I don't get a one line summary of the files, like I used to. This makes looking things up in the FAQ, NeXTAnswers, NewsGrazer folder, etc., very difficult to do. I have to guess which one is useful. Is there an option that I can set either in the indexing script or in the searching script? ixbuild.1 and ixsearch.1 don't seem to help. Does Librarian use these? I assume so. The second thing is that I can't seem to index links to NewsGrazers folders correctly. In 2.1 I created a bunch of links to each *.nfold file and put the links into Librarian. This worked fine. But now if I put in the link it passes through the link and puts in the name of the file, e.g. faqs.nfold instead of faqs-news. Then when I try to index it says that it works, but it doesn't. I have appropriate permissions and a .index.store file does exist. The *.nfold files are actually on another mounted filesystem in a subdirectory of Library which I have linked to ~/Library. (Does this make sense?) This is exactly the same setup as in NS2.1 and it worked there. The third thing (and least important, but still annoying) is that I have the "Open in Librarian" checked for Text Files in Librarian Preferences. However, it still opens these in Edit. Is this proper? Am I misunderstanding what this means? I greatly appreciate all help. I rely on Librarian a lot. If I could use it correctly now, I probably wouldn't have to ask this. (And if this is a RTFM question, please tell me so, but also tell me where! :-) -- Sincerely, charles d. kincaid -------------------------------------------------------------------- Dept. of Statistics 'Damn fine coffee...and hot, too!' Univ. of Florida Pres: G-ville NeXT Users Group
From: giddings@whitewater.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Daily panic: NS Turbo Color: "out of softints" Date: 7 Oct 1993 17:06:27 GMT Organization: Division of Information Technology Distribution: world Message-ID: <291iaj$aoa@news.doit.wisc.edu> Keywords: panic Hello, We have a network of NeXT and Intel hardware, and ONE machine panics on a daily basis. This machine is an NS Turbo Color with 64 MB memory, running NS 3.1 developer. The message buffer goes something like follows: DOS File System: Initialized Panic: (CPU 0) out of softints Next Rom Monitor 3.3 v74 Panic: NEXT Mach 3.1 . . . . Panic: (CPU 0) out of softints kernel flag . unknown kernel flag exit unknown The only things that I know are unique to this machine is that it is running the MetroTools Login Window screen saver daemon, and that at boot time it often gives the message: sc: scintr program error Any suggestions or help would be appreciated! Michael Giddings UW Madison Chemistry
From: averill@bela.music.washington.edu (Ron Averill) Newsgroups: comp.sys.next.bugs Subject: Re: Need help with screen problem Date: 7 Oct 1993 17:32:47 GMT Organization: University of Washington Message-ID: <291jrv$4ol@news.u.washington.edu> References: <28v7mu$f7v@news.u.washington.edu> In article <28v7mu$f7v@news.u.washington.edu> root@anton.music.washington.edu (Operator) writes: > The screen on our network server began going dark at random time intervals > of about a minute two days ago. Now it goes dark every few seconds, and > the problem seems to be spreading to other machines on the network. > > Can anyone offer some advice? > > Ron Averill > School of Music Computer Center, > University of Washington > raverill@u.washington.edu We found a problem in LogoutHook which runs a program called VidLev which causes the screen to go dark after logging out. For some reason, this program was running over and over even when the machine was in use. Ron Averill
From: ren@nin.asd.sgi.com (Ron Nikel) Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs Subject: Next CD-ROM under NS 3.0 Date: 7 Oct 1993 22:25:15 GMT Organization: Silicon Graphics, Inc. Distribution: world Message-ID: <29250b$bil@fido.asd.sgi.com> Hi, I just got a NeXT CD-ROM drive and have it running on a Station under NS 3.0. Question is I tested it running as root to play an audio CD. Does not work, I have identified it as everything from device #2 - #6. No change in its operation. I boot from an external SCSI drive which is now sd0 and my internal is sd1. What do I have to do to get this up and running, I know this was already discussed some time ago, but can't seem to find the discussion. Ron.
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Severe bug in fsck Date: 5 Oct 1993 09:15:58 +0100 Organization: Palumbian Research Labs Message-ID: <28rafu$1b1@marsu.tynet.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi NeXTfolks! I'd like to give a brief summary of my horrible experience of yesterday: (Happend on a NeXTSTEP/Intel machine, but I'm not sure whether it could happen on black hardware, too.) The Create3 demo was all fun. After a few minutes it claimed to be the one and only task around, no way to stop - total hang. Press reset to continue. But then... fsck -p found an "unknown error". Thus, I ran fsck manually. It found "PARTIALLY TRUNCATED INODE I=79388". Any attempts to fix this inode (enter 'y') resulted in a "bus error" of fsck. No way to get the filesystem back! I had to reformat the partition and restore the backup tape. So, keep to your backups and don't rely on fsck!!! Regards, Markus. -- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Expert in quantum bogodynamics
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs From: jwdb@dutnak2.tn.tudelft.nl (Jan-Willem de Bruijn) Subject: Re: Preferences(.app) corrupted by Cub'X ??? Message-ID: <jwdb.750100187@dutnak2> Keywords: mouse preferences Cub'X Sender: news@news.tudelft.nl (UseNet News System) Organization: Delft University of Technology References: <jwdb.749989533@dutnak2> Date: Fri, 8 Oct 1993 17:09:47 GMT In a previous posting I wrote about the strange behaviour of Preferences.app. >After I had installed >the Cub'X-Window software, although I must say I don't know if this is >the real cause, the mouse no longer had a menu button. >Trying to change this back again with the Preferences.app, causes the >latter program to crash. There is no way to configure the mouse with a >menu button anymore. >Also the Volume and Brightness sliders keep on moving back to their >minimum and maximum positions respectively, no matter what you do. >The Key Repeat Rate is reset to its slowest position, and although you >can click on the buttons in the Keyboard Preferences panel, this has no >effect. After noticing that BackSpace also wouldn't run anymore. I checked the console, and there it said something like NXOpenEventStatus failed: no such file. I checked the list of files in /dev (wild guess) against that of another machine and, indeed, a file /dev/evs0 seemed to be missing. This couldn't be a coincidence, so I (re-)created it with 'mknod /dev/evs0 c 40 0', give it rw--w--w- permission, and rebooted my machine (a NeXTcube, BTW). And the problem had disappeared! I was so glad about this that I immediately wrote this message. Now we'll have to see what happens if I install Cub'X again... Thanks for your attention, Jan-Willem -- Jan-Willem de Bruijn jwdb@dutnak2.tn.tudelft.nl Lab. of Seismics and Acoustics NeXT-mail: jwdb@delphi.tn.tudelft.nl Dep. of Applied Physics Discipline is never an end in itself, Delft University of Technology only a means to an end.
From: ivo@next.agsm.ucla.edu (Ivo Welch) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Severe bug in fsck Followup-To: comp.sys.next.sysadmin,comp.sys.next.bugs Date: 8 Oct 1993 21:40:11 GMT Organization: UCLA Microcomputer Support Office Message-ID: <294mns$3qg@news.mic.ucla.edu> References: <28rafu$1b1@marsu.tynet.sub.org> I have posted exactly the same problem a few weeks ago. I have it confirmed from NeXT: ANY CRASH MAY FORCE YOU TO REFORMAT YOUR HARDDISK, IF YOU ARE UNLUCKY ENOUGH THAT THE FILE SYSTEM HAPPENS TO BE CORRUPTED IN A PARTICULAR WAY. The reason is a bug in fsck (which is likely not to be fixed in 3.2, either). Usually, you can still boot in single-user mode, and backup to another disk (the inode is simply 1 corrupted file). With NS/Intel software and/or hardware as-of-yet not rock-stable, desaster can strike you any minute. All of us! (The same may apply to NS/040.) This is one reason why I suggested your pleading with NeXT for more stability. /ivo welch Markus Wenzel (mow@marsu.tynet.sub.org) wrote: : Hi NeXTfolks! : I'd like to give a brief summary of my horrible experience of yesterday: : (Happend on a NeXTSTEP/Intel machine, but I'm not sure whether it could : happen on black hardware, too.) : The Create3 demo was all fun. After a few minutes it claimed to be the : one and only task around, no way to stop - total hang. Press reset to : continue. But then... : fsck -p found an "unknown error". Thus, I ran fsck manually. It found : "PARTIALLY TRUNCATED INODE I=79388". Any attempts to fix this inode : (enter 'y') resulted in a "bus error" of fsck. : No way to get the filesystem back! I had to reformat the partition : and restore the backup tape. : So, keep to your backups and don't rely on fsck!!! : Regards, : Markus. : -- : Markus Wenzel System administration, Consulting, Networking : mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT : IRC: Marsu Expert in quantum bogodynamics -- Ivo Welch ivo@128.97.74.50 = next.agsm.ucla.edu Asst Prof of Finance iwelch@agsm.ucla.edu AGSM at UCLA
From: ssircar@canon.com (Subrata Sircar) Newsgroups: comp.sys.next.bugs Subject: Project Builder Install Field Bug #50523 Date: 8 Oct 1993 17:57:47 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9310082257.AA10419@alychne-nc.canon.com> Under 3.0, 3.1E (Motorola) and 3.1J (Intel) Project Builder has a serious bug. 1. Create a new project and go to the Attributes view. 2. Change the install directory (to an absolute pathname, say). 3. Save the file and close the window. 4. Open the file and go the Attributes window - the old install path is still there! The only obvious option was to edit the Makefile and PB.project by hand. --- Subrata Sircar|ssircar@canon.com (NextMail ok)|Prophet & SPAMIT Charter Member Canon Information Systems and I do not share the same views on everything. "I'm just mad that I missed the sexual revolution." - me "Yes, but you dress much better as a result." - Mike
From: infospan@infospan.com. (Max Tardiveau) Newsgroups: comp.sys.next.bugs Subject: Re: NS3.1 telnetd Date: 9 Oct 1993 00:03:31 GMT Organization: Minnesota Regional Network Distribution: world Message-ID: <294v4j$dqu@cedar.mr.net> References: <293373$ako@vixen.cso.uiuc.edu> Keywords: telnetd, stty In article <293373$ako@vixen.cso.uiuc.edu> lemson@ux1.cso.uiuc.edu (David Lemson) writes: > eoliver@ralph.cs.haverford.edu (Erik Oliver) writes: > > >Same here, we use NCSA telnet on our Appletalk and Ethertalk macs to > >copnnect to our NextStation Color running 3.0 and previously 2.X without > >any trouble. Additionally, we use telnet from any number of other uix > >platforms, Vax, and also occasionally PC' s > >running DOS without problems... > > >So, I would really love to know what the problem is!!! I assume you know about : stty -extproc Since I put this in my .cshrc, things have worked just fine for me. ------------------------------------------------------------------- Infospan Corp. (612) 939-0088 Fax (612) 939-0380 5700 Smetana Drive - Minneapolis, MN 55343-9686 This is a shared account. Reply to infospan@infospan.com and specify the intended recipient of the message (i.e. Attn : Jane Doe).
From: runderwo@banach.Mines.Colorado.EDU (Robert Underwood) Newsgroups: comp.sys.next.bugs Subject: Next Step bugs Message-ID: <1993Oct8.222400.13510@slate.mines.colorado.edu> Date: 8 Oct 93 22:24:00 GMT Sender: news@slate.mines.colorado.edu Organization: Colorado School of Mines Fri 10-9-93 I have had the following problem and would like to get some feed back from the "NeXT" community. (1) A colleague of mine brought a disk to copy material from my 486 NEXT STEP machine. He has a "NeXT" identical to mine. He had been having trouble with his machine crashing when he used his floppy drive. (2) While transferring material on and off my machine, the computer said it was still copying material but in fact it was through. The message was posted on the right hand side of the shelf in the usual location. (3) He had placed a directory called "test1" on the shelf. (4) When I got on the machine I could not remove "test1" from the shelf. (5) Furthermore, anytime I tried to compile using cc the computer froze requiring a power on off reboot. (6) I then renamed the directory "test1". With its new name in place I was able compile some of the time. (7) I then checked in /bin to see if cc had been changed. It had at char 53 on line. I copied in a copy of cc from the Next Developer CD. Things improved but the system still froze on occasional compiles. (8) I discovered that the the files from the "developer" CD in bin had all been changed at char 53 line 1. Almost all, since cc++ was OK. (9) We checked all DOS related disks for viruses but found none. Any ideas or suggestions? I can be contacted at runderwo@banach.Mines.Colorado.EDU Thanks Robert Underwood runderwo@banach.Mines.Colorado.EDU
From: isbell@cats.ucsc.edu (Art Isbell) Newsgroups: comp.sys.next.bugs Subject: Re: Project Builder Install Field Bug #50523 Date: 9 Oct 1993 17:30:40 GMT Organization: Cubic Solutions - NeXT software development and consulting Message-ID: <296sg0$s28@darkstar.UCSC.EDU> References: <9310082257.AA10419@alychne-nc.canon.com> In article <9310082257.AA10419@alychne-nc.canon.com> ssircar@canon.com writes: > Under 3.0, 3.1E (Motorola) and 3.1J (Intel) Project Builder has a >serious bug. > > 1. Create a new project and go to the Attributes view. > 2. Change the install directory (to an absolute pathname, say). > 3. Save the file and close the window. > 4. Open the file and go the Attributes window - the old install > path is still there! > > The only obvious option was to edit the Makefile and PB.project by >hand. Huh? I do this all the time under 3.0 and 3.1E with no problems. Do you save your project after making this change or do you have the PB "Save When Modified" preference checked? Maybe I don't understand because I've been unable to reproduce this behavior either with new or existing projects. -- Art Isbell Cubic Solutions NeXT Registered Developer NEXTSTEP software development and consulting NeXTmail: art@cubicsol.com Voice: +1 408 335 1154 USmail: 95018-9442 Fax: +1 408 335 2515
Newsgroups: comp.sys.next.bugs From: verket@venice.sedd.trw.com (Paul Verket) Subject: Re: Q: "ls -lR" bug with CD-ROMS? Message-ID: <1993Oct10.003638.16855@venice.sedd.trw.com> Organization: TRW Systems Engineering & Development Division, Carson, CA References: <1993Oct4.021344.2353@cs.wisc.edu> <1993Oct5.120751.1185@gamelan> Date: Sun, 10 Oct 1993 00:36:38 GMT Thomas Funke (thf@zelator.in-berlin.de) wrote: : In article <1993Oct4.021344.2353@cs.wisc.edu> bestor@caracal.cs.wisc.edu : (Gareth Bestor) writes: : > I'm trying to get an ls -lR listing of some of my CD-ROMs and keep : > getting a weird "XXX not found" error on a few of them. For example: : > : Yes, this is a feature of the 3.1 'downgrade': : You have to get the CDROM.fs from a 3.0 system.: : ... Beware that the 3.1 CD-ROM filesystem has additional capabilities that the 3.0 version lacks. I have an ISO9660/RockRidge disk that 3.0 can't read but 3.1 can (though with intermittant problems). Paul Verket (NeXTmail ok)
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: Missing examples in 3.1 & 3.0 Developer??? Message-ID: <1993Oct8.135836.8629@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Fri, 8 Oct 1993 13:58:36 GMT Can anyone confirm that ALL CD-ROMS for 3.0 and 3.1 had no source included in the: > ls /NextLibrary/Documentation/NextDev/Examples/IBTutorial/Images/ ProgressPalette.tiff willy.tiff and only the sounds in: > ls /NextLibrary/Documentation/NextDev/Examples/IBTutorial/Sounds/ drum1.snd drum2.snd drum3.snd Have I missed the accompanying source examples somewhere inline in the text?
Newsgroups: comp.sys.next.bugs From: davis@sonata.cc.purdue.edu (Robert Davis) Subject: Re: Missing examples in 3.1 & 3.0 Developer??? Message-ID: <CEo803.CDq@mentor.cc.purdue.edu> Sender: news@mentor.cc.purdue.edu (USENET News) Organization: Purdue University, West Lafayette, IN References: <1993Oct8.135836.8629@totsyssoft.com> Date: Sun, 10 Oct 1993 07:40:51 GMT In article <1993Oct8.135836.8629@totsyssoft.com>, Bruce Gingery <bruce@TotSysSoft.com> wrote: > >Can anyone confirm that ALL CD-ROMS for 3.0 and 3.1 had no >source included in the: > >> ls >/NextLibrary/Documentation/NextDev/Examples/IBTutorial/Images/ >ProgressPalette.tiff willy.tiff > See /NextLibrary/Documentation/NextDev/DevTools/18_CustomPalette. >and only the sounds in: >> ls >/NextLibrary/Documentation/NextDev/Examples/IBTutorial/Sounds/ >drum1.snd drum2.snd drum3.snd > See /NextLibrary/Documentation/NextDev/DevTools/16_CalculatorApp. Rob -- | Robert Davis davis@sonata.cc.purdue.edu | "Look up, Hannah." NeXT Mail accepted --
From: jgshir@athena.mit.edu (John G Shirlaw) Newsgroups: comp.sys.next.bugs Subject: DOS Floppy problem on Black Hardware. Date: 12 Oct 1993 02:07:22 GMT Organization: Massachusetts Institute of Technology Distribution: world Message-ID: <29d3gq$437@senator-bedfellow.MIT.EDU> Dear All, Could some please test this posible bug out for me..I'm not sure if it is just my set up, a unix funny or a NeXT bug. My System is a NeXT Turbo Color running NS 3.1 for reference. Do the following: 1) Open up Edit and open a new document. 2) Type a few lines...garbage will do 3) Save file as "Q.txt" 4) Insert DOS formated floppy ( mine was unlabeled) 5) Go into File Browser and attempt to drag copy "Q.txt" to floppy. The console pops up and say can't do it...reason I can remember and gives you the choice of stopping or proceeding both of which don't copy the file. 6) Close the console window 7) Change the name of the file to "q.txt" 8) Now attempt to copy the file to the floppy. result copies perfectly. anyone get the Next to do this as well? john
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 12 Oct 1993 00:34:31 -0400 Organization: Next Announcements Message-ID: <29dc4k$1qd@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs From: schaik@cnplss5.cnps.philips.nl (Willem van Schaik) Subject: Re: DOS Floppy problem on Black Hardware. Message-ID: <1993Oct12.121149.20257@cnplss5.cnps.philips.nl> Sender: news@cnplss5.cnps.philips.nl (USENET News System) Organization: Philips Communications & Processing Services, Eindhoven References: <29d3gq$437@senator-bedfellow.MIT.EDU> Date: Tue, 12 Oct 1993 12:11:49 GMT jgshir@athena.mit.edu (John G Shirlaw) writes: >3) Save file as "Q.txt" >4) Insert DOS formated floppy ( mine was unlabeled) >5) Go into File Browser and attempt to drag copy "Q.txt" to floppy. >The console pops up and say can't do it...reason I can remember and gives you the >choice of stopping or proceeding both of which don't copy the file. >john You missed some discussions about this a while ago: to copy files from harddisk to DOS floppy, the names HAVE TO BE 8.3 format and all lowercase. THis is ofcourse not a very intelligent choice of NeXT, but we'll have to live with it. Willem
From: Roland Telfeyan <roland@gomidas.mi.org> Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 12 Oct 1993 18:03:18 GMT Organization: University of Michigan EECS Dept. Distribution: world Message-ID: <29erh6$7cn@zip.eecs.umich.edu> References: <294mns$3qg@news.mic.ucla.edu> Maybe this is naieve, but older versions of buildafmdir, disk, and other programs have been reputed to work better than the 3.0 versions. Could the 2.0 version of fsck have helped Markus or Ivo? Any sysadmins out there know the reason for this bug? Roland
From: wardm@well.sf.ca.us(Ward Mullins) Newsgroups: comp.sys.next.bugs Subject: Floppy Drive Failure Date: 12 Oct 1993 18:55:14 GMT Organization: THOUGHT Inc. Distribution: world Message-ID: <29euii$3ut@male.EBay.Sun.COM> Keywords: floppy HINT EISA VESA VLB driver I have a 100% failure rate mounting floppies on a HINT 486 EISA/VESA motherboard! My configuration is an adaptec 1542B with 1 hard disk and 1 cdrom drive. I have the tried the on board flopply controller (which of course fails), and two other floppy controllers with no success... I get the infamous RDP exception error everytime I attempt to mount a floppy... I am very fond of NSFIP, but this is becoming a very irritating situation! I've called support, written email to several people at NeXT, and have yet to get a resolution, or an *attempt* at resolution on the part of NeXT... Ward Mullins President Thought Inc.
From: djep@fountainhills.az.stratus.com (Dave_Jepson) Newsgroups: comp.sys.next.bugs Subject: Re: Floppy Drive Failure Date: 12 Oct 1993 20:50:35 GMT Organization: Stratus Computer Inc, Marlboro MA Distribution: world Message-ID: <29f5ar$eol@transfer.stratus.com> References: <29euii$3ut@male.EBay.Sun.COM> In comp.sys.next.bugs article <29euii$3ut@male.EBay.Sun.COM> you wrote: > I have a 100% failure rate mounting floppies on a HINT 486 EISA/VESA motherboard! > My configuration is an adaptec 1542B with 1 hard disk and 1 cdrom drive. I have > the tried the on board flopply controller (which of course fails), and two other > floppy controllers with no success... I get the infamous RDP exception error > everytime I attempt to mount a floppy... I am very fond of NSFIP, but this is > becoming a very irritating situation! [stuff deleted] This looks like another case of motherboard bashing again. The Next Docs specifically state that the on board floppy controller is NOT supported on the Adaptec boards. Unfortunately it does not state which "stand alone" floppy controller IS supported (brand). As a work-around, we installed small (~20mb) dos partitions on all of our NS/FIP systems. We boot dos & copy the files we need to the dos partition, reboot Nextstep and drag the files to the Nextstep partition. A bit time consuming, but it's the best there is at this point. This is only used while setting up new systems. Once the system is up, we use the network to move files. -David Jepson- Stratus Computer Inc. #Include std.disclaimer
Newsgroups: comp.sys.next.bugs From: ciu@ubszh.net.ch Subject: Problems with fat precompiled headers Content-Type: text/plain Message-ID: <ciu.93Oct13152158@nol510> Keywords: Precompiled Headers, Fat Binaries Sender: usenet@ubszh.net.ch (news) Organization: Union Bank of Switzerland Mime-Version: 1.0 Date: Wed, 13 Oct 1993 14:21:58 GMT I wonder, if anybody else had the same or similar problems, or if I'm just doing something wrong... We are using NeXTstep Rel 3.1 on both our Intel-CPUs and NeXT-CPUs. To precompile I say: $cc -precomp -arch m68k -arch i386 -Wprecomp ourHeaders.h -o ourHeaders.p Precompiling works fine. Compiling a project on an Intel-CPU works fine if I precompiled on an Intel-CPU. Compiling a project on a NeXT-CPU works fine if I precompiled on a NeXT-CPU. (Note, that compiling for m68k, or i386, or m68k_i386 just works...) BUT: precompiling on either Intel-CPUs or NeXT-CPUs and then compiling a project on the other CPUs DOES NOT WORK. It produces errors such as: For architecture m68k: Demo.m: In method `foo:' Demo.m:10: `NO' undeclared (first use this function) Demo.m:10: (Each undeclared identifier is reported only once Demo.m:10: for each function it appears in.) *** Exit 1 Stop. This is really a precompiler-problem, since after removing 'ourHeaders.p' these problems don't appear anymore. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NeXT-mail: ciu@ubszh.net.ch | home: Zurich, Switzerland non-NeXT: 100016.662@compuserve.com | 08 34'01" E 47 17'26" N phone: +41 1 722 17 10 | 685 200 / 238 300 470 m - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
From: otto@tukki.jyu.fi (Otto J. Makela) Newsgroups: comp.sys.next.bugs,comp.lang.postscript Subject: Printing TIFFs on the NeXT printer, again Followup-To: comp.sys.next.bugs Date: 13 Oct 1993 18:48:48 +0200 Organization: The Crimson Permanent Assurance Company Sender: otto@network.cc.jyu.fi Distribution: comp Message-ID: <OTTO.93Oct13184845@tukki.jyu.fi> In article <27u4ds$g2h@news.cs.tu-berlin.de> marcel@cs.tu-berlin.de (Marcel Weiher) wrote about patching the TIFF printing problem in NS3.1: > This bug is actually described in the release notes, which > also describe a workaround: > "...put an invisible rotation on the image..." > > This is fine if you have a document to work with, but no > help for finished layouts. So here's a workaround: > > In the directory "/usr/lib/NextPrinter/Drivers/NXNLPDriver" > create the file "image_bugfix.ps" with the following contents: > /image { gsave .1 rotate image grestore } bind def > Then, using NetInfoManager, add the property "InitFiles" > with the value "/usr/lib/NextPrinter/Drivers/NXNLPDriver/image_bugfix.ps" > to the "Admin" subdirectory of any NeXT Laserprinter entry. (agnus@amylnd.stgt.sub.org (Matthias Zepf) noted that .1 isn't even close to invisible, but should be something like .001!) john@klein.Mines.Colorado.EDU (John Stockwell) said it didn't work for him. Well, neither did it for me. Oh yes, it is doing it (I checked by setting the rotation to .1 which really was visible) but it did not affect the right-edge cropping the TIFF image. To exaggerate a bit, this is what happens: the ###'s are a TIFF image which was placed in a draw document with some text. The image moves a bit to the right and gets slightly cropped. It sounds exactly like the problem described in the bug description, but the patch doesn't help. Screen Printout +-----------+ +-----------+ | TEXT TEXT | | TEXT TEXT | | ##### | | ####| | | ##### | | ####| | | ##### | | ####| | | More Text | | More Text | +-----------+ +-----------+ Anyone have more ideas? -- /* * * Otto J. Makela <otto@jyu.fi> * * * * * * * * * * * * * * * * * * */ /* Phone: +358 41 613 847, BBS: +358 41 211 562 (V.32bis/USR-HST,24h/d) */ /* Mail: Kauppak. 1B18/FIN-40100 Jyvaskyla/Finland, ICBM: 62.14N 25.44E */ /* * * Computers Rule 01001111 01001011 * * * * * * * * * * * * * * * * */
Newsgroups: comp.lang.c,comp.sys.next.bugs,comp.sys.dec From: bill@sfu.ca (Bill Baines) Subject: clib atof() question Message-ID: <1993Oct14.043648.1611@sfu.ca> Keywords: atof Sender: news@sfu.ca Organization: Simon Fraser University, Burnaby, B.C., Canada Date: Thu, 14 Oct 1993 04:36:48 GMT I was porting a program called SatTrack from Sun to neXT and VAX/VMS in preparation for tracking the shuttle STS-58 due to launch on Thursday. The program was written by Manfred Bester, (DL5KR) is excellent, and works well on the Sun platforms I have run it on. On the NeXT, I ran into som problems. The satellite orbital data is read from ascii files which are parsed up calculated upon by SatTrack. One function makes extensive use of atof(). Return values from that function are wild -- beyond anything that could be called round-off error. I am not a great c programmer, so I wrote a little test program to validate my understanding ot atof(). The outputs on various systems is below the source. -------------------- #include <math.h> int main() { double f1; char *s1 = "1234.567"; f1 = atof(s1); printf("%s, %f\n",s1, f1); } -------------------- 1) On SunOS 4.? 1234.567, 1234.567000 [OK!] 2) On NeXTOS 3.0 1234.567, 1083394628.000000 [Not ok] 3) Silicon Graphics IRIX 4.? 1234.567, 1234.567000 [OK!] 4) VAX/VMS (D_FLOAT) 1234.567, 1378108826.000000 [Not ok] (G_FLOAT) 1234.567, 1245986995.000000 [Not ok] So, Sun and SGI seem to work while Next and VMS don't. Have I left something out here? Compiler switches? Ideas appreciated. -- Bill Baines, Operations and Tech. Support, Simon Fraser University, Vancouver, British Columbia, Canada bill@sfu.ca, (604) 291-3955, (fax 291-4242), VE7FML
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: clib atof() question Message-ID: <1993Oct14.050943.1426@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: Stanford University References: <1993Oct14.043648.1611@sfu.ca> Date: Thu, 14 Oct 93 05:09:43 GMT Bill Baines writes > I was porting a program called SatTrack from Sun to neXT and > VAX/VMS in preparation for tracking the shuttle STS-58 due to > launch on Thursday. If you get this to work, I'd be grateful if you could put the binary on the archives. -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@leland.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
From: cowan@btgmax.zko.dec.com (Ken Cowan) Newsgroups: comp.lang.c,comp.sys.next.bugs,comp.sys.dec Subject: Re: clib atof() question Date: 14 Oct 1993 13:18:26 GMT Organization: Digital Equipment Corporation Distribution: world Message-ID: <29jjj2$bfu@jac.nuo.dec.com> References: <1993Oct14.043648.1611@sfu.ca> Keywords: atof In article <1993Oct14.043648.1611@sfu.ca>, bill@sfu.ca (Bill Baines) writes: |>Newsgroups: comp.lang.c,comp.sys.next.bugs,comp.sys.dec |>Path: jac.nuo.dec.com!crl.dec.com!crl.dec.com!caen!usenet.cis.ufl.edu!usenet.ufl.edu!darwin.sura.net!howland.reston.ans.net!sol.ctr.columbia.edu!destroyer!nntp.cs.ubc.ca!newsserver.sfu.ca!news |>From: bill@sfu.ca (Bill Baines) |>Subject: clib atof() question |>Message-ID: <1993Oct14.043648.1611@sfu.ca> |>Keywords: atof |>Sender: news@sfu.ca |>Reply-To: bill@sfu.ca |>Organization: Simon Fraser University, Burnaby, B.C., Canada |>Date: Thu, 14 Oct 93 00:36:48 GMT+5:00 |>Lines: 50 |>Xref: jac.nuo.dec.com comp.lang.c:22504 comp.sys.next.bugs:896 comp.sys.dec:7062 |> |>I was porting a program called SatTrack from Sun to neXT and VAX/VMS in |>preparation for tracking the shuttle STS-58 due to launch on Thursday. |> |>The program was written by Manfred Bester, (DL5KR) is excellent, and works |>well on the Sun platforms I have run it on. |> |>On the NeXT, I ran into som problems. The satellite orbital data is |>read from ascii files which are parsed up calculated upon by SatTrack. One |>function makes extensive use of atof(). Return values from that function |>are wild -- beyond anything that could be called round-off error. |> |>I am not a great c programmer, so I wrote a little test program to validate my |>understanding ot atof(). The outputs on various systems is below the source. |> |>-------------------- |>#include <math.h> |>int main() |>{ |> double f1; |> char *s1 = "1234.567"; |> |> f1 = atof(s1); |> printf("%s, %f\n",s1, f1); |>} |>-------------------- |> |>1) On SunOS 4.? |> 1234.567, 1234.567000 [OK!] |> |>2) On NeXTOS 3.0 |> 1234.567, 1083394628.000000 [Not ok] |> |>3) Silicon Graphics IRIX 4.? |> 1234.567, 1234.567000 [OK!] |> |>4) VAX/VMS |> (D_FLOAT) |> 1234.567, 1378108826.000000 [Not ok] |> |> (G_FLOAT) |> 1234.567, 1245986995.000000 [Not ok] |> |>So, Sun and SGI seem to work while Next and VMS don't. Have I left something |>out here? Compiler switches? |> |>Ideas appreciated. |>-- |>Bill Baines, Operations and Tech. Support, |>Simon Fraser University, Vancouver, British Columbia, Canada |>bill@sfu.ca, (604) 291-3955, (fax 291-4242), VE7FML |> atof() is declared in stdlib.h, not math.h. Without a declaration the routine is implicitly declared as returning an int. Just change math.h to stdlib.h and it'll work on VAX. The ANSI C standard requires the definition be in stdlib.h, so the change should still work back on the SG and Sun machines. -- Ken Cowan, ZK2-3/Q8 cowan@rtl.enet.dec.com Digital Equipment Corporation decwrl!rtl!cowan 110 Spit Brook Rd, Nashua, NH 03062
From: steve@estel.uindy.edu (Steve Spicklemire) Newsgroups: comp.sys.next.bugs Subject: Re: clib atof() question Date: 14 Oct 1993 13:25:22 GMT Organization: Truevision Inc., Indianapolis, IN Distribution: world Message-ID: <29jk02INNi19@epic.truevision.com> References: <1993Oct14.043648.1611@sfu.ca> In article <1993Oct14.043648.1611@sfu.ca> bill@sfu.ca (Bill Baines) writes: From the man page: NAME atof, atoi, atol - convert strings to numbers SYNOPSIS #include <stdlib.h> double atof(const char *nptr); int atoi(const char *nptr); long atol(const char *nptr); put in the #include <stdlib.h>, and <stdio.h> and : #include <stdlib.h> #include <stdio.h> int main() { double f1; char *s1 = "1234.567"; f1 = atof(s1); printf("%s, %f\n",s1, f1); return 0; } estel> cc -Wall -o try try.c estel> try 1234.567, 1234.567000 -- --------------------------< cut here >---------------------------- Steve Spicklemire (317) 788-3313 steve@estel.uindy.edu Dept of Physics and Earth-Space Science NeXTmail Welcome! University of Indianapolis 1400 East Hanna Avenue, Indpls. IN, 46227
From: fxg@piccomin.informatik.rwth-aachen.de (Felix Gatzemeier) Newsgroups: comp.sys.next.bugs Subject: Re: Why entry still in services menu ?? Date: 14 Oct 93 14:00:21 GMT Organization: Rechnerbetrieb Informatik - RWTH Aachen Message-ID: <fxg.750607221@piccomin> References: <28r47f$dq2@turin.research.otc.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit michaell@swdev.research.otc.com.au (Michael) writes: >I down loaded sometime ago a copy of DataBag ! I tried >it out and then removed from my machine. ^^^^^^ Where? It is possible that DataBag (which I haven't seen yet) placed some files in ~/Library/Services or /LocalLibrary/Services. You'd have to remove them, too. >Still my applications ( Workspace manager, edit etc ) >have a Services menu entry for the removed DataBag application !! >Why is it still there. I thought that the Workspace >manager investigates when it starts up what applications >are availabe ? Well... Read the Developer's Documentation for Services. Actually, the Services System checks /LocalApps, ~/Apps, /LocalLibrary/Services, ~/Library/Services for Services EACH TIME A SERVICES MENU is brought up! >How can I get rid of it ?? >Running NS 3.1 on motorola ! >Michael -- Felix (fxg@Pool.Informatik.RWTH-Aachen.de, No NeXT-Mail, please!)
From: doherty@bhnrc.usda.gov (Bob Doherty) Newsgroups: comp.lang.c,comp.sys.dec,comp.sys.next.bugs Subject: Re: clib atof() question Message-ID: <1993Oct14.090651.80@bhnrc.usda.gov> Date: 14 Oct 93 09:06:51 EDT References: <1993Oct14.043648.1611@sfu.ca> Organization: Beltsville Human Nutrition Research Center -- USDA In article <1993Oct14.043648.1611@sfu.ca>, bill@sfu.ca (Bill Baines) writes: [snip, snip] > -------------------- > #include <math.h> > int main() > { > double f1; > char *s1 = "1234.567"; > > f1 = atof(s1); > printf("%s, %f\n",s1, f1); > } > -------------------- [snip, snip] > So, Sun and SGI seem to work while Next and VMS don't. Have I left something > out here? Compiler switches? > The problem is that the atof prototype is specified by the ANSI standard to be in stdlib.h, not math.h. Even though VAX/VMS C is not an ANSI C compiler, the atof prototype is in stdlib.h. The same situation obtains for Next, apparently. It appears as if SunOS and IRIX get it wrong. With the change in the included file to stdlib.h, under VAX/VMS C and gcc under VMS, the above program produces the same output as SunOS and IRIX. -- ********************************************************************* * Bob Doherty * Beltsville Human Nutrition Research Center * * B161 R216A * EMAIL: doherty@bhnrc.usda.gov * * BARC-East * doherty@Eisner.DECUS.Org * * Beltsville, MD 20705 * bob.doherty@his.com * * (301)-504-8147 * * *********************************************************************
Newsgroups: comp.sys.next.bugs From: brian@il.us.swissbank.com (Brian Welsh) Subject: Re: clib atof() question Message-ID: <1993Oct14.143416.19693@il.us.swissbank.com> Sender: root@il.us.swissbank.com (Operator) Organization: Swiss Bank Corporation CM&T Division References: <1993Oct14.043648.1611@sfu.ca> Date: Thu, 14 Oct 1993 14:34:16 GMT Bill Baines writes > I was porting a program called SatTrack from Sun to neXT and VAX/VMS in > preparation for tracking the shuttle STS-58 due to launch on Thursday. > > The program was written by Manfred Bester, (DL5KR) is excellent, and works > well on the Sun platforms I have run it on. > > On the NeXT, I ran into som problems. The satellite orbital data is > read from ascii files which are parsed up calculated upon by SatTrack. One > function makes extensive use of atof(). Return values from that function > are wild -- beyond anything that could be called round-off error. > > I am not a great c programmer, so I wrote a little test program to validate my > understanding ot atof(). The outputs on various systems is below the source. > > -------------------- > #include <math.h> > int main() > { > double f1; > char *s1 = "1234.567"; > > f1 = atof(s1); > printf("%s, %f\n",s1, f1); > } > -------------------- > > 1) On SunOS 4.? > 1234.567, 1234.567000 [OK!] > > 2) On NeXTOS 3.0 > 1234.567, 1083394628.000000 [Not ok] > > 3) Silicon Graphics IRIX 4.? > 1234.567, 1234.567000 [OK!] > > 4) VAX/VMS > (D_FLOAT) > 1234.567, 1378108826.000000 [Not ok] > > (G_FLOAT) > 1234.567, 1245986995.000000 [Not ok] > > So, Sun and SGI seem to work while Next and VMS don't. Have I left something > out here? Compiler switches? > > Ideas appreciated. > -- > Bill Baines, Operations and Tech. Support, > Simon Fraser University, Vancouver, British Columbia, Canada > bill@sfu.ca, (604) 291-3955, (fax 291-4242), VE7FML Try including <stdlib.h> in your program. <math.h> on the NeXT (3.0) doesn't seem to include the prototype for atof(3), but there is a comment saying that <stdlib.h> does. I tested your program and that seemed to work. What I don't know is why the compiler doesn't complain about atof(3) being undefined since, as far as I can tell, the compiler defaulted atof(3) to returning an integer result in your original program. Brian Welsh Swiss Bank Corporation email: brian@il.us.swissbank.com 141 West Jackson Blvd. phone: 312-554-5366 Chicago, Il 60604 USA Any opinions expressed are my own, and not necessarily those of SBC.
From: zryx0376@awsin1.rus.uni-stuttgart.de (Markus Wenzel (Hiwi bei R.Rabenseifner)) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 14 Oct 1993 17:09:04 GMT Organization: Visualization Group Comp.Center (RUS) U of Stuttgart, FRG Distribution: world Message-ID: <29k13g$ikn@info2.rus.uni-stuttgart.de> References: <294mns$3qg@news.mic.ucla.edu> <29erh6$7cn@zip.eecs.umich.edu> In article <29erh6$7cn@zip.eecs.umich.edu> Roland Telfeyan <roland@gomidas.mi.org> writes: >Maybe this is naieve, but older versions of buildafmdir, disk, and other >programs have been reputed to work better than the 3.0 versions. Could the >2.0 version of fsck have helped Markus or Ivo? I'm almost sure that a fsck taken from NS 2.0 would not run on Intel :-)) And if I could lay my hands on the source, I'd rather look for the bug! Regards, Markus.
Newsgroups: comp.sys.next.bugs From: mms@world.std.com (Malcolm M Sanders) Subject: open -a bug on Black NS3.1? Message-ID: <MMS.93Oct14141118@world.std.com> Sender: mms@world.std.com (Malcolm M Sanders) Organization: The World Public Access UNIX, Brookline, MA Date: Thu, 14 Oct 1993 19:11:18 GMT I have a problem with open on my NeXT Cube running NS 3.1. I issue the command: open -a Terminal /usr/local/bin/term I expect that I will get a new Terminal.app window with the program, term, running in it. Instead, I get: open: can't open connection to Terminal on local host. I find that this problem is epidemic on my machine, e.g. open -a AnyApp ... results in open: can't open connection to AnyApp on local host. Is it just me, or what? Thanks, Malcolm Sanders mms@jax.org
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: jnicolas@image.mit.edu (Julien Nicolas) Subject: Is /usr/etc/rshd broken??? Message-ID: <JNICOLAS.93Oct14165920@image.mit.edu> Sender: news@news.media.mit.edu (USENET News System) Organization: Massachusetts Institute of Technology, Cambridge, USA Distribution: usa Date: Thu, 14 Oct 1993 20:59:19 GMT The following does NOT work: pluto% rsh pluto ls where pluto is the name of the NeXT computer runnning NS 3.1. There are no error messages, rsh returns with error status 0, yet no output is generated. Yes, the hostname is in /etc/host.equiv etc. I replaced /usr/etc/rshd with a publicly available version and everything works as it should. What gives? Julien Nicolas jnicolas@image.mit.edu
Newsgroups: comp.sys.next.bugs,comp.lang.c,comp.sys.dec From: bill@sfu.ca (Bill Baines) Subject: Re: clib atof() question resolved... Thanks!!! Message-ID: <1993Oct15.003244.1849@sfu.ca> Sender: news@sfu.ca Organization: Simon Fraser University, Burnaby, B.C., Canada References: <1993Oct14.043648.1611@sfu.ca> Date: Fri, 15 Oct 1993 00:32:44 GMT In article <1993Oct14.043648.1611@sfu.ca> I posted the following code: > -------------------- > #include <math.h> > int main() > { > double f1; > char *s1 = "1234.567"; > > f1 = atof(s1); > printf("%s, %f\n",s1, f1); > } > -------------------- Today I rec'd several replys -- most suggesting that I #include <stdlib.h> which I did -- both in the above example, and in the original code I am porting. PROBLEM SOLVED! Thanks again for your kind suggestions. Several also mentioned that I should have checked the man page for atof() which would have advised me that atof() was prototyped in stdlib.h. Interesting, that NeXT 2.1, NeXT 3.0 and Sun 4.? don't mention stdlib.h in their atof man page. Same goes for the NeXT Digital Librarian I have. (My own system has been diddled up and down a few times, so I may not have the latest man pages loaded -- perhaps I should reload the man pages from the CD-Rom). VAX/VMS help and SGI Irix do make mention of stdlib.h in their references to atof(). Anyways, lesson learned... Thanks again for your kind responses... -- Bill Baines, Operations and Tech. Support, Simon Fraser University, Vancouver, British Columbia, Canada bill@sfu.ca, (604) 291-3955, (fax 291-4242), VE7FML
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: john@oceania.com (John Robison) Subject: Re: Severe bug in fsck Message-ID: <CEsxqC.Fru@oceania.com> Followup-To: comp.sys.next.sysadmin Summary: fsck bug and work-around Sender: john@oceania.com Organization: Oceania Health Care Systems References: <28rafu$1b1@marsu.tynet.sub.org> Date: Tue, 12 Oct 1993 20:47:00 GMT In article <28rafu$1b1@marsu.tynet.sub.org>, Markus Wenzel <mow@marsu.tynet.sub.org> wrote: >Hi NeXTfolks! > >I'd like to give a brief summary of my horrible experience of yesterday: >(Happend on a NeXTSTEP/Intel machine, but I'm not sure whether it could >happen on black hardware, too.) > >The Create3 demo was all fun. After a few minutes it claimed to be the >one and only task around, no way to stop - total hang. Press reset to >continue. But then... >fsck -p found an "unknown error". Thus, I ran fsck manually. It found >"PARTIALLY TRUNCATED INODE I=79388". Any attempts to fix this inode >(enter 'y') resulted in a "bus error" of fsck. > >No way to get the filesystem back! I had to reformat the partition >and restore the backup tape. > >So, keep to your backups and don't rely on fsck!!! > I am led to believe that this fsck bug will be encountered quite often, but there does exist a fairly simple work-around. I noticed that this happened after running a process that eats up all the swapfile. Basically, the swapfile grows HUGE and locks the machine. The problem is that the machin hangs, and the swapfile inode becomes "partially truncated". Notmally, fsck would just move something like that into lost+found, but the swapfil is HUGE, and the disk is full. WHat's a poor fsck to do?? :-) :-) WHat *I* did was start looking around for INODE 79388 (in the above example). I suspected the swapfile, and any other recently touched files. You *can* boot in single-user mode and do a lot of playing. You have find, ls -i, and a host of othe resources at your disposal. Fortunately, the swapfile was the problem. After I removed it, and "sync"'d the disk, upon re-boot fsck worked fine. The point is that there is a valid work-around for this bug, and unfortunately it is not well publicized. (IMHO, however, a crashing fsck is "unacceptible") FYI, John -- John Robison | john@oceania.com | This Space Available NeXTMail Accepted. | Call: 555-SIGS Opinions are my own. |
Newsgroups: comp.sys.next.bugs From: sanders-malcolm@cs.yale.edu (Malcolm Sanders) Subject: open -a bug on Black NS3.1? Message-ID: <29k43lINN764@FROG.ZOO2.CS.YALE.EDU> Sender: news@cs.yale.edu (Usenet News) Organization: /homes/ee/sanders/.organization Date: Thu, 14 Oct 1993 18:00:21 GMT I have a problem with open on my NeXT Cube running NS 3.1. I issue the command: open -a Terminal /usr/local/bin/term I expect that I will get a new Terminal.app window with the program, term, running in it. Instead, I get: open: can't open connection to Terminal on local host. I find that this problem is epidemic on my machine, e.g. open -a AnyApp ... results in open: can't open connection to AnyApp on local host. Is it just me, or what? Thanks, Malcolm Sanders mms@jax.org
Newsgroups: comp.sys.next.bugs From: sengwil@duc.auburn.edu (William F. Seng) Subject: audio-CD and photo-CD probs Message-ID: <sengwil.931014154126@lab4.duc.auburn.edu> Sender: usenet@news.duc.auburn.edu (News Account) Organization: Auburn University, Alabama Date: Thu, 14 Oct 1993 20:41:26 GMT Hello! I seem to be having a problem with my Toshiba 3401TA CD-ROM player (in a Micronet white box!) Currently running NeXTStep 3.0 on black hardware (48 Meg Ram, B/W monitor, Cube) it seems that just inserting an audio CD into the CDROM drive will simply cause it to be spit out. However, if I start up CDPlayer.app first, and it queries me for to insert a disk in the external drive, it plays just fine. Is this normal? It doesn't feel too NeXTish... Now for my real problem. I was told this drive was multisession capable, and that it would read Photo-CDs. Popping a photo CD in the drive simply causes it to be spit out without mounting. I noticed that pCD.app (the photo reader) requires the CD to be mounted, so I figure someone out there has gotten it to work. I tried mounting the photo CD via the /usr/etc/mount /dev/sd3a /CD command, but kept getting an error: qb2:2# mount /dev/sd3h /CD mount: /dev/sd3h on /CD: Invalid argument mount: giving up on: /CD Pretty obnoxious. The /usr/etc/disk program was a little more helpful. It at least allowed me to read a block of the photo CD disk, making me believe in the Toshiba's abilities again: qb2:17# disk /dev/rsd3a disk> read starting block? 1 # sectors per transfer? 1 number of transfers? 1 sector increment? 1 2048 bytes in 1377 ms = 1494 bytes/s disk> quit The CDROM.util in /usr/filesystems was not of much use in this debacle: qb2:20# ./CDROM.util -m sd3a /CD mount: /dev/rsd3a on /CD: I/O error mount: giving up on: /CD qb2:21# ./CDROM.util -p sd3a qb2:22# ./CDROM.util -M sd3a /CD Not much feedback from qb2 (oh, that's my computer's name. Cute, huh?) (the first cube's name is qb - pronounced "cubie" - my little sister came up with these names for our cubes) Well, Am I doing something really foolish?? I've generally been able to fix my CDROM problems (finally got it to work with SoftPC, and Insignia was sooooooooooo helpful * NOT!* ) but this one has me befuddled. If only I could mount the photoCD (wistful look into the distance) Thanks in advance for any help. If you've been over this problem a million times, and this is just another dumb newbie question, go ahead and flame me. I just want an answer. Thanks again. -Bill
Newsgroups: comp.sys.next.bugs From: sengwil@duc.auburn.edu (William F. Seng) Subject: Re: audio-CD and photo-CD probs Message-ID: <sengwil.931014184737@lab4.duc.auburn.edu> Sender: usenet@news.duc.auburn.edu (News Account) Organization: Auburn University, Alabama References: <sengwil.931014154126@lab4.duc.auburn.edu> Date: Thu, 14 Oct 1993 23:47:37 GMT Hi! Sorry to use the bandwidth concerning audio CD probs - a missing cdaudio.util in /usr/filesystems/cdaudio.fs seems to have caused the failure of the auto-play of audio-cd's. Replacing the file (with correct permissions...) cured the problem. However, the problem with photo CD's still exists. Perhaps the following will help some guru spot my problem: Well, using more persistence I was able to get the following response out of my cube after it spun the photoCD for quite a while: qb2:18# ./CDROM.util -m sd3 /CD mount: /dev/rsd3h on /CD: Invalid argument mount: giving up on: /CD Suddenly a console message appeared: Disk is Write Protected cdrom: Unknown disc type. Mount aborted. I hope this narrows it. Any help in mounting PhotoCDs for use with pCD.app would be appreciated. -Bill ps Has anybody ever wondered why necessary files (like cdaudio.util) just disappear?
Newsgroups: comp.sys.next.bugs From: mms@world.std.com (Malcolm M Sanders) Subject: Re: open -a bug on Black NS3.1? In-Reply-To: mms@world.std.com's message of Thu, 14 Oct 1993 19:11:18 GMT Message-ID: <MMS.93Oct15075028@world.std.com> Sender: mms@world.std.com (Malcolm M Sanders) Organization: The World Public Access UNIX, Brookline, MA References: <MMS.93Oct14141118@world.std.com> Date: Fri, 15 Oct 1993 12:50:28 GMT In article <MMS.93Oct14141118@world.std.com> mms@world.std.com (Malcolm M Sanders) writes: open -a Terminal /usr/local/bin/term I expect that I will get a new Terminal.app window with the program, term, running in it. Instead, I get: open: can't open connection to Terminal on local host. The solution (Thanks to Pedja Bogdanovich) is that one must turn on the "Public Window Server" preference using Preferences.app. Malcolm Sanders mms@jax.org
Newsgroups: comp.sys.next.bugs From: peter@beast.math.ualberta.ca (Peter Karbaliotis) Subject: Re: clib atof() question Message-ID: <1993Oct15.152001.4738@kakwa.ucs.ualberta.ca> Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <1993Oct14.043648.1611@sfu.ca> Date: Fri, 15 Oct 1993 15:20:01 GMT In article <1993Oct14.043648.1611@sfu.ca> bill@sfu.ca (Bill Baines) writes: .. >-------------------- >#include <math.h> >int main() >{ > double f1; > char *s1 = "1234.567"; > > f1 = atof(s1); > printf("%s, %f\n",s1, f1); >} >-------------------- > >1) On SunOS 4.? > 1234.567, 1234.567000 [OK!] > >2) On NeXTOS 3.0 > 1234.567, 1083394628.000000 [Not ok] Compiling the program above with 'cc -Wall' (show all warnings) gives: test.c: In function `main': test.c:7: warning: implicit declaration of function `atof' test.c:8: warning: implicit declaration of function `printf' test.c:9: warning: control reaches end of non-void function The function atof() is defined in stdlib.h (it wouldn't hurt to include stdio.h as well). -- Peter Karbaliotis - peter@beast.math.ualberta.ca - NeXTmail ok X is proof that something can fill a vacuum but still suck. --- Dennis Ritchie
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 13 Oct 1993 10:12:52 +0100 Organization: Palumbian Research Labs Message-ID: <29ggqk$670@marsu.tynet.sub.org> References: <28rafu$1b1@marsu.tynet.sub.org> <294mns$3qg@news.mic.ucla.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit ivo@next.agsm.ucla.edu (Ivo Welch) writes: >I have posted exactly the same problem a few weeks ago. I have it confirmed >from NeXT: ANY CRASH MAY FORCE YOU TO REFORMAT YOUR HARDDISK, IF YOU ARE >UNLUCKY ENOUGH THAT THE FILE SYSTEM HAPPENS TO BE CORRUPTED IN A PARTICULAR >WAY. The reason is a bug in fsck (which is likely not to be fixed in 3.2, >either). Usually, you can still boot in single-user mode, and backup to >another disk (the inode is simply 1 corrupted file). Some wise gurus informed me about find / -inum [insert your favoured truncated inode] -exec rm "{}" \; would solve the problem. I never used find to search for inode numbers, so I didn't know this possibility. After deleting the file to the corresponding smashed inode, fsck should work for the rest of the file system. Regards, Markus. -- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Expert in quantum bogodynamics
Newsgroups: comp.sys.next.bugs From: agnus@amylnd.stgt.sub.org (Matthias Zepf) Subject: CDROM failure Content-Type: text/plain; charset=ISO-8859-1 Message-ID: <1993Oct16.001343.718@amylnd.stgt.sub.org> Content-Transfer-Encoding: 8bit Organization: Agnus' Home, Leonberg/Warmbronn, Germany Mime-Version: 1.0 Date: Sat, 16 Oct 1993 00:13:43 GMT Today, a friend brought his "Lost Treasures of Infocom CDROM" with him. I tried to read this CDROM (for PCs and Macs) with my NeXT CDROM Drive. But it failed. The CDROM should be normal ISO 9660 format and I tried the CDROM drivers from NS 3.0 and NS 3.1. Both failed. The CD is being ejected immediately. Any ideas? Matthias -- ** Matthias Zepf, Riegelaeckerstrasse 27, 71 229 Leonberg, Germany ** ** +49 7152 41917 Email: agnus@amylnd.stgt.sub.org (use NeXTmail!) **
From: kiwi@cs.tu-berlin.de (Axel Habermann) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Is /usr/etc/rshd broken??? Date: 16 Oct 1993 15:33:20 GMT Organization: Technical University of Berlin, Germany Distribution: usa Message-ID: <29p480$4f3@news.cs.tu-berlin.de> References: <JNICOLAS.93Oct14165920@image.mit.edu> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit jnicolas@image.mit.edu (Julien Nicolas) writes: >The following does NOT work: >pluto% rsh pluto ls >where pluto is the name of the NeXT computer runnning NS 3.1. There are no >error messages, rsh returns with error status 0, yet no output is >generated. Yes, the hostname is in /etc/host.equiv etc. I replaced >/usr/etc/rshd with a publicly available version and everything works as >it should. What gives? Hello! For a first try, change your login-shell on your NeXT to /bin/csh and see if it works then... Some weeks ago I had the same problem and found out that the tcsh I was using was corrupted so it didn.t start up from rshd but exited with bus error. Because I like the comfort of tcsh I tried to figure out why it happened and after I recompiled tcsh the bug disappeared. Axel -- Axel Habermann \\|// "Wenn Du kiwi@cs.tu-berlin.de (NO NeXT MAIL) )o o( nicht weisst kiwi@belly.in-berlin.de (NeXT Mail) \ | / was Du tust, FaxFon: +49 30 4543046 \~/ mach's mit Eleganz!"
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: Re: open -a bug on Black NS3.1? Message-ID: <1993Oct16.170806.5031@altsys.com> Organization: Altsys Corporation, Richardson, TX References: <MMS.93Oct14141118@world.std.com> Date: Sat, 16 Oct 1993 17:08:06 GMT In article <MMS.93Oct14141118@world.std.com> mms@world.std.com (Malcolm M Sanders) writes: >I have a problem with open on my NeXT Cube running NS 3.1. I issue the command: > >open -a Terminal /usr/local/bin/term > >I expect that I will get a new Terminal.app window with the program, term, >running in it. Instead, I get: > >open: can't open connection to Terminal on local host. > >I find that this problem is epidemic on my machine, e.g. > >open -a AnyApp ... > >results in > >open: can't open connection to AnyApp on local host. > >Is it just me, or what? > >Thanks, > >Malcolm Sanders >mms@jax.org I think you have to set your machine to be a Public Window server for open -a to work. I understand this is some kind of security risk, but I don't know why. Anyone care to enlighten me? Thx -- Lorin Rivers Lorin_Rivers@altsys.com NEXTSTEP Sales Manager 214.680.2060 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
Newsgroups: comp.sys.next.bugs From: lorinr@altsys.com (Lorin Rivers III) Subject: man pages in edit, solved Message-ID: <1993Oct16.171210.5115@altsys.com> Keywords: man, Edit.app Organization: Altsys Corporation, Richardson, TX References: <MMS.93Oct14141118@world.std.com> <1993Oct16.170806.5031@altsys.com> Date: Sat, 16 Oct 1993 17:12:10 GMT I posted a while back that I couldn't get Edit to find the man pages. Yesterday, I figured out what was up! After I updated my machine to 3.1 I mounted some directories (parts of NextLibrary abnd so forth) but I did not make a link from /NextLibrary/Documentation/ManPages to /usr/man. After I did, everything worked fine. Nayway, I thought I'd pass that along in case anyone else was having trouble. -- Lorin Rivers Lorin_Rivers@altsys.com NEXTSTEP Sales Manager 214.680.2060 269 W. Renner Parkway NeXT Mail Expected Richardson, Texas 75080 I said it, not my boss
Newsgroups: comp.sys.next.bugs From: alastair@farli.otago.ac.nz (Alastair Thomson) Subject: Librarian shelf problems. Message-ID: <CF0Csy.1yF@news.otago.ac.nz> Sender: usenet@news.otago.ac.nz (News stuff) Organization: University of Otago Date: Sat, 16 Oct 1993 20:55:46 GMT Hi there, I have a problem with the shelf in Librarian. Whenever I save it, or resize the shelf, I end up with the various documents sitting on top of on another. If I resize more than three or four times, I end up with only one icon visible, and all the rest stacked underneath. I have fourteen icons arranged in three rows, six on the top two, and two on the bottom. Is this a common problem, or just the size I have my window set to? Alastair -- Alastair Thomson, | Phone +64-3-479-8347 Chief Programmer, | Fax +64-3-479-8529 The Black Albatross Project, | University of Otago, | alastair@farli.otago.ac.nz Dunedin, New Zealand | NeXTmail Welcome
Newsgroups: comp.sys.next.bugs From: lmccullo@nyx.cs.du.edu (Michael McCulloch) Subject: Trig function broken? Message-ID: <1993Oct17.131649.18826@mnemosyne.cs.du.edu> of Denver for the Denver community. The University has neither control over nor responsibility for the opinions of users. Sender: usenet@mnemosyne.cs.du.edu (netnews admin account) Organization: Nyx, Public Access Unix at U. of Denver Math/CS dept. Date: Sun, 17 Oct 93 13:16:49 GMT I was developing an app on 3.1 Intel and have encountered some strange behavior with cos(). Try running the program below *on an Intel box*: #include <stdio.h> #include <math.h> void main() { double value,result; printf("Enter value for cos(): "); scanf("%lf", &value); result = cos(value); printf("Result = %lf", result); printf("\n"); } Enter a value of greater than around 1x10^29 and the cos() function either returns a ridiculous result or just hangs without ever returning. Am I missing something obvious here, or is this a pretty serious bug in the math library? -- Michael McCulloch michael@hsv.tybrin.com (NextMail Accepted!) Huntsville, Alabama
From: bkr@drdhh.hanse.de (Bjoern Kriews) Newsgroups: comp.sys.next.bugs Subject: new_posix_proc() panic (help !) Date: 16 Oct 1993 18:31:58 +0100 Organization: Digital Island Message-ID: <bkr.750791718@drdhh> Keywords: panic, kernel >Path: drdhh!bkr Good morning - or whatever ! My machine (mono station, non-turbo, 16M, 3.1) is running as a local uucp server, having a lot of modem traffic. Eventually, I had panics like: Oct 16 18:08:15 drdhh mach: panic: (Cpu 0) new_posix_proc(): attempt to create posix proc struct for pid 384, found existing struct; process exists. This happened 3 or 4 times in one week. 2 times attended by me: 1.) no machine action except uucp transfer [38400 rtscts] -> crash 2.) zmodem 38400 download (incoming) - then 'cp' command by me -> crash The crashes seem to be related to modem action. The pid was not the same. I few days ago, I read that one should better leave ones fingers off the NeXT pseudo posix stuff - well, I compiled taylor uucp with some posix kludges - and thought it might well be worth fixing. So I compiled taylor cleanly. Today, I am sitting here, running 'term' to some remote machine, pasting a lot of lines into a terminal window -> crash. I have not yet done logging to see which procs are crashing. One of the crashes was a bit more verbose: Oct 10 14:40:12 drdhh mach: Oct 10 14:40:12 drdhh mach: Killing all processes .trap: type 0xc fcode 269556000 rw 1 faultaddr 0x4 Oct 10 14:40:12 drdhh mach: trap: pc 0x40019c8 sp 0x3ffff2c sr 0x2700 Oct 10 14:40:12 drdhh mach: trap: cpu 0 th 0x1015163c proc 0x101712c0 pid 23710 pcb 0x1109f010 Oct 10 14:40:12 drdhh mach: traceback: fp 0x405dd34 Oct 10 14:40:12 drdhh mach: last fp 0x405dd34 Oct 10 14:40:12 drdhh mach: panic: (Cpu 0) address error The last crash happened after 3 days of problem-free operation. the machine had lots of ours of modem traffic these days. I am not sure but I think I've seen a 'silo overflow' message near the kernel panics once (the first log is gone :-/ ). If somebody has made the same experiences or is able to give me a hint - please mail me for help or let's dig into it together. I'm a bit frustrated - I never ran 3.0 - I loved my 2.1 for it's speed and relative robustness. Now I paid a lot of student money for 3.1 and have a slower, sometimes badly scheduled machine that throws 4 panics in one week at me. I hope that this is somehow my fault. Last info: The machine is non-networked and the only non-NeXT daemon is inn1.4 (compiled with -bsd). Thanks for your time !!! - Bjoern -- bkr@drdhh.hanse.de - Bjoern Kriews - Stormsweg 6 - D-2000 Hamburg 76 - FRG By definition, a properly functioning kernel doesn't allow user programs to make it crash unless they say "please". (Richard Stallman)
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: Trig function broken? Date: Sun, 17 Oct 1993 14:11:14 -0400 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Message-ID: <ogkMf2G00WB=A8O3Ff@andrew.cmu.edu> In-Reply-To: <1993Oct17.131649.18826@mnemosyne.cs.du.edu> Excerpts from netnews.comp.sys.next.bugs: 17-Oct-93 Trig function broken? by Michael McCulloch@nyx.cs > I was developing an app on 3.1 Intel and have encountered some strange > behavior with cos(). > > Try running the program below *on an Intel box*: > > [munch] > > Enter a value of greater than around 1x10^29 and the cos() function > either returns a ridiculous result or just hangs without ever > returning. > > Am I missing something obvious here, or is this a pretty serious bug > in the math library? Trying to compute cos(10^29) is not a reasonable thing to do. The values for these functions are normalized (for trig, mod 2*pi), and the phase error associated with the limited precision of digital math means that cos() *cannot* possibly return anything but a random number between -1..1. You should not try to use the trig functions on values larger than 10^8 without losing accuracy. To see this, try entering these values into your program: 3.1415926536 31.415926536 314.15926536 <etc> Note that cos() should never return a value outside of -1..1, and should never hang either; but this is possibly due to a problem with the floating point trig function implementation on the CPU or math coprocessor chip in your machine (you *do* have a math coprocessor, right?) -Chuck Charles William Swiger -- CMU...*crunch*! | 1. You can't fly. ------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@mon.slip.andrew.cmu.edu | 4. Fire burns.
From: Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU> Newsgroups: comp.sys.next.bugs Subject: re: new_posix_proc() panic (help !) Date: Sun, 17 Oct 1993 14:45:07 -0700 Organization: University of Washington Message-ID: <MS-C.750894307.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII To: Bjoern Kriews <bkr@drdhh.hanse.de> In-Reply-To: <bkr.750791718@drdhh> I have seen this panic too. In my case, this is on a machine that was completely idle, module an active SLIP and Ethernet link. Of course, this panic *always* happen when I am not around to fix the machine, and a good hour or more of travel time away, so the network link supported by this machine is also down for the duration. This is yet another one of the bugs introduced in 3.1, easily the WORST new version of NEXTSTEP ever released. I'm eagerly awaiting 3.2 to see how many more things they contrive to break.
From: ralf@reswi.en.open.de (Ralf E. Stranzenbach) Newsgroups: comp.sys.next.bugs Subject: does lockf does it's job ? Date: 17 Oct 1993 21:18:47 GMT Organization: News Server fuer en.open.de Message-ID: <RALF.93Oct17221847@jodokus.en.open.de> Hi, i tried to write a simple data storing application and need file locking for it to work. But as far as i can see, lockf() and fcntl() do not work on 3.1(m68k). Below this line there is a simple test program i used to check this out. I hope, that it's a mistake on my own. flock() works, but i would like to lock-out single records, not only the whole file... - ralf #include <stdio.h> #include <sys/file.h> #include <sys/stat.h> #include <fcntl.h> main () { extern int errno; int fd; char tmp [100]; struct flock lbuf; fd = open ("testfile", O_RDWR | O_CREAT, 0666); if (fd < 0) { printf ("open returns %d\n", errno); exit (1); } if (write (fd, tmp, 100) != 100) { printf ("write failed with %d\n", errno); exit (1); } if (lseek (fd, 0, 0) < 0) { printf ("lseek returns %d\n", errno); exit (1); } if (lockf (fd, F_LOCK, 1) < 0) { printf ("lockf(F_LOCK) returns %d\n", errno); } else { if (lockf (fd, F_ULOCK, 1) < 0) { printf ("lockf(F_ULOCK) returns %d\n", errno); exit (1); } } lbuf.l_type = F_WRLCK; lbuf.l_whence = 0; lbuf.l_start = 0; lbuf.l_len =1; if (fcntl (fd, F_SETLKW, &lbuf) < 0) { printf ("fcntl(F_WRLCK) returns %d\n", errno); } else { lbuf.l_type = F_UNLCK; if (fcntl (fd, F_SETLK, &lbuf) < 0) { printf ("fcntl(F_UNLCK) returns %d\n", errno); exit (1); } } close (fd); exit (0); } -- Ralf E.Stranzenbach - (NeXT)-Mail: ralf@reswi.en.open.de Fido: Ralf_Stranzenbach 2:245/5800.12 (Voice)-Phone: +49 2302 / 68403 -- Computer sind die praktische Anwendung der Murphyschen Gesetze.
Newsgroups: comp.sys.next.bugs From: robocop@p232.informatik.Uni-Bremen.DE (Dirk Lehmann + Co) Subject: Major Problems with CD-CROM on NS 3.1 (Black) Message-ID: <1993Oct18.124204.1597@informatik.uni-bremen.de> Sender: robocop@p232 (Dirk Lehmann + Co) Organization: Universitaet Bremen Date: Mon, 18 Oct 1993 12:42:04 GMT Last weekend a might have found a big bug in NS 3.1 while accessing my CD-ROM(Apple150 = NeXT-drive). I only wanted to copy some data from a NOVA-CD to my harddisk via the Workspace, but after a while my machine hang up, by showing the busycursor. I could open the nmi-monitor but a reboot command couldn't stop my machine. So I had to pull the wire out of the machine. The same thing happend once again. The next time I tried to copy the files from the shell, but there also was no success. Also tar (later gtar) were not able to build an archive in my homedirectory. By double-clicking a rtfd-document on the CD , Edit opened with the warning : Filesystem Error !, while the Workspace-Inspector for rtfd-documents showed the correct content. In a shell I couldn't even list the directory of some folders. For those who want to backtrack the bug: Copying from Workspace /NOVA/Apps/Communications/pcomm (I guess) -> ~ ls -l in /NOVA/Demos/Graphics/Tesseract/Tesseract.app/English.lproj/Help/ or tar fcv ~/test.tar /NOVA/Demos/Graphics/Tesseract/Tesseract.app/English.lproj/Help Hope this bug isn't in 3.2 ! Dirk
Newsgroups: comp.sys.next.bugs From: Greg_Anderson@afs.com (Gregory H. Anderson) Subject: Re: does lockf does it's job ? Message-ID: <1993Oct18.141014.4010@afs.com> Sender: greg@afs.com References: <RALF.93Oct17221847@jodokus.en.open.de> Date: Mon, 18 Oct 1993 14:10:14 GMT In article <RALF.93Oct17221847@jodokus.en.open.de> ralf@reswi.en.open.de (Ralf E. Stranzenbach) writes: > Hi, > > i tried to write a simple data storing application and need file > locking for it to work. But as far as i can see, lockf() and fcntl() > do not work on 3.1(m68k). Never have worked, probably never will. -- Gregory H. Anderson | "History is the fiction we invent to Revisionist Autobiographer | persuade ourselves that events are Anderson Financial Systems | knowable and that life has order and greg@afs.com (NeXTmail OK) | direction." -- Calvin & Hobbes, 7/19/93
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 19 Oct 1993 00:34:34 -0400 Organization: Next Announcements Message-ID: <29vqoo$slo@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Interesting promotion to i486 via htonl(). Message-ID: <SCOTT.93Oct20023434@nic.gac.edu> From: scott@nic.gac.edu (Scott Hess) Date: 20 Oct 93 02:34:34 Distribution: world Organization: Is a sign of weakness This evening while building an app that uses TCP sockets, I was checking to make certain that I'd gotten everything MAB. So, I ran the TickleServices Lipo/Edit Files option on the .app/ wrapper, and Lo!, one of the files _wasn't_! After a rebuild with the file _still_ not coming out fat, I looked more closely and it turned out that the file had m68k and i486 archs - not i386! So, I'm thinking "Well, that's neat." Watch the build go by ... and, yes indeed, all those flags are -arch i386. Not an i486 to be seen. So, I look at the object files, and trace the i486 arch down through the subprojects until I find that it's in Socket.m. Hmm. So, I start commenting out code, and reduced the problem to this: // cc -g -O -Wall -arch m68k -arch i386 -c ack.c // lipo ack.o -info // Architectures in the fat file: ack.o are: m68k i486 #import <libc.h> void main( void) { unsigned i=10; i=htonl( i); } So, there appears to be a bug in htonl() which does automagic promotion to i486. Joy. Now for my question - does this make a difference? Presumably not, because all NeXTSTEP (oops, NEXTSTEP) compliant Intel machines are already supposed to be i486, right? On the other hand, why didn't NeXT use -arch i386 switch with the build tools instead of -arch i486, then? [ie, presumably there's a reason.] [BTW, I ran an egrep through the include files on __asm__, and it looks like the only file which uses __asm__ is <architecture/i386/byte_order.h>. I suppose that _could_ be the cause of the problem.] Later, -- scott hess <scott@nic.gac.edu> <I can handle NeXTMail, but don't like it> 12901 Upton Avenue South, #326 Burnsville, MN 55337 (612) 895-1208 Anytime! <C++: ... One Language to bring them all and in the darkness bind them> <In the Land of Redmond where the Shadows lie.>
From: Roland Telfeyan <roland@gomidas.mi.org> Newsgroups: comp.sys.next.bugs Subject: DOS floppy looks like DOS CD-ROM on 3.1 cube Date: 20 Oct 1993 18:34:34 GMT Organization: University of Michigan EECS Dept. Distribution: world Message-ID: <2a40bq$5iu@zip.eecs.umich.edu> When I insert a DOS floppy into my 3.1 cube's PLI SuperFloppy drive, it appears on the shelf with a DOS CD-ROM icon. Any ideas why? Roland
Newsgroups: comp.sys.next.bugs From: tom@basil.icce.rug.nl (Tom R.Hageman) Subject: accented characters in Ohlfs font [RTF] Message-ID: <CF63xB.1F4@basil.icce.rug.nl> Sender: tom@basil.icce.rug.nl (Tom R.Hageman) Organization: Warty Fowls Date: Tue, 19 Oct 1993 23:29:35 GMT Is it just me, or are the accented characters in the Ohlfs font really displayed as Courier? For example: Ohlfs: a A (16pt) Courier: a A (20pt) Will this be corrected in NS 3.2? (just kidding ;-) -- __/__/__/__/ Tom Hageman (tom@basil.icce.rug.nl) [NeXTMail accepted] __/ __/_/ __/__/__/ __/ _/_/ <space for quote intentionally left blank> -- NewsGrazer, a NeXTstep(tm) news reader, posting -- M>UQR=&8P7&%N<VE[7&9O;G1T8FQ<9C!<9G-W:7-S($AE;'9E=&EC83M<9C%< M9FUO9&5R;B!/:&QF<SM<9C)<9FUO9&5R;B!#;W5R:65R.WT*7&UA<F=L,3(P M"EQM87)G<C$R,`I[7&-O;&]R=&)L.UQR960X,UQG<F5E;C@S7&)L=64X,SM< M<F5D,38X7&=R965N,38X7&)L=64Q-C@[?0I<<&%R9%QT>#$Q-3)<='@R,S`T M7'1X,S0U-EQT>#0V,#A<='@U-S8P7'1X-CDQ,EQT>#@P-C1<='@Y,C$V7'1X M,3`S-CA<='@Q,34R,%QF,%QB,%QI,%QU;&YO;F5<9G,R-%QF8S!<8V8P($ES M(&ET(&IU<W0@;64L(&]R(&%R92!T:&4@86-C96YT960@8VAA<F%C=&5R<R!I M;B!T:&4@3VAL9G,@9F]N="!R96%L;'D@9&ES<&QA>65D(&%S($-O=7)I97(_ M7`I<"D9O<B!E>&%M<&QE.EP*7`I/:&QF<SH)"EQF,5QF<S,R(&'9084)"EQF M,%QF<S(T("@Q-G!T*5P*0V]U<FEE<CH)"EQF,EQF<S0P(&'9084)"EQF,%QF M<S(T("@R,'!T*5P*7`I7:6QL('1H:7,@8F4@8V]R<F5C=&5D(&EN($Y3(#,N M,C\@("AJ=7-T(&MI9&1I;F<@.RTI7`I<"BTM7`H*7'!A<F1<='@Y-C!<='@Q M.3(P7'1X,C@X,%QT>#,X-#!<='@T.#`P7'1X-3<V,%QT>#8W,C!<='@W-C@P M7'1X.#8T,%QT>#DV,#!<9C%<9G,R,%QG<F%Y,S,S7&9C,5QC9C$@7U\O7U\O M7U\O7U\O"EQG<F%Y,%QF8S!<8V8P("`@"EQF,%QF<S(T(%1O;2!(86=E;6%N M("`@*'1O;4!B87-I;"YI8V-E+G)U9RYN;"D@("`*7&=R87DS,S-<9F,Q7&-F M,2!;3F585$UA:6P@86-C97!T961="EQF,5QF<S(P7&=R87DP7&9C,%QC9C`@ M7`H*7&=R87DS,S-<9F,Q7&-F,2`@(%]?+R!?7R]?+UP*(%]?+U]?+U]?+UP* M7U\O("!?+U\O"EQG<F%Y,%QF8S!<8V8P("`@("`@("`@("`@"EQF,%QI7&9S M,C1<9W)A>38V-EQF8S)<8V8R(#QS<&%C92!F;W(@<75O=&4@:6YT96YT:6]N M86QL>2!L969T(&)L86YK/@I<9C%<:3!<9G,R,%QG<F%Y,%QF8S!<8V8P(%P* #"GT* `
From: wardm@well.sf.ca.us(Ward Mullins) Newsgroups: comp.sys.next.bugs Subject: NS/FIP corrupts Dos partition Date: 20 Oct 1993 20:14:09 GMT Organization: THOUGHT Inc. Distribution: world Message-ID: <2a466h$1l6@male.EBay.Sun.COM> I have a dos partition which I am attempting to access from NS/FIP. NS mounts the partition correctly and I can see the files and filesystem, but when I boot dos and modify the partition, NS does *not* see the changes to the disk when it is rebooted. Not only that, but it corrupts the FAT of the dos partition and requires me to do a chkdsk in dos... Has *anyone* seen this problem, and do you know what to do to get around it? Ward Mullins THOUGHT Inc. ------------------------------------------------------------- |Win NT is Not unix, although it would like to be... | -------------------------------------------------------------
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: cedman@princeton.edu (Carl Edman) Subject: Re: Interesting promotion to i486 via htonl(). In-Reply-To: scott@nic.gac.edu's message of 20 Oct 93 02:34:34 To: scott@nic.gac.edu (Scott Hess) Message-ID: <CEDMAN.93Oct20091937@capitalist.princeton.edu> Originator: news@nimaster Sender: news@Princeton.EDU (USENET News System) Organization: Princeton University References: <SCOTT.93Oct20023434@nic.gac.edu> Date: Wed, 20 Oct 1993 13:19:36 GMT In article <SCOTT.93Oct20023434@nic.gac.edu> scott@nic.gac.edu (Scott Hess) writes: So, there appears to be a bug in htonl() which does automagic promotion to i486. Joy. Now for my question - does this make a difference? Presumably not, because all NeXTSTEP (oops, NEXTSTEP) compliant Intel machines are already supposed to be i486, right? On the other hand, why didn't NeXT use -arch i386 switch with the build tools instead of -arch i486, then? [ie, presumably there's a reason.] [BTW, I ran an egrep through the include files on __asm__, and it looks like the only file which uses __asm__ is <architecture/i386/byte_order.h>. I suppose that _could_ be the cause of the problem.] Exactly. This problem occurs with all the byte-order mangling functions under NS/FIP. Apparently 486s can implement those swaps faster than 386s can. I would not necessarily consider this a bug. However, it is a nuisance. That is why it says in the Makefile for the Mail.app utilities: thin-i386: $(BINS) -for i in $(BINS) ; do lipo -remove m68k -output $$i $$i; done Rather than (which would make a lot more sense): thin-i386: $(BINS) -for i in $(BINS) ; do lipo -thin i386 -output $$i $$i; done Carl Edman
Newsgroups: comp.sys.next.bugs From: smith@nextone.niehs.nih.gov (Howard C. Smith) Subject: NETINFO failure on ethernet address Message-ID: <1993Oct21.165316.3403@alw.nih.gov> Keywords: netinfo ethernet ip internet Sender: postman@alw.nih.gov (AMDS Postmaster) Organization: National Institutes of Health Date: Thu, 21 Oct 1993 16:53:16 GMT Has anyone seen the following: We have a network with all black hardware, now just attemplting to add the first intel box to the netinfo db. When using HostManager.app and adding the correct ip_address and en_address, during a save to domain operation I get an alert panel: Invalid ethernet address. Aborting. Has anyone else seen this behaivior? Im positive the ip and ethernet addresses are correct. We ARE doing subnetting. -- Howard C. Smith National Institute of Environmental Health Sciences smith@nextone.niehs.nih.gov
From: milhouse!dmitri (Dmitri Linde) Newsgroups: comp.sys.next.bugs Subject: Bug in RemoteVote Date: 21 Oct 1993 17:48:43 GMT Organization: California Institute of Technology, Pasadena Distribution: world Message-ID: <2a6i1s$oo6@gap.cco.caltech.edu> Keywords: bug distributed objects Originator: dmitri@milhouse Hi! I am wrote a simple server called Software.app to collect information about software on a network server. You may ftp it from physics.stanford.edu. Several people have told me that there is a bug in it. Specifically, after the client quits there are still connections left to the server. This is bad for security reasons. What is worse is that these connections are also present on the server. So now my server has about 100 connections which I can't disconnect (one can check using netstat command) and it is working very very slowly. I tried to fix that bug for a couple of days but I could not. Then I tried another Distributed Objects application -- RemoteVote in /NextDeveloper/Examples/DistributedObjects. It has the same bug!!! How to test it: Assume you have two NeXT computers foo and bar on local network. Compile RemoteVote on computer foo. Run it. execute command netstat | grep bar on computer foo to see that there are no connections between foo and bar. Then Run RemoteVote on bar. execute the same command again on foo to check that now there are connections between foo and bar. Now quit RemoteVote on bar and check that there still are connections between foo and bar. For more fun, run RemoteVote on other NeXT computers and quit it. Then check that you have a load of connections on foo and it works like a turtle. What can be done? I have not been able to find anything in documentation about disconnecting connections. Has anybody solved this problem? If not I would have to rewrite Software.app using UDP which is a pain in the neck compared to Distributed Objects. Comments greatly appreciated... Dmitri Linde dmitri@cco.caltech.edu
From: izumi@pinoko.berkeley.edu (Izumi Ohzawa) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: Bug in RemoteVote Date: 21 Oct 1993 18:44:30 GMT Organization: University of California, Berkeley Distribution: world Message-ID: <2a6lae$l14@agate.berkeley.edu> References: <2a6i0a$oo1@gap.cco.caltech.edu> In article <2a6i0a$oo1@gap.cco.caltech.edu> milhouse!dmitri (Dmitri Linde) writes: >I am wrote a simple server called Software.app to collect information >about software on a network server. You may ftp it from >physics.stanford.edu. > >Several people have told me that there is a bug in it. Specifically, after >the client quits there are still connections left to the server. Additional note on this bug is that, these lingering connections are not in xxx_WAIT states which usually go away in 10 minutes or so. Connections left over by distrubuted objects are still in the ESTABLISHED state which will hang around until either the server or client is rebooted. This is what I get AFTER Software.app quits: % netstat Active Internet connections Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 moica.2453 physics.Stanford.2747 ESTABLISHED tcp 0 0 moica.3033 physics.Stanford.2453 ESTABLISHED .... -- Izumi Ohzawa [ $@Bg_78^=;(J ] USMail: University of California, 360 Minor Hall, Berkeley, CA 94720 Telephone: (510) 642-6440 Fax: (510) 642-3323 Internet: izumi@pinoko.berkeley.edu (NeXTMail OK)
Newsgroups: comp.sys.next.bugs From: tom@basil.icce.rug.nl (Tom R.Hageman) Subject: Re: Interesting promotion to i486 via htonl(). Message-ID: <CF9pH4.10F@basil.icce.rug.nl> Sender: tom@basil.icce.rug.nl (Tom R.Hageman) Organization: Farty Owls References: <CEDMAN.93Oct20091937@capitalist.princeton.edu> Date: Thu, 21 Oct 1993 22:07:51 GMT In article <CEDMAN.93Oct20091937@capitalist.princeton.edu> cedman@princeton.edu (Carl Edman) writes: > In article <SCOTT.93Oct20023434@nic.gac.edu> scott@nic.gac.edu (Scott Hess) writes: > So, there appears to be a bug in htonl() which does automagic > promotion to i486. Joy. > [munch] > > Exactly. This problem occurs with all the byte-order mangling > functions under NS/FIP. Apparently 486s can implement those swaps > faster than 386s can. I would not necessarily consider this a bug. > However, it is a nuisance. That is why it says in the Makefile for > the Mail.app utilities: > > thin-i386: $(BINS) > -for i in $(BINS) ; do lipo -remove m68k -output $$i $$i; done > > Rather than (which would make a lot more sense): > > thin-i386: $(BINS) > -for i in $(BINS) ; do lipo -thin i386 -output $$i $$i; done > (with this they'll get what they deserve when they release NS/HP }-) Unfortunately, `lipo -thin i386' does not thin a fat file that contains a sub-architecture like "i486", as I think it should. As a workaround I wrote this shell script, appropriately called "thin", that handles sub-architectures when thinning. (it also spits out non-fat files unmodified--these are considered "thin" by definition): begin 755 thin M(R$O8FEN+W-H"B,@4D-3("1)9#H@=&AI;BQV(#$N,2`Q.3DS+S`X+S,P(#$P M.C0X.C(X('1O;2!%>'`@)`HC('1H:6XZ(&!@<V%F92<G(&QI<&]S=6-T:6]N M"@IC87-E("0C(&EN"C,I(#L["BHI(&5C:&\@(E5S86=E.B`D,"`\87)C:&ET M96-T=7)E/B`\:6YP=71F:6QE/B`\;W5T<'5T9FEL93XB"F5S86,*"G)E<W5L M=#TB8&QI<&\@+71H:6X@)#$@+6]U='!U="`D,R`D,B`R/B8Q8"(*8V%S92`B M)')E<W5L="(@:6X*(B(I"B`@(R!3=6-C97-S(0H@(#L["BID;V5S*FYO="IC M;VYT86EN*BD*("`C($]H(&)O>2$@24U(3R!L:7!O('-H;W5L9"!E>'1R86-T M('1H92!M;W)E('-P96-I86QI>F5D(&-P=2US=6)T>7!E"B`@(R!I9B!T:&%T M(&UA=&-H97,@=&AE(&=E;F5R:6,@8W!U+71Y<&4@=V4@=V5R92!A<VMI;F<@ M9F]R+@H@(",@0G5T('-I;F-E(&ET(&1O97-N)W0L('!R;V-E960@8GD@=')I M86P@86YD(&5R<F]R+BXN"B`@8V%S92`B)#$B(&EN"B`@;38X:RD@86QT<STB M;38X,#,P(&TV.#`T,"(@.SL*("!I,S@V*2!A;'1S/2)I-#@V(&DT.#936"!I M-3@V(&DU.#936"(@.SL*("`J*0EE8VAO("(D<F5S=6QT(B`^)C(*"65X:70@ M,0H@(&5S86,*("!F;W(@86QT(&EN("1A;'1S"B`@9&\*("`@(&EF(&QI<&\@ M+71H:6X@)&%L="`M;W5T<'5T("0S("0R(#(^+V1E=B]N=6QL"B`@("!T:&5N M"@EE>&ET"B`@("!F:0H@(&1O;F4*("`C(&1I9&XG="!S=6-C965D(&EN(&5X M=')A8W1I;F<@86X@86QT97)N871I=F4@87)C:&ET96-T=7)E+BXN"B`@96-H M;R`B)')E<W5L="(@/B8R"B`@97AI="`Q"B`@.SL**F-A;BIT*F9I9W5R92IO M=70J87)C:&ET96-T=7)E*BD*("`C(%1H:7,@:7,@;F]T(&$@9F%T(&9I;&4L M(&%P<&%R96YT;'DN("!3;R!C;W!Y(&ET('5N8VAA;F=E9"X*("!C<"`M<"`D M,B`D,PH@(#L["BHI"B`@96-H;R`B)')E<W5L="(@/B8R"B`@97AI="`Q"F5S %86,*"@H@ ` end Enjoy, -- __/__/__/__/ Tom Hageman (tom@basil.icce.rug.nl) [NeXTMail accepted] __/ __/_/ __/__/__/ __/ _/_/ <space for quote intentionally left blank>
From: jklinke@aeon.UCSD.EDU (Jochen Klinke) Newsgroups: comp.sys.next.bugs Subject: Re: DOS floppy looks like DOS CD-ROM on 3.1 cube Date: 22 Oct 1993 11:59:48 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9310221543.AA00424@aeon.UCSD.EDU> >When I insert a DOS floppy into my 3.1 cube's PLI SuperFloppy drive, >it appears on the shelf with a DOS CD-ROM icon. Any ideas why? No idea why, but your floppy is probably write protected, since a non-write protected DOS floppy appears with an optical disk icon on my shelf. Jochen
From: erikkay@next.com (Erik Kay) Newsgroups: comp.sys.next.bugs Subject: Re: DOS floppy looks like DOS CD-ROM on 3.1 cube Date: 21 Oct 1993 22:41:09 GMT Organization: NeXT, Inc. Distribution: world Message-ID: <2a7365$qcn@rosie.next.com> References: <2a40bq$5iu@zip.eecs.umich.edu> In article <2a40bq$5iu@zip.eecs.umich.edu> Roland Telfeyan <roland@gomidas.mi.org> writes: > When I insert a DOS floppy into my 3.1 cube's PLI SuperFloppy drive, it > appears on the shelf with a DOS CD-ROM icon. Any ideas why? > > Roland It's a known bug in NS 3.1 / 3.2. Icons for most floppies put into SCSI floppy drives come out incorrectly in the viewer. Erik
Newsgroups: comp.sys.next.bugs From: thf@zelator.in-berlin.de (Thomas Funke) Subject: Severe TCP/IP-Bug: Sybase still crashes 3.1 Message-ID: <1993Oct21.105557.251@gamelan> Sender: thomas@gamelan (thomas) Organization: Disorganization Date: Thu, 21 Oct 1993 10:55:57 GMT It has been reported before for NS2.x and NS3.0, but this bug is still in NS3.1 (Motorola): If you use the limited Sybase server with standard configuration, log into the database about 1000 times, the NeXT will completely hang, reboot is necessary. The reason is a collision if internal (tcp) portnumbers with the ports Sybase is listening to. Sybase uses ports 3696+4696. If you change Sybase's configuration to use ports > 5000, everything is fine. Thus: Don't use portnumbers <= 5000 for applications. The following program can verify this bug: /* ** bug.c ** Crashes NeXTSTEP 2.x + 3 .x ** ** */ #include <stdio.h> #include <sybfront.h> #include <sybdb.h> #define DATELEN 26 #define TYPELEN 2 /* Forward declarations of the error handler and message handler. */ int err_handler(); int msg_handler(); main(argc, argv) int argc; char *argv[]; { DBPROCESS *dbproc; /* Our connection with SQL Server. */ LOGINREC *login; /* Our login information. */ /* These are the variables used to store the returning data. */ RETCODE result_code; int i,j,k; for (i=0; i<2000; i++) { /* Initialize DB-Library. */ if (dbinit() == FAIL) exit(ERREXIT); /* Install the user-supplied error-handling and message-handling * routines. They are defined at the bottom of this source file. */ dberrhandle(err_handler); dbmsghandle(msg_handler); /* ** Get a LOGINREC structure and fill it with the necessary ** login information. */ login = dblogin(); DBSETLPWD(login, ""); DBSETLAPP(login, "crashtest"); DBSETLUSER(login, "sa"); /* ** Get a DBPROCESS structure for communicating with SQL Server. ** A NULL servername defaults to the server specified by DSQUERY. */ dbproc = dbopen(login, NULL); if (dbproc) dbclose (dbproc); dbloginfree (login); printf ("PASSED: %d\n", i); dbexit(); // sleep (1); } dbexit(); exit(STDEXIT); } int err_handler(dbproc, severity, dberr, oserr, dberrstr, oserrstr) DBPROCESS *dbproc; int severity; int dberr; int oserr; char *dberrstr; char *oserrstr; { if ((dbproc == NULL) || (DBDEAD(dbproc))) return(INT_EXIT); else { printf("DB-Library error:\n\t%s\n", dberrstr); if (oserr != DBNOERR) printf("Operating-system error:\n\t%s\n", oserrstr); return(INT_CANCEL); } } int msg_handler(dbproc, msgno, msgstate, severity, msgtext, srvname, procname, line) DBPROCESS *dbproc; DBINT msgno; int msgstate; int severity; char *msgtext; char *srvname; char *procname; DBUSMALLINT line; { printf ("Msg %ld, Level %d, State %d\n", msgno, severity, msgstate); if (strlen(srvname) > 0) printf ("Server '%s', ", srvname); if (strlen(procname) > 0) printf ("Procedure '%s', ", procname); if (line > 0) printf ("Line %d", line); printf("\n\t%s\n", msgtext); return(0); } Hardware Configuration: Processor: MC680x0 (68040) Processor speed: 25 MHz Primary memory: 24.00 MB Software Configuration: NeXT Mach 3.1: Fri Apr 30 08:31:15 PDT 1993; root(rcbuilder):mk-149.22.3.obj~2/RC_m68k/RELEASE_M68K -- ------------------------------------------------------------------ Thomas Funke ** Unix-Consultant ** thf@zelator.in-berlin.de Brooks's Law: Adding manpower to a late software project makes it later ------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: ed@joker.fdn.org (Erik Dasque) Subject: Re: NS/FIP corrupts Dos partition Message-ID: <1993Oct23.171127.4377@joker.fdn.org> Sender: ed@joker.fdn.org Organization: French Guy Corp. - Paris, France. References: <2a466h$1l6@male.EBay.Sun.COM> Date: Sat, 23 Oct 1993 17:11:27 GMT In article <2a466h$1l6@male.EBay.Sun.COM> wardm@well.sf.ca.us(Ward Mullins) writes: > I have a dos partition which I am attempting to access from NS/FIP. NS mounts > the partition correctly and I can see the files and filesystem, but when I boot > dos and modify the partition, NS does *not* see the changes to the disk when > it is rebooted. Not only that, but it corrupts the FAT of the dos partition > and requires me to do a chkdsk in dos... > > Has *anyone* seen this problem, and do you know what to do to get around it? > > Ward Mullins > THOUGHT Inc. > > ------------------------------------------------------------- > |Win NT is Not unix, although it would like to be... | > ------------------------------------------------------------- > Did you re-format the DOS partition after installing NEXTSTEP ? I think you should have. I re-formated it and had no problems since. Ed. -- Erik Dasque "The French Guy" Intuitive Technologies (ex-Cub'x Systemes) only SMALL NeXTMAIL pleeeeease... ed@cubx.com It all started 2 full back-up ago... -- Erik Dasque "The French Guy" Intuitive Technologies (ex-Cub'x Systemes) only SMALL NeXTMAIL pleeeeease... ed@cubx.com It all started 2 full back-up ago...
From: joisha@bodhi.esys.cwru.edu (Prashanth Joisha) Newsgroups: comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 24 Oct 1993 20:38:24 GMT Organization: Case Western Reserve University, Cleveland, Ohio (USA) Message-ID: <2aep40$t00@usenet.INS.CWRU.Edu> References: <29ggqk$670@marsu.tynet.sub.org> In article <29ggqk$670@marsu.tynet.sub.org> mow@marsu.tynet.sub.org (Markus Wenzel) writes: > ivo@next.agsm.ucla.edu (Ivo Welch) writes: > >I have posted exactly the same problem a few weeks ago. I have it confirmed > >from NeXT: ANY CRASH MAY FORCE YOU TO REFORMAT YOUR HARDDISK, IF YOU ARE > >UNLUCKY ENOUGH THAT THE FILE SYSTEM HAPPENS TO BE CORRUPTED IN A PARTICULAR > >WAY. The reason is a bug in fsck (which is likely not to be fixed in 3.2, > >either). Usually, you can still boot in single-user mode, and backup to > >another disk (the inode is simply 1 corrupted file). > > Some wise gurus informed me about > > find / -inum [insert your favoured truncated inode] -exec rm "{}" \; > > would solve the problem. I never used find to search for inode numbers, > so I didn't know this possibility. After deleting the file to the > corresponding smashed inode, fsck should work for the rest of the file > system. > > Regards, > Markus. > > > -- > Markus Wenzel System administration, Consulting, Networking > mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT > IRC: Marsu Expert in quantum bogodynamics I have been having a similar problem.My machine crashes immediately after booting.Could this be attributed to bug in fsck.If yes,how ?? :-) To explain in detail : After completion of boot process I get into my account.I then get my Workspace but my mouse fails to respond.Only solution I can think of right now is reboot again (This in turn corrupts some files in the process). I am in such a situation that I can't use <cmd> q to exit either. -Joisha ---------------------------------------------------------------------- -G.PRASHANTH JOISHA joisha@bodhi.esys.cwru.edu
From: joisha@bodhi.esys.cwru.edu (Prashanth Joisha) Newsgroups: comp.sys.next.bugs Subject: Is it bug in fsck again !!!! Date: 24 Oct 1993 20:49:11 GMT Organization: Case Western Reserve University, Cleveland, Ohio (USA) Message-ID: <2aepo7$q6@usenet.INS.CWRU.Edu> I have particular problem with my machine.This problem occurs after I reboot/boot the machine (intermitent problem ). The problem is follows : I get into my account after rebooting/booting my machine.I then get my workspace manager but my mouse fails to respond.I am now in such a situation that I can't logout using <cmd q>.This problem is on a intel m/c using an adaptec card.The solution I have right now is reboot the m/c which corrupts couple of files in the process. Sometime back Mr.Markus Wenzel reported a bug in fsck.Can this be attributed to the same problem. Regards, -Joisha -- NewsGrazer, a NeXTstep(tm) news reader, posting -- M>UQR=&8P7&%N<VE[7&9O;G1T8FQ<9C!<9FUO9&5R;B!#;W5R:65R.WT*7&UA M<F=L,3(P"EQM87)G<C$R,`I[7&-O;&]R=&)L.UQR960P7&=R965N,%QB;'5E M,#M]"EQP87)D7'1X,3$U,EQT>#(S,#1<='@S-#4V7'1X-#8P.%QT>#4W-C!< M='@V.3$R7'1X.#`V-%QT>#DR,39<='@Q,#,V.%QT>#$Q-3(P7&8P7&(P7&DP M7'5L;F]N95QF<S(T7&9C,%QC9C`@7`I)(&AA=F4@<&%R=&EC=6QA<B!P<F]B M;&5M('=I=&@@;7D@;6%C:&EN92Y4:&ES('!R;V)L96T@;V-C=7)S(&%F=&5R M($D@<F5B;V]T+V)O;W0@=&AE(&UA8VAI;F4@*&EN=&5R;6ET96YT('!R;V)L M96T@*2Y<"EP*5&AE('!R;V)L96T@:7,@9F]L;&]W<R`Z7`I<"@E)(&=E="!I M;G1O(&UY(&%C8V]U;G0@869T97(@<F5B;V]T:6YG+V)O;W1I;F<@;7D@;6%C M:&EN92Y)('1H96X@9V5T7`IM>2!W;W)K<W!A8V4@;6%N86=E<B!B=70@;7D@ M;6]U<V4@9F%I;',@=&\@<F5S<&]N9"Y)(&%M(&YO=R!I;B!S=6-H(&$@<VET M=6%T:6]N('1H870@22!C86XG="!L;V=O=70@=7-I;F<@/&-M9"!Q/BY4:&ES M('!R;V)L96T@:7,@;VX@82!I;G1E;"!M+V,@=7-I;F<@86X@861A<'1E8R!C M87)D+E1H92!S;VQU=&EO;B!)(&AA=F4@<FEG:'0@;F]W(&ES(')E8F]O="!T M:&4@;2]C('=H:6-H7`IC;W)R=7!T<R!C;W5P;&4@;V8@9FEL97,@:6X@=&AE M('!R;V-E<W,N7`H)4V]M971I;64@8F%C:R!-<BX*7&9C,5QC9C$@36%R:W5S M(%=E;GIE;`I<9F,P7&-F,"`@<F5P;W)T960@82!B=6<@:6X@9G-C:RY#86X@ M=&AI<R!B95P*871T<FEB=71E9"!T;R!T:&4@<V%M92!P<F]B;&5M+EP*7`I2 596=A<F1S+%P*7`HM2F]I<VAA"GT* `
Newsgroups: comp.sys.next.bugs From: martin@cube.han.de Subject: Re: NS/FIP corrupts Dos partition Message-ID: <1993Oct24.152717.404@cube.han.de> Organization: not organized References: <2a466h$1l6@male.EBay.Sun.COM> Date: Sun, 24 Oct 1993 15:27:17 GMT Ward Mullins (wardm@well.sf.ca.us) wrote: : dos and modify the partition, NS does *not* see the changes to the disk when : it is rebooted. Not only that, but it corrupts the FAT of the dos partition : and requires me to do a chkdsk in dos... : Has *anyone* seen this problem, and do you know what to do to get around it? well, something like that happened here two days ago. After I killed some files on my dos partion with NeXTStep it was corrupted. The system was unable to reboot under dos. Chkdsk did not help at all! Because I don©t want to reproduce this behaviour I am not in the position to call this a bug but it really seems to be one. Ciao, -Martin -- ====================================================== Martin Ortlepp Tel.: (49) 511 421278 Goettinger Chaussee 162 A Fax : (49) 511 814451 30459 Hannover email: martin@cube.han.de
Newsgroups: comp.sys.next.bugs From: next@lehre25.informatik.Uni-Bremen.DE (Kai Fuhrmeister) Subject: NS3.1 Installer + NS2.x Package = Bugs? Message-ID: <1993Oct25.133615.7625@informatik.uni-bremen.de> Sender: next@lehre25 (Kai Fuhrmeister) Organization: Universitaet Bremen Date: Mon, 25 Oct 1993 13:36:15 GMT Hi, I have got some trouble installing the "old" Mouse-X package under NEXTSTEP 3.1! (I had installed/deinstalled it under 2.1 several times without problems!) 1.) Installer asked me to install the package in "/Apps" . (I think, that should be ~/Apps or /LocalApps but NOT /Apps) 2.) Installer installed all files but no links! (e.g. /usr/bin/X11 or /usr/lib/X11) 3.) When I tried to deinstall the package one day later, Installer wasn't able to list the complete package contents. Installer checked: "/LocalApps/X" and deleted only this file. No Errors were reported. So I deleted all the other files with the WorkspaceManager. Does anybody know an explanation for this strange behaviour? Is the Installer of NS3.1 no more able to read (some) old packages? BTW.: Does somebody know the fixes to get Mouse-X X11R4 running under NS3.1? (I don't think "Get the X11R5-Version!" is the right fix.. ;-) ) - Kai ---------------------------------------------------------------------------- Kai Fuhrmeister next@lehre.informatik.uni-bremen.de Voltastr. 52 (PLEASE NO NEXTMAIL) 28357 Bremen GERMANY ---------------------------------------------------------------------------- "No, no, I am not an BETA-Tester, I've PAID for this OS!"
From: ctm@ardi.com Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP corrupts Dos partition Message-ID: <CFGLyx.EFC@cobra.cs.unm.edu> Date: 25 Oct 93 15:35:22 GMT Article-I.D.: cobra.CFGLyx.EFC References: <2a466h$1l6@male.EBay.Sun.COM> <1993Oct24.152717.404@cube.han.de> Sender: news@cobra.cs.unm.edu Organization: ARDI In article <1993Oct24.152717.404@cube.han.de> martin@cube.han.de writes: >Ward Mullins (wardm@well.sf.ca.us) wrote: >: dos and modify the partition, NS does *not* see the changes to the disk when >: it is rebooted. Not only that, but it corrupts the FAT of the dos partition >: and requires me to do a chkdsk in dos... >: Has *anyone* seen this problem, and do you know what to do to get around it? > >well, something like that happened here two days ago. After I killed >some files on my dos partion with NeXTStep it was corrupted. The system >was unable to >reboot under dos. Chkdsk did not help at all! > >Because I dont want to reproduce this behaviour I am not in the >position to call this a bug but it really seems to be one. As best as I can tell, if your DOS partition is > 64Mb, you're playing with fire. On a system over here, with an 80Mb DOS partition it was *trivial* to get NEXTSTEP to trash the DOS filesystem. I just had to have the disk failry full (70Mb full), and then run a disk optimizing program under DOS that would assure that all the free space was at the end of the parition and I'd find under NEXTSTEP that even with 10Mb free, NEXTSTEP would see 0MB free. *Please* do not tell me that this is the slop reserved for the Berkeley Fast Filesystem. It is not. The DOS filesystem is not the Berkeley Fast Filesystem. It is a bug. The really great thing though is not only are those blocks not available, if I then deleted some files under NEXTSTEP and added some new ones, the DOS filesystem would be corrupted. I suspect it would only happen if the files that I deleted happened to have allocation blocks that sat past the 64Mb mark. Some of the details above are speculation. I do not know for a fact that it is 64Mb that gives us trouble. I do know the trouble exists and that NeXT knows about it. I got the impression that it's *not* fixed in 3.2, but I don't know. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: Ralph_Jung@radical.com (Ralph Jung) Subject: Re: NS/FIP corrupts Dos partition Message-ID: <1993Oct25.205441.7002@radical2.radical.com> Sender: ralph@radical2.radical.com Organization: Radical System Solutions, Inc. References: <CFGLyx.EFC@cobra.cs.unm.edu> Distribution: usa Date: Mon, 25 Oct 1993 20:54:41 GMT In article <CFGLyx.EFC@cobra.cs.unm.edu> ctm@ardi.com writes: > > As best as I can tell, if your DOS partition is > 64Mb, you're playing > with fire. On a system over here, with an 80Mb DOS partition it was > *trivial* to get NEXTSTEP to trash the DOS filesystem. I just had to > have the disk failry full (70Mb full), and then run a disk optimizing > program under DOS that would assure that all the free space was at the > end of the parition and I'd find under NEXTSTEP that even with 10Mb > free, NEXTSTEP would see 0MB free. *Please* do not tell me that this > is the slop reserved for the Berkeley Fast Filesystem. It is not. The > DOS filesystem is not the Berkeley Fast Filesystem. It is a bug. The > really great thing though is not only are those blocks not available, > if I then deleted some files under NEXTSTEP and added some new ones, > the DOS filesystem would be corrupted. I suspect it would only happen > if the files that I deleted happened to have allocation blocks that sat > past the 64Mb mark. > > Some of the details above are speculation. I do not know for a fact > that it is 64Mb that gives us trouble. I do know the trouble exists > and that NeXT knows about it. I got the impression that it's *not* > fixed in 3.2, but I don't know. > There's a remark in the Release Notes or README file for Windows NT about NEXTSTEP using a "non-standard" way of doing something. I don't remember the exact wording and I don't have NT loaded at the moment. Anyone recall the details? -- Ralph Jung ( Ralph_Jung@Radical.Com ) Radical System Solutions, Inc. NeXTmail accepted rad~i~cal \'rad-i-kel\ adj. - marked by a considerable departure from the usual or traditional: EXTREME
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 25 Oct 1993 23:54:01 -0400 Organization: Next Announcements Message-ID: <2ai70m$787@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: ereidell@media.mit.edu (Evan A. Reidell) Subject: QUESTION: /private/vm/swapfile.front Message-ID: <1993Oct26.182537.20448@news.media.mit.edu> Sender: news@news.media.mit.edu (USENET News System) Organization: MIT Media Laboratory Distribution: usa Date: Tue, 26 Oct 1993 18:25:37 GMT Can anyone tell me anything interesting about this file? Like why it's 22Megs and growing each day, and I can't delete it even when I'm root?
Newsgroups: comp.sys.next.bugs From: nicolev@number_one.apana.org.au Subject: Re: NS/FIP corrupts Dos partition,... it's a feature Message-ID: <CFHs3I.12y@number_one.apana.org.au> Sender: nicolev@number_one.apana.org.au (Nicole A Vincent) Organization: Cafe Seacombe - the Virtual NeXTSTEP Cafe Downunder. References: <2a466h$1l6@male.EBay.Sun.COM> Date: Tue, 26 Oct 1993 06:45:17 GMT In article <2a466h$1l6@male.EBay.Sun.COM> wardm@well.sf.ca.us(Ward Mullins) writes: > I have a dos partition which I am attempting to access from NS/FIP. NS mounts > the partition correctly and I can see the files and filesystem, but when I boot > dos and modify the partition, NS does *not* see the changes to the disk when > it is rebooted. Not only that, but it corrupts the FAT of the dos partition > and requires me to do a chkdsk in dos... > > Has *anyone* seen this problem, and do you know what to do to get around it? > Why would anyone want to get around this so called "problem"? Corrupting the DOS partition is a feature not a bug :-) He, he he he ,.... (and off I go smirking to myself in a corner) Nicole --- ----------------------NeXTmail Accepted and preferred ---------------------- Nicole Vincent : nicolev@number_one.apana.org.au Melbourne Victoria AUSTRALIA It looked good-natured, she thought; Still it had very long claws and a great many teeth, so she felt it ought to be treated with respect.
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs Subject: Re: NETINFO failure on ethernet address Date: 26 Oct 1993 21:59:13 GMT Organization: University of Houston Message-ID: <2ak6jh$1ot@menudo.uh.edu> References: <1993Oct21.165316.3403@alw.nih.gov> In article <1993Oct21.165316.3403@alw.nih.gov> smith@nextone.niehs.nih.gov (Howard C. Smith) writes: # #Has anyone seen the following: # # We have a network with all black hardware, #now just attemplting to add the first intel box to the netinfo db. #When using HostManager.app and adding the correct ip_address and #en_address, during a save to domain operation I get an alert panel: # # Invalid ethernet address. # Aborting. # #Has anyone else seen this behaivior? Im positive the ip #and ethernet addresses are correct. We ARE doing subnetting. # #-- #Howard C. Smith #National Institute of Environmental Health Sciences #smith@nextone.niehs.nih.gov Make sure you leave out the leading zeros... If you have an address like this (for example): 00:00:A0:11:33:0e then you need to enter it like this: 0:0:a0:11:33:e -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 26 Oct 1993 22:15:44 GMT Organization: University of Houston Message-ID: <2ak7ig$52q@menudo.uh.edu> References: <2aep40$t00@usenet.INS.CWRU.Edu> In article <2aep40$t00@usenet.INS.CWRU.Edu> joisha@bodhi.esys.cwru.edu (Prashanth Joisha) writes: #In article <29ggqk$670@marsu.tynet.sub.org> mow@marsu.tynet.sub.org #(Markus Wenzel) writes: #> ivo@next.agsm.ucla.edu (Ivo Welch) writes: #> >I have posted exactly the same problem a few weeks ago. I have it #confirmed #> >from NeXT: ANY CRASH MAY FORCE YOU TO REFORMAT YOUR HARDDISK, IF YOU #ARE #> >UNLUCKY ENOUGH THAT THE FILE SYSTEM HAPPENS TO BE CORRUPTED IN A #PARTICULAR #> >WAY. The reason is a bug in fsck (which is likely not to be fixed in #3.2, #> >either). Usually, you can still boot in single-user mode, and backup #to #> >another disk (the inode is simply 1 corrupted file). #> #> Some wise gurus informed me about #> #> find / -inum [insert your favoured truncated inode] -exec rm "{}" \; #> #> would solve the problem. I never used find to search for inode numbers, #> so I didn't know this possibility. After deleting the file to the #> corresponding smashed inode, fsck should work for the rest of the file #> system. #> #> Regards, #> Markus. #> #> #> -- #> Markus Wenzel System administration, Consulting, #Networking #> mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / #Windows NT #> IRC: Marsu Expert in quantum bogodynamics # # # I have been having a similar problem.My machine crashes immediately #after booting.Could this be attributed to bug in fsck.If yes,how ?? :-) #To explain in detail : # After completion of boot process I get into my account.I then get #my Workspace but my mouse fails to respond.Only solution I can think of #right now is reboot again (This in turn corrupts some files in the #process). I am in such a situation that I can't use <cmd> q to exit #either. # How did you reboot the machine? It sounds like you pushed "reset" to reboot. This is not a DOS machine. It is unix. You don't "reboot" unix unless you want to have disk problems. You shutdown the system. You said your mouse didn't work but did your keyboard? If so, then you could have shut the system down cleanly by pressing right-alt and num-lock and then typing r to restart. If you consistantly press the "reset" button while you are in NS, you will have disk related problems that eventually fsck can't even repair... We have been running 30 Gateway2000 4DX2-66V PCs for months with only one disk related problem... And, yes, we do have then crash sometimes but without serious problems. Thes machines are used (and abused) heavily.... #-Joisha # #---------------------------------------------------------------------- # #-G.PRASHANTH JOISHA # joisha@bodhi.esys.cwru.edu -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
From: sears@tree.egr.uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs Subject: Re: NS/FIP corrupts Dos partition Date: 26 Oct 1993 22:21:08 GMT Organization: University of Houston Message-ID: <2ak7sk$603@menudo.uh.edu> References: <1993Oct24.152717.404@cube.han.de> In article <1993Oct24.152717.404@cube.han.de> martin@cube.han.de writes: #Ward Mullins (wardm@well.sf.ca.us) wrote: #: dos and modify the partition, NS does *not* see the changes to the disk when #: it is rebooted. Not only that, but it corrupts the FAT of the dos partition #: and requires me to do a chkdsk in dos... #: Has *anyone* seen this problem, and do you know what to do to get around it? # #well, something like that happened here two days ago. After I killed some files on my dos partion with NeXTStep it was corrupted. The system was unable to #reboot under dos. Chkdsk did not help at all! # #Because I don t want to reproduce this behaviour I am not in the position to call this a bug but it really seems to be one. # First, a question. Did you reformat the DOS partition after you installed NEXTSTEP? If no, then that is the problem. During the install you can set aside some space for DOS. What the install program does is simple repartitions the disk. So DOS still thinks that the entire disk is DOS, when in reality it isn't. And for some reason, if the partitions aren't reformatted, DOS doesn't pay any attention to the partition table and proceeds to corrupt everything when it needs large chunks of space... #Ciao, # #-Martin # # #-- #====================================================== #Martin Ortlepp Tel.: (49) 511 421278 #Goettinger Chaussee 162 A Fax : (49) 511 814451 #30459 Hannover email: martin@cube.han.de -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: QUESTION: /private/vm/swapfile.front Date: Tue, 26 Oct 1993 21:21:12 -0400 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Distribution: usa Message-ID: <cgnQo8S00WB2QFeWoa@andrew.cmu.edu> In-Reply-To: <1993Oct26.182537.20448@news.media.mit.edu> Excerpts from netnews.comp.sys.next.bugs: 26-Oct-93 QUESTION: /private/vm/swapf.. by Evan A. Reidell: > Can anyone tell me anything interesting about this file? > Like why it's 22Megs and growing each day, > and I can't delete it even when I'm root? You are very, very lucky that you didn't crash your machine in a truely grotesque fashion. A suggestion: it might be prudent to be a little more careful in the future about what you do as root, or you will end up with your machine not working and you being very unhappy... ;-) To answer your questions: The /private/vm subdirectory is where the virtual memory system stores pages of memory which have been swapped or paged out. If this file were deleted, your machine would have absolutely no way to recover, and it would promptly die at the next physical VM access. Anything you were doing at that point loses irrevocably. Your specific setup, which has the swapfile.front as a special mountpoint, uses the compressed swapping feature. (BTW, this was why you couldn't delete swapfile.front.) The file grows with time as a function of the VM activities on your system. It is an operating system misfeature (not a bug, per se) that the swapfile does not shrink. However, you can reboot your machine to reset the size of the swapfile down to the default of 16Mb. -Chuck Charles William Swiger -- CMU...*crunch*! | 1. You can't fly. ------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@mon.slip.andrew.cmu.edu | 4. Fire burns.
From: mitterma@fstgds06.tu-graz.ac.at (Ralf Mittermayr) Newsgroups: comp.sys.next.bugs Subject: Re: Major Problems with CD-CROM on NS 3.1 (Black) Date: 27 Oct 1993 10:47:49 GMT Organization: Graz University of Technology, Austria Message-ID: <2aljklINNnfr@fstgds15.tu-graz.ac.at> References: <1993Oct18.124204.1597@informatik.uni-bremen.de> Dirk Lehmann + Co (robocop@p232.informatik.Uni-Bremen.DE) wrote: : Last weekend a might have found a big bug in NS 3.1 while accessing my : CD-ROM(Apple150 = NeXT-drive). I only wanted to copy some data from a NOVA-CD : to my harddisk via the Workspace, but after a while my machine hang up, by : showing the busycursor. I could open the nmi-monitor but a reboot command : couldn't stop my machine. So I had to pull the wire out of the machine. The same : thing happend once again. The next time I tried to copy the files from the shell, : but there also was no success. Also tar (later gtar) were not able to build an : archive in my homedirectory. By double-clicking a rtfd-document on the CD , Edit : opened with the warning : Filesystem Error !, while the Workspace-Inspector for : rtfd-documents showed the correct content. In a shell I couldn't even list the : directory of some folders. : For those who want to backtrack the bug: : Copying from Workspace /NOVA/Apps/Communications/pcomm (I guess) -> ~ : ls -l in /NOVA/Demos/Graphics/Tesseract/Tesseract.app/English.lproj/Help/ : or : tar fcv ~/test.tar /NOVA/Demos/Graphics/Tesseract/Tesseract.app/English.lproj/Help : Hope this bug isn't in 3.2 ! : Dirk I have the same problem with a CD-News disk. (You don't have to pull the wire; Exit to the nmi-monitor and from there go to with ">monitor" to the NeXT-Monitor and do a Boot >b). 8-( I used some other disks and it looks as if NS3.1 seems to have problems with very deep file-structures or very long filenames. NS had no problem with Disks which have short filenames but also worked with its NS3.1 User-Disk, which I think is in a different CD-Format. This was never a problem in NS3.0!! Is there a workaround for this fatal bug in NS3.1?? Charly -- mitterma@fstgds06.tu-graz.ac.at
From: averill@bela.music.washington.edu (Ron Averill) Newsgroups: comp.sys.next.bugs Subject: Screen saver problem Date: 27 Oct 1993 16:43:05 GMT Organization: University of Washington Message-ID: <2am8ep$1ps@news.u.washington.edu> We have a screen saver program called VidLev which is called in LogoutHook, so when a user logs out, the screen saver automatically comes on. After installing system 3.1, we began having problems with the screens constantly going dark. We finally discovered that the VidLev program was being called over and over. As there were no problems with it before system 3.1, I assume that the new operating system is causing it not to work. My question is: does anyone have a suggestion for an alternative method of saving the screen? There is a screen saver which the operating system uses, but it doesn't kick in for about an hour and I haven't been able to find a way to make it start up sooner. Thanks for your help. Ron Averill University of Washington School of Music Computer Center raverill@u.washington.edu
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: Screen saver problem Date: Wed, 27 Oct 1993 17:19:53 -0400 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Message-ID: <ggniLty00WB74FBd4t@andrew.cmu.edu> In-Reply-To: <2am8ep$1ps@news.u.washington.edu> Excerpts from netnews.comp.sys.next.bugs: 27-Oct-93 Screen saver problem by Ron Averill@bela.music.w > My question is: does anyone have a suggestion for an alternative method > of saving the screen? There is a screen saver which the operating system > uses, but it doesn't kick in for about an hour and I haven't been able to > find a way to make it start up sooner. > > Thanks for your help. Here's some dwrites that will help do what you want: loginwindow MoveWhenIdle YES loginwindow MovementScale 2 loginwindow MovementTimeout 5 loginwindow TimeToDim 2040 To use them, do the dwrite as root. -Chuck Charles William Swiger -- CMU...*crunch*! | 1. You can't fly. ------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@mon.slip.andrew.cmu.edu | 4. Fire burns.
Newsgroups: comp.sys.next.bugs From: martin@cube.han.de Subject: Re: NS/FIP corrupts Dos partition Message-ID: <1993Oct27.073758.375@cube.han.de> Organization: not organized References: <CFGLyx.EFC@cobra.cs.unm.edu> <1993Oct25.205441.7002@radical2.radical.com> Distribution: usa Date: Wed, 27 Oct 1993 07:37:58 GMT Ralph Jung (Ralph_Jung@radical.com) wrote: : In article <CFGLyx.EFC@cobra.cs.unm.edu> ctm@ardi.com writes: : There's a remark in the Release Notes or README file for Windows NT about : NEXTSTEP using a "non-standard" way of doing something. I don't remember the : exact wording and I don't have NT loaded at the moment. Anyone recall the : details? I didn©t take a look at this file on the CD before. However, there is the following statement in it: [...] 10.0 Installing Windows NT over NextStep NextStep makes nonconventional changes to partition tables that can distort measurement of the amount of space remaining on a drive. If more space is reported than is actually available, installation can fail due to lack of space on the drive. [...] Ciao, -Martin -- ====================================================== Martin Ortlepp Tel.: (49) 511 421278 Goettinger Chaussee 162 A Fax : (49) 511 814451 30459 Hannover email: martin@cube.han.de
Newsgroups: comp.sys.next.bugs From: fozztexx@nvcc.uucp (Chris Osborn) Subject: Can no longer halt after upgrade to 3.1 Message-ID: <CFL47A.M0q@nvcc.uucp> Sender: news%nvcc.uucp@groucho.sonoma.edu Organization: Napa Valley College Date: Thu, 28 Oct 1993 01:59:32 GMT HELP! I decided to go ahead and upgrade my NeXT from 3.0 to 3.1, and now I can no longer halt! If I try to power off or halt, it gets pretty far, but never completely does, and *never* syncs the disk. I'm getting tired of having to break into the monitor and power off, and I'm really tired of having to fix the disk (I've lost a cople of files already). I've tried halting from inside a terminal, from the NMI, powering off with the power key, and a halt -p, and nothing works. HELP! -- Chris Osborn, Network Administrator Voice: 707 253 3130 Napa Valley College Fax: 707 253 3063 fozztexx%nvcc.uucp@groucho.sonoma.edu fozztexx@groucho.sonoma.edu NeXTMail ok at both
Newsgroups: comp.sys.next.software,comp.sys.next.bugs From: jhh@genesis5.physics.yale.edu (Jim Horne) Subject: Bug in MouseX? Message-ID: <1993Oct28.141805.18910@cs.yale.edu> Followup-To: comp.sys.next.software Sender: news@cs.yale.edu (Usenet News) Organization: Yale Physics Department Date: Thu, 28 Oct 1993 14:18:05 GMT I have a NeXTstation Turbo (ADB keyboard) running NeXTSTEP 3.0, and I installed MouseX version 2.3 over the weekend. I got it from foxtrot.ccmrc.ucsb.edu and just followed the instructions. It compiled fine and works almost perfectly. The problem is that in some text fields, the "a" key is interpreted as DELETE, and the delete key is ignored. For example, in the search field of xmosaic, and anywhere in the crossfire window. By random fiddling, I discovered a painful workaround: typing alt-a alt-a does give an "a". This is extremely annoying. The sole reason I installed MouseX was to run xmosaic (okay, I admit to wanting to play crossfire too), and this bug greatly decreases its functionality. Anyone know how to fix it? Also, how does one fool it into thinking you have a middle mouse button? The documentation seems to be silent. -- Jim Horne jhh@genesis5.physics.yale.edu "With stupidity the gods themselves struggle in vain." Friedrich von Schiller
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: Re: Is the connect() bug fixed in NS 3.2? Message-ID: <1993Oct29.021257.21387@csus.edu> Sender: news@csus.edu Organization: San Francisco State University References: <1993Oct26.074219.12964@csus.edu> Date: Fri, 29 Oct 1993 02:12:57 GMT I've received two responses from NeXT confirming that this is fixed in 3.2 so the connect() fails with ECONNREFUSED instead of locking up the machine. -=EPS=-
Newsgroups: comp.sys.next.bugs From: andy@research.canon.oz.au (Andy Newman) Subject: Re: Is the connect() bug fixed in NS 3.2? Message-ID: <CFn1xr.KwB@research.canon.oz.au> Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia References: <1993Oct26.074219.12964@csus.edu> Date: Fri, 29 Oct 1993 03:05:51 GMT You'll be glad to now that the program also hosed my SparcStation running SunOS 4.1.2. -- Andy Newman (andy@research.canon.oz.au)
Newsgroups: comp.sys.next.bugs From: eps@futon.SFSU.EDU (Eric P. Scott) Subject: apparent race condition in 3.1 / workaround for telnetd Message-ID: <1993Oct29.093130.5714@csus.edu> Sender: news@csus.edu Organization: San Francisco State University Date: Fri, 29 Oct 1993 09:31:30 GMT Background: we recently upgraded some of our machines from NS 2.1 to NS 3.1 and received numerous "I can't telnet in from the network" complaints. Typical report: "I see the greeting banner and login: prompt, type my username, but never get a Password: prompt. Anything I type is echoed back. Half a minute later the connection closes." However, sometimes everything works without problem some of the time. Success rates varied from 10%-50%. rlogin did not exhibit the problem. (Note that we have many users dialing in to terminal servers that only support telnet, and only a minimal implementation at that.) Once a user got in, the session wouldn't croak unexpectedly. It was all or nothing. After several *dozen* hours of investigation (because f---ing NeXT doesn't make their source code available!), the problem now appears to result from a kernel bug not present in NS 2.1. NeXT has been shipping a known defective version of telnetd since 2.0. We'd replaced it with a slightly modified copy of the "91.03.25" release. Protocol traces revealed no difference between functional and nonfunctional sessions. Scrutiny of the telnetd and rlogind sources shined little light on the situation (other than their network code, which had already been cleared of suspicion). Each performed more or less the same steps, albeit not in the same order. The most obvious difference was that rlogind opened both the master and slave sides of its pty before fork()ing, and *recent* versions of telnetd deferred opening the slave side to the child process. This suggested a race condition, improper state propagation between pty and tty, or an uninitialized variable *in the kernel*. It still did not explain the observed behavior. Slowing the master side down seemed to have an effect. Inserting a brief sleep() in the parent process made the problem less likely to occur, but only when telnetd was run with -debug from a command line. It still failed miserably when launched from inetd. Later, someone discovered that he got in nearly all the time at 300 bps, but as his terminal speed was increased, the probability went down. This was consistent with previous observations that slowing down the master (it displays the banner from gettytab before paying attention to its child) made a difference. Then I thought about trying telnet with the -l option to pass a username though telnet subnegotiation. The first time, everything worked. The second time, I saw Password: Login incorrect login: The obvious implication here was that /bin/login was reading end-of-file. EOF to login: says "I want out," but EOF to Password: is treated as an incorrect password, and another login: prompt issued. But why didn't the connection immediately close? BUG #1 (which obscured what was really going on) Control-D typed to a login: prompt does not result in an immediate session drop. Characters input are echoed, line editing is performed, ^C has no effect, etc. Occurs with both telnetd (all versions) and rlogind under 3.1. Does not occur in 3.0 or previous releases. Cause: UNDOCUMENTED CHANGE to /bin/login in 3.1 to always sleep(20) when EOF received after login: prompt, presumably for misguided "security-related" reasons. This still didn't answer the question: where's the EOF coming from? Since /bin/login uses stdio, there was a fair chance something really strange was going on. I made a copy of the telnetd executable and used emacs to replace its /bin/login string with a path to EPS' Bogus Ersatz Login(tm). This program used read() instead of stdio. Reads weren't returning EOF. read() was FAILING with EIO! Sometimes it would do so forever, sometimes it would right itself after a while. At this point, fingers started pointing at the pty driver, or its interaction with the tty driver. We know this code had been massively raped for 3.1 to inflict POSIX braindamage, and only Intel users had received any sort of terminal driver fix. So I started printing out all sorts of state information--was the controlling terminal being set up any differently the times when things worked versus the times they didn't? At first, I couldn't find anything. What does it mean to get EIO on a pty? Well, there's a comment in the telnetd source about this. It says that on some systems it's possible for the master side to return EIO if the slave side isn't open. But the error is on the slave side, and the master side has to be open--it was opened first, and never closed. That can't be it. So, in desperation, I used Digital Librarian to find every place where EIO was mentioned. When using the new terminal driver, if a process which is not in the distinguished process group of its control termi- nal attempts to read from that terminal its process group is sent a SIGTTIN signal. This signal normally causes the members of that process group to stop. If, however, the pro- cess is ignoring SIGTTIN, has SIGTTIN blocked, or is in the middle of process creation using vfork(2)), the read will return -1 and set errno to EIO. That's clearly not applicable--since /bin/login performs a TIOCSETD to force its terminal into OTTYDISC. But just for the hell of it, I decided to print out getpgrp() and TIOCGPGRP's return. THEY WERE DIFFERENT. Except for those _few_ times when everything worked--then they were the same! So I tried the same test on a 2.1 system. The process groups *always* matched, and were *always* identical to login's pid. telnetd does a setpgrp(0, 0) to declare itself a process group leader. This corresponds to setpgrp() in traditional UNIX. I changed this to setpgrp(0, getpid()), which I expected to have no effect. WRONG! Suddenly, /bin/login was happy. I still can't explain what NeXT changed, or why my "fix" works. NeXT broke *something*, and their documentation clearly doesn't agree with their software. In the meantime, several hundred users can log in again (I've only seen login fail once since then, so while it may not be 100% perfect, it seems to be pretty close). I have no clue whether this is fixed in 3.2. Maybe one of these years we'll take most of our machines beyond 2.1/2.2. But I'm not holding my breath. In the meantime, we keep shelling out bucks for software releases we can't in good conscience install. ------- So far, 3.1 has NOT survived well against undergraduates, and brings some surprising new security problems :-( not seen under 2.1. I hope 3.2 is a *lot* better. Based on my experiences with 3.x, I've been making "strong no" recommendations to commercial firms asking my expert opinion on whether they should purchase several thousand copies of NEXTSTEP for their "mission critical" applications, and NeXT has done NOTHING to convince me that I should change this opinion, other than e-mail messages claiming that "[I'm] really going to like their next release." Stop feeding me BULLSHIT! If it's that much better--SEND ME A COPY! I'll judge for myself. All I'm seeing is NEXTSTEP's quality of workmanship steadily plummeting, nonexistent QA, no beta test program ... and NeXT DOES NOT SEEM TO CARE. Also, it appears that we'll be sticking with HP/UX on our PA-RISC machines for the forseeable future. The initial enthusiasm when NEXTSTEP for PA-RISC was announced has completely faded now. The lameness of the Intel port destroyed much of NeXT's credibility, and many people here feel that NeXT should forget about meeting artificial marketing deadlines and concentrate on making products that work--no matter how long it takes. Many students who'd been saving their money to purchase NS/FIP before the educational price goes up at the end of this month are now considering NetBSD instead for their home machines. It doesn't matter how many NEXTSTEP applications are out there, or how good they are, if NEXTSTEP itself remains a dysfunctional, unsupported, poorly documented, nonsecure product. I guess that's exactly what Microsoft wants to see. -=EPS=- -- "What's the best feature in NEXTSTEP 3.2?" "It now ships with SoftPC!" Gimme a break...
Newsgroups: comp.sys.next.bugs From: martin@cube.han.de Subject: Re: NS/FIP corrupts Dos partition Message-ID: <1993Oct28.073302.241@cube.han.de> Organization: not organized References: <1993Oct24.152717.404@cube.han.de> <2ak7sk$603@menudo.uh.edu> Date: Thu, 28 Oct 1993 07:33:02 GMT Paul S. Sears (sears@tree.egr.uh.edu) wrote: : First, a question. Did you reformat the DOS partition after you installed : NEXTSTEP? If no, then that is the problem. : During the install you can set aside some space for DOS. What the install : program does is simple repartitions the disk. So DOS still thinks that the : entire disk is DOS, when in reality it isn't. And for some reason, if the : partitions aren't reformatted, DOS doesn't pay any attention to the : partition table and proceeds to corrupt everything when it needs large : chunks of space... Well, this could be a good explanation for what has happened to users who used NeXTStep©s install program but I dont think that this is the problem here. I have two partitions on my disk: 300 MB for DOS and NT and 700 MB for NeXTStep. This has been done with (DOS-) fdisk. After that I installed NS on the second, non-foramtted area. So the install program didn©t make any changes to the partition table (at least I hope so!). Ciao, -Martin -- ====================================================== Martin Ortlepp Tel.: (49) 511 421278 Goettinger Chaussee 162 A Fax : (49) 511 814451 30459 Hannover email: martin@cube.han.de
From: rfschtkt%banruc60.bitnet@cc1.kuleuven.ac.be Newsgroups: comp.sys.next.bugs Subject: &((char*)pointertovoid): should the compiler refuse this? Date: 30 Oct 1993 07:19:58 -0500 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9310291517.AA03946@flexus> LS, If you receive this in duplicate (well, triplicate, with my first attempt that I think failed), I apologise. I am sending this to both comp.sys.next.bugs@magnus.acs.ohio-state.edu and comp-sys-next-bugs@cs.utexas.edu, in the assumption that the former is not functional (just to test that assumption). After the conversion from 3.0 to 3.1, the compiler flagged something that was previously accepted and that I still think is correct, as an error, refusing to generate a binary: NXGetMemoryBuffer( pNXStream,&((char*)stream_buf),&stream_length,&stream_maxlength); The error message is: invalid lvalue in unary `&' I declared stream_buf as ``void *stream_buf'', an instance variable. NXGetMemoryBuffer is declared in some system header file as: extern void NXGetMemoryBuffer(NXStream *s, char **addr, int *len, int *maxlen); I would think that the second argument should better be void **addr, because a string is more easily fetched from a stream using NXGets or what is it; now a programmer almost always has to use casting. But that's beside the issue here. More seriously: isn't the refusal of the compiler to process my code a bug (workaround: (char**)&stream_buf)? I'd like to verify this before including it in KBNS, the only public and comprehensive database of bugs with workarounds in NEXTSTEP (available by anonymous ftp from cs.orst.edu (and sonata.cc.purdue.edu, sometimes), currently 11.1)! This collection is a repository for the sort of knowledge that NeXT mostly chooses to refuse you to have, a purely personal initiative and in no way endorsed by NeXT, nor do I receive *any* sort of cooperation from them (if I'm repeating myself, it's only meant as a hint to change that!). So fetch it, use it, and send me reports about whatever is still missing (mostly stuff about DBKit), or a note about what you think of KBNS (if you think it stinks, I won't know unless you tell me). It's up to YOU! Raf Schietekat, RfSchtkt@banruc60.bitnet, Flanders, Belgium RfSchtkt%banruc60.bitnet@uunet.uu.net or so if the above does not work for you (real, i.e., with triangle in the Deliver button) NeXTmail preferred I can't reach sites with ! or % in their address, or ending in .at or .uucp PS: No non-NeXT vendor-specific hardware issues in KBNS!
From: bkr@drdhh.hanse.de (Bjoern Kriews) Newsgroups: comp.sys.next.bugs Subject: cat: not enough mem (Anybody seen this ?) Date: 30 Oct 1993 22:52:47 +0100 Organization: Digital Island Message-ID: <bkr.752017683@drdhh> Hi ! I just played around with a ~70MB file, trying to move it as a raw stream to tape: drdhh:bkr /private/spool # cat br.snd > /dev/nrst0 cat: write error: Not enough memory drdhh:bkr /private/spool # cat >>/dev/nrst0 blubber fasel ^D (went ok) drdhh:bkr /private/spool # mt rewind drdhh:bkr /private/spool # cat brothers.snd .sndgh$,DDDD... drdhh:bkr /private/spool # cat brothers.snd | cat >/dev/nrst0 ok, tape is streaming... Can anybody explain this to me ? Its a 16M machine, the swaphiwat set to 64M. vmstat appended. Mach Virtual Memory Statistics: (page size of 8192 bytes) Pages free: 39. Pages active: 981. Pages inactive: 565. Pages wired down: 340. "Translation faults": 2396130. Pages copy-on-write: 262955. Pages zero filled: 173114. Pages reactivated: 611285. Pageins: 112703. Pageouts: 23127. Object cache: 142351 hits of 153549 lookups (92% hit rate) Greetings & thanks for your time, -- Bjoern -- bkr@drdhh.hanse.de - Bjoern Kriews - Stormsweg 6 - D-2000 Hamburg 76 - FRG By definition, a properly functioning kernel doesn't allow user programs to make it crash unless they say "please". (Richard Stallman)
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: NS/FIP corrupts Dos partition Message-ID: <CFuC63.2Jy@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI References: <1993Oct24.152717.404@cube.han.de> <2ak7sk$603@menudo.uh.edu> <1993Oct28.073302.241@cube.han.de> Date: Tue, 2 Nov 1993 01:30:07 GMT In article <1993Oct28.073302.241@cube.han.de> martin@cube.han.de writes: >Paul S. Sears (sears@tree.egr.uh.edu) wrote: >: First, a question. Did you reformat the DOS partition after you installed >: NEXTSTEP? If no, then that is the problem. > >: During the install you can set aside some space for DOS. What the install >: program does is simple repartitions the disk. So DOS still thinks that the >: entire disk is DOS, when in reality it isn't. And for some reason, if the >: partitions aren't reformatted, DOS doesn't pay any attention to the >: partition table and proceeds to corrupt everything when it needs large >: chunks of space... > > >Well, this could be a good explanation for what has happened to users who used NeXTStep©s install program but I dont think that this is the problem here. > >I have two partitions on my disk: 300 MB for DOS and NT and 700 MB for NeXTStep. This has been done with (DOS-) fdisk. After that I installed NS on the second, non-foramtted area. So the install program didn©t make any changes to the partition table (at least I hope so!). There are definitely bugs associated with DOS partitions. I personally suspect that it can happen with any partition > ~64Mb, but I don't know for sure. I am not imagining this, and I know a fair amount about filesystem implementation and have looked carefully at our setup (80Mb DOS partition). --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.hardware,comp.sys.next.bugs From: cuilla@black_silk (Chris Cuilla) Subject: Booting NS/Intel Message-ID: <1993Nov2.214726.3276@il.us.swissbank.com> Sender: root@il.us.swissbank.com (Operator) Organization: Swiss Bank Corporation CM&T Division Date: Tue, 2 Nov 1993 21:47:26 GMT I have a NS/Intel machine...when I boot it...everything is fine, etc, etc. And I'm asked which mode I want to boot in (NS or DOS) (after a delay of a few seconds (if I don't respond) it automatically boots in DOS/Windows.) This happens everytime, even when I choose NS, the next time it does the same thing. I believe it should be booting in NS by default once I select NS. What am I doing wrong. Also, I'm asked to press "F1" to proceed each time (before I'm prompted for the OS of choice). Thoughts? -- Chris Cuilla chris@its.com --- Opinions voiced are my own and only my own and I defend to the death my right to deny I said anything. --------------------------------------------------------------------- "There's no such thing a as 'part-time' perfectionist." ---------------------------------------------------------------------
Newsgroups: comp.sys.next.bugs From: fabien@free.fdn.org (Fabien Roy) Subject: Re: cat: not enough mem (Anybody seen this ?) Message-ID: <1993Nov2.235500.16156@free.fdn.org> Sender: news@free.fdn.org Organization: Fabien Roy Electronic Engineering (F.R.E.E.) - Paris, France. References: <bkr.752017683@drdhh> Date: Tue, 2 Nov 1993 23:55:00 GMT In article <bkr.752017683@drdhh> bkr@drdhh.hanse.de (Bjoern Kriews) writes: > Hi ! > > I just played around with a ~70MB file, trying to move it > as a raw stream to tape: > > drdhh:bkr /private/spool # cat br.snd > /dev/nrst0 > cat: write error: Not enough memory > > drdhh:bkr /private/spool # cat >>/dev/nrst0 > blubber > fasel > ^D (went ok) > drdhh:bkr /private/spool # mt rewind > drdhh:bkr /private/spool # cat brothers.snd > ..sndgh$,DDDD... > drdhh:bkr /private/spool # cat brothers.snd | cat >/dev/nrst0 > ok, tape is streaming... > > Can anybody explain this to me ? Its a 16M machine, the swaphiwat set to > 64M. vmstat appended. > > Mach Virtual Memory Statistics: (page size of 8192 bytes) > Pages free: 39. > Pages active: 981. > Pages inactive: 565. > Pages wired down: 340. > "Translation faults": 2396130. > Pages copy-on-write: 262955. > Pages zero filled: 173114. > Pages reactivated: 611285. > Pageins: 112703. > Pageouts: 23127. > Object cache: 142351 hits of 153549 lookups (92% hit rate) > > > Greetings & thanks for your time, > -- Bjoern > -- > bkr@drdhh.hanse.de - Bjoern Kriews - Stormsweg 6 - D-2000 Hamburg 76 - FRG > By definition, a properly functioning kernel doesn't allow user programs to > make it crash unless they say "please". (Richard Stallman) Did you try dd <br.snd >/dev/nrst0 bs=20b Fabien-- --------------------------------------------------------------------- Reply to Fabien_Roy@free.fdn.org or if your mail bounce back to Fabien_Roy@free.fr. (uucp road-map problem) NextMails accepted Fabien Roy Electronic Engineering (Former NeXT Distributor) ----------> Almost killed by NEXT when they stop the hardware. ---------------> Still alive with NEXTSTEP FOR INTEL PROCESSORS.
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: NEXTSTEP or Motorola bug? Message-ID: <CFwAvs.HxM@cobra.cs.unm.edu> Sender: news@cobra.cs.unm.edu Organization: ARDI Date: Wed, 3 Nov 1993 02:57:30 GMT Dear bargain bug hunters and eaters of fine mexican foods, This is an interesting bug. It could be as trivial as a bug in the 68040 documentation, or as severe as an exceedingly rare, but very dangerous bug in NEXTSTEP. I don't know. I only have one '040 to play with, and it's running NS 3.1. This letter will not make sense to you who do not diddle bits, but to those of you without lives of your own, I'd *love* to know what happens on your machines, especially if running NS 2.x or NS 3.2 or NS 3.0. Apparently "move16"s can fail to transfer 16 bytes at a time if the addresses that are being used aren't 16 bit aligned. The documentation *I* have (M68000PM/AD (c) 1989) has an example on page 2-120 that strongly suggests that unaligned addresses are silently aligned and then have the same net effect as if the aligned accesses are used. Why would we notice such a bizarre discrepency? It turns out that one of the ways we test our synthetic CPU is to feed a bunch (and I'm talking about a *BIG* bunch) of instructions to our synthetic CPU while feeding the same instructions to the 68040 directly. We then compare results. It's not clear whether or not we had the move16 problems under NS 3.1, but we definitely have them now. Our synthetic CPU *always* transfers 16 bytes, but as my test below shows, under NS 3.1, sometimes only 12, 8 or 4 bytes are transferred. I haven't reported this to NEXT because it could just be an '040 anamoly (like what happens when you execute "unlk a7"--don't do it before backing your system up). However, it could be that NEXTSTEP's bus handling code botches a rare type of access under peculiar circumstances. If this is true, finding and fixing this bug *could* fix mystery NEXTSTEP bugs that would be exceedingly unlikely to be fixed otherwise. Here's a demo program: #include <stdio.h> #include <string.h> void dump(unsigned char *p) { int i; unsigned char c; unsigned short us; p = (unsigned char *) ((long) p & ~0xFL); us = 0; for (i = 16; --i >= 0;) { us <<= 1; switch ((c = *p++)) { case 0: break; case 0xFF: us |= 1; break; default: fprintf(stderr, "Unexpected char 0x%x\n", c); break; } } printf("0x%04x,\n", us); } int main(int argc, char *argv[]) { unsigned char source[512], dest[512], *p1, *p2, *unused1, *unused2; int i, j; memset(source, 0xFF, sizeof(source)); for (p1 = (unsigned char *) ((long) (source + 15) & ~0xFL), i = 16; --i >= 0; ++p1) for (p2 = (unsigned char *) ((long) (dest + 15) & ~0xFL), j = 16; --j >= 0; ++p2) { memset(dest, 0x00, sizeof(dest)); asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : "0" (p1), "1" (p2)); dump(p2); } return 0; } If you compile and run this program, you'll probably get 256 lines of: 0xffff, since I'm using hex notation to show which of the sixteen bytes that *should* have been transferred actually were transferred. 256 lines of 0xffff, is correct. Here's where it gets fun. Put a breakpoint on the move16 instruction (line 39) and then run the program and use the "c" (continue) command to run through the loop a few times. If your system is like mine, you'll get output like this: (gdb) b 39 Breakpoint 1 at 0x3e76: move16.c:39. (gdb) r Starting program: /usr/local2/dirs/ctm/tmp/move16 Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) c Continuing. 0xffff, Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) Continuing. 0x7777, Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) Continuing. 0x3333, Notice that the first access is aligned and we get "0xffff," as output, but then we get "0x7777," and "0x3333,". What gives? I don't know and my wife's making me Chile Rellenos for dinner, so I gotta run. If *you* know for sure what's going on and are one of the first to clue me in, I'll get her to make Chile Rellenos for you as well, but you gotta pick them up yourself. --Cliff ctm@ardi.com
From: schmolzi@janus.theo-physik.uni-kiel.de (Klaus Schmoltzi) Newsgroups: comp.sys.next.bugs Subject: Re: Booting NS/Intel Date: 3 Nov 1993 09:20:51 GMT Organization: Department of Theoretical Physics, University of Kiel, Germany Message-ID: <2b7t5j$32a@solid.theo-physik.uni-kiel.de> References: <1993Nov2.214726.3276@il.us.swissbank.com> In article <1993Nov2.214726.3276@il.us.swissbank.com> cuilla@black_silk (Chris Cuilla) writes: > I have a NS/Intel machine...when I boot it...everything is fine, etc, etc. > And I'm asked which mode I want to boot in (NS or DOS) (after a delay of a > few seconds (if I don't respond) it automatically boots in DOS/Windows.) > > This happens everytime, even when I choose NS, the next time it does the > same thing. I believe it should be booting in NS by default once I select > NS. What am I doing wrong. This is only a suggestion: Maybe your activated partition is DOS? Then you should change this under DOS with the fdisk program. Choose Nextstep partition to be activated. -:) > Also, I'm asked to press "F1" to proceed each time (before I'm prompted > for the OS of choice). ? more details about the CMOS settings??
From: joisha@bodhi.esys.cwru.edu (Prashanth Joisha) Newsgroups: comp.sys.next.bugs Subject: Re: Severe bug in fsck Date: 3 Nov 1993 16:45:37 GMT Organization: Case Western Reserve University, Cleveland, Ohio (USA) Message-ID: <2b8n7h$roj@usenet.INS.CWRU.Edu> In article <2aep40$t00@usenet.INS.CWRU.Edu> joisha@bodhi.esys.cwru.edu (Prashanth Joisha) writes: #In article <29ggqk$670@marsu.tynet.sub.org> mow@marsu.tynet.sub.org #(Markus Wenzel) writes: #> ivo@next.agsm.ucla.edu (Ivo Welch) writes: #> >I have posted exactly the same problem a few weeks ago. I have it #confirmed #> >from NeXT: ANY CRASH MAY FORCE YOU TO REFORMAT YOUR HARDDISK, IF YOU #ARE #> >UNLUCKY ENOUGH THAT THE FILE SYSTEM HAPPENS TO BE CORRUPTED IN A #PARTICULAR #> >WAY. The reason is a bug in fsck (which is likely not to be fixed in #3.2, #> >either). Usually, you can still boot in single-user mode, and backup #to #> >another disk (the inode is simply 1 corrupted file). #> #> Some wise gurus informed me about #> #> find / -inum [insert your favoured truncated inode] -exec rm "{}" \; #> #> would solve the problem. I never used find to search for inode numbers, #> so I didn't know this possibility. After deleting the file to the #> corresponding smashed inode, fsck should work for the rest of the file #> system. #> #> Regards, #> Markus. #> #> #> -- #> Markus Wenzel System administration, Consulting, >>#Networking >>#> mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / #Windows NT #> IRC: Marsu Expert in quantum bogodynamics # # # I have been having a similar problem.My machine crashes immediately #after booting.Could this be attributed to bug in fsck.If yes,how ?? :-) #To explain in detail : # After completion of boot process I get into my account.I then get #my Workspace but my mouse fails to respond.Only solution I can think of #right now is reboot again (This in turn corrupts some files in the #process). I am in such a situation that I can't use <cmd> q to exit #either. # >>How did you reboot the machine? It sounds like you pushed "reset" to >>reboot. This is not a DOS machine. It is unix. You don't "reboot" unix >>unless you want to have disk problems. You shutdown the system. >>You said your mouse didn't work but did your keyboard? If so, then you >>could have shut the system down cleanly by pressing right-alt and num-lock >>and then typing r to restart. >>If you consistantly press the "reset" button while you are in NS, you will >>have disk related problems that eventually fsck can't even repair... >>We have been running 30 Gateway2000 4DX2-66V PCs for months with only one >>disk related problem... And, yes, we do have then crash sometimes but >>without serious problems. Thes machines are used (and abused) heavily.... #-Joisha # #---------------------------------------------------------------------- # #-G.PRASHANTH JOISHA # joisha@bodhi.esys.cwru.edu -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime." As I mentioned earlier ,I am in such a situation that 1>> I can't type anything because Terminal.app has not been launched as yet. 2>> Mouse does not respond (Connection is fine to the serial port) 3>> <cmd> Tilde "r" (i.e. right-alt,num lock and "r" ) does not work neither can I halt the system. 4>> <cmd> q does not work either. This leaves me with no other choice but to reboot the system.Yes,in this process some of the files get corrupted. This problem is on the white box( intel 486,33MHz m/c). Any suggestions ... Regards, G.Prashanth Joisha (joisha@bodhi.esys.cwru.edu)
From: jklinke@aeon.UCSD.EDU (Jochen Klinke) Newsgroups: comp.sys.next.bugs Subject: wrong partition sizes under NSFIP and DOS Date: 3 Nov 1993 12:28:20 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311031828.AA03467@aeon.UCSD.EDU> The following problems have occurred on a NSFIP platform: I installed NSFIP on a 330MB IDE hard disk using 120MB for the DOS partition and 210MB for NSFIP User software. As suggested, I reformatted the DOS partition after installing NS. But while fdisk under DOS shows the correct partition sizes for both NS and DOS partition, the DOS format command went on formatting a 170MB partition. This is also what DOS's chkdsk and UNIX's df now show. Actually this was the DOS partition size I chose in an earlier attempt to install NSFIP. I am afraid that by not having correct information about the remaining disk space on the DOS partition, I will overwrite part of the NS partition. How can I fix this? Also, when I use tar to back up data (~50MB/archive) on a DAT drive from a NeXTcube and read it back on the DOS partition of a NSFIP PC, the File Viewer there claims that the archive is twice as big (~100MB). I know for sure that the archive is ~50MB. Why is this? Any help appreciated, Jochen Jochen Klinke Scripps Institution of Oceanography PORD 0230 La Jolla, CA 92093-0230 E-mail: jklinke@ucsd.edu
From: richard@cicero.jpl.nasa.gov ( Richard Weidner) Newsgroups: comp.sys.next.bugs Subject: Bug in mach_traps.h in OS3.1 Date: 3 Nov 1993 19:57:15 GMT Organization: Image Analysis Systems Group, JPL Distribution: usa Message-ID: <2b92er$3qq@elroy.jpl.nasa.gov> I found an error in /NextDeveloper/Headers/mach/mach_traps.h. Line 75 gives an error when compiled. task_t (task_self)(void); task_self is a macro and neither cc++ or g++ accept this line as written. It does work if you just comment it out. /*task_t (task_self)(void); */
From: bakker@cyclon.aoml.erl.gov (Cary Bakker) Newsgroups: comp.sys.next.bugs Subject: Slab crashed in a really weird way.... Why? Date: 3 Nov 1993 18:45:48 GMT Organization: U.S. Department of Commerce, NOAA/AOML Message-ID: <2b8u8s$jgg@wave.aoml.erl.gov> I was working on a slab yesterday, and it gave me the spinning disk for a while whenever I went to do anything. Eventually it would complete the task. The strange stuff started when I went to log out. I clicked the log out button, and eventually it took effect (I saw it light up), and the Workspace manager disappeared. The other apps remained !!! ??? All of the apps that were running (hidden or not) were still there and working as usual. I was able to click on Mail.app (hidden in the dock) and continue running Mail, hide it, continue again, etc... I was unable to start apps that were not running, and this seems normal if the workspace app is gone. But why were the other apps there? I rebooted from the terminal app, and the system came back up and appears to be running normally... The only thing I did out of the ordinary was to test the command posted to a c.s.n. newsgroup on how to eject a floppy from the command line. I think it was: /etc/disk -e /dev/rfd0a I think I had to be root, but I can't remember. Could this have had something to do with it???? Does *ANYONE* have any idea what happened? thanks in advance, Cary -- ------------------------------------------------------------------------- Cary A. Bakker | Music is the pleasure the human soul C.S. Major | experiences from counting without FLorida International University | being aware that it is counting... NeXT Programmer | NOAA/AOML | -- Gottfried W. Leibniz
From: mycroft@colourbox.utexas.edu (Alex Currier) Newsgroups: comp.sys.next.bugs Subject: Re: Slab crashed in a really weird way.... Why? Date: 3 Nov 1993 23:54:56 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <2b9gcg$96i@geraldo.cc.utexas.edu> References: <2b8u8s$jgg@wave.aoml.erl.gov> In article <2b8u8s$jgg@wave.aoml.erl.gov> bakker@cyclon.aoml.erl.gov (Cary Bakker) writes: > The strange stuff started when I went to log out. I clicked the log out > button, and eventually it took effect (I saw it light up), and the > Workspace manager disappeared. The other apps remained !!! ??? It would appear you crashed the Workspace Manager. I've done that quite a few times, all other active apps can be used but no new dock items can be opened and the Workspace menu and file brouser (Inspector, Console, Process Monitor) disappear. Usually whan that happens I get a dialogue box stating that the Workspace is crashed and I should save work in other active apps before logging out. I've never seen it happen where this notice did not appear. -- ============================================================================== Alex Currier | mycroft@ccwf.cc.utexas.edu | Time is just one damn thing after another. NeXTmail capable! | ==============================================================================
Newsgroups: comp.sys.next.bugs,comp.sys.next.software From: twilson@risc.uni-linz.ac.at (Todd Wilson) Subject: Active.mbox corruption? Swapfile explosion? Message-ID: <CFz62n.565@risc.uni-linz.ac.at> Sender: netnews@risc.uni-linz.ac.at (Netnews SW Account) Organization: RISC Linz Date: Thu, 4 Nov 1993 16:06:23 GMT It's happened to me twice, now, and I'd like to see if anyone knows about it. The problem is that somehow my Active.mbox becomes corrupted, and because of this Mail.app won't start up. It took some time to figure out that if I simply moved Mailboxes/* to, say, Mailboxes.old/*, then Mail.app _would_ start up and create Mailboxes/Active.mbox/* for me, and I could then open my various mailboxes in Mailboxes.old. All of these mailboxes would open fine, except for Active.mbox, which caused Mail.app to crash immediately whenever I tried to open it. The only thing that happened between today, when I had the problem, and yesterday, when I didn't, was that I had to reboot my machine after getting NO SPACE ON HARD DISK messages due to, apparently, a swapfile that had grown out of control. The reboot reset the swapfile, and after that there was no space problem, but then the Mail problem appeared. Both times this happened to me only Active.mbox was corrupted. Also, it is possible that this swapfile problem has something to do with Mathematica, since I seem to recall that these problems occured after I did some computations with Mathematica, which I have done only rarely. But I'm not sure about this at all. Ring any bells? Please mail me any responses, and I will post a summary. Thank you, --Todd Wilson
From: mycroft@colourbox.utexas.edu (Alex Currier) Newsgroups: comp.sys.next.bugs Subject: ImagePortfolio, McFilter, ImageViewer, and swapfile... Date: 4 Nov 1993 20:17:10 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <2bbo06$b1l@geraldo.cc.utexas.edu> Yesterday I was using ImagePortfolio to catalogue a list of 180+ jpgs and gifs. I am using the McFilter service (which uses the decoder in ImageViewer) to allow ImagePortfolio to include JPGs in it's activities. I dropped the entire 180 images into the ImagePortfolio window and switched it to the back while it did it's thing. After about 20 minutes of continuous disk access I switched it back to the front and about 45 images had been thumbnailed. Then I noticed I had only 31MB of free space on my drive (which normally has 182MB of free space on it). I had swapped out 150MB and it was fast approaching the end of my drive. I killed ImagePortfolio and rebooted to get my space back. My question is this... who is at fault here? Is NeXTSTEP not letting the swapfile shrink or is one of the image manipulation apps decoding these jpgs and gifs into memory and leaving them there? I know this shouldn't require that much memory. I've done similar work on a Mac with 8MB of RAM without any problem. Somewhere something is wrong. These files should be decompressed into RAM, scaled down to thumbnail size and either held in RAM at a reduced size or written to disk. I shouldn't have to have five hundred megs of memory space to thumbnail 180 images. -- ============================================================================== Alex Currier | mycroft@ccwf.cc.utexas.edu | Time is just one damn thing after another. NeXTmail capable! | ==============================================================================
From: rfschtkt%banruc60.bitnet@cc1.kuleuven.ac.be Newsgroups: comp.std.c,comp.sys.next.bugs Subject: SUMMARY: &((char*)pointertovoid): should the compiler refuse this? Date: 4 Nov 1993 18:18:31 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311041029.AA06385@flexus> LS, Thanks to Peter Kron <pkron@corona.com> (who got part of the answer and also suggested I'd try other compilers, but I'm too chauvinistic to do that :-) ), to gah@cco.caltech.edu (Geln A. Herrmannsfeldt) (who pointed me to comp.std.c), and to tom@basil.icce.rug.nl (Tom R.Hageman) (who explained the law to me). >>>>> I'm the administrator of KBNS, if you're wondering. KBNS.11.2.018 Something with & of a cast expression, that changed from 3.0 to 3.1 (but I can't decide how to classify this), relevant legislation pointed out by Tom_Hageman K&R II states (A7.5) that an expression with a cast isn't (or ``doesn't have''?) an lvalue, and (A7.4.2) that the operand of & has to be (``have''?) an lvalue. I've used &((char*)stream_buf) as an argument to a function that requires a char** argument, and this compiled cleanly before 3.1, but in 3.1 this was flagged as an error and no object file was produced. Workaround: (char**)&stream_buf. Now, there are two ways to see this. Either the compiler was overly permissive before 3.1 (question if you're still running 3.0: did it notice this if the flag -pedantic was used?), or the compiler is now overly restrictive (I still like my original solution better, and I think that, without the -pedantic flag, the compiler should at most give a warning). Tom_Hageman agreed that this should be warning rather than an error, and illustrated that by the fact that the following is allowed by the compiler (not verified) even though K&R II states (A7.3.4) that the operand of a postfix ++ or -- has to be (``have''?) an lvalue: char *lp; ... ((int *) lp)++; <<<<< To the comp.std.c people: this is about NEXTSTEP's GNU cc, and if you have anything to say about this please *e-mail* to me as well. Raf Schietekat, RfSchtkt@banruc60.bitnet, Flanders, Belgium RfSchtkt%banruc60.bitnet@uunet.uu.net or so if the above does not work for you (real, i.e., with triangle in the Deliver button) NeXTmail preferred I can't reach sites with ! or % in their address, or ending in .at or .uucp PS: To postmaster@magnus.acs.ohio-state.edu and others who might be able to corroborate or have other experience: twice before have I tried comp.sys.next.bugs@magnus.acs.ohio-state.edu, but the message didn't get through but I received no diagnostic message of any kind. Maybe it is the format with periods before the @ (my mailhost imposes a lot of restrictions like that on me), but I normally get error mail for that.
From: diamond@jit.dec.com (Norman Diamond) Newsgroups: comp.std.c,comp.sys.next.bugs Subject: Re: SUMMARY: &((char*)pointertovoid): should the compiler refuse this? Date: 5 Nov 1993 00:57:45 GMT Organization: Digital Equipment Corporation Japan , Tokyo Message-ID: <2bc8e9INNn2u@usenet.pa.dec.com> References: <9311041029.AA06385@flexus> In article <9311041029.AA06385@flexus> RfSchtkt%banruc60.bitnet@cc1.kuleuven.ac.be writes: >K&R II states (A7.5) that an expression with a cast isn't (or ``doesn't >have''?) an lvalue, The result of a cast expression isn't an lvalue. (If a cast is contained in a sub-expression of some larger expression, then the characteristics of the larger expression depend on its operator, though the cast sub-expression still isn't an lvalue.) >and (A7.4.2) that the operand of & has to be (``have''?) an lvalue. The operand of unary & has to be an lvalue or a function designator. >Either the compiler was overly permissive before 3.1 It was. So what? >Tom_Hageman agreed that this should be warning rather than an error, The standard doesn't care. The implementation must issue a diagnostic, but it can proceed to execute the program or to delete all your files or to just exit, or anything else, as long as it issues a diagnostic. >the following is allowed by the compiler [...] ((int *) lp)++; If the compiler issued a diagnostic, no problem. If the compiler didn't issue a diagnostic, then it's not a conforming C implementation. >even though K&R II states (A7.3.4) that the operand of a postfix ++ >or -- has to be (``have''?) an lvalue: The operand of ++ must be an lvalue. -- << If this were the company's opinion, I would not be allowed to post it. >> A program in conformance will not tend to stay in conformance, because even if it doesn't change, the standard will. Force = program size * destruction. Every technical corrigendum is met by an equally troublesome new defect report.
From: rfschtkt%banruc60.bitnet@cc1.kuleuven.ac.be Newsgroups: comp.sys.next.bugs Subject: Re: Active.mbox corruption? Swapfile explosion? Date: 5 Nov 1993 16:56:59 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311052203.AA01447@flexus> LS, This is described in KBNS.00.0.082_o3.0o, KBNS.00.0.083_o3.0o, KBNS.10.2.015_o3.0o, KBNS.10.3.009_o3.0o (well, I ought to renumber that because they're all in the same paragraph), including the solution (which *does* preserve the present contents of the offending .mbox). KBNS can be obtained from cs.orst.edu. Use it! Raf Schietekat, RfSchtkt@banruc60.bitnet, Flanders, Belgium RfSchtkt%banruc60.bitnet@uunet.uu.net or so if the above does not work for you (real, i.e., with triangle in the Deliver button) NeXTmail preferred I can't reach sites with ! or % in their address, or ending in .at or .uucp
From: rfschtkt%banruc60.bitnet@cc1.kuleuven.ac.be Newsgroups: comp.sys.next.bugs Subject: SUMMARY (bis): &((char*)pointertovoid): should the compiler refuse this Date: 5 Nov 1993 16:57:05 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311052230.AA01514@flexus> LS, This ought to be a bit more to the liking of those who responded (thanks): >>>>> KBNS.11.2.018 Something with &/++/-- of a cast expression, that changed for & from 3.0 to 3.1, relevant legislation pointed out by Tom_Hageman K&R II states (A7.5) that a cast expression isn't an lvalue, and (A7.4.2) that the operand of & has to be an lvalue or a function. I've used &((char*)stream_buf) as an argument to a function that requires a char** argument, and this compiled cleanly before 3.1, but in 3.1 this was flagged as an error and no object file was produced. Workaround: (char**)&stream_buf. Now, there are two ways to see this. Either the compiler was overly permissive before 3.1 (question if you're still running 3.0: did it notice this if the flag -pedantic was used?), or the compiler is now overly restrictive (I think that, without the -pedantic flag, and for simple conversions like this, the compiler should just give a warning). Tom_Hageman agreed that this should be a warning rather than an error, and illustrated that by the fact that the following is allowed by the compiler (not verified) even though K&R II states (A7.3.4) that the operand of a postfix ++ or -- has to be an lvalue (just as with &): char *lp; ... ((int *) lp)++; <<<<< My ``overly permissive'': with a warning before, the compilation wouldn't have failed now, and ordinary C would have one less porting hurdle. (That thing about ``delete all your files'' (Norman Diamond) is hopefully a joke...) Raf Schietekat, RfSchtkt@banruc60.bitnet, Flanders, Belgium RfSchtkt%banruc60.bitnet@uunet.uu.net or so if the above does not work for you (real, i.e., with triangle in the Deliver button) NeXTmail preferred I can't reach sites with ! or % in their address, or ending in .at or .uucp
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: rawyatt@netcom.com (Robert Wyatt) Subject: Need help with addresses file in NEXTSTEP 3.0 Message-ID: <rawyattCG5ssJ.3zK@netcom.com> Organization: Netcom Online Communications Services (408-241-9760 login: guest) Date: Mon, 8 Nov 1993 06:02:42 GMT I am posting this to both sysadmin and bugs groups. Either the problem is my inability to understand NEXTSTEP, or a bug...I'll let the net decide... I wanted to create a shared addresses file for our network (ie: for faxing; we all fax to the same people!). NeXT never sent us a 3.0 User Guide when we upgraded (they said there weren't significant changes from the 2.0 guide). Anyway, I created an addresses file and put it in LocalLibrary, then linked the file to each user's Addresses folder (we are a small network of about 10 users). Each user is able to add addresses to the file, but the other users can't see them. Is there any reason addresses files can not be linked? Has anyone figured out how to do this (I'm sure this is a piece of cake for all experienced NEXTSTEPers!)? I would *greatly* appreciate any insight or assistance! Please reply to: rob%zeus.uucp@netcom.com I can receive NeXTmail at this address and it is my work address (I am posting from home). Thanks in advance to all kind helping souls! -Rob Wyatt
From: frank@atlas.physchem.chemie.uni-tuebingen.de (Frank Siegert) Newsgroups: comp.sys.next.bugs Subject: Bug in CDROM filesystem (ISO9660/RR)? Date: 8 Nov 1993 12:25:30 GMT Organization: IPC, University of Tuebingen, Germany Message-ID: <2bldrq$jui@klaus.physchem.chemie.uni-tuebingen.de> Keywords: ISO CDROM FILESYSTEM Today I encountered a strange problem. I mounted an ISO 9660/Rockridge Extensions CDROM and everything worked fine at first. However as I was browsing throu it Workspace became slower and slower as I descend the directory. In the directoy /SPRITE_0193/src/machserver/notes I double clicked on a file named "sendtimes.sprite". Edit came up telling me this file does not exist. I checked the permissions but it was readable for world. So I double clicked again on it and Edit told me again the same story BUT opened it this time! So I started a shell, changed dir to /SPRITE_0193/src/machserver/notes and did an ls: p2 12:21 [29] ls caller callsMach callsSched 00_TRANS.TBL callsDev callsNet callsSig andrew callsFs callsProc callsSync callee callsFsdm callsRpc callsSys No sendtimes.sprite anywhere... An ls -l told me much more: p2 12:21 [30] ls -l total 39 -rwxr-xr-x 1 frank 1743 Jan 9 1993 00_TRANS.TBL -rw-r--r-- 1 frank 1979 Dec 1 1992 README -rw-r--r-- 1 frank 1979 Dec 1 1992 README -rw-r--r-- 1 frank 2231 Nov 19 1992 andrew -rwxr-xr-x 1 frank 969 Sep 26 1990 callee -rwxr-xr-x 1 frank 783 Sep 26 1990 caller -rw-r--r-- 1 frank 44437 Jul 26 1991 callsDev -rw-r--r-- 1 frank 3360 Nov 17 1991 callsFs -rw-r--r-- 1 frank 4374 Oct 24 1990 callsFsdm -rw-r--r-- 1 frank 9575 Mar 31 1992 callsMach ... -rw-r--r-- 1 frank 7130 Jun 5 1992 sendtimes.mach -rw-r--r-- 1 frank 7130 Jun 5 1992 sendtimes.mach -rw-r--r-- 1 frank 7132 Jun 5 1992 sendtimes.sprite -rw-r--r-- 1 frank 7132 Jun 5 1992 sendtimes.sprite ... So I typed this p2 12:20 [46] more sendtimes.sprite sendtimes.sprite: No such file or directory p2 12:21 [47] more sendtimes.sprite sendtimes.sprite: No such file or directory p2 12:21 [48] more sendtimes.sprite sendtimes.sprite: No such file or directory p2 12:21 [49] ls -l total 39 ...[ls output deleted]... And suddenly, out of the blue.... p2 12:21 miranda[31] more sendtimes.sprite Rpc Send Test: N = 100 ...[more output deleted]... This CDROM works perfectly on a SUN. Am I missing somthing? Do I have to change something to read this CDROM? Is it the phase of the moon? Or is it a bug? Thanks Frank Siegert -- // God is real, unless declared integer ////////////////////////////
Newsgroups: comp.sys.next.bugs From: Atze (Alexander Spohr) Subject: Re: Major Problems with CD-CROM on NS 3.1 (Black) Message-ID: <1993Nov8.133744.513@dart.de> Sender: aspohr@dart.de Organization: d'ART Computersysteme GmbH References: <2aljklINNnfr@fstgds15.tu-graz.ac.at> Date: Mon, 8 Nov 93 13:37:44 GMT In article <2aljklINNnfr@fstgds15.tu-graz.ac.at> mitterma@fstgds06.tu-graz.ac.at (Ralf Mittermayr) writes: > Dirk Lehmann + Co (robocop@p232.informatik.Uni-Bremen.DE) wrote: > : Last weekend a might have found a big bug in NS 3.1 while accessing my > : CD-ROM(Apple150 = NeXT-drive). I only wanted to copy some data from a NOVA-CD [munch] > I used some other disks and it looks as if NS3.1 seems to have problems with very > deep file-structures or very long filenames. NS had no problem with Disks which > have short filenames but also worked with its NS3.1 User-Disk, which I think > is in a different CD-Format. > > This was never a problem in NS3.0!! This is not the whole truth, see below. And so the Story goes: I have a Toshiba 3401 and the Big Green CD. It is almost impossible to get things from it onto my HD. It works better if I use Terminal and "cp -R xxx" (sorry for not using tar). I have to retry several times to get an error free copy. However, most times the CD stops to be readable, i.e. you just see an ? as the Icon of directories. And if it gets worse my machine panics. I tried the CD on my machine (3.1 Black), on one friends (3.1 & _3.0_ cd-rom drivers Black) and on another friends (3.1 White). If anybody else has the same errors with the Big Green please e-mail me. I want to be shure that it is not my Disc which could just be corrupted. Atze -- Alexander Spohr, Hamburg, Germany Alexander_Spohr@dART.de (Mail ) Faces and faces (+49) 40 / 380 23-0 (Sound) See them and complain not (+49) 40 / 380 23-290 (Fax ) And am content with all
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 8 Nov 1993 14:55:59 -0500 Organization: Next Announcements Message-ID: <2bm88d$bq3@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
From: dave@softpac.com.au (Dave Thomas) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs,comp.sys.next.hardware Subject: AudiPro16 and Logitech Bus Mouse IRQ's Summary: Anybody got them working ? Keywords: AudioPro Bus Mouse Message-ID: <6M53sAoEBh107h@softpac.com.au> Date: Tue, 9 Nov 93 07:55:22 +1100 Organization: Softpac Pty Ltd Some guidance would be appreciated please.. We are testing the above. Can anyone give us some suggestions? DOS/Audio Spectrum16 is not flexible as to interupts, and will only allow interupts 5 and 7. At present, IRQ5 is used by the parrallel port and we are having difficulty changing this. Is NeXTStep able to work around this? How? It will not allow us to use IRQ5 for LPT1. What other fixed IRQ's (eg com ports) are built in? Also, what is the best setting for a Logitech Bus mouse? Any body got one working out there? Any gudance and/or feedback would be appreciated. Thanks in advance. Rgds dave t -- dave@softpac.com.au For NeXT Sales Service & Support Voice: +61 2 214-2692 FAX: +61 2 436-1336
Newsgroups: comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs From: mark@cyantic.com (Mark T. Dornfeld) Subject: NeXT Freezes Organization: CYANTIC Systems Date: Mon, 08 Nov 1993 22:41:13 GMT Message-ID: <1993Nov08.224113.11206@cyantic.com> Last week I posted this article: #We just upgraded two NS slabs to NS 3.1. On one of them we have been #experiencing a problem reading pages from a fax. A Postscript error is #encountered and the system crashes. Sometime last night, my Turbo "froze". #This morning, I couldn't halt or reboot the system, so I had to unplug it. #Everything seems fine, but the 3.1 upgrade seems to have introduced some #instability. #There were no console messages for the Turbo crash. #Is 3.1 less stable than 3.0? I have since discovered that the /usr/adm/daily maintenance shell script that runs at 4:00AM does a find on all mounted file systems to look for stale ".nfs*" files. The system crashed two out of four nights since I did the upgrade to 3.1. On those nights I left the Nova CD mounted in the CD drive and the time on the NeXT clock in the Dock was 4:01AM. I ran the find command manually and crashed the system. Find returns: BAD Status on the first three files it meets and then bombs. I guess this is a bug. Has anyone else had this problem? -- Mark T. Dornfeld, CYANTIC Systems Voice: (416) 234-9048 101 Subway Crescent Suite 2103 Facsimile: (416) 234-0477 Etobicoke, Ontario, M9B 6K4 CANADA Email: mark@cyantic.com
Newsgroups: comp.sys.next.bugs From: BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) Subject: German Keyboard Problem - "B"-Key ist undefined Message-ID: <CG9450.7xt@bernina.ethz.ch> Sender: news@bernina.ethz.ch (USENET News System) Organization: ETH a school stuck in a dead city Date: Wed, 10 Nov 1993 01:00:32 GMT Hi there I have installed NeXTStep for Intel with the US Keyboard setting, everything worked fine. I changed to the German Keyboard, which I am using, and suddenly the B-Key is undefinde, that means, I cannot type B at all, I can set it up again in Keyboard.App just as often as I want to.... is there any fix for this really annoying bug ? (It is not unique to m coputer, I've seen it before).... Thanx... Chris
Date: Mon, 8 Nov 1993 20:48:56 MET From: OCS@earn.cvut.cs Newsgroups: comp.sys.next.bugs Subject: Terminal.app bug? (3.1 release on Gateway 2000) Message-ID: <16C80123F3.OCS@earn.cvut.cs> Organization: VC CVUT Hi All, Sometimes launching of the Terminal locks the NEXTSTEP (3.1, evaluation kit). The lock occurs before Terminal is fully started. Whole system, including the mouse pointer, is freezed. I can recall the 'halt/restart' window with the combination Alt-NumLock, but 'h' or 'r' only close this window - system is neither halted nor restarted. The only solution is hardware reset; it's very unsatisfactory, as buffers are not flushed (once whole filesystem was corrupted and I had to reinstall NEXTSTEP!). No other application does this (at least since yet), only the Terminal. I had not count it exactly, but the probability of the lock seems to be about 2-5%. Is it known bug? Is there any action we can do to prevent the lock? Tomas Hurka DATA.25
From: zryx0376@awssg7.rus.uni-stuttgart.de (Markus Wenzel (Hiwi bei R.Rabenseifner)) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs,comp.sys.next.hardware Subject: Re: AudiPro16 and Logitech Bus Mouse IRQ's Date: 11 Nov 1993 08:55:43 GMT Organization: Visualization Group Comp.Center (RUS) U of Stuttgart, FRG Message-ID: <2bsumf$1evv@info2.rus.uni-stuttgart.de> References: <6M53sAoEBh107h@softpac.com.au> Keywords: AudioPro Bus Mouse In article <6M53sAoEBh107h@softpac.com.au> dave@softpac.com.au writes: >DOS/Audio Spectrum16 is not flexible as to interupts, and will only allow >interupts 5 and 7. At present, IRQ5 is used by the parrallel port and we are >having difficulty changing this. Is NeXTStep able to work around this? How? >It will not allow us to use IRQ5 for LPT1. What other fixed IRQ's (eg com >ports) are built in? > >Also, what is the best setting for a Logitech Bus mouse? Any body got one >working out there? I have a Logitech bus mouse installed at IRQ 5. LPT1 of course has to be set to IRQ 7, I cannot see why this should not be possible. However, you could go and try jumpering the bus mouse card to IRQ 2, which NS reports free on my system. Furthermore, I havo no problems configuring the ProAudio Spectrum 16 to IRQ 10,12,13,15 - choose whatever you want. I think 15 is best. Regards, Markus. -- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Expert in quantum bogodynamics
From: zryx0376@awssg7.rus.uni-stuttgart.de (Markus Wenzel (Hiwi bei R.Rabenseifner)) Newsgroups: comp.sys.next.bugs Subject: Re: German Keyboard Problem - "B"-Key ist undefined Date: 11 Nov 1993 08:57:53 GMT Organization: Visualization Group Comp.Center (RUS) U of Stuttgart, FRG Message-ID: <2bsuqh$12qg@info2.rus.uni-stuttgart.de> References: <CG9450.7xt@bernina.ethz.ch> In article <CG9450.7xt@bernina.ethz.ch> BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) writes: >Hi there > >I have installed NeXTStep for Intel with the US Keyboard setting, everything >worked fine. I changed to the German Keyboard, which I am using, and suddenly >the B-Key is undefinde, that means, I cannot type B at all, I can set it up >again in Keyboard.App just as often as I want to.... >is there any fix for this really annoying bug ? (It is not unique to m coputer, >I've seen it before).... ftp ftp.uni-stuttgart.de cd /pub/systems/next/i486/Keymaps mget * Regards, Markus. -- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Expert in quantum bogodynamics
From: ulf@poincare.physik.uni-konstanz.de (Ulf Jasper) Newsgroups: comp.sys.next.bugs Subject: Re: Terminal.app bug? and frame buffer?? Date: 11 Nov 1993 14:28:43 GMT Organization: University of Constance Message-ID: <2bti6r$9gr@hermes.uni-konstanz.de> References: <16C80123F3.OCS@earn.cvut.cs> Hello there! In article <16C80123F3.OCS@earn.cvut.cs> OCS@earn.cvut.cs writes: > Hi All, > > Sometimes launching of the Terminal locks the NEXTSTEP (3.1, evaluation > kit). The lock occurs before Terminal is fully started. Whole system, > including the mouse pointer, is freezed. > [...] I had these crashes several times with the same results. And now there are additional problems when booting: sometimes there appears a message "class 'frame buffer' not linked into application". Does anybody know what there is wrong? Many thanks in advance Ulf
From: Rebecca.Hunter@launchpad.unc.edu (Rebecca Hunter) Newsgroups: comp.sys.next,comp.sys.next.bugs,comp.sys.next.programmer Subject: DBKit/Sybase problem Date: 11 Nov 1993 22:01:41 GMT Organization: University of North Carolina Extended Bulletin Board Service Distribution: usa Message-ID: <2buco5$5n1@samba.oit.unc.edu> Summary: next bug? Keywords: Bug, HELP NextStep version 3.0 DEModeler version 0.7 using Sybase Adaptor Sometimes when we send two fetches, and the database delegate tells us that it is performing two SELECT statements in quick succession, the two are merged into one nonsensical statement, which then fails. Has anyone else experienced a similar problem? Does anyone know a fix for it? Details: Various debug print statements indicate that for the binders isFlushEnabled returns NO, sharesContext returns NO, and areObjectsFreedOnFlush returns Yes. All properties of the binders return YES for isDeferredExpression. We suspect that the actual selects are being deferred (until the data is actually needed) but that this is not being done cleanly, allowing mixing of commands. Example: The two commands which should be executing are: "SELECT t0.evaluation, tO.sourceProject FROM tl_evaluation_sourceProject tO" and "SELECT tO.name, tO.key FROM tv_staffOfficer tO WHERE tO.key = 121906061" Instead, we get: "SELECT to.name, tO.key, t1.evaluation, t1.sourceProject FROM tv_staffOfficer tO WHERE t1.evaluation = Ot1.sourceProject = 1073746836" Any help would be greatly appreciated. Please send any answers to [rhunter@kosmos.agu.org], not the address above. Thanks! -Rebecca -- The opinions expressed are not necessarily those of the University of North Carolina at Chapel Hill, the Campus Office for Information Technology, or the Experimental Bulletin Board Service. internet: laUNChpad.unc.edu or 152.2.22.80
From: johannes@scribes.english.uiuc.edu (John B. Friedman) Newsgroups: comp.sys.next.bugs Subject: Printer 3/0 bug Date: 11 Nov 1993 22:54:20 GMT Organization: University of Illinois at Urbana Message-ID: <2bufqs$csf@vixen.cso.uiuc.edu> I have a bug in which after upgrading a station to 3.0 I have had 5 hangs in the last month all associated with the printer.These hangs are disturbing because NOTHING gets me out of them except to shut off at the surgebar. The cursor, power off switch &c simply become inoperative. These can occur while printing, or if the printer runs out of paper and I don't get paper into it quickly enough or if the print panel comes up and I don't respond to it quickly enough. Please send suggested fixes or ways to halt less drastically to johannes@scribes.english.uiuc.edu. Thank you very much for your help
From: haker@whitewater.chem.wisc.edu (M Haker) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Wierd 3.1 DriverKit bug Date: 13 Nov 1993 01:35:30 GMT Organization: Division of Information Technology Message-ID: <2c1dl2$3jo@news.doit.wisc.edu> Hello all, I thought I'd just pass on this very strange bug I discovered recently while writing a 3.1 DriverKit driver for a National Instruments data aquisition board (it's a subclass of IODirectDevice). I wrote a method called - initializeBoard which reset the board to a startup state. At first I just called this method from within another method -configureBoard (initializes, then sets the board according to object parameters). Well all was working well until I decided to also initialize the board in the -initFromDeviceDescription method. The strange part about all this is that it initialized the board fine with the call from initFromDeviceDescription (I followed it with IOLog messages), but when I asked it to configure the board (and hence initialize the board) I got a System Panic with the message something like: -<3>: Objc error, object NatInstMIO16x does not respond to selector -<3> which I tracked down to be this call to - initializeBoard. When I comment out the call in initFromDeviceDescription, the other call works again (and I can call multiple times). I also thought it might have something special to do with the initFromDeviceDescription method so I provided another means of accessing it directly (here a subset of my setIntValue procedure, which I also use to have the driver execute methods by just passing in nothing, and other related code): - (IOReturn)setIntValues : (unsigned int *)parameterArray forParameter : (IOParameterName)parameterName count : (unsigned int)count { unsigned int temp, temp2, x; inputConfigType *tempConfig; if(strcmp(parameterName, SAMPLES_PER_TRIGGER) == 0){ temp = parameterArray[0]; if(temp<=65535) { samplesPerTrigger=temp; return IO_R_SUCCESS; } else return IO_R_UNSUPPORTED; } else if (strcmp(parameterName, SET_DEVICE)==0) { IOLog("setting device\n"); [self configureBoard]; return IO_R_SUCCESS; } else if (strcmp(parameterName, INITIALIZE_BOARD)==0) { IOLog("INITIALIZE_BOARD\n"); [self initializeBoard]; return IO_R_SUCCESS; } else { /* Pass parameters we don't recognize to our superclass. */ return [super setIntValues:parameterArray forParameter:parameterName count:count]; } } - initializeBoard { IOLog("initializeBoard\n"); [self clearBoard]; [self initAm9513a]; [self disableRTSIswitch]; return self; } - configureBoard { IOLog("Start configureBoard\n"); [self initializeBoard]; [self programChannelConfig]; [self setSampleTimer]; [self setSampleCounter]; IOLog("finished configureBoard\n"); return self; } So apparently the kernalLoaded driverKit objects are doing some funky stuff with objective C method translation. If I understand this Objective C stuff right, methoding is handled by the Objective C RunTime system, which is not running in the kernal(the kernal is not objective C). I switched the method over to a C function and I can call it from multiple places in my code (just not as a method). I hope this bug is fixed in 3.2 either through userLevel drivers or by someother means, because I want to be able to write driver code with methods and object level variable scopeing. Hope this is some help. Mike Haker Department of Chemistry, UW-Madison haker@whitewater.chem.wisc.edu
Newsgroups: comp.sys.next.bugs From: yanik@planon.qc.ca (Yanik Crepeau) Subject: Re: German Keyboard Problem - "B"-Key ist undefined Message-ID: <1993Nov10.153926.221@CAM.ORG!planon> Sender: yanik@CAM.ORG!planon References: <CG9450.7xt@bernina.ethz.ch> Date: Wed, 10 Nov 1993 15:39:26 GMT In article <CG9450.7xt@bernina.ethz.ch> BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) writes: Hi there I have installed NeXTStep for Intel with the US Keyboard setting, everything worked fine. I changed to the German Keyboard, which I am using, and suddenly the B-Key is undefinde, that means, I cannot type B at all, I can set it up again in Keyboard.App just as often as I want to.... is there any fix for this really annoying bug ? (It is not unique to m coputer, I've seen it before).... Thanx... Chris I tried it and I found nothing abnormal. Have you tried the "Schweizer" choice? Yanik -- Yanik Crepeau Programmer Planon Telexpertise E-Mail: yanik@planon.qc.ca (NeXT)
Newsgroups: comp.sys.next.bugs From: gsl@netcom.com (Greg Lindholm) Subject: Re: Bug in CDROM filesystem (ISO9660/RR)? Message-ID: <gslCGF48u.Mnx@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) References: <2bldrq$jui@klaus.physchem.chemie.uni-tuebingen.de> Date: Sat, 13 Nov 1993 06:48:30 GMT Frank Siegert (frank@atlas.physchem.chemie.uni-tuebingen.de) wrote: : Today I encountered a strange problem. : I mounted an ISO 9660/Rockridge Extensions CDROM and everything worked fine : at first. However as I was browsing throu it Workspace became slower and : slower as I descend the directory. In the directoy [Munch munch munch...] : This CDROM works perfectly on a SUN. Am I missing somthing? Do I have to : change something to read this CDROM? Is it the phase of the moon? : Or is it a bug? : Thanks : Frank Siegert I've had the same problems and I'm told by several netsters that it's a *known* bug in 3.1. If your on blackware you can revert to your 3.0 CDROM filesystem stuff. If your on whiteware you can hope and pray it's fixed in 3.2. Greg Lindholm gsl@netcom.com
Newsgroups: comp.sys.next.bugs From: norm@cfctech.cfc.com (Norman J. Meluch) Subject: Re: Terminal.app bug? and frame buffer?? Message-ID: <1993Nov12.002737.27879@cfctech.cfc.com> Organization: Chrysler Financial Corp., Southfield, MI References: <16C80123F3.OCS@earn.cvut.cs> <2bti6r$9gr@hermes.uni-konstanz.de> Date: Fri, 12 Nov 1993 00:27:37 GMT In article <16C80123F3.OCS@earn.cvut.cs> OCS@earn.cvut.cs writes: > Sometimes launching of the Terminal locks the NEXTSTEP (3.1, evaluation > kit). The lock occurs before Terminal is fully started. Whole system, > including the mouse pointer, is freezed. And ulf@poincare.physik.uni-konstanz.de (Ulf Jasper) writes: >I had these crashes [too..]. And now there >are additional problems when booting: sometimes there appears a message >"class 'frame buffer' not linked into application". >Does anybody know what there is wrong? On the Terminal.app freeze: We've had several (read ~25) real Terminal.app users here using 3.1 for a while, and one guy's machine seemed to have this problem *constantly*, while everyone else never saw the problem at all. All machines are exact same HW config. LGI 486DX2/66 450IDE 32RAM B-Mse. Recently, that particular user upgraded to 3.2 (early access) and he has not had the problem since. So, (not that this is really a fix but...) looks like it might have been (for us at least) a particular machine that brought out that bug, but it looks like it's fixed (or much more well hidden :-) for 3.2. On the 'frame buffer' message, I've seen that too. But I've never found what caused it. I've never seen it hurt anything though. - Norm. -- Who : Norman J. Meluch E-mail : norm@cfc.com What : Networking Specialist Uucp : ...!heifetz!cfctech!norm Fax : (313)948-3342 Voice : (313)948-4809 >> We're running NeXTSTEP on Intel. It doesn't get any beta than this. <<
Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.sysadmin From: emarinos@marcon.ka.sub.org (Evstathios Marinos) Subject: NSFIP does not recognize DOS Partition Message-ID: <1993Nov12.122536.824@marcon.ka.sub.org> Sender: emarinos@marcon.ka.sub.org (Evstathios Marinos) Organization: Marinos EDV - Consulting Date: Fri, 12 Nov 1993 12:25:36 GMT Hi, I have a problem with NSFIP when I boot from OS/2 Bootmanager. In this case no DOS partitions are recognized, everything else works right. If I boot with NS bootmanager, the DOS partitions are recognized. Does anybody know a solution or had the same problem? Thanks for help. Stathis -- Marinos EDV - Consulting | NEXTSTEP Software and Consulting Services Evstathios Marinos | Phone : +49 721 37 71 78 Gartenstr. 2 | Fax : +49 721 37 71 79 76133 Karlsruhe (GERMANY) | E-Mail: emarinos@marcon.ka.sub.org
Newsgroups: comp.sys.next.bugs From: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Subject: Re: German Keyboard Problem - "B"-Key ist undefined Message-ID: <CGFzrE.8nz@muaddib.isar.muc.de> Keywords: Bugfix Sender: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Organization: Foo Software, inc. References: <1993Nov10.153926.221@CAM.ORG!planon> Distribution: isar.muc.de Date: Sat, 13 Nov 1993 18:09:14 GMT In article <1993Nov10.153926.221@CAM.ORG!planon> yanik@planon.qc.ca (Yanik Crepeau) writes: > In article <CG9450.7xt@bernina.ethz.ch> BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) writes: > Hi there > > I have installed NeXTStep for Intel with the US Keyboard setting, everything > worked fine. I changed to the German Keyboard, which I am using, and suddenly > the B-Key is undefinde, that means, I cannot type B at all, I can set it up > again in Keyboard.App just as often as I want to.... > is there any fix for this really annoying bug ? (It is not unique to m coputer, > I've seen it before).... > > Thanx... > Chris > > I tried it and I found nothing abnormal. Have you tried the "Schweizer" choice? > > Yanik > > -- > Yanik Crepeau > Programmer > Planon Telexpertise > E-Mail: yanik@planon.qc.ca (NeXT) Hello Yanik, yes there is a bugfix out there. It is called GermanKeyboards.pkg can be the found on several ftp-sites -- Michael Maximilian Goedel _____________________ Internet: mgoedel@muaddib.isar.muc.de Adresse: Gerhardstrasse 33 - 81543 Muenchen Telefon: +49 89 65 29 18
Newsgroups: comp.sys.next.bugs From: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Subject: Re: Bug in CDROM filesystem (ISO9660/RR)? Message-ID: <CGG0Bx.8rI@muaddib.isar.muc.de> Keywords: Bugfix Sender: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Organization: Foo Software, inc. References: <gslCGF48u.Mnx@netcom.com> Distribution: nymphe Date: Sat, 13 Nov 1993 18:21:33 GMT In article <gslCGF48u.Mnx@netcom.com> gsl@netcom.com (Greg Lindholm) writes: > Frank Siegert (frank@atlas.physchem.chemie.uni-tuebingen.de) wrote: > : Today I encountered a strange problem. > : I mounted an ISO 9660/Rockridge Extensions CDROM and everything worked fine > : at first. However as I was browsing throu it Workspace became slower and > : slower as I descend the directory. In the directoy > [Munch munch munch...] > : This CDROM works perfectly on a SUN. Am I missing somthing? Do I have to > : change something to read this CDROM? Is it the phase of the moon? > : Or is it a bug? > > : Thanks > > : Frank Siegert > > I've had the same problems and I'm told by several netsters that it's > a *known* bug in 3.1. If your on blackware you can revert to your 3.0 CDROM > filesystem stuff. If your on whiteware you can hope and pray it's fixed > in 3.2. > > Greg Lindholm > gsl@netcom.com > This is a known bug in 3.1. Try to get GermanKeyboards.pkg from your local Dealer or an ftp-site next door. -- Michael Maximilian Goedel _____________________ Internet: mgoedel@muaddib.isar.muc.de Adresse: Gerhardstrasse 33 - 81543 Muenchen Telefon: +49 89 65 29 18
Newsgroups: comp.sys.next.bugs From: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Subject: Re: German Keyboard Problem - "B"-Key ist undefined Message-ID: <CGG2uz.996@muaddib.isar.muc.de> Sender: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Organization: Foo Software, inc. References: <1993Nov10.153926.221@CAM.ORG!planon> Distribution: all Date: Sat, 13 Nov 1993 19:16:10 GMT In article <1993Nov10.153926.221@CAM.ORG!planon> yanik@planon.qc.ca (Yanik Crepeau) writes: > In article <CG9450.7xt@bernina.ethz.ch> BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) writes: > Hi there > > I have installed NeXTStep for Intel with the US Keyboard setting, everything > worked fine. I changed to the German Keyboard, which I am using, and suddenly > the B-Key is undefinde, that means, I cannot type B at all, I can set it up > again in Keyboard.App just as often as I want to.... > is there any fix for this really annoying bug ? (It is not unique to m coputer, > I've seen it before).... > > Thanx... > Chris > > I tried it and I found nothing abnormal. Have you tried the "Schweizer" choice? > > Yanik > > -- > Yanik Crepeau > Programmer > Planon Telexpertise > E-Mail: yanik@planon.qc.ca (NeXT) Hello Yanik, yes there is a bugfix out there. It is called GermanKeyboards.pkg can be the found on several ftp-sites -- Michael Maximilian Goedel _____________________ Internet: mgoedel@muaddib.isar.muc.de Adresse: Gerhardstrasse 33 - 81543 Muenchen Telefon: +49 89 65 29 18
Newsgroups: comp.sys.next.bugs From: wdi@ztivax.zfe.siemens.de (Werner Dittmann) Subject: Serious_problem_in_memory_on_Nextstation Message-ID: <CGJ134.LHC@ztivax.zfe.siemens.de> Keywords: memory,pagein Sender: news@ztivax.zfe.siemens.de (The System Manager) Organization: Siemens AG Date: Mon, 15 Nov 1993 09:30:40 GMT Serious and strange memory problem on a NeXTstation (monochrome) running NeXTstep V3.0. During the port of gcc-2.5.0a I encountered a very strange and serious problem on my NeXtstation. Running the "cc1obj" compiler caused an illegal instruction trap. After tracking down the problem the following scenario showed up: As one of the first steps in "cc1obj" the function "_obstack_begin" is called. This function is also used in the "cc1" and "cc1plus" compilers for "C" and "C++" where it works perfectly. The module where this function is in is compiled only once and then used in all three compilers. The arguments to this function are shown in the following GDB-output. The interresting part of the story is, that "_obstack_begin" stores its argument "chunkfun", which is a pointer to a function, in a structure whose address is given in argument "h". In this case the address of the structure is 0xf1fe2, the offset into the structure where the "chunkfun"-address is stored is 28 (0x1c). If you sum it up, the resulting address is 0xf1ffe, which is just 2 bytes below a 4KB boundary, i.e. a new page in memory. The "movel" operation stores only the most significant part of the address at 0xf1ffe (the NeXT is a big endian) the rest of the address is completely lost. The address stored in the structure pointed to by "h" is 0x20000 instead of 0x25192!!! Using this as a function address later on causes the program to "run into the forrest" :-). After relocating the object file (tree.o) in the linker command line the structure gets another address and "cc1obj" works perfectly (see GDB-output below). I believe the problem is caused due to a bug either in hardware or in the paging part of the operating system. This because the problem occurs at a very early stage in the program where the following memory page was probably never valid before and during the "movel" operation the page gets used the first time. Unfortunaly, the page fault occurs right in the middle of the "movel" operation and either the hardware or the operating system didn't recognize that or the recovery of the "movel" operation after the page was brought into memory failed. Did someboby hear about such a problem on a NeXTstation, NeXTstep V3.0? Is it a known bug? If yes, is it fixed? It would by nice if someboby can give me some more infos. If possible via mail. Thank You. If this is a real bug I think this is a serious problem because it may happen any time to any program without warning and causing very mysterious failures of programs. For those of you who are familiar with GDB and 68k assembler I include the GDB outputs of the two program runs. The first one shows the illegal instruction, the second one runs ok. Breakpoint 1 at 0xc2736: file obstack.c:97. (gdb) run Starting program: /wdi/gcc-2.5.0/objc/../cc1obj cc.i -quiet -dumpbase Object.m -g -O -version -fgnu-runtime -lang-objc -o cc.s GNU Obj-C version 2.5.0 (68k, MIT syntax) compiled by GNU C version 2.5.0. Breakpoint 1, _obstack_begin (h=0xf1fe2, size=8192, alignment=0, chunkfun=0x25192 <xmalloc>, freefun=0x5002546 <libsys_s.B.shlib_jmp_table+1350>) at obstack.c:97 97 if (alignment == 0) (gdb) disass Dump of assembler code from 0xc2724 to 0xc27a8: 0xc2724 <_obstack_begin>: linkw fp,#0 0xc2728 <_obstack_begin+4>: movel a2,sp@- 0xc272a <_obstack_begin+6>: moveal fp@(8),a2 0xc272e <_obstack_begin+10>: movel fp@(12),d0 0xc2732 <_obstack_begin+14>: moveal fp@(16),a0 0xc2736 <_obstack_begin+18>: tstl a0 0xc2738 <_obstack_begin+20>: bne 0xc273e <_obstack_begin+26> 0xc273a <_obstack_begin+22>: moveaw #2,a0 0xc273e <_obstack_begin+26>: tstl d0 0xc2740 <_obstack_begin+28>: bne 0xc2748 <_obstack_begin+36> 0xc2742 <_obstack_begin+30>: movel #4072,d0 0xc2748 <_obstack_begin+36>: movel fp@(20),a2@(28) ***** store chunkfun !!! 0xc274e <_obstack_begin+42>: movel fp@(24),a2@(32) 0xc2754 <_obstack_begin+48>: movel d0,a2@ 0xc2756 <_obstack_begin+50>: subqw #1,a0 0xc2758 <_obstack_begin+52>: movel a0,a2@(24) 0xc275c <_obstack_begin+56>: andib #127,a2@(40) 0xc2762 <_obstack_begin+62>: bge 0xc2772 <_obstack_begin+78> 0xc2764 <_obstack_begin+64>: movel a2@,sp@- 0xc2766 <_obstack_begin+66>: movel a2@(36),sp@- 0xc276a <_obstack_begin+70>: moveal a2@(28),a0 ****** use stored func-addr 0xc276e <_obstack_begin+74>: jsr a0@ ****** wrong address !!! 0xc2770 <_obstack_begin+76>: bra 0xc277a <_obstack_begin+86> 0xc2772 <_obstack_begin+78>: movel a2@,sp@- 0xc2774 <_obstack_begin+80>: moveal a2@(28),a0 0xc2778 <_obstack_begin+84>: jsr a0@ 0xc277a <_obstack_begin+86>: moveal d0,a1 0xc277c <_obstack_begin+88>: movel a1,a2@(4) 0xc2780 <_obstack_begin+92>: lea a1@(8),a0 0xc2784 <_obstack_begin+96>: movel a0,a2@(8) 0xc2788 <_obstack_begin+100>: movel a0,a2@(12) 0xc278c <_obstack_begin+104>: movel a1,d0 0xc278e <_obstack_begin+106>: addl a2@,d0 0xc2790 <_obstack_begin+108>: movel d0,a1@ 0xc2792 <_obstack_begin+110>: movel d0,a2@(16) 0xc2796 <_obstack_begin+114>: clrl a1@(4) 0xc279a <_obstack_begin+118>: andib #-65,a2@(40) 0xc27a0 <_obstack_begin+124>: moveal fp@(-4),a2 0xc27a4 <_obstack_begin+128>: unlk fp 0xc27a6 <_obstack_begin+130>: rts End of assembler dump. ...... after checking some other variables, continuing of the program ..... Program generated(2): Illegal instruction. 0x20000 in pop_init_level (implicit=991202) at c-typeck.c:5185 5185 if (p->next == 0 && constructor_decl != 0 (gdb) backtrace #0 0x20000 in pop_init_level (implicit=991202) at c-typeck.c:5185 #1 0x2809c in gcc_obstack_init (obstack=0x0) at tree.c:299 #2 0x27e42 in init_obstacks () at tree.c:261 #3 0x25760 in compile_file (name=0x3fffd26 "obj.i") at toplev.c:1622 #4 0x27bd0 in main (argc=11, argv=0x3fffcb4, envp=0x3fffce4) at toplev.c:3496 (gdb) l obstack.c:90 85 CHUNKFUN is the function to use to allocate chunks, 86 and FREEFUN the function to free them. */ 87 88 void 89 _obstack_begin (h, size, alignment, chunkfun, freefun) 90 struct obstack *h; 91 int size; 92 int alignment; 93 POINTER (*chunkfun) (); 94 void (*freefun) (); (gdb) l 119 114 } 115 116 h->chunkfun = (struct _obstack_chunk * (*)()) chunkfun; 117 h->freefun = freefun; 118 h->chunk_size = size; 119 h->alignment_mask = alignment - 1; 120 h->use_extra_arg = 0; 121 122 chunk = h->chunk = CALL_CHUNKFUN (h, h -> chunk_size); 123 h->next_free = h->object_base = chunk->contents; Check program size to be certain the addresses are valid: localhost> size cc1 cc1obj cc1plus __TEXT __DATA __OBJC others dec hex 909312 73728 0 2154496 3137536 2fe000 cc1 966656 73728 0 2252800 3293184 324000 cc1obj 1187840 81920 0 2899968 4169728 3fa000 cc1plus ************** After new link where "tree.c" was moved (forward) ************** in the link command line: Now the address of the structure (argument "h") is 0xf1f16!!!!! localhost> ls -l ../cc1o* -rwxr-xr-x 1 wdi 3227500 Nov 13 11:00 ../cc1obj* -rwxr-xr-x 1 wdi 3227500 Nov 7 20:38 ../cc1obj.err* localhost> gdb ../cc1obj Reading symbol data from ../cc1obj...done. Reading symbol data from /usr/shlib/libsys_s.B.shlib...done. (gdb) break 97 Breakpoint 1 at 0xc2736: file obstack.c:97. (gdb) set args cc.i -quiet -dumpbase Object.m -g -O -version -fgnu-runtime -lang-objc -o cc.s (gdb) run Starting program: /wdi/gcc-2.5.0/objc/../cc1obj cc.i -quiet -dumpbase Object.m -g -O -version -fgnu-runtime -lang-objc -o cc.s GNU Obj-C version 2.5.0 (68k, MIT syntax) compiled by GNU C version 2.5.0. Breakpoint 1, _obstack_begin (h=0xf1f16, size=8192, alignment=0, chunkfun=0x2904e <xmalloc>, freefun=0x5002546 <libsys_s.B.shlib_jmp_table+1350>) at obstack.c:97 97 if (alignment == 0) (gdb) clear Deleted breakpoint 1 (gdb) cont Continuing. Program exited normally. Thanx in advance for your help Werner Dittmann wdi@ztivax.zfe.siemens.de
Newsgroups: comp.sys.next.bugs From: Atze (Alexander Spohr) Subject: Re: German Keyboard Problem - "B"-Key ist undefined Message-ID: <1993Nov15.110541.384@dart.de> Sender: aspohr@dart.de Organization: d'ART Computersysteme GmbH References: <1993Nov10.153926.221@CAM.ORG!planon> Date: Mon, 15 Nov 93 11:05:41 GMT In article <1993Nov10.153926.221@CAM.ORG!planon> yanik@planon.qc.ca (Yanik Crepeau) writes: > > In article <CG9450.7xt@bernina.ethz.ch> BOOSC@EZINFO.VMSMAIL.ETHZ.CH (Chris Boos) writes: > > Hi there > > > > I have installed NeXTStep for Intel with the US Keyboard setting, everything > > worked fine. I changed to the German Keyboard, which I am using, and suddenly > > the B-Key is undefinde, that means, I cannot type B at all, I can set it up > > again in Keyboard.App just as often as I want to.... Not inly the B is missing. F1 does not work either. And the old problem is still there: Caps-lock doesn't lock Y and Z. > > is there any fix for this really annoying bug ? Call d'ART in Hamburg, Germany. They have a new German Keyboard with B and F1 working. And a second one which is like NeXTUSA with the Shift, Command and Alternate keys, just German. > > I tried it and I found nothing abnormal. Do you have a _German_ keyboard??? I do and it does not work. > Have you tried the "Schweizer" choice? Unusable for Germans. There is no sz (looks like a beta) and other keys are at wrong places too. Atze -- Alexander Spohr, Hamburg, Germany Alexander_Spohr@dART.de (Mail ) Faces and faces (+49) 40 / 380 23-0 (Sound) See them and complain not (+49) 40 / 380 23-290 (Fax ) And am content with all
Newsgroups: comp.sys.next.bugs From: Atze (Alexander Spohr) Subject: Re: Terminal.app bug? and frame buffer?? Message-ID: <1993Nov15.111753.447@dart.de> Sender: aspohr@dart.de Organization: d'ART Computersysteme GmbH References: <1993Nov12.002737.27879@cfctech.cfc.com> Date: Mon, 15 Nov 93 11:17:53 GMT In article <1993Nov12.002737.27879@cfctech.cfc.com> norm@cfctech.cfc.com (Norman J. Meluch) writes: > In article <16C80123F3.OCS@earn.cvut.cs> OCS@earn.cvut.cs writes: > > Sometimes launching of the Terminal locks the NEXTSTEP (3.1, evaluation > > kit). The lock occurs before Terminal is fully started. Whole system, > > including the mouse pointer, is freezed. > > > And ulf@poincare.physik.uni-konstanz.de (Ulf Jasper) writes: > >I had these crashes [too..]. And now there > >are additional problems when booting: sometimes there appears a message > >"class 'frame buffer' not linked into application". > >Does anybody know what there is wrong? > > On the Terminal.app freeze: We've had several (read ~25) real Terminal.app [sqsh] > Terminal.app hates if you double-click a shell script or a little C-prog (a.out) in WS. This IS the bug. And maybe if the shell you give in preferences is not so clean it will chrash too. And I have no idea what happens if your startup-file makes problems. The "Frame buffer bla" message appears if you told Configure.app that you have a graphic-card with a frame-buffer (e.g. ATI) and you don't put the buffer (with the graphic card setup) where you told Configure.app to look for it. This will not allow to complete booting. Why this message appears only sometimes on your machine... do have a local bus running at more than 40Mhz? Just a guess. Atze -- Alexander Spohr, Hamburg, Germany Alexander_Spohr@dART.de (Mail ) Faces and faces (+49) 40 / 380 23-0 (Sound) See them and complain not (+49) 40 / 380 23-290 (Fax ) And am content with all
Newsgroups: comp.sys.next.bugs From: davis@symphony.cc.purdue.edu (Robert Davis) Subject: Re: Terminal.app bug? and frame buffer?? Message-ID: <CGJxBn.Ayp@mentor.cc.purdue.edu> Sender: news@mentor.cc.purdue.edu (USENET News) Organization: Purdue University, West Lafayette, IN References: <1993Nov12.002737.27879@cfctech.cfc.com> <1993Nov15.111753.447@dart.de> Date: Mon, 15 Nov 1993 21:06:58 GMT In article <1993Nov15.111753.447@dart.de>, Alexander Spohr <Alexander_Spohr@dART.de> wrote: > >Terminal.app hates if you double-click a shell script or a little C-prog >(a.out) in WS. This IS the bug. And maybe if the shell you give in >preferences is not so clean it will chrash too. And I have no idea >what happens if your startup-file makes problems. > Hmm, I'm not sure that is THE problem. I experienced the same sort of total lock up and it took me a while to track it down. About one out of five logins, the computer would hang shortly after login. It made me think NS/FIP was really unstable. Eventually I discovered that it was Terminal.app, which would occasionally hang the machine. I was using zsh, so that was what I suspected first. I switched the shell preference to /bin/sh -- same problem. I noticed that this rarely (if ever) happened after a cold boot. I was running with only 16MB, so I would occasionally log out and type 'exit' at the login panel, then log back in. Out of curiosity, I stopped doing that -- problem went away. I could stop Terminal, restart it, over and over with no problem. I could reboot, log in, Terminal would auto-launch, no problem. I haven't experienced a crash, panic, or lock-up of any sort in months. I haven't investigated further because I recently got hold of a MAB version of Stuart, but it *seems* related to killing the window server. Rob -- | Robert Davis davis@sonata.cc.purdue.edu | "Look up, Hannah." NeXT Mail accepted --
Newsgroups: comp.sys.next.bugs From: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Subject: Sorry for the garbage Message-ID: <CGK3K3.28z@muaddib.isar.muc.de> Sender: mgoedel@muaddib.isar.muc.de (Maximilian Goedel) Organization: Michael Maximilian Goedel Distribution: all Date: Mon, 15 Nov 1993 23:21:39 GMT Sorry, if there were a lot same postings to this newsgroup, but I'd some problems with my newsgrazer and c-news. Seems it works now correctly again. Again, I'm very very sorry :-{ O -|- /\__ ___o/\_____ -- Michael Maximilian Goedel _____________________ Internet: mgoedel@muaddib.isar.muc.de Adresse: Gerhardstrasse 33 - 81543 Muenchen Telefon: +49 89 65 29 18
From: ssircar@canon.com (Subrata Sircar) Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer Subject: ProjectBuilder bug [#50523] (Correction) Date: 16 Nov 1993 10:41:31 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311161639.AA03637@alychne-nc.canon.com> I previously reported: ***** Under 3.0, 3.1E (Motorola) and 3.1J (Intel) Project Builder has a serious bug. 1. Create a new project and go to the Attributes view. 2. Change the install directory (to an absolute pathname, say). 3. Save the file and close the window. 4. Open the file and go the Attributes window - the old install path is still there! The only obvious option was to edit the Makefile and PB.project by hand. ***** This behavior depends on the 3.0/3.1 AutoSave setting; if the AutoSave preference is set, this bug can be seen. If the AutoSave preference is off, then the bug does not occur. --- Subrata Sircar|ssircar@canon.com (NextMail ok)|Prophet & SPAMIT Charter Member Canon Information Systems and I do not share the same views on everything. "I'm just mad that I missed the sexual revolution." - me "Yes, but you dress much better as a result." - Mike
From: david@jaffe.com Newsgroups: comp.sys.next.bugs Subject: Music Kit beta bugs Date: 16 Nov 1993 23:24:20 GMT Organization: University of California, Berkeley Message-ID: <2cbnf4$ifg@agate.berkeley.edu> Keywords: Music Kit, 4.0, Bugs, beta There have been a few bugs discovered in the Music Kit 4.0 beta release. This means we will definitely put out a "true 4.0" release some time soon. Keep those bug reports coming! For your info, I'm providing below the current list of bugs and how to work around them. Anything not mentioned below means we haven't heard about it yet. By the way, when you install the Music Kit package, if it asks to overwrite something, say Yes. Otherwise, you may get an incomplete and inconsistant release. For example, Ensemble has changed its document format. ------------------------------ 1. Ensemble and WaveEdit get "Can't open DSP" error when run on a machine other than the one where the MusicKit_4.0 distribution was installed. Status: We have a fix. Fix will be available in true 4.0 release Workaround: Find the machine where the MK distribution WAS installed and copy /usr/local/lib/dsp/monitor/mkmon_A_8k.dsp to the Ensemble.app and WaveEdit.app folders. 2. 030 machines can't do sound synthesis. This was a bug in the DSP memory sensing. Status: We have a fix. Fix will be available in true 4.0 release Workaround: Copy mkmon_A_8k.dsp to mkmon_A_32k.dsp in Ensemble.app, ScorePlayer.app and WaveEdit app folders. Do the same to the programming examples. Finally, copy /usr/local/lib/dsp/monitor/mkmon_A_8k.dsp to /usr/local/lib/dsp/monitor/mkmon_A_32k.dsp. 3. programming example /LocalDeveloper/Examples/DSP/SoundControl doesn't work. Status: We have a fix. Fix will be available in true 4.0 release Workaround: None. Nib files are missing. 4. WaveEdit emits endless postscript errors when you edit the phase window sometimes. Status: Still debugging it Workaround: Don't edit phase--it doesn't make much difference anyway! 5. Music Kit available only as a huge package that is too big for some folks. Status: Fixed. You can now get it in smaller chunks from ccrma-ftp.stanford.edu. 6. SynthBuilder (not a part of the Music Kit release, but related) doesn't make in some circumstances Status: Fixed. You can get a new version from ccrma-ftp. Also, SynthBuilder is now available as binary as well as source. So if you only want SynthBuilder, but don't want the whole Music Kit package, you just get the binaries now. 7. Apps that use unit generator In1aUG (or any other unit generator that sets register M_I1) can crash the DSP. Status: We have a fix. Fix will be available in true 4.0 release Workaround: If you really need it and want to edit dsp assembly language and rebuild the world, let me know. 8. Some problems playing scorefiles on 030 machines Status: Still under investigation.
Newsgroups: comp.sys.next.bugs From: yanik@planon.qc.ca (Yanik Crepeau) Subject: Re: Music Kit beta bugs Message-ID: <1993Nov17.163349.5533@CAM.ORG!planon> Sender: yanik@CAM.ORG!planon References: <2cbnf4$ifg@agate.berkeley.edu> Date: Wed, 17 Nov 1993 16:33:49 GMT In article <2cbnf4$ifg@agate.berkeley.edu> david@jaffe.com writes: There have been a few bugs discovered in the Music Kit 4.0 beta release. This means we will definitely put out a "true 4.0" release some time soon. Keep those bug reports coming! For your info, I'm providing below the current list of bugs and how to work around them. Anything not mentioned below means we haven't heard about it yet. By the way, when you install the Music Kit package, if it asks to overwrite something, say Yes. Otherwise, you may get an incomplete and inconsistant release. For example, Ensemble has changed its document format. ------------------------------ [...] 5. Music Kit available only as a huge package that is too big for some folks. Status: Fixed. You can now get it in smaller chunks from ccrma-ftp.stanford.edu. [...] I am the guy who requested the smaller chunks. The job has been done and done very well. I used a ftp-mail relay to get the chuncks. Each of the 8 chuncks has 1200K in size, except the last one which is a little bit smaller. Each of these chunck has been re-chuncked in even smaller mail. For each of the 1200K file, I received 29 mails I needed to put together. I have written a C-Shell script that use sed (stream editor) that take the 29 files, strip the mail header and but all the bunch together. However, I spent 2 days to finish the job. I would like to not have to re-download all the 8 files (8 X 29 = 232 mails) to fix the bugs. Just create a package that will put the new needed files. Yanik -- Yanik Crepeau Programmer Planon Telexpertise E-Mail: yanik@planon.qc.ca (NeXT)
From: haker@whitewater.chem.wisc.edu (M Haker) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: HELP: unable to link 3.1 driver with mach messages Date: 17 Nov 1993 21:13:24 GMT Organization: Division of Information Technology Message-ID: <2ce45k$578@news.doit.wisc.edu> Hello all, My 3.1 driver is at a point where I need to start dealing with handling mach messages. I've added some really simple port watching code (msg_receive) which compiles fine. But when I try to load the driver into the kernal I get these log messages Nov 17 14:53:22 swamp kern_loader: kern_loader: Link failed Nov 17 14:53:22 swamp kern_loader: kern_loader: Link failed Nov 17 14:53:22 swamp kern_loader: kern_loader: server NatInstMIO16x won't link Nov 17 14:53:22 swamp kern_loader: kern_loader: server NatInstMIO16x won't link Nov 17 14:53:22 swamp syslog: kern_loader_add_server: error 108 I know this probably has something to do with the fact that it can't link to the mach functions (msg_receive,port_allocate,mach_error,task_self) but it sounds fishy (the kernal_loader can't like to mach kernal functions?) Thanks for any help Michael Haker dept Chemistry, UW-Madison haker@whitewater.chem.wisc.edu
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 18 Nov 1993 01:53:25 -0500 Organization: Next Announcements Message-ID: <2cf653$hl@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
From: wuj9@ac.wfu.edu (joe wu) Newsgroups: comp.sys.next.bugs Subject: Mount 128M MO drive as 2.88 Mac CD! Date: 19 Nov 1993 08:59:38 GMT Organization: Wake Forest University Message-ID: <2ci1tq$i2b@quad.wfunet.wfu.edu> Keywords: Tahoe/Pinnacle 128M MagnitoOptical --: Please help! NS3.1 on black hardware is incorrectly reporting the mounted preformatted Mac 128M MO disk as 2.88 Mac CD. When I used BuildDisk, the program recognized it as 122Meg removable_rw_scsi but gave me a list of error messages in console. I asked the technician at Pinnacle, the best he could do was to give me the MO disk configuration. 10367 cylinders 1 head 24 sectors 512 bytes - sector size 3600 rpm 248808 sectors I do not know how to create a disktab entry from these. I tried just entering what is known (hoping the system will calculate the missing pieces) and got "Incomplete disk transfer" messages. (Where does one go to figure out what disktab is asking for?) Is this a bug? ...why does it correctly recognize external Mac HD and not Mac formatted MO disk? Why does it report 122M in BuildDisk and 1.9M in Workspace? Please send solutions, suggestions, disktab hints to: wuj9@ac.wfunet.wfu.edu Thank you. Yours, Joe
From: jofeng@wam.umd.edu (Jo-Feng Hsieh) Newsgroups: comp.sys.next.bugs Subject: 1993 Honda Civic DX for SALE Date: 19 Nov 1993 14:25:50 GMT Organization: University of Maryland, College Park Sender: jofeng@wam.umd.edu Distribution: dc Message-ID: <2cil1e$fd3@cville-srv.wam.umd.edu> ******************************************************* 1. 1993 Honda Civic DX with White color and 4 doors 2. Auto, A/C, Cassette, Power Steering, Air Bag. 3. Civic Floor Mats, added on the right-side mirror 4. Excellent condition with good maintainness (Oil Change 3 times and twice maintainness at Honda dealer's shop) 5. 9000 miles(now) 6. $10,600 ******************************************************** If interest, please mail jofeng@wam.umd.edu or call (301) 935-5149, Ms. Hsieh
Newsgroups: comp.sys.next.bugs From: bruce@TotSysSoft.com (Bruce Gingery) Subject: 3.1 to 3.2 bug info posted on ftp.next.com Message-ID: <1993Nov19.124028.5305@ToTSySSoft.com> Sender: news@ToTSySSoft.com Organization: Total System Software Date: Fri, 19 Nov 1993 12:40:28 GMT The title says it all.
Newsgroups: comp.sys.next.bugs From: greyham@research.canon.oz.au (Graham Stoney) Subject: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGq4AL.9sH@research.canon.oz.au> Summary: Thankyou NeXT! Keywords: move16, 68040, exceptions Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia Date: Fri, 19 Nov 1993 05:23:09 GMT I remember seeing this mentioned on comp.sys.next.bugs before and I could have sworn I'd saved a copy of the info, but now I cannot for the life of me find it... move16 on 68040 based black hardware appears to be broken in NeXTstep 3.0 and 3.1, which is a worry because we currently use it to generate burst NeXTbus transfers. It works fine on 2.1, and it appears that what happens under 3.0 and 3.1 is that page faults which occur due to a move16 instruction are mishandled, resulting in the data not being copied correctly to the destination. I searched NeXTanswers, but there is no reference to move16 there. I recall the previous postings here being from Cliff at ARDI, referring to problems getting Executor to run correctly. Does anyone know if the problem was resolved, and if so, what the resolution was?. Thanks, Graham -- Graham Stoney, Hardware/Software Engineer Canon Information Systems Research Australia Ph: + 61 2 805 2909 Fax: + 61 2 805 2929
Newsgroups: comp.sys.next.bugs From: mark@xexos.com (Mark Chamberlain) Subject: Re: 1993 Honda Civic DX for SALE Message-ID: <1993Nov19.180029.14637@xexos.com> Sender: news@xexos.com Organization: Xexos, Ltd (London) References: <2cil1e$fd3@cville-srv.wam.umd.edu> Distribution: dc Date: Fri, 19 Nov 1993 18:00:29 GMT In article <2cil1e$fd3@cville-srv.wam.umd.edu> jofeng@wam.umd.edu (Jo-Feng Hsieh) writes: > > ******************************************************* > > 1. 1993 Honda Civic DX with White color and 4 doors > Hmm... a DX model with 4 slots. Have NeXT certified it? -- Mark Chamberlain +44 71 237 4535 Xexos Ltd fax +44 71 231 0844 London mark@xexos.com
From: luomat@alleg.edu (Timothy J. Luoma) Newsgroups: comp.sys.next.bugs Subject: Re: 1993 Honda Civic DX for SALE Date: 19 Nov 1993 20:10:57 GMT Organization: Allegheny College Distribution: world Message-ID: <2cj98h$3ch@ftp.alleg.edu> References: <1993Nov19.180029.14637@xexos.com> In article <1993Nov19.180029.14637@xexos.com> mark@xexos.com (Mark Chamberlain) writes: In article <2cil1e$fd3@cville-srv.wam.umd.edu> jofeng@wam.umd.edu (Jo-Feng Hsieh) writes: > > 1. 1993 Honda Civic DX with White color and 4 doors > Hmm... a DX model with 4 slots. Have NeXT certified it? What a great idea! No more cubes or pizza boxes, a totally new innovation!! Portable, compatable with your lifestyle needs.... now you can drive to work and do work all at the same time.... I bet it can really *boot*. I must admit though.... if this is their idea of an upgrade, I can't wait until NS 4.0.!!!! {{ only by the strongest will-power did a smiley face _not_ appear anywhere in this post }} -- Timothy J. Luoma Email: luomat@alleg.edu Allegheny College, Meadville PA USA Using: NS 3.1 Black NeXT Mail Welcomed
Newsgroups: comp.sys.next.bugs From: spagiola@frinext.stanford.edu (Stefano Pagiola) Subject: Re: 1993 Honda Civic DX for SALE Message-ID: <1993Nov19.211833.1952@leland.Stanford.EDU> Sender: news@leland.Stanford.EDU (Mr News) Organization: Stanford University References: <2cj98h$3ch@ftp.alleg.edu> Date: Fri, 19 Nov 93 21:18:33 GMT Timothy J. Luoma writes > > > > 1. 1993 Honda Civic DX with White color and 4 doors > > > Hmm... a DX model with 4 slots. Have NeXT certified it? > > What a great idea! No more cubes or pizza boxes, a totally new > innovation!! Portable, compatable with your lifestyle needs.... > now you can drive to work and do work all at the same time.... The only problem is that its white. Can I get it in black? -- - Stefano Pagiola Food Research Institute, Stanford University spagiola@leland.stanford.edu (NeXTMail encouraged) spagiola@FRI-nxt-Pagiola.stanford.edu (NeXTMail encouraged)
From: luomat@alleg.edu (Timothy J. Luoma) Newsgroups: comp.sys.next.bugs Subject: Re: 1993 Honda Civic DX for SALE Date: 19 Nov 1993 22:23:54 GMT Organization: Allegheny College Distribution: world Message-ID: <2cjh1q$6d2@ftp.alleg.edu> References: <1993Nov19.211833.1952@leland.Stanford.EDU> In article <1993Nov19.211833.1952@leland.Stanford.EDU> spagiola@frinext.stanford.edu (Stefano Pagiola) writes: Timothy J. Luoma writes > > > > 1. 1993 Honda Civic DX with White color and 4 doors > > > Hmm... a DX model with 4 slots. Have NeXT certified it? > > What a great idea! No more cubes or pizza boxes, a totally new > innovation!! Portable, compatable with your lifestyle needs.... > now you can drive to work and do work all at the same time.... The only problem is that its white. Can I get it in black? Sorry, we don't make them in black anymore, but you could at one time.... (see .sig for more sentimentality) You _could_ always have it painted... but it just wouldn't be the same ~TjL -- Timothy J. Luoma Email: luomat@alleg.edu Allegheny College, Meadville PA USA Using: NS 3.1 Beloved Black NeXT Mail Welcomed
From: robocop@p231.informatik.Uni-Bremen.DE (Dirk Lehmann + Co) Newsgroups: comp.sys.next.misc,comp.sys.next.bugs Subject: PhotoAlbum.App = buggy ?? Date: 19 Nov 1993 09:46:24 GMT Organization: Universitaet Bremen Sender: robocop@p231 (Dirk Lehmann + Co) Distribution: world Message-ID: <2ci4lg$jmu@ina.zfn.uni-bremen.de> A few day's ago a bought a Phillips photo-CD. Several trials on opening the pictures with PhotoAlbum.app were answered with: Wrong Format ! The next time I used pCD ( an alternative PhotoCD App from Nova), all pictures could be displayed without any problems. Also the Workspace had problems with the CD. On double-clicking the photo-CD icon, only opening lines of a wondow were drawn, but nothing else happend. I could only access the files on the CD out of a shell. My question only belongs to the App PhotoAlbum, not the buggy (3.1) CD-ROM device driver (This bug is already known ). Thanks in advance Dirk
Newsgroups: comp.sys.next.bugs From: dave@prim.demon.co.uk (Dave Griffiths) Subject: Overwriting fields in DBTableView Message-ID: <1993Nov20.161450.505@prim.demon.co.uk> Organization: Primitive Software Ltd. Date: Sat, 20 Nov 1993 16:14:50 GMT There is a bug in DBTableView which causes fields to appear corrupted whenever the data supplied by the data source has changed since the last time it was requested. The problem is caused by [DBLayout vectors::inRange::] returning two rows when the supplied range is that of just one row. The rectangle is only cleared for the bottom row with the result that the row above overwrites itself. Does anyone know if this bug is fixed in 3.2? (Soapbox: bugs like this demonstrate just how useful access to the sources would be. What do you say to your mission-critical customer when the values in their dealing room app are messed-up? "Oh I've mailed bug_next but no reply, maybe it'll be fixed in the next release. Fingers crossed.". No. You have to sit there and reverse-engineer private classes/methods and try and override the behaviour. I modified the rectangle in [DBLayout vectors::inRect::] to overcome this bug only to find it had the side-effect of not drawing the grid lines under certain circumstances. Without the source you're just stumbling in the dark.) There's also another bug in DBGridView which results in too many rows being updated when you call -rowsChangedFrom:to:. This one results from the fact that [DBGridView updateVectors::isRow:] calculates too large a rectangle to supply to -drawSelf:: (it uses endRowYPos + endRowHeight for the height instead of endRowYPos + endRowHeight - startRowYPos). This bug obviously affects performance. Is anyone else out there doing workarounds for DBTableView bugs? Attached are the Controller files for a simple application to demonstrate these bugs. Simply create a new project and drag a DBTableView into a window. Give it one column and make it editable. Attach the outlet tableView from an instantiation of Controller to the DBTableView. Make the window smaller than 50 rows. Run it and edit the lowest displayed row and hit return. This row will then appear overwritten. Try scrolling up and down and see the mess it produces. Try running it again with rowsChanged line uncommented. Edit the bottom line again and see how more than just row 4 is being changed. Dave Griffiths === Controller.h === #import <appkit/appkit.h> @interface Controller:Object { id tableView; } - appDidInit:sender; - (unsigned int)rowCount; - getValueFor:identifier at:(unsigned int)aPosition into:aValue; - setValueFor:identifier at:(unsigned int) aPosition from:aValue; @end === Controller.m === #import <dbkit/dbkit.h> #import "Controller.h" int value; @implementation Controller - appDidInit:sender { [[tableView setDataSource:self] reloadData:self]; return self; } - (unsigned int)rowCount { return 50; } - getValueFor:identifier at:(unsigned int)aPosition into:aValue { [aValue setIntValue:value++]; return self; } - setValueFor:identifier at:(unsigned int) aPosition from:aValue { // [tableView rowsChangedFrom:4 to:4]; // uncomment for second bug return self; } @end
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGtKxt.9uL@boa.cs.unm.edu> Keywords: move16, 68040, exceptions Sender: news@boa.cs.unm.edu Organization: ARDI References: <CGq4AL.9sH@research.canon.oz.au> Date: Sun, 21 Nov 1993 02:15:31 GMT I was the person that posted a nice little test program that behaved differently depending on whether or not you put a breakpoint in right before a move16. I asked people to try it on their machines and I found people trying it under NS3.0 and NS3.2 were able to run it, but at least some others with NS3.1 were not able to. However, I didn't think to tell everyone to report how much memory they had and what else they were running at the time, so it could just be coincidence that it worked on some machines and not on others. The question generated a lot of spurious replies telling me that I didn't understand how the instruction worked and whatnot. The issues involved here are tricky, and it's easy to see how people would get confused. I also don't have a habit of stressing my background when I post, so it was easy to assume that I didn't know what I'm talking about, but it turns out that I know a whole heck of a lot about 680x0 in general, the move16 instruction in specific, the 68040 copyback cache in specific and the internals of UNIX and Mach, including NEXT's error handling code. For the record: I don't think this *particular* bug would affect *any* software written for NS, including Executor. The only way we found it was when we were comparing our synthetic CPU to a real '040, and that's when we found the discrepency. In order to trigger this *particular* bug, you have to issue a move16 with arguments that are not aligned. PLEASE do NOT write me and tell me that the move16 requires aligned arguments; Motorola's own specs say otherwise (at least the ones from 1989 do -- if you have other docs *FROM MOTOROLA* that are newer and contradict this, let me know). However, it could be that this particular bug is a manifestation of something much more evil. It has not yet been officially reported to NEXT, but it has been unofficially reported to NEXT. I haven't done anything on this bug for a while, because I've been swamped with work. I don't post directly from ARDI and as such, I don't keep a copy of my outgoing articles. If someone else has the original article, with the bug producing program, it would probably be a good idea to repost it, along with a request for more people to try the test with as few other things as possible running in the background and to report how much physical memory they have in addition to what happened. It is my recollection that the "bugs fixed in 3.1" file contained mention of a bug related to bus errors and they copy-back cache being fixed. That fix, *may* have caused the bug that I found. --Cliff ctm@ardi.com In article <CGq4AL.9sH@research.canon.oz.au> greyham@research.canon.oz.au (Graham Stoney) writes: >I remember seeing this mentioned on comp.sys.next.bugs before and I could have >sworn I'd saved a copy of the info, but now I cannot for the life of me find >it... > >move16 on 68040 based black hardware appears to be broken in NeXTstep 3.0 and >3.1, which is a worry because we currently use it to generate burst NeXTbus >transfers. It works fine on 2.1, and it appears that what happens under 3.0 >and 3.1 is that page faults which occur due to a move16 instruction are >mishandled, resulting in the data not being copied correctly to the >destination. > >I searched NeXTanswers, but there is no reference to move16 there. I recall >the previous postings here being from Cliff at ARDI, referring to problems >getting Executor to run correctly. Does anyone know if the problem was >resolved, and if so, what the resolution was?. > >Thanks, >Graham >-- >Graham Stoney, Hardware/Software Engineer >Canon Information Systems Research Australia >Ph: + 61 2 805 2909 Fax: + 61 2 805 2929
Newsgroups: comp.sys.next.bugs From: pjoe@charon.muc.de (Peter Eybert) Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <1993Nov21.114808.699@charon.muc.de> Sender: pjoe@charon.muc.de Organization: Peter Eybert References: <CGtKxt.9uL@boa.cs.unm.edu> Date: Sun, 21 Nov 1993 11:48:08 GMT In article <CGtKxt.9uL@boa.cs.unm.edu> ctm@ardi.com writes: > I was the person that posted a nice little test program that behaved > differently depending on whether or not you put a breakpoint in right > before a move16. I asked people to try it on their machines and I [...] > I haven't done anything on this bug for a while, because I've been > swamped with work. I don't post directly from ARDI and as such, I > don't keep a copy of my outgoing articles. If someone else has the > original article, with the bug producing program, it would probably be > a good idea to repost it, along with a request for more people to try > the test with as few other things as possible running in the background > and to report how much physical memory they have in addition to what > happened. The original article from Cliff follows: Subject: NEXTSTEP or Motorola bug? Dear bargain bug hunters and eaters of fine mexican foods, This is an interesting bug. It could be as trivial as a bug in the 68040 documentation, or as severe as an exceedingly rare, but very dangerous bug in NEXTSTEP. I don't know. I only have one '040 to play with, and it's running NS 3.1. This letter will not make sense to you who do not diddle bits, but to those of you without lives of your own, I'd *love* to know what happens on your machines, especially if running NS 2.x or NS 3.2 or NS 3.0. Apparently "move16"s can fail to transfer 16 bytes at a time if the addresses that are being used aren't 16 bit aligned. The documentation *I* have (M68000PM/AD (c) 1989) has an example on page 2-120 that strongly suggests that unaligned addresses are silently aligned and then have the same net effect as if the aligned accesses are used. Why would we notice such a bizarre discrepency? It turns out that one of the ways we test our synthetic CPU is to feed a bunch (and I'm talking about a *BIG* bunch) of instructions to our synthetic CPU while feeding the same instructions to the 68040 directly. We then compare results. It's not clear whether or not we had the move16 problems under NS 3.1, but we definitely have them now. Our synthetic CPU *always* transfers 16 bytes, but as my test below shows, under NS 3.1, sometimes only 12, 8 or 4 bytes are transferred. I haven't reported this to NEXT because it could just be an '040 anamoly (like what happens when you execute "unlk a7"--don't do it before backing your system up). However, it could be that NEXTSTEP's bus handling code botches a rare type of access under peculiar circumstances. If this is true, finding and fixing this bug *could* fix mystery NEXTSTEP bugs that would be exceedingly unlikely to be fixed otherwise. Here's a demo program: #include <stdio.h> #include <string.h> void dump(unsigned char *p) { int i; unsigned char c; unsigned short us; p = (unsigned char *) ((long) p & ~0xFL); us = 0; for (i = 16; --i >= 0;) { us <<= 1; switch ((c = *p++)) { case 0: break; case 0xFF: us |= 1; break; default: fprintf(stderr, "Unexpected char 0x%x\n", c); break; } } printf("0x%04x,\n", us); } int main(int argc, char *argv[]) { unsigned char source[512], dest[512], *p1, *p2, *unused1, *unused2; int i, j; memset(source, 0xFF, sizeof(source)); for (p1 = (unsigned char *) ((long) (source + 15) & ~0xFL), i = 16; --i >= 0; ++p1) for (p2 = (unsigned char *) ((long) (dest + 15) & ~0xFL), j = 16; --j >= 0; ++p2) { memset(dest, 0x00, sizeof(dest)); asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : "0" (p1), "1" (p2)); dump(p2); } return 0; } If you compile and run this program, you'll probably get 256 lines of: 0xffff, since I'm using hex notation to show which of the sixteen bytes that *should* have been transferred actually were transferred. 256 lines of 0xffff, is correct. Here's where it gets fun. Put a breakpoint on the move16 instruction (line 39) and then run the program and use the "c" (continue) command to run through the loop a few times. If your system is like mine, you'll get output like this: (gdb) b 39 Breakpoint 1 at 0x3e76: move16.c:39. (gdb) r Starting program: /usr/local2/dirs/ctm/tmp/move16 Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) c Continuing. 0xffff, Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) Continuing. 0x7777, Breakpoint 1, main (argc=1, argv=0x3fffd3c) at move16.c:39 39 asm volatile("move16 %0@+, %1@+" : "=a" (unused1), "=a" (unused2) : (gdb) Continuing. 0x3333, Notice that the first access is aligned and we get "0xffff," as output, but then we get "0x7777," and "0x3333,". What gives? I don't know and my wife's making me Chile Rellenos for dinner, so I gotta run. If *you* know for sure what's going on and are one of the first to clue me in, I'll get her to make Chile Rellenos for you as well, but you gotta pick them up yourself. --Cliff ctm@ardi.com -- ____________________________________________________________ Peter Eybert pjoe@charon.muc.de Appenzellerstr. 123 Tel: +49-89-7593734 81475 Muenchen (NeXTMail welcome) --
Newsgroups: comp.sys.next.bugs From: ctm@ardi.com Subject: Re: move16 ... Message-ID: <CGup3J.BIM@boa.cs.unm.edu> Sender: news@boa.cs.unm.edu Organization: ARDI References: <CGtKxt.9uL@boa.cs.unm.edu> <1993Nov21.114808.699@charon.muc.de> Date: Sun, 21 Nov 1993 16:42:56 GMT Thank you Peter for dredging that up. I'm volunteering to collate results. If you have black hardware and know enough about gcc and gdb to feel comfortable running the test, could you please do so on as many different configurations as possible and send the results to me (ctm@ardi.com)? Please have only Terminal or Stuart, Workspace and Preferences running and let me know how much physical memory your machine has, what type of machine it is (mono, turbo, color, color-turbo, cube, cube turbo) and what version of NEXTSTEP you're running. --Cliff ctm@ardi.com
Newsgroups: comp.sys.next.bugs From: duvall@sage.wlu.edu (Danek Duvall) Subject: strange behavior w/ xterm Sender: news@liberty.uc.wlu.edu (CNEWS Userid) Message-ID: <1993Nov22.025345.7091@liberty.uc.wlu.edu> Date: Mon, 22 Nov 1993 02:53:45 GMT Organization: Washington & Lee University Hi all, I've been X on an HP, and connecting to a NeXT, but I'm having real problems with missing carriage returns. What happens, is that randomly, when I do some kind of listing (primarily ls, but other things as well), the lines will have a linefeed at the end, but not a carriage return. The first few lines will come out ok, and then the rest stairstep back and forth across the screen. I can't find any pattern to it. Sometimes, an ls will work perfectly, sometimes the last line is screwy, sometimes two thirds is bad, and sometimes all of it is bad. It'll happen twenty times in a row, and then vanish for a few. I'm wondering if there's something wrong with the termcap entry, but I really don't know enough about that to tell offhand. This is *so* annoying!! Does anyone know of this problem? (I hope I'm posting to the right group. This problem has happened, not to me, but to a friend, from a DEC, not using X, so I think it's more likely to be a NeXT problem, if anything.) Also (pushing my luck, I know), in the same situation (telnetting from HP to NeXT under X), ^Z and ^C don't work unless the program specifically captures them (like emacs). I guess this is related somehow ... but how? Thanks for any help, Danek
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.bugs Subject: Re: strange behavior w/ xterm Date: 22 Nov 1993 05:14:20 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <2cphrd$db8@usenet.rpi.edu> References: <1993Nov22.025345.7091@liberty.uc.wlu.edu> duvall@sage.wlu.edu (Danek Duvall) writes: > I've been X on an HP, and connecting to a NeXT, but I'm having real > problems with missing carriage returns. What happens, is that > randomly, when I do some kind of listing (primarily ls, but other > things as well), the lines will have a linefeed at the end, but not a > carriage return. The first few lines will come out ok, and then the > rest stairstep back and forth across the screen. I can't find any > pattern to it. Sometimes, an ls will work perfectly, sometimes the > last line is screwy, sometimes two thirds is bad, and sometimes all of > it is bad. It'll happen twenty times in a row, and then vanish for a > few. I'm wondering if there's something wrong with the termcap entry, > but I really don't know enough about that to tell offhand. > > This is *so* annoying!! Does anyone know of this problem? (I hope > I'm posting to the right group. This problem has happened, not to me, > but to a friend, from a DEC, not using X, so I think it's more likely > to be a NeXT problem, if anything.) You want to put the command: stty -extproc in your .cshrc or .bashrc file of the account on your NeXT. I don't know what extproc does, but for some telnet connections it ends up on when it really needs to be off. -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Newsgroups: comp.sys.next.bugs From: greyham@research.canon.oz.au (Graham Stoney) Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGvoFv.E1s@research.canon.oz.au> Keywords: move16, 68040, exceptions Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia References: <CGq4AL.9sH@research.canon.oz.au> <CGtKxt.9uL@boa.cs.unm.edu> Date: Mon, 22 Nov 1993 05:26:19 GMT ctm@ardi.com writes: >For the record: I don't think this *particular* bug would affect *any* >software written for NS, including Executor. The only way we found it >was when we were comparing our synthetic CPU to a real '040, and that's >when we found the discrepency. In order to trigger this *particular* >bug, you have to issue a move16 with arguments that are not aligned. Well, the problem I've found even hits in normal use when the arguments _are_ aligned; this is a definite worry! I include a test program below which works fine on 2.1, but fails on 3.0 and 3.1; I haven't got access to a 3.2 system yet. I'd really appreciate it if all 68040 black hardware owners could try running it on your available systems and please mail me the output. Don't bother if you've got a 68030 system, since the instruction isn't supported there. The test does a simple linear copy and compare, and always fails on a destination address which is aligned to the start of a page; in other words, on the first access to that page. This strongly suggests that NeXTstep is mishandling page faults generated by move16. The test fails within about the first second when run, but not at the same point each time. Note that this problem effectively renders move16 unreliable and useless. Now it would be really good if I've just made a terrible mistake and this is all just a bad dream, so if that's the case, let the flames start rolling in. But otherwise, it looks a lot like move16 is dead as a dodo on NeXTStep 3.n. Regards, Graham /* COMPILE: cc move16test.c * Test that shows move16 failure under NeXTstep 3.0 & 3.1; works OK on 2.1. */ #include <stdlib.h> #include <assert.h> void m16cpy(unsigned char *dst, const unsigned char *src, int length) { assert(((unsigned long)dst & 15) == 0 && ((unsigned long)src & 15) == 0 && (length & 15) == 0); asm("moveql #16,d1\n" "\tbra LL1\n" "LL0:\tmove16 %0+,%1+\n" "LL1:\tsubl d1,%2\n" "\tbpl LL0" : : "m" (*src), "m" (*dst), "r" (length) : "d1"); } inline void *align(void *p) { return (void *)(((long)p + 15) & ~15); } inline void *alloc(size_t s) { /* leave enough room for alignment */ void *p = malloc(s + 15); if (p == NULL) { fprintf(stderr,"out of memory!\n"); abort(); } return p; } int main() { size_t usize, size; int retval = EXIT_FAILURE; for (usize = 16; usize < 10000000; usize = usize*1.17 + 1) { void *usource, *udest; /* unaligned versions */ unsigned char *source, *dest; int count; size = usize & ~15; fprintf(stderr,"%lu\r", (unsigned long)size); source = align(usource = alloc(size)); dest = align(udest = alloc(size)); /* fill source area */ for (count = 0; count < size; count++) source[count] = count; /* fill dest area with something different */ for (count = 0; count < size; count++) dest[count] = ~count; /* do the copy */ m16cpy(dest, source, size); /* compare the data */ for (count = 0; count < size; count++) { unsigned char d = dest[count], s = source[count]; if (d != s) { printf("destination %2.2x at %p doesn't match " "source %2.2x at %p (count %d) on size %lu\n", (unsigned)d, (void *)&dest[count], (unsigned)s, (void *)&source[count], count, (unsigned long)size); goto error; } } free(usource); free(udest); } printf("move16 test passed!\n"); retval = EXIT_SUCCESS; error: system("hostinfo"); return retval; } -- Graham Stoney, Hardware/Software Engineer Canon Information Systems Research Australia Ph: + 61 2 805 2909 Fax: + 61 2 805 2929
Newsgroups: comp.sys.next.bugs From: duvall@sage.wlu.edu (Danek Duvall) Subject: Re: strange behavior w/ xterm Sender: news@liberty.uc.wlu.edu (CNEWS Userid) Message-ID: <1993Nov22.144446.11029@liberty.uc.wlu.edu> Date: Mon, 22 Nov 1993 14:44:46 GMT References: <1993Nov22.025345.7091@liberty.uc.wlu.edu> <2cphrd$db8@usenet.rpi.edu> Organization: Washington & Lee University Thanks for the responses I got! The first one I tried (the one posted before this article) got rid of my ^C/^Z problem, so that worked. Also, setting 'stty -nl' got rid of the cr/lf problem. Another idea was to rlogin to the NeXTs. That works, too. Thanks, all! Danek
From: sears@uh.edu (Paul S. Sears) Newsgroups: comp.sys.next.bugs Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Date: 22 Nov 1993 19:07:15 GMT Organization: University of Houston Message-ID: <2cr2l3$s6d@menudo.uh.edu> References: <CGvoFv.E1s@research.canon.oz.au> In article <CGvoFv.E1s@research.canon.oz.au> greyham@research.canon.oz.au (Graham Stoney) writes: #ctm@ardi.com writes: #>For the record: I don't think this *particular* bug would affect *any* #>software written for NS, including Executor. The only way we found it #>was when we were comparing our synthetic CPU to a real '040, and that's #>when we found the discrepency. In order to trigger this *particular* #>bug, you have to issue a move16 with arguments that are not aligned. # #Well, the problem I've found even hits in normal use when the arguments _are_ #aligned; this is a definite worry! I include a test program below which works #fine on 2.1, but fails on 3.0 and 3.1; I haven't got access to a 3.2 system #yet. I'd really appreciate it if all 68040 black hardware owners could try #running it on your available systems and please mail me the output. Don't #bother if you've got a 68030 system, since the instruction isn't supported #there. # #The test does a simple linear copy and compare, and always fails on a #destination address which is aligned to the start of a page; in other words, on #the first access to that page. This strongly suggests that NeXTstep is #mishandling page faults generated by move16. The test fails within about the #first second when run, but not at the same point each time. # #Note that this problem effectively renders move16 unreliable and useless. # #Now it would be really good if I've just made a terrible mistake and this is #all just a bad dream, so if that's the case, let the flames start rolling in. #But otherwise, it looks a lot like move16 is dead as a dodo on NeXTStep 3.n. # #Regards, #Graham # # Ok. Here are my results: thanatos> cc move16test.c thanatos> a.out move16 test passed! Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x1 Primary memory available: 20.00 megabytes. Default processor set: 61 tasks, 97 threads, 1 processors Load average: 2.25, Mach factor: 0.38 -- Paul S. Sears * sears@uh.edu (NeXT Mail OK) The University of Houston * suggestions@tree.egr.uh.edu (NeXT Engineering Computing Center * comments, complaints, questions) NeXT System Administration * DoD#1967 '83 NightHawk 650SC >>> SSI Diving Certification #755020059 <<< "Programming is like sex: One mistake and you support it a lifetime."
Newsgroups: comp.sys.next.bugs From: kiwi@belly.in-berlin.de (Axel Habermann) Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGx6u3.4s0@belly.in-berlin.de> Keywords: result Sender: usenet@belly.in-berlin.de Organization: - none - References: <2cr2l3$s6d@menudo.uh.edu> Date: Tue, 23 Nov 1993 01:01:13 GMT [..] My results of the test: belly kiwi 65: cc move16test.c belly kiwi 66: a.out destination 05 at 0x54c000 doesn't match source 50 at 0x3a220 (count 18512) on size 5316048 Mach kernel version: NeXT Mach 3.1: Fri Apr 30 08:31:15 PDT 1993; root(rcbuilder):mk-149.22.3.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x0 Primary memory available: 20.00 megabytes. Default processor set: 82 tasks, 147 threads, 1 processors Load average: 1.83, Mach factor: 0.57 -- Axel Habermann \\|// "Wenn Du nicht kiwi@belly.in-berlin.de (NeXT-Mail) )o o( weisst was Du kiwi@cs.tu-berlin.de (NO NeXT-Mail) \ | / tust, mach's FaxFon: +49 30 4543046 \~/ mit Eleganz!"
Newsgroups: comp.sys.next.bugs From: greyham@research.canon.oz.au (Graham Stoney) Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGxAGt.5zq@research.canon.oz.au> Keywords: move16, 68040, exceptions Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia References: <CGq4AL.9sH@research.canon.oz.au> <CGtKxt.9uL@boa.cs.unm.edu> <CGvoFv.E1s@research.canon.oz.au> Date: Tue, 23 Nov 1993 02:19:40 GMT The test program I posted yesterday requires the following line to be added at the top in order to compile under 3.1: #include <stdio.h> Thanks to everyone who has replied so far; keep those test results rolling in, and if you have any hints or clues what might be going on, please let me know. I haven't had any results from anyone running 3.2 yet, so if you have a 3.2 68040 system, please give the test program a try. Thanks, Graham -- Graham Stoney, Hardware/Software Engineer Canon Information Systems Research Australia Ph: + 61 2 805 2909 Fax: + 61 2 805 2929
From: grw@oahu.cs.ucla.edu (George Wu) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Does fcntl() support the record locking commands ? Message-ID: <1993Nov23.054340.1691@cs.ucla.edu> Date: 23 Nov 93 05:43:40 GMT Distribution: usa Organization: UCLA, Computer Science Department Does anyone know if fcntl() under NEXTSTEP 3.0 support the following commands: F_SETLK F_SETLKW F_GETLK These commands were not mentioned in the man pages for fcntl() but they were in fcntl.h. I tried using the above commands and always got an invalid argument error. So, I suspect that they are not supported but I wanted to make sure this is the case. If the above commands are not supported under NEXTSTEP 3.0, are they supported under NEXTSTEP 3.1 or 3.2 ? A more general question I have is whether NEXTSTEP will become more POSIX-like in the future. I remember hearing that NeXT was going to provide POSIX support but maybe as an add-on option. Is this still true ? George
Newsgroups: comp.sys.next.bugs From: jmack@skye.phys.ualberta.ca Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <1993Nov23.074517.11204@kakwa.ucs.ualberta.ca> Keywords: memory management, compilers Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <2cr2l3$s6d@menudo.uh.edu> Date: Tue, 23 Nov 1993 07:45:17 GMT In article <CGvoFv.E1s@research.canon.oz.au> greyham@research.canon.oz.au (Graham Stoney) writes: > #Well, the problem I've found even hits in normal use when the arguments > _are_ > #aligned; this is a definite worry! I include a test program below which > works > #fine on 2.1, but fails on 3.0 and 3.1; I haven't got access to a 3.2 system > #yet. I'd really appreciate it if all 68040 black hardware owners could try > #running it on your available systems and please mail me the output. Don't > #bother if you've got a 68030 system, since the instruction isn't supported > #there. Ok here are mine: The problem (I think) lies in the fact that stdio.h is not included. I was able to make the problem go away by adding #include <stdio.h> However I only realized this when I tried to compile with gcc rather than the NeXT supplied cc. Additionally this also could depend on which versions of the compilers (of both types) you are using. Note that it fails under 'gcc' but does work under 'cc' with the added include file, so there is something odd about the generic gcc compiler. All of this on the same machine, mind you... 1) original code, without the #include: skye:/TEMP/membug>cc -v Reading specs from /lib/m68k/specs gcc version 1.93 (68k, MIT syntax) skye:/TEMP/membug>cc move16test.c skye:/TEMP/membug>a.out destination 05 at 0xc8000 doesn't match source e0 at 0x7b1b0 (count 284640) on size 314944 Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x0 Primary memory available: 20.00 megabytes. Default processor set: 64 tasks, 96 threads, 1 processors Load average: 0.88, Mach factor: 0.18 ---- 2) OK try gcc (also without the #include - note the error caught) skye:/tmp>gcc -v Reading specs from /usr/local/lib/gcc-lib/next/2.3.3/specs gcc version 2.3.3 skye:/tmp>gcc move16test.c move16test.c: In function `alloc': move16test.c:26: `stderr' undeclared (first use this function) move16test.c:26: (Each undeclared identifier is reported only once move16test.c:26: for each function it appears in.) move16test.c: In function `main': move16test.c:43: `stderr' undeclared (first use this function) (arghh!! :-) ---- 3) So add the include, compile under gcc, and test: skye:/TEMP/membug>gcc move16test.c skye:/TEMP/membug>a.out destination 05 at 0x48000 doesn't match source 20 at 0x22890 (count 75296) on size 104928 Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x0 Primary memory available: 20.00 megabytes. Default processor set: 65 tasks, 97 threads, 1 processors Load average: 0.82, Mach factor: 0.61 ---- 4) re-compile under cc with the include file (just to make sure!) skye:/TEMP/membug>cc move16test.c skye:/TEMP/membug>a.out move16 test passed! Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x0 Primary memory available: 20.00 megabytes. Default processor set: 65 tasks, 97 threads, 1 processors Load average: 1.08, Mach factor: 0.54 Success at last. Also doesn't depend on the board revision. I had initially thought that might be part of the mess. 5) grok this! Ran it again to verify it, but since after the first run I had a rather large swapfile, it failed (for a totally different reason - I'd expect this, of course! -CHECK the page and swap before you run this - you may have to re-boot to have enough free vm to let it run to completion.) skye:/TEMP/membug>a.out destination 04 at 0x30000 doesn't match source 20 at 0x1d480 (count 53792) on size 76656 Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 1 Board revision: 0x0 Primary memory available: 20.00 megabytes. Default processor set: 65 tasks, 97 threads, 1 processors Load average: 1.04, Mach factor: 0.58 My 1.51 cents ($CANADIAN of course) worth. -- James S. MacKinnon Office: P-139 Avahd-Bhatia Physics Lab Computing/Networking Phone : (403) 492-8226 Department of Physics email : jmack@phys.ualberta.ca University of Alberta uucp : uofaphys!jmack iskye!jmack Edmonton, Canada T6G 2N5 bitnet: jmack@triumfcl jsm1@ualtamts
Newsgroups: comp.sys.next.software,comp.sys.next.misc,comp.sys.next.bugs,news.software.readers From: hbu@wag.ch (Hans Burkard) Subject: NewsGrazer crashes... Message-ID: <CGy88x.JF@wag.ch> Keywords: NewsGrazer Sender: usenet@wag.ch Organization: workstation ag, Rohrstr. 36/38, CH-8152 Glattbrugg, Switzerland Date: Tue, 23 Nov 1993 14:29:21 GMT Since weeks I am using NewsGrazer without any problem. However since today NewsGrazer is crashing regulary and I have no idea why! We are using C-News and a local nntp-Server. I know this topic was already discussed. Has anybody a collection of answers? Thanks -Hans- ============================ Hans Burkard workstation ag, Switzerland e-mail: hbu@wag.ch
From: mikep@hack.dragoman.com (Mike Park) Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.sysadmin Subject: Auto reboot after a crash? Date: 23 Nov 1993 17:12:02 -0800 Organization: Hoopy Froods, Inc. Message-ID: <2cucd2$352@hack.dragoman.com> Keywords: crash autoboot reboot 3.1 Does anyone have a kernel hack to allow a 3.1 black hardware machine do an auto-reboot after a crash? I'm sick of finding my machine dead with the "duplicate posix control structure" bug. If it would at least auto-reboot then news and mail would not backlog. There must be an adb kernel hack to make panics do an auto-reboot. Who has it? Mike -- Mike Park mikep@dragoman.com
Newsgroups: comp.sys.next.bugs From: erik@ensuing.com (Erik Kraft) Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Message-ID: <CGzKuK.2nI@ensuing.com> Keywords: 68040 move bug Sender: erik@ensuing.com (Erik Kraft) Organization: Ensuing Technologies Inc. References: <CGxAGt.5zq@research.canon.oz.au> Date: Wed, 24 Nov 1993 07:59:07 GMT In article <CGxAGt.5zq@research.canon.oz.au> greyham@research.canon.oz.au (Graham Stoney) writes: [munch] > I haven't had any results from anyone running 3.2 yet, so if you have a > 3.2 > 68040 system, please give the test program a try. > I got different results depending when I ran the program. It took anywhere from 2 to 20 tries to get the program to exit with a good code. Most of the errors occured right away and around the 50K to 100K count. Once the program made it past 200K, it never failed. I re-compiled the program for each machine in its own /tmp directory. Here are the results for 3 68040 systems running 3.2B: 1) 040 Cube, run twice... oghma:/tmp>a.out destination 06 at 0x30000 doesn't match source 20 at 0x1d480 (count 53792) on size 76656 Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 28.00 megabytes. Default processor set: 68 tasks, 110 threads, 1 processors Load average: 1.83, Mach factor: 0.18 Exit 1 oghma:/tmp>a.out move16 test passed! Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 28.00 megabytes. Default processor set: 68 tasks, 110 threads, 1 processors Load average: 0.77, Mach factor: 0.68 2) Colour Station, run twenty times... satva:/tmp>a.out destination 04 at 0x30000 doesn't match source 00 at 0x44000 (count 49152) on size 65504 Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 3 Board revision: 0x0 Primary memory available: 16.00 megabytes. Default processor set: 38 tasks, 61 threads, 1 processors Load average: 0.20, Mach factor: 0.79 Exit 1 satva:/tmp>a.out move16 test passed! Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 3 Board revision: 0x0 Primary memory available: 16.00 megabytes. Default processor set: 38 tasks, 61 threads, 1 processors Load average: 0.22, Mach factor: 0.77 3) 040 Cube, run eight times bodi:/tmp>a.out destination 04 at 0x90000 doesn't match source 00 at 0x5ffd0 (count 173568) on size 196640 Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 16.00 megabytes. Default processor set: 69 tasks, 109 threads, 1 processors Load average: 1.95, Mach factor: 0.31 Exit 1 bodi:/tmp>a.out move16 test passed! Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 16.00 megabytes. Default processor set: 71 tasks, 111 threads, 1 processors Load average: 0.79, Mach factor: 0.67 > Thanks, > Graham > -- > Graham Stoney, Hardware/Software Engineer > Canon Information Systems Research Australia > Ph: + 61 2 805 2909 Fax: + 61 2 805 2929 -- Erik Kraft e-mail: erik@ensuing.com (NeXT-Mail preferred) I don't talk or post for Ensuing; they don't talk or post for me. NeXT: I STILL believe in the vision and live for the quest. -- Erik Kraft e-mail: erik@ensuing.com (NeXT-Mail preferred) I don't talk or post for Ensuing; they don't talk or post for me. NeXT: I STILL believe in the vision and live for the quest.
From: rfschtkt%banruc60.bitnet@cc1.kuleuven.ac.be Newsgroups: comp.sys.next.bugs Subject: Re: Does fcntl() support the record locking commands ? Date: 24 Nov 1993 17:47:47 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9311242335.AA01990@flexus> See KBNS.11.2.032
Newsgroups: comp.sys.next.bugs From: tobi@swabsib.stgt.sub.org (Tobias Hennerich) Subject: Problems with Cells Message-ID: <1993Nov24.183746.21450@swabsib.stgt.sub.org> Keywords: Cell floatValue strlen lovaleconv Organization: Swabian Siberian Software Solutions Date: Wed, 24 Nov 1993 18:37:46 GMT Hi, we have a lot of problems with Cells, which we want to use in different inspectors. If we try to read or write (float-)values in these cells, the application crashes. On a NS486, it looks like this: Program generated(1): Memory access exception on address 0x0 (protection failure). 0x505eec2 in localeconv () (gdb) where Reading in symbols for PadInspector.m...done. Reading in symbols for CheckBrowserCell.m...done. Reading in symbols for LibraryApp.m...done. Reading in symbols for Library_main.m...done. Reading in symbols for crt0.c...done. #0 0x505eec2 in localeconv () #1 0x609a03f in _NXKitAtoF () #2 0x6099ff2 in -[Cell floatValue] () #3 0x609935e in -[ActionCell floatValue] () #4 0x398c1 in -[PadInspector setPadSize:] (self=0x4814f4, _cmd=0x68934, sender=0x4814f4) at PadInspector.m:770 #5 ... On black hardware it's nearly the same: Program generated(1): Memory access exception on address 0x0 (protection failure). 0x5007194 in strlen () (gdb) where Reading in symbols for PadInspector.m...done. Reading in symbols for CheckBrowserCell.m...done. Reading in symbols for LibraryApp.m...done. Reading in symbols for Library_main.m...done. #0 0x5007194 in strlen () #1 0x5054bb4 in localeconv () #2 0x6089d06 in _NXKitAtoF () #3 0x6089ccc in -[Cell floatValue] () #4 0x608911a in -[ActionCell floatValue] () #5 0x33cfc in -[PadInspector setPadSize:] (self=0x478168, _cmd=0x60189, sender=0x478168) at PadInspector.m:770 #6 ... Some inspectors don't have such problems - if we use such an inspector first, all is working. We have rebuild the inspectors from scratch, same problems. Any comments? Greetings Tobi -- MM <' \__/| \_ _/ ___][___ Tobias.Hennerich@swabsib.stgt.sub.org Leben am Anschlag
Newsgroups: comp.sys.next.bugs From: lloyd@world.std.com (Chris Lloyd) Subject: Re: Problems with Cells Message-ID: <CH11J5.Bp2@world.std.com> Keywords: Cell floatValue strlen lovaleconv Organization: The World Public Access UNIX, Brookline, MA References: <1993Nov24.183746.21450@swabsib.stgt.sub.org> Date: Thu, 25 Nov 1993 02:57:05 GMT In article <1993Nov24.183746.21450@swabsib.stgt.sub.org> tobi@swabsib.stgt.sub.org (Tobias Hennerich) writes: >we have a lot of problems with Cells, which we want to use >in different inspectors. If we try to read or write (float-)values >in these cells, the application crashes. > > Program generated(1): Memory access exception on address 0x0 > (protection failure). >[...] > #0 0x505eec2 in localeconv () > #1 0x609a03f in _NXKitAtoF () > #2 0x6099ff2 in -[Cell floatValue] () > #3 0x609935e in -[ActionCell floatValue] () >[...] >Any comments? I had the exact same problem very recently and tracked it down to the sequence: * [self setFrameUsingName:[self name]]; * [self setFrameAutosaveName:[self name]]; + [self setFrameAutosaveName:NULL]; I had an info panel which inherited the * methods, and later did the + method. Eliminating this sequence, which is unneccesary anyways, fixed it. I would guess there is some interaction in the defaults database, window frame saving, and the float formatting string. I could reproduce it all the time by turning the window frame saving on, then off, then for the first time creating a cell and getting it's float value. I haven't reported this to NeXT yet ... maybe I'll go do an example now... shrug, -- :: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: :: boy, don't we all look _smashing_ in red. ::
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 25 Nov 1993 02:48:50 -0500 Organization: Next Announcements Message-ID: <2d1o12$824@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
From: lee@daruma.zoo.duke.edu (Lee Altenberg) Newsgroups: comp.sys.next.bugs Subject: Edit bug: "Contract All" structure Message-ID: <24304@news.duke.edu> Date: 27 Nov 93 03:30:30 GMT Sender: news@news.duke.edu Organization: Duke University Zoology Dept.; Durham, N.C. For some unknown reason, Edit on my NS/I 3.1 now opens files with the display in the Format/Structure/Contract All mode. So now every time I open a file I have to go to the menu and click Format/Structure/Expand All. Why did this start happening and how do I fix it? Is it something in the Preferences menu that causes this? Thanks, Lee Altenberg altenber@acpub.duke.edu
From: rcfa@cubiculum.com (Ronald C.F. Antony) Newsgroups: comp.sys.next.bugs Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Date: 27 Nov 1993 17:14:58 GMT Organization: NeXT-BUG (NeXT at Brown University Group) Distribution: world Message-ID: <2d81ui$h9h@tunix.cubiculum.com> References: <CGvoFv.E1s@research.canon.oz.au> Keywords: works on 3.2 Except making my disk sound like a chainsaw things worked just fine. Running INN and this program made sure there were plenty of page faults. Ronald ================= tunix> /tmp/test move16 test passed! Mach kernel version: NeXT Mach 3.2: Tue Sep 14 19:25:36 PDT 1993; root(rcbuilder):mk-149.30.12.obj~2/RC_m68k/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 16.00 megabytes. Default processor set: 81 tasks, 117 threads, 1 processors Load average: 0.33, Mach factor: 0.66 ============================================================================== "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." G.B. Shaw ------------------------------------------------------------------------------ rcfa@cubiculum.com rcfa@ANDI.org rcfa@sleepy.cis.brown.edu | NeXT-mail welcome
From: rcfa@cubiculum.com (Ronald C.F. Antony) Newsgroups: comp.sys.next.bugs Subject: Re: move16 worked on NeXTstep 2.1, but it's broken in 3.0 & 3.1. Date: 27 Nov 1993 17:22:17 GMT Organization: NeXT-BUG (NeXT at Brown University Group) Distribution: world Message-ID: <2d82c9$hdu@tunix.cubiculum.com> References: <2d81ui$h9h@tunix.cubiculum.com> Anyone tried to get statistics if that might have to do with compressed swapfiles? The system I ran the test on once (it passed that one time), does NOT have a compressed swapfile. -- Ronald ============================================================================== "The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man." G.B. Shaw ------------------------------------------------------------------------------ rcfa@cubiculum.com rcfa@ANDI.org rcfa@sleepy.cis.brown.edu | NeXT-mail welcome
Newsgroups: comp.sys.next.bugs From: f92-hst@byse.nada.kth.se (Henrik Ståhl) Subject: NS/FIP 3.1 installation problem (Adaptec 1542b) Message-ID: <1993Nov28.100416.28321@kth.se> Sender: usenet@kth.se Organization: Royal Institute of Technology, Stockholm, Sweden Date: Sun, 28 Nov 1993 10:04:16 GMT When trying to install NS/FIP 3.1 on my machine I get the following error messages: aha at 330: mb_init failed AHAController: couldn't set up mailbox area ... No CD-ROM drives found I have an Adaptec 1542b (3.20 BIOS) at the default settings, a Conner 1.3 GB SCSI-2 drive and a NEC CDR 84 drive. I have checked cabling and termination and all works. There are no other cards in my system except for a plain VGA controller (ET4000). Funny thing is, I get it to work if I switch the drive to a 170MB Quantum I have. Only when I hook the Conner up on the SCSI chain do I get this problem. Since the drive is > 1 GB, I have the "sector remapping" (or whatever) jumper installed on my Adaptec. Could this be the problem? I also have a 700 MB DOS partition which maybe could screw things up, but shouldn't that be at a later stage? Please help, this is getting very annoying. Sincerly, Henrik Stahl Royal Institute of technology Stockholm, Sweden f92-hst@nada.kth.se
Newsgroups: comp.sys.next.bugs From: greyham@research.canon.oz.au (Graham Stoney) Subject: 68040 move16 worked on NeXTstep 2.1, but it's broken in 3.0, 3.1 & 3.2. Message-ID: <CH8s0n.Lnz@research.canon.oz.au> Summary: Don't use move16; it doesn't work reliably. Keywords: broken, broken, broken. Sender: news@research.canon.oz.au Organization: Canon Information Systems Research Australia Date: Mon, 29 Nov 1993 07:12:23 GMT Well, thank you everyone who sent me results from the move16test program I posted last week; it confirmed that the 68040 instruction move16 is indeed unreliable in NeXTstep releases 3.0, 3.1 and 3.2. Since it affects even the latest release, I've submitted the following bug report to bug_next. Thanks for your help, Graham ------------------------------------------------------------------------------ move16 on 68040 based black hardware appears to be broken in NeXTstep 3.0, 3.1 and 3.2, which is a worry because we currently use it to generate burst NeXTbus transfers. It works fine on 2.1, but it appears that under 3.X page faults which occur due to a move16 instruction are sometimes mishandled, resulting in the data not being copied correctly to the destination. I include a test program below which works fine on 2.1, but fails on 3.0, 3.1 and 3.2. The problem is intermittent, so the program does not necessarily fail on every run. Many readers of comp.sys.next.bugs have verified this problem; it would certainly be in NeXT's interest to monitor that group; I hope you read it already. The test program does a simple linear copy and compare, and always fails on a destination address which is aligned to the start of a page; in other words, on the first access to that page. This strongly suggests that NeXTstep is mishandling page faults generated by move16. The test usually fails within about the first second when run, but not at the same point each time; it may take longer if you have more RAM, and it sometimes runs successfully to completion but will often fail immediately when run again. Note that this problem effectively renders move16 unreliable and useless. Here is a sample output from a failed run of the test, including my hostinfo: destination 05 at 0xa8000 doesn't match source a0 at 0x66470 (count 240288) on size 269184 Mach kernel version: NeXT Mach 3.0: Wed Jul 29 19:43:28 PDT 1992; root(rcbuilder):mk-127.15/BUILD/RELEASE_M68K Kernel configured for a single processor only. 1 processor is physically available. Processor type: MC680x0 (68040) Processor speed: 25 MHz Processor active: 0 System type: 2 Board revision: 0x0 Primary memory available: 32.00 megabytes. Default processor set: 68 tasks, 108 threads, 1 processors Load average: 3.28, Mach factor: 0.17 [Process exited - exit code 1] Here is the test program; just double-click it on a 68040 machine: [executable deleted] Here is the source; note that this is a very simple test: [source deleted] Could you please inform me of your progress in tracking this bug; I'd be very interested in an official response to this problem. It seems at the moment that the workaround is "move16 is broken: don't use it". Publishing a NeXTanswer stating this would certainly help developers who would otherwise naturally assume that this CPU instruction is reliable. -- Graham Stoney, Hardware/Software Engineer Canon Information Systems Research Australia Ph: + 61 2 805 2909 Fax: + 61 2 805 2929
From: max@cuefa.grenet.fr (max Barel) Newsgroups: comp.sys.next.bugs Subject: CDPlayer summary anyone Date: 30 Nov 1993 16:08:49 GMT Organization: C.I.C.G. , Grenoble Message-ID: <2dfr6hINNs8n@cicg-communication.grenet.fr> I read all posting pertaining to CDPlayer, and checked the FAQ. Could someone summarize the subject since i never read answer on this question (asked on the net). Q: On black hw, with several units on the SCSI bus, CDPlayer give repetitive errors on the console and do not work at all. -- Max Barel max@cuefa.grenet.fr (Next Mail OK)
From: andrewd@sematech.tamu.edu (Andrew Duchowski) Newsgroups: comp.sys.next.bugs Subject: Help: disk won't eject Date: 30 Nov 1993 16:31:41 GMT Organization: Sematech Research, Texas A&M University Distribution: usa Message-ID: <2dfshd$obt@TAMUTS.TAMU.EDU> Hi, I've been away from the c.s.n.* newsgroups for a while, so I might have missed this problem/solution. If it's archived somewhere, please point me in the right direction, and if you don't mind giving me the solution outright, email it along! The problem: My cube ('040, NS3.0) won't eject my 2.8M diskettes when I stick them in the recycler. The directory /NextDisk remains (is not unmounted). I have no idea what the problem is -- I think disks used to get ejected before, but it's been so long I can't remember what I might have done to upset the black box. The disk does get ejected when I log out though. (Is it anything to do with me being a public window server -- I set this so that I can play CDs). Thanks in advance! -- -- Andrew Duchowski | #include <std/disclaimer.h> -- -- | #include <std/apologies.h> -- -- Texas A&M University | #include <std/salutations.h> -- -- andrewd@cs.tamu.edu (NeXTmail ok) | #include <std/asbestos.h> --
From: pedja@cs.umd.edu (& Bogdanovich) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Subprocess exit notification Date: 01 Dec 1993 01:15:04 GMT Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Distribution: world Message-ID: <PEDJA.93Nov30201504@midgard.cs.umd.edu> Does anyone know how to get Subprocess object *reliably* notify of subprocess death? More detailed description of how to replicate the problem is attached. Is there another easy way to get reliable subprocess death notification (other than forking a thread and doing wait4)? Terminal.app works fine: you can open any number of terminal windows and they will all exit when the shell inside dies. Does anyone know what Terminal.app does? Thanks. Pedja <pedja%luka@umiacs.umd.edu> ----------------------------------------------------------------------------- Subprocess exit notification bug exhibited by: Subprocess.m (v10) by Charles L. Oei pty support by Joe Freeman Subprocess Example, Release 2.0 NeXT Computer, Inc. distributed with NS3.1/Motorola, compiled and run under NS 3.1. Good behavior: 1. Launch MyShell.app from workspace. 2. Type exit after $ prompt. What happens: As subprocess exits, DPS invokes fdHandler, we get into -[Subprocess fdHandler:], bufferCount<0 => we get into -[Subprocess childDidExit], and the Subprocess delegate gets subprocessDone message. BAD behavior: Start by logging in. Let define N to be 4. (If you cannot reproduce behavior below, just increase N and eventually you will be able to reproduce it.) 1. Launch MyShell.app. 2. Launch N-1 more MyShell.app copies (Alt-double-click). 3. In the N-th running copy of MyShell.app type exit after $ prompt. What happens: Subprocess exits (one can verify this by doing `ps ux|grep sh' in a Terminal window before and after typing exit), but the Subprocess delegate does NOT get subprocessDone message! (DPS does not invoke fdHandler.) More BAD behavior: 1. Open M<N Terminal windows in Terminal.app. 2. Now you just need to run roughly N-M copies of MyShell.app to get the bad behavior. 1. If the Subprocess object is used in an app which runs N Subprocesses, we get the bad behavior (no exit notification).
From: altenber@acpub.duke.edu Newsgroups: comp.sys.next.bugs Subject: dvips 300dpi Broken in NS/I 3.2 Message-ID: <24502@news.duke.edu> Date: 1 Dec 93 03:23:54 GMT Sender: news@news.duke.edu Organization: Duke University; Durham, N.C. Originator: altenber@carr5.acpub.duke.edu Under NS/I 3.2, dvips breaks when trying to output 300dpi Postscipt: localhost> dvips -D300 test.dvi -o t.ps This is dvips 5.51 Copyright 1986, 1993 Radical Eye Software ' TeX output 1993.11.30:1913' -> t.ps dvips: ! Bad PK file cmmi8.300pk: expected pre Has anyone else had this happen, or been able to fix it? Lee Altenberg altenber@acpub.duke.edu
From: slwdz@cc.usu.edu Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: RTF Source problems in 3.2 Message-ID: <1993Nov30.173451.4922@cc.usu.edu> Date: 30 Nov 93 17:34:51 MDT Organization: Utah State University I have found which could either be considered a bug, or an oversight. I hope it gets "fixed" soon, because it is rather annoying... With 3.2 you can now have RTF source. Way cool. I like it a lot. But...you cannot have RTF header files because then Iterface Builder cannot parse them! Argh! I went through RTF'ing my source...adding nice little links in my headers that will "zap" me to the method in the ".m" file. Very slick. But...alas, interface builder is not smart enough to strip the RTF info when you want to parse back in a header file. Please release a fix? John Zollinger Programmer/Analyst/Network Admin @ Moore BCS slwdz@cc.usu.edu P.S. If there is some work around for this (short of un-RTF'ing my headers) I would like to hear about it.
From: pedja@cs.umd.edu (& Bogdanovich) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: Subprocess exit notification Date: 01 Dec 1993 14:05:41 GMT Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Distribution: world Message-ID: <PEDJA.93Dec1090542@midgard.cs.umd.edu> References: <PEDJA.93Nov30201504@midgard.cs.umd.edu> In-reply-to: pedja@cs.umd.edu's message of 01 Dec 1993 01:15:04 GMT Thanks to all who replied. The bad behavior was caused by master pty not being closed when open() for slave fails in getptys(). Pedja
Newsgroups: comp.sys.next.bugs From: kpompei@netcom.com (Kevin Pompei) Subject: Help! Freezes during shutdown. Message-ID: <kpompeiCHDHHI.Jn0@netcom.com> Organization: NETCOM On-line Communication Services (408 241-9760 guest) Date: Wed, 1 Dec 1993 20:12:53 GMT Recently I upgraded my NS/I system from 16mb RAM to 32mb RAM. When I run it everythings works fine, but when I am shutting down the system hangs during the "Killing all processes" line. This is annoying because it means I have to go through the "Checking Disks" business during startup. At first I thought maybe something happened to my CMOS settings during the upgrade but I've checked them carefully and they are exactly the same as before. BTW, I have a 486DX2-66, 510mb Maxtor, Adaptec 1542C, PAS Sound Card, ATI GUP VLB, AMI BIOS, etc. Thanks, Kevin Pompei kpompei@netcom.com -- kpompei@netcom.com
From: slwdz@cc.usu.edu Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Re: Can't init integer var to zero! Help Message-ID: <1993Dec1.123953.5015@cc.usu.edu> Date: 1 Dec 93 12:39:53 MDT References: <1993Dec1.112316.5003@cc.usu.edu> Organization: Utah State University In article <1993Dec1.112316.5003@cc.usu.edu>, slwdz@cc.usu.edu writes: > I just upgraded to 3.2 and have come across a problem. I cannot initialize an > integer variable to zero. If I do it gives some big hairy integer instead of a > nice round zero. I can set it to 1 o.k., and I know I was able to do this in > 3.1. What gives? To update this a bit. It only does this when I run the "debug" file. The normally compiled app works just fine. What compile flag is causing this? John Zollinger slwdz@cc.usu.edu
From: davec@fa.disney.com Newsgroups: comp.sys.next.bugs Subject: Sybase Administration Date: 1 Dec 1993 17:16:18 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <m0p50gF-000FaOC@dalsdb> Thomas, I read your net mail from Oct 21 regarding using Sybase ports > 5000, and wondered if you could point me to any further documentation about administration, client library, etc. Sybase won't even spend time on the phone without a $7000 per year contract. Although Sybase came bundled with our original NeXT machines years ago, I've only recently attempted an installation. This is no mean feat. So far I managed to get the following error when executing the examp1 sample program, but I'm sure there will be more to come: Msg 4002, level 14, state 1 Login failed DB-Library: Login incorrect Sybase.wn (off the archives) says this error will show up if the sybase user has been setup incorrectly, but what does this mean? Does the Sybase password have to be identical to the Sybase user login password? Do I really have to run the examples in Sybase.wn after logging in as Sybase? Another net mailing suggested fetching the former 3.0 client library if we want to use the original 2.1 version of the server, as they updated the library in 3.1. Can I just reinstall Sybase_DB-Library.pkg from my 3.0 CD-ROM? Has anyone ever written a book entitled something like: "How I Bloodied My Knuckles Installing the NeXT Sybase Server" David Coons Walt Disney Feature Animation davec@fa.disney.com
Newsgroups: comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: New Bug No.39685 - Bug in Distributed Objects Message-ID: <1993Dec1.231915.4329@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. Date: Wed, 1 Dec 1993 23:19:15 GMT This bug concerns Protocols that are not properly encoded in a mixed c++/ObjC compile. This bug appears in both 3.0 and 3.1 and confirmed in 3.2. It has been reported to Bug_NeXT and is assigned 39685. It is illustrated by the following code example. Compile the first like so: cc -o objc protoTest_objc.m Compile the second test like so: cc -ObjC++ -o mixed protoTest_mixed.M When you run these tests, the first one will output the correctly encoded protocol: TestProto @16@8:12@16O@20 Note the correctly encoded "bycopy" as indicated by the "O". The second test, which is ObjC mixed with c++ builds an incorrect encoding. It fails to encode the "bycopy" keyword. TestProto @16@8:12@16@20 The effect of this bug is dramatic. Where you thought objects were being passed by copy, they are in fact being received as proxies. Here's the code. Try it out on 3.2 ======= /* * * protoTest_objc.m * * Bug test to show the correct output of an encoded protocol. The bug * is that "bycopy" is not properly encoded in a mixed compile * (c++ / ObjC) * */ #import <objc/Object.h> #import <objc/Protocol.h> #import <stdio.h> @protocol TestProto - this:(id)hi that:(bycopy id)hello; @end void main() { struct objc_method_description* md; md = [@protocol(TestProto) descriptionForInstanceMethod: @selector(this:that:)]; fprintf(stderr, "%s %s\n", [@protocol(TestProto) name], md->types); } ======= /* * * protoTest_mixed.m * * Bug test to show the incorrect output of an encoded protocol. The bug * is that "bycopy" is not properly encoded in a mixed compile (c++ / ObjC) * */ extern "Objective-C" { #import <objc/Object.h> #import <objc/Protocol.h> } extern "C" { #import <stdio.h> } @protocol TestProto - why:(id)hi that:(bycopy id)hello; @end void main() { struct objc_method_description* md; md = [@protocol(TestProto) descriptionForInstanceMethod: @selector(why:that:)]; fprintf(stderr, "%s %s\n", [@protocol(TestProto) name], md->types); } ==== Valid 3.0 Valid 3.1 Valid 3.2 (unfortunately) Thanks to all who took the time to confirm this bug in 3.2 Brad. -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs From: brad@instep.wimsey.bc.ca Subject: What's the deal with the release scheduling of NeXTSTEP? Message-ID: <1993Dec1.232356.4472@instep.wimsey.bc.ca> Sender: brad@instep.wimsey.bc.ca (Bradley Head) Organization: InStep Mobile Communications Inc. Date: Wed, 1 Dec 1993 23:23:56 GMT NeXTSTEP is suffering from a bad case of feature-itis. Why, under a minor release (3.2), aimed at making NeXTSTEP more robust would NeXT spend resources adding unnecessary features? Take Edit.app for example. RTF source code was added in 3.2. This is cool, but highly unnecessary. Here are some examples of what I would have thought to be necessary "features" (read bug fixes) for NS 3.2. I'll focus on one aspect of NeXTSTEP - The Distributed Object Kit: 1. Fix the bug where in DO, if I pass data across the wire, declared with the keyword "const", such as "const char *", that that data is automatically freed when the method returns (on the remote side). Currently, one has to explicitly free the data passed. This bug conflicts with the documented design of Distributed Objects and Protocols, and restricts your code to be "Distributed Object Aware". This bug was reported since Release 3.0 and as of 3.2 is still not fixed. 2. Fix the bug, just reported by myself, where Protocols are not encoded properly when compiling mixed c++ with Objective-C. In addition, Release 3.1 (and I would assume 3.2) introduced new bugs that have made BSD Release utility programs break. The /usr/bin/calendar program is an example. Others have been cited previously. I used to use calendar quite a bit since Cassandra, Date, et al, are horribly cumbersome apps. calendar did what I wanted - mailed me appointment reminders that I could write into a plain-jane ascii file. Now this doesn't work. I'm steamed. I know it seems trivial, but it's important to me. I paid for software - I expect it to work. What Release of NeXTSTEP do I have to wait for to see these bugs fixed. Release 3.8? Release 4.0? Release 5.0? When? I would like to propose that NeXT adopt a minor release schedule that concentrates on removing known bugs. Perhaps one would send a request to NeXTanswers@next.com to retrieve the latest system patches. It's done with drivers, why not with the Application kit and system utilities? Yeah, I know, bug fixing isn't as glamorous a job as is developing new tools, object kits and apps; but it is very necessary. I spend a considerable amount of my time and my employers money discovering bugs in NeXTSTEP. Yes, it isn't all that much fun. Frustrating is what it is... Brad. -- Bradley Head Software Developer, InStep Mobile Communications Inc. brad@instep.wimsey.bc.ca (NeXTmail accepted) 604 872-7116 fax: 604 872-7125
From: hketola@agsm.ucla.edu (Heikki Ketola) Newsgroups: comp.sys.next.bugs Subject: "Fax later" from PreView fails. Known bug? Date: 2 Dec 1993 07:48:16 GMT Organization: UCLA Microcomputer Support Office Message-ID: <2dk6k1$cod@news.mic.ucla.edu> I noticed a couple of days ago the following weirdness. I saved some Create docs as ps files. I viewed them in PreView and tried to use the "fax later" option. The docs were faxed immediately, not later. A quickie check showed that I was able to "fax later" the original docs (PrintManager showed the fax as waiting for a later transmission). I think this has happened to me a couple of times earlier, but I didn't pay any attention to it. Is this a know bug, or am I just observing some weird random behaviour in my systems (NS 3.1, black, ND)? Heikki
From: robert@steffi.demon.co.uk (Robert Nicholson) Newsgroups: comp.sys.next.bugs Subject: Interesting Workspace occurence Date: 2 Dec 1993 12:21:26 -0000 Organization: me organized? That's a joke! Message-ID: <2dkmk6$12j@steffi.demon.co.uk> Today, I was uncompressing a file thru the workspace's content inspector and the thing just complained that it didn't look like a tar archive and simply removed the file from disc. Nice one.
Message-ID: <+i%@byu.edu> Date: Thu, 2 Dec 93 09:13:58 MST Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Sound Kit strangeness under NS/I Sender: Sean Luke Followup-To: comp.sys.next.programmer Organization: Brigham Young University From: feijai@kolob (Sean Luke) I'm releasing a sound editor in a while, and I'd like to make it available under NS/I, but I only rarely have access to an Intel GX, so I can't determine exactly _what_ these problems are, though my gut feeling is bugs in the Sound Kit as regards NS/I. 1) My editor generates new Sound instances, then records into them. But on intel boxes, the first recording attempt after the program launches results in zero bytes recorded. Is there some flag that needs to be set to wake up the sound driver? 2) Updating information like peak samples in an NXSoundStream or NXSoundDevice is VERY VERY slow--about 2 updates a second. Perhaps this is just the nature of sound hardware without a DSP and custom DACs, but I was wondering if there's a way to get this very fast machine to dedicate more resources to these kinds of updates... 3) The SoundView suffers from a variety of ailments, including bizarre sound display which I think stems from big-little-endian problems. It appears that sounds store their sound information only in big-endian format, and convert the sound when playing out, and this sometimes confuses a SoundView which has been compiled to deal with little-endian formats. 4) While we're on the subject of big-little-endian stupidity, the big-endian bug bites big in my custom modules, most of which mathematically adjust the sound. Since _they've_ been compiled for intel, they too expect the sound data to be little-endian. As a result, simple programs like a sine wave generator produce astonishingly strange amounts of noise instead of a sine wave. 5) Some conversions using NeXT's conversion functions not only don't work in NS/I, they *bomb* the machine! Of course, none of these problems exists in the Black version of my software, which may force me to only release it in Black. I'd hate to do this. Can anyone help? Discounting the bugs, I'd like to know at least if there are functions which 1) Indicate if I'm on big- or little-endian hardware, and 2) Convert chars, shorts, ints, longs, floats, and doubles to big- or little- endian formats. Even if I can't fix (perceived) errors in the Sound Kit, at least I might be able to deal with the endianness in my own code. Can anyone help here? Please reply to the address below (my reply-to header is broken)... Thanks very much, Sean Luke -- -------------------------------------------------------------------- Sean Luke MILK: It Comes From Cows sean@digaudio.byu.edu NeXTmail, MIME OK --------------------------------------------------------------------
From: luomat@alleg.edu (Timothy J. Luoma) Newsgroups: comp.sys.next.bugs Subject: Re: Interesting Workspace occurence Date: 2 Dec 1993 16:19:43 GMT Organization: Allegheny College Distribution: world Message-ID: <2dl4iv$qas@ftp.alleg.edu> References: <2dkmk6$12j@steffi.demon.co.uk> In article <2dkmk6$12j@steffi.demon.co.uk> robert@steffi.demon.co.uk (Robert Nicholson) writes: Today, I was uncompressing a file thru the workspace's content inspector and the thing just complained that it didn't look like a tar archive and simply removed the file from disc. Nice one. The only time I have seen this (and it may have been a separate occurance) was when I ftp'd a 'compressed' file and forgot to set 'binary' before I did so... You're right, thou... very interesting trick... -- Timothy J. Luoma Email: luomat@alleg.edu Allegheny College, Meadville PA USA Using: NS 3.1 Black NeXT Mail Welcomed
From: haker@whitewater.chem.wisc.edu (M Haker) Newsgroups: comp.sys.next.bugs Subject: DriverKit problem (even in 3.2) Date: 2 Dec 1993 20:34:56 GMT Organization: Division of Information Technology Message-ID: <2dljhg$891@news.doit.wisc.edu> Hello All (again), Well I just got 3.2 installed on my machine and converted my driver over to 3.2. It's so close but I've got one little problem: I can't get the data I've collected out of the driver. It's a driver for a data aquisition board, so it operates not by requesting data, but instead you configure and arm the board for external triggers. When an external trigger triggers the board it collects data at which point I need to have the driver send it to the user level program which is controlling the board. I think the only logical way to do this is through a mach port. The problem is I can't figure out how to establish a port connection between a kernel(driver)task and a user task. Here are somethings I've found out so far: - I can't find any driverKit functions to do this - I've tried to get the driver to register a port with "netname_check_in" but it can't find "name_server_port" so it won't compile. And if I include <mach/mach.h> the header definitions conflict with some driverkit headers. - Loadable Kernel Servers (LKS), which the driver kit is a super set of, allow ports to be ADVERTISED by specifying in as a Load Command (appendix A in the writing LKS's manual section) It would make sense to me to have the IODevice and IODeviceMaster be able to establish mach ports between the kernel driver and the user level tasks using the driver with the IODeviceMaster object. Maybe in 3.3. Thanks for any help (please email responses) Michael Haker dept chemistry, UW-Madison haker@whitewater.chem.wisc.edu
From: jgshir@athena.mit.edu (John G Shirlaw) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs Subject: Re: What's the deal with the release scheduling of NeXTSTEP? Date: 3 Dec 1993 05:20:10 GMT Organization: Massachusetts Institute of Technology Distribution: world Message-ID: <2dmiaa$6sk@senator-bedfellow.MIT.EDU> References: <1993Dec1.232356.4472@instep.wimsey.bc.ca> In article <1993Dec1.232356.4472@instep.wimsey.bc.ca>, brad@instep.wimsey.bc.ca writes: |> |> NeXTSTEP is suffering from a bad case of feature-itis. Why, under a minor |> release (3.2), aimed at making NeXTSTEP more robust would NeXT spend |> resources adding unnecessary features? |> |> Take Edit.app for example. RTF source code was added in 3.2. This is cool, |> but highly unnecessary. |> |> Here are some examples of what I would have thought to be necessary |> "features" (read bug fixes) for NS 3.2. I'll focus on one aspect of |> NeXTSTEP - The Distributed Object Kit: |> |> 1. Fix the bugs < various bugs deleted> |> |> In addition, Release 3.1 (and I would assume 3.2) introduced new bugs that |> have made BSD Release utility programs break. < bit deleted> |> I didn't think NeXTStep claimed to be BSD complient, in which case its tough, but then again I don't remember seeing anything that says they are not BSD complient either. |> What Release of NeXTSTEP do I have to wait for to see these bugs fixed. |> Release 3.8? Release 4.0? Release 5.0? When? |> |> I would like to propose that NeXT adopt a minor release schedule that |> concentrates on removing known bugs. Perhaps one would send a request |> to NeXTanswers@next.com to retrieve the latest system patches. It's done |> with drivers, why not with the Application kit and system utilities? NeXT has very rarly given patches out. The drivers and the floppy on 3.0 being the only ones I remember. This may be policy, it would be interesting to know why they don't like patches. |> |> Yeah, I know, bug fixing isn't as glamorous a job as is developing new |> tools, object kits and apps; but it is very necessary. |> So is improving the environment, that after all is what people pay for and as such NeXT has to keep improving the available tools and apps to make the system more atractive than the competition. This activity I'm sure never stops and as such when new tools are ready then they can be released/demoed on the next release. I would be interested to know how many bugs NeXT did fix in 3.2. before I say they haven't been doing there job. Yes I agree it may be unfortunate that they haven't fixed the bugs that most affect you, but I like to give them the benifit of the dought. |> |> |> Brad. just my thoughts john.
From: lparkyn@saturn (Lyle Parkyn) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs Subject: Re: What's the deal with the release scheduling of NeXTSTEP? Date: 3 Dec 1993 05:05:58 GMT Organization: Rogers Communications Distribution: world Message-ID: <2dmhfm$lbb@mail.Rogers.Com> References: <2DEC199312224723@violet.ccit.arizona.edu> In article <2DEC199312224723@violet.ccit.arizona.edu> citdem@violet.ccit.arizona.edu (MCCOLLAM, DON) writes: > Bugs? Wasn't it in 3.0 or 3.1 that support for formatting 2.88 MB > floppies on an external drive "disappeared"? Now in 3.2, you can't > format ANYTHING on an external floppy drive (I believe). Is this true or are you just exaggerating? -- Lyle D. Parkyn (416)250-4810 lparkyn@corpit.cantel.rogers.com NeXT Mail welcome Opinions expressed are my own.
From: nevai@math.ohio-state.edu (Paul Nevai) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: CD-ROM problems on a CUBE with 3.2 Date: 3 Dec 1993 18:42:09 GMT Organization: Department of Mathematics, The Ohio State University Sender: Paul Nevai Message-ID: <2do1a1$ne1@mathserv.mps.ohio-state.edu> Originator: nevai@ops.mps.ohio-state.edu I have a BLACK CUBE with NS 3.2. I did do the "public windowserver" job as suggested by the 3.2 upgrade notes. Still, when I insert a regular music CD, it gets ejected UNLESS I am logged in as root. In addition, when I am root, the CDPlayer.app works with the CD in the player BUT there is no sound. What's going on? Any ideas? Please respond by email. Thanks. Take care...Paul Paul Nevai nevai@math.ohio-state.edu Dept Math - Ohio State University 1-614-292-3317 (Office) Columbus, Ohio 43210-1174, U.S.A. 1-614-292-1479 (Math Dept Fax)
From: bakker@cyclon.aoml.erl.gov (Cary Bakker) Newsgroups: comp.sys.next.bugs Subject: Should an app be able to crash the Window Server??? Date: 4 Dec 1993 21:38:21 GMT Organization: U.S. Department of Commerce, NOAA/AOML Message-ID: <2dr00d$m85@wave.aoml.erl.gov> Just now, an app that I'm working on crashed the window server, and because of that, I was completely logged off. (I'm using a slab) I'm not doing anything wierd, but I know there's a bug in my app.... Should it be able to cause a SIGSEGV for the window server??? It was really screwy, a whole bunch of colors streaked across the screen before it froze and logged me out.... Cary
From: bakker@cyclon.aoml.erl.gov (Cary Bakker) Newsgroups: comp.sys.next.bugs Subject: Possible serious problem with compress...???? Date: 5 Dec 1993 00:34:34 GMT Organization: U.S. Department of Commerce, NOAA/AOML Message-ID: <2draaq$qbl@wave.aoml.erl.gov> Just a few mins ago, I went to compress a project directory.. I realized that I didn't need to yet, so I got the process inspector, and clicked "stop" for compress.. It stopped...and the previous directory re-appeared... But when I went to the directory that I was compressing and tried to run the app, I got a "?" icon...A second later, the directory disappeared. So, after stopping the compress, both the .compressed file *and* the source directory disappeared... I LOST THE WHOLE APP DIRECTORY, SOURCE AND ALL.. ! I tried to reproduce this on a small directory unsuccessfully... I have an older version of the lost app that I will use to try and reproduce this problem with on Mon., but I have no more time today. Obviously, at least the directory or the compressed file should still be around, but it got rid of both... The only thing that came up was a problem with the filenames being too long for gnutar and it said it was giving a @MANGLED name, or something....if you know more about how it handles long filenames with the Mangled stuff, please let me know... Also, tell me if this problem has happened to you with compress...or if it has been posted before, and I simply missed it... I'm using 3.1 on a slab.. If I find out anything else, like the ability to reproduce the problem (I'll try on Mon.), I'll post more info, but this is all I have right now.. Sincerely, Cary A. Bakker
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: Possible serious problem with compress...???? Date: Sun, 5 Dec 1993 05:26:21 -0500 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Message-ID: <4h0PRBm00iUy80ogMf@andrew.cmu.edu> In-Reply-To: <2draaq$qbl@wave.aoml.erl.gov> Excerpts from netnews.comp.sys.next.bugs: 5-Dec-93 Possible serious problem wi.. by Cary Bakker: > The only thing that came up was a problem with the filenames being > too long for gnutar and it said it was giving a @MANGLED name, or > something....if you know more about how it handles long filenames with the > Mangled stuff, please let me know... Without commenting on the rest of what you describe, the @MANGLED stuff is how gnutar deals with file/pathnames longer than the 128 byte limitation of standard Unix tar so that gnutar archives remain compatible with Unix tar. After everything gets extracted, gnutar will correctly rename the @MANGLED files to what they should be. -Chuck Charles William Swiger -- CMU...*splat*! | 1. You can't fly. --------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@cswiger.slip.andrew.cmu.edu | 4. Fire burns.
From: lsloan@umcc.umcc.umich.edu (Lance Sloan) Newsgroups: comp.soft-sys.nextstep,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs Subject: HELP! Problems with terrible terminal emulation! Date: 5 Dec 1993 16:05:46 -0500 Organization: UMCC, Ann Arbor, MI, USA Distribution: inet Message-ID: <2dtifa$1qc@umcc.umcc.umich.edu> I'm a new user to NeXT systems, but semi-experienced with Unix in general. If I login to my friend's NeXT from anyplace other than the console, I always have problems with the terminal types. The most noticeable problem is with carriage returns and linefeeds. I don't always get carriage returns, and output looks like: line 1 line 2 line 3 etc. I've tried different terminals, terminal programs for PCs, and xterms on Sun and HP workstations and I get the same results from all of them. However, using any of the above to connect to ANY OTHER place always looks perfect. Has anybody else seen this problem? Please email me at lsloan@umcc.umich.edu if you have any advice. I will get the OS version and model of workstation I am using and post it here. Thanks in advance! -- Lance Sloan lsloan@umcc.umich.edu
From: kerry@totara.cs.waikato.ac.nz (Kerry Guise) Newsgroups: comp.sys.next.bugs Subject: lockf() under NS3.0 ; does it work ? Date: 6 Dec 1993 06:00:34 GMT Organization: The University of Waikato Message-ID: <2duhq2$1s1i@thebes.cc.waikato.ac.nz> Keywords: lockf I can't seem to make lockf() work properly ; am I missing something or just plain dumb ? The following program always fails (no matter the permissions on the file, whether it is remote or local etc.) : ==================================================== #include <stdio.h> #include <strings.h> #include <sys/errno.h> #include <sys/file.h> #include <sys/fcntl.h> #define NOTOK (-1) extern int errno; int lkopen (file, access) register char *file; register int access; { register int fd, i, j; for (i = 0; i < 2; i++) { j = access; access &= ~O_APPEND; /* make sure we open at the beginning */ if ((access & 03) == O_RDONLY) { access &= ~O_RDONLY; access |= O_RDWR; } if ((fd = open (file, access | O_NDELAY)) == NOTOK) return NOTOK; if (lockf (fd, F_TLOCK, 0L) != NOTOK) return fd; if (errno == EACCES) errno = EWOULDBLOCK; j = errno; (void) close (fd); sleep (5); } (void) close (fd); errno = j; return NOTOK; } FILE * lkfopen (file, mode) register char *file, *mode; { register int fd; register FILE *fp; if ((fd = lkopen (file, strcmp (mode, "r") ? 2 : 0)) == NOTOK) return NULL; if ((fp = fdopen (fd, mode)) == NULL) { (void) close (fd); return NULL; } return fp; } ========================================== main.c ==================== #include <stdio.h> extern FILE *lkfopen(); int main(int argc, char **argv) { FILE *in; if ((in = lkfopen (argv[1], "w")) == NULL) { puts("failed ..."); return 1; } return 0; }
From: srosie@umich.edu (Steven S. Rosenblum) Newsgroups: comp.sys.next.advocacy,comp.sys.next.bugs Subject: Re: What's the deal with the release scheduling of NeXTSTEP? Date: 5 Dec 1993 17:06:25 GMT Organization: University of Michigan -- Ann Arbor Distribution: world Message-ID: <2dt4eh$bil@terminator.rs.itd.umich.edu> References: <2DEC199312224723@violet.ccit.arizona.edu> <2dmhfm$lbb@mail.Rogers.Com> Originator: srosie@dante.ccs.itd.umich.edu In article <2dmhfm$lbb@mail.Rogers.Com> lparkyn@corpit.cantel.rogers.com writes: >In article <2DEC199312224723@violet.ccit.arizona.edu> >citdem@violet.ccit.arizona.edu (MCCOLLAM, DON) writes: >> Bugs? Wasn't it in 3.0 or 3.1 that support for formatting 2.88 MB >> floppies on an external drive "disappeared"? Now in 3.2, you can't >> format ANYTHING on an external floppy drive (I believe). > >Is this true or are you just exaggerating? >-- >Lyle D. Parkyn (416)250-4810 >lparkyn@corpit.cantel.rogers.com NeXT Mail welcome >Opinions expressed are my own. According to the release notes, external floppies on Moto hardware can not be formatted from the workspace. A mention is made of contacting NeXTAnswers for help on this matter. So, to answer your question, Mr. McCollam's statement is not an exageration. -rosie (srosie@umich.edu) (no NeXTMail, Please)
Newsgroups: comp.sys.next.bugs From: kent@infoserv.com Subject: Re: CD-ROM problems on a CUBE with 3.2 Message-ID: <CHJGp8.nB@infoserv.com> Sender: kent@infoserv.com (Kent L. Shephard) Organization: K. L. Shephard Consulting References: <2do1a1$ne1@mathserv.mps.ohio-state.edu> Distribution: na Date: Sun, 5 Dec 1993 01:41:32 GMT In article <2do1a1$ne1@mathserv.mps.ohio-state.edu> nevai@math.ohio-state.edu (Paul Nevai) writes: #I have a BLACK CUBE with NS 3.2. I did do the "public windowserver" job as #suggested by the 3.2 upgrade notes. # #Still, when I insert a regular music CD, it gets ejected UNLESS I am logged #in as root. In addition, when I am root, the CDPlayer.app works with the CD #in the player BUT there is no sound. What's going on? Any ideas? You need to reinstall the software. It needs to be installed by root to work properly. The permission is set wrong on the app. Also no sound indicate that you don't have anyspeakers, etc. hooked up to the CD player. You can't play audio through the NeXT speakers using that app. You also need a CD drive that supports audio over SCSI. Kent -- /* K.L. Shephard Consulting is my company. Infoserv only delivers my mail. */ /* Please direct mail to kent@infoserv.com other adresses may not work. */
Newsgroups: comp.sys.next.software,comp.sys.next.bugs From: jhh@genesis5.physics.yale.edu (Jim Horne) Subject: GatorFTP 1.4 bug? Message-ID: <1993Dec6.172738.24876@cs.yale.edu> Followup-To: comp.sys.next.bugs Sender: news@cs.yale.edu (Usenet News) Organization: Yale Physics Department Date: Mon, 6 Dec 1993 17:27:38 GMT The newest version of GatorFTP (version 1.4) has an annoying, but intermittent bug. I'm running it on a NeXTstation Turbo with 3.0. GatorFTP manages to get the first directory tree properly, but occasionally is unable to get any directory after that. Instead of displaying the file names, it shows first "cd" and then the protection settings for the files (such as -rwxr-wr-w). The only way to unconfuse GatorFTP is to log out and log back in again. Some times this happens numerous times in a row. Anyone know how to fix this? Should I just go back to version 1.3 which did not have this bug? -- Jim Horne jhh@waldzell.physics.yale.edu "With stupidity the gods themselves struggle in vain." Friedrich von Schiller
Newsgroups: comp.sys.next.bugs From: val@proxima.cc.colorado.edu (val veirs) Subject: can't log on Message-ID: <CHMLBz.D8v@csn.org> Sender: news@csn.org (The Daily Planet) Organization: Colorado SuperNet, Inc. Date: Mon, 6 Dec 1993 18:14:22 GMT I have recently upgraded to NeXTStep 3.1 and now every day or two I can't log on. After typing my password I get the 'new mail' box and in a few seconds I am told to login via the standard dialog box. I have to power down and power up before I can complete the login process. Does anyone have any suggestions? thanks a lot, val veirs physics department colorado college colorado springs, co 80903
From: madler@cco.caltech.edu (Mark Adler) Newsgroups: comp.sys.next.bugs Subject: Re: GatorFTP 1.4 bug? Date: 6 Dec 1993 19:56:33 GMT Organization: California Institute of Technology, Pasadena Message-ID: <2e02ph$mnf@gap.cco.caltech.edu> References: <1993Dec6.172738.24876@cs.yale.edu> I believe that I have worked around the problem by waiting for the last ftp command to complete (by watching the command window) before selecting another directory to look at. I think the problem only occurs if you try to initiate a new command before the old one is finished. mark
Newsgroups: comp.sys.next.bugs From: jhh@genesis5.physics.yale.edu (Jim Horne) Subject: Re: GatorFTP 1.4 bug? Message-ID: <1993Dec6.203244.26267@cs.yale.edu> Sender: news@cs.yale.edu (Usenet News) Organization: Yale University, Department of Computer Science, New Haven, CT References: <2e02ph$mnf@gap.cco.caltech.edu> Date: Mon, 6 Dec 1993 20:32:44 GMT In article <2e02ph$mnf@gap.cco.caltech.edu> madler@cco.caltech.edu (Mark Adler) writes: > > I believe that I have worked around the problem by waiting for the > last ftp command to complete (by watching the command window) before > selecting another directory to look at. I think the problem only > occurs if you try to initiate a new command before the old one is > finished. > > mark No, that's a different bug which does indeed get GatorFTP confused. Easy to work around though, either by being patient or using "update directory." The bug I'm talking about was introduced in version 1.4, and results in GatorFTP completely screwing up its file listings and just listing "cd" and the protections. The only way to fix it is to log out. -- Jim Horne jhh@waldzell.physics.yale.edu "With stupidity the gods themselves struggle in vain." Friedrich von Schiller
From: lsloan@montego.umcc.umich.edu (Lance Sloan) Newsgroups: comp.soft-sys.nextstep,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs Subject: SUMMARY: Terrible terminal emulation Date: 6 Dec 1993 19:01:04 -0500 Organization: UMCC, Ann Arbor, MI, USA Distribution: inet Message-ID: <2e0h40$a18@montego.umcc.umich.edu> References: <2dtifa$1qc@umcc.umcc.umich.edu> Summary: telnetd is broke, stty -extproc is undocumented Thanks to all of you who emailed me or followed up to my article about my NeXT terminal emulation problem. For those of you just tuning in, my situation was that I would telnet into my friend's NeXT and newlines would be sent to me as a LF only, not CR/LF. I had tried using different VT-series terminals, PC packages, and xterms on Sun workstations and had this problem on all of them, even when all of those worked fine teletting to ANY other host. (When I used any of the above, if I was going through another Unix host to my destination, TERM and TERMCAP were set correctly before running telnet.) My .login file contained the line: eval `tset -Q -s` And it always got my terminal type right, but it never looked right. I got two good solutions from all these replies: 1. Use rlogin instead of telnet. I was told that telnetd on some NeXT machines is broken, but rlogind is better. I tried this and rlogin does do the trick perfectly. I wonder if there's a telnetd replacement or patch available? 2. stty -extproc If this line is put in my .login, everything looks fine, too. I tried to find extproc in the manpages, but couldn't find it, so I don't know why it works. If you know, PLEASE tell me. Again, thanks for all the info! If you know of a telnetd patch or why "stty -extproc" works, please mail me. -- Lance Sloan lsloan@umcc.umich.edu
Newsgroups: comp.sys.next.bugs From: glen@instep.wimsey.bc.ca Subject: Re: Possible serious problem with compress...???? Message-ID: <1993Dec6.171719.7739@instep.wimsey.bc.ca> Sender: glen@instep.wimsey.bc.ca Organization: InStep Mobile Communications Inc. References: <2draaq$qbl@wave.aoml.erl.gov> Date: Mon, 6 Dec 1993 17:17:19 GMT In article <2draaq$qbl@wave.aoml.erl.gov> bakker@cyclon.aoml.erl.gov (Cary Bakker) writes: > > Just a few mins ago, I went to compress a project directory.. > I realized that I didn't need to yet, so I got the process inspector, and > clicked "stop" for compress.. > It stopped...and the previous directory re-appeared... > > But when I went to the directory that I was compressing and tried to run the > app, I got a "?" icon...A second later, the directory disappeared. > > ...deleted I've had this happen to me with 3.0 on a Next slab. I couldn't find the lost files either. -- Glen Biagioni Software Developer glen@instep.wimsey.bc.ca (small NeXTmail accepted) 604 872-7116 604 872-7125 fax
Newsgroups: comp.sys.next.bugs From: peter@corsica (Peter Eisch) Subject: Re: Possible serious problem with compress...???? Message-ID: <CHn9J7.26F@news2.cis.umn.edu> Sender: news@news2.cis.umn.edu (Usenet News Administration) Organization: University of Minnesota Hospital and Clinic, Laboratory Information Services References: <2draaq$qbl@wave.aoml.erl.gov> <1993Dec6.171719.7739@instep.wimsey.bc.ca> Date: Tue, 7 Dec 1993 02:51:42 GMT glen@instep.wimsey.bc.ca wrote: : In article <2draaq$qbl@wave.aoml.erl.gov> bakker@cyclon.aoml.erl.gov (Cary : Bakker) writes: : > : > clicked "stop" for compress.. : > It stopped...and the previous directory re-appeared... : > : > But when I went to the directory that I was compressing and tried to run : the : > app, I got a "?" icon...A second later, the directory disappeared. : > : > ...deleted : I've had this happen to me with 3.0 on a Next slab. I couldn't find the : lost files either. I had this happen on 3.0 about a year ago as I was putting away some source for a program that is still in production... It's a good thing we haven't needed to do any fixes to it... peter -- Always looking for a handy place to nap... peter@tahiti.umhc.umn.edu (Peter Eisch) peter.a.eisch@uwrf.edu
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to the comp.sys.next.* newsgroups Date: 6 Dec 1993 23:23:17 -0500 Organization: Next Announcements Message-ID: <2e10fl$9lk@digifix.digifix.com> The current menagerie: comp.sys.next.advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. comp.sys.next.announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. comp.sys.next.bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. comp.sys.next.hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. comp.sys.next.marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. comp.sys.next.misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! comp.sys.next.programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. comp.sys.next.software This is a place to talk about [third party] software products that run on NEXTSTEP systems. comp.sys.next.sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups comp.soft-sys.nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. comp.lang.objective-c Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. comp.object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original comp.sys.next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. --------------------------------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe -------------------------------------------------------------------- Written by: Eric P. Scott eps@toaster.SFSU.EDU Minor editing: Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.bugs From: d90-sce@tophat.nada.kth.se (Samuel Cederlund) Subject: NextStep bug? Message-ID: <1993Dec8.004811.18566@kth.se> Keywords: workspace request protocol, remote, NXHost Sender: usenet@kth.se Organization: Royal Institute of Technology, NADA Date: Wed, 8 Dec 1993 00:48:11 GMT The workspace request protocol doesn't seem to work with apps that run remotely using the -NXHost switch. Is this a NeXT bug? cheers, Samuel Cederlund
From: rpopp@ebigek01.ciw.uni-karlsruhe.de (Ruediger Popp) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Q: Floppy Error Message (internal Error 38000) ? Followup-To: comp.sys.next.bugs Date: 8 Dec 1993 09:43:01 GMT Organization: University of Karlsruhe, Germany Message-ID: <2e47j5$qev@nz12.rz.uni-karlsruhe.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Does anybody know what might have happened with the inserted floppy? I inserted it and the Workspace did not mount the floppy but reported an Internal Error 38000. The floppy could not be mounted on several stations running NS3.0. ------- from: /usr/adm/messages ---------------------------- Dec 7 17:17:19 ebigek10 mach: Disk Label: Untitled Dec 7 17:17:19 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; Missing Address Mark: RETRY Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:22 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RECALIBRATE Dec 7 17:17:29 ebigek10 mach: fd0: Sector 224(d) cmd = Read; Missing Address Mark: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RECALIBRATE Dec 7 17:17:41 ebigek10 WM[149]: Unknown error code 38000 in NXReportError Dec 7 17:17:53 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:18:11 ebigek10 syslog: Workspace logged in Dec 7 17:18:43 ebigek10 mach: Disk Label: Untitled Dec 7 17:18:43 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:19:00 ebigek10 WM[164]: Unknown error code 38000 in NXReportError Dec 7 17:19:09 ebigek10 last message repeated 2 times Dec 7 17:19:16 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:19:30 ebigek10 syslog: Workspace logged in Dec 7 17:20:19 ebigek10 mach: Disk Label: Untitled Dec 7 17:20:19 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:20:48 ebigek10 WM[180]: Unknown error code 38000 in NXReportError Dec 7 17:21:02 ebigek10 last message repeated 7 times Dec 7 17:21:08 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:21:25 ebigek10 syslog: Workspace logged in Dec 7 17:21:49 ebigek10 mach: Disk Label: Untitled Dec 7 17:21:49 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:22:22 ebigek10 WM[197]: Unknown error code 38000 in NXReportError Dec 7 17:22:29 ebigek10 last message repeated 3 times Dec 7 17:22:36 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:22:49 ebigek10 syslog: Workspace logged in
From: rpopp@ebigek01.ciw.uni-karlsruhe.de (Ruediger Popp) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Q: Floppy Error Message (internal Error 38000) ? Followup-To: comp.sys.next.bugs Date: 8 Dec 1993 09:43:22 GMT Organization: University of Karlsruhe, Germany Message-ID: <2e47jq$qfd@nz12.rz.uni-karlsruhe.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Does anybody know what might have happened with the inserted floppy? I inserted it and the Workspace did not mount the floppy but reported an Internal Error 38000. The floppy could not be mounted on several stations running NS3.0. ------- from: /usr/adm/messages ---------------------------- Dec 7 17:17:19 ebigek10 mach: Disk Label: Untitled Dec 7 17:17:19 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; Missing Address Mark: RETRY Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:21 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:22 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RECALIBRATE Dec 7 17:17:29 ebigek10 mach: fd0: Sector 224(d) cmd = Read; Missing Address Mark: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RETRY Dec 7 17:17:30 ebigek10 mach: fd0: Sector 224(d) cmd = Read; DMA Over/underrun: RECALIBRATE Dec 7 17:17:41 ebigek10 WM[149]: Unknown error code 38000 in NXReportError Dec 7 17:17:53 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:18:11 ebigek10 syslog: Workspace logged in Dec 7 17:18:43 ebigek10 mach: Disk Label: Untitled Dec 7 17:18:43 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:19:00 ebigek10 WM[164]: Unknown error code 38000 in NXReportError Dec 7 17:19:09 ebigek10 last message repeated 2 times Dec 7 17:19:16 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:19:30 ebigek10 syslog: Workspace logged in Dec 7 17:20:19 ebigek10 mach: Disk Label: Untitled Dec 7 17:20:19 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:20:48 ebigek10 WM[180]: Unknown error code 38000 in NXReportError Dec 7 17:21:02 ebigek10 last message repeated 7 times Dec 7 17:21:08 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:21:25 ebigek10 syslog: Workspace logged in Dec 7 17:21:49 ebigek10 mach: Disk Label: Untitled Dec 7 17:21:49 ebigek10 mach: Disk Capacity 1440 KB, Device Block 512 bytes Dec 7 17:22:22 ebigek10 WM[197]: Unknown error code 38000 in NXReportError Dec 7 17:22:29 ebigek10 last message repeated 3 times Dec 7 17:22:36 ebigek10 -[143]: loginwindow: Workspace exited ts 0 cd 0 rc 0 sv 0 ss 0. Dec 7 17:22:49 ebigek10 syslog: Workspace logged in
From: giddings@sadie.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs Subject: Upgrade to 3.2 broke the keyboard! Date: 8 Dec 1993 15:11:11 GMT Organization: Division of Information Technology Distribution: world Message-ID: <2e4qqf$2dk@news.doit.wisc.edu> Keywords: 3.2 nextstep keyboard I upgraded a Toshiba 4400C (20 MB RAM/200 MB HD/486-25DX) yesterday to 3.2. There was a little surprise: during the boot process, the CapsLock and NumLock lights light up and the keyboard freezes. It is useable at the pre-boot prompt, so it is not a hardware failure, but when the log in window comes up it is completely unusable. This configuration is listed in the 3.2 compatibility guide, so the behavior seems strange. It happens when booted with "config=Default" as well. It worked fine in 3.1. Any ideas as to how to fix this, or how to "downgrade" back to 3.1 would be appreciated. Thanks, Michael Giddings UW Madison Chemistry
From: Mark Crispin <mrc@Tomobiki-Cho.CAC.Washington.EDU> Newsgroups: comp.sys.next.bugs Subject: re: lockf() under NS3.0 ; does it work ? Date: Wed, 8 Dec 1993 19:48:42 -0800 Organization: University of Washington Message-ID: <MS-C.755408922.1147902781.mrc@Tomobiki-Cho.CAC.Washington.EDU> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII To: Kerry Guise <kerry@totara.cs.waikato.ac.nz> In-Reply-To: <2duhq2$1s1i@thebes.cc.waikato.ac.nz> No, lockf() does not work under NEXTSTEP since the underlying fcntl() functionality is missing. It may work under 3.2; I haven't checked yet.
From: obsta@nvtcp1.esm.vt.edu (Andreas Obst) Newsgroups: comp.sys.next.bugs Subject: Re: GatorFTP 1.4 bug? Date: 9 Dec 1993 14:41:09 GMT Organization: Virginia Tech, Blacksburg, Virginia Distribution: world Message-ID: <2e7de5$rui@vtserf.cc.vt.edu> References: <1993Dec6.203244.26267@cs.yale.edu> In article <1993Dec6.203244.26267@cs.yale.edu> jhh@genesis5.physics.yale.edu (Jim Horne) writes: > In article <2e02ph$mnf@gap.cco.caltech.edu> madler@cco.caltech.edu > (Mark Adler) writes: > > stuff deleted > > The bug I'm talking about was introduced in version 1.4, and results in > GatorFTP completely screwing up its file listings and just listing "cd" > and the protections. The only way to fix it is to log out. > > -- > Jim Horne jhh@waldzell.physics.yale.edu > > "With stupidity the gods themselves struggle in vain." > Friedrich von Schiller This happened to me a couple of times, too. But only on some archive sites. In most cases it has to do with some informational messages that are sent from the archive site. These can be usually turned off by using a dash (-) as the first character of the password. Whenever I run into an archive site, that lists only cd and protections on the first try, I log out again and then log in with dash (-) as the first character of the password and that usually works. You should read some of the informational messages that are send by the archve sites. Here is an example from the university of stuttgart archive site. After login as anonymous the following message was displayed: 331 Guest login ok, send your complete e-mail address as password. 230- PROBLEMS 230- If your FTP client crashes or hangs shortly after login please try 230- using a dash (-) as the first character of your password.This will 230- turn off the informational messages that may be confusing your FTP 230- client. 230- 230- Hope that helps -- Andreas Obst (obsta@nvtcp1.esm.vt.edu) Department of Engineering Science and Mechanics Virginia Tech of the password. Whenever I run into an archive site, that lists only cd and protections on the first try, I log out again and then log in with dash (-) as the first character of the password and that usually works. You should read some of the informational messages that are send by the archve sites.
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs Subject: ProAudio + ISA in NS/I 3.2 Date: 9 Dec 1993 11:40:38 +0100 Organization: Palumbian Research Labs Message-ID: <2e6vb6$90@marsu.tynet.sub.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Hi, after a few days of experimenting with NS/I 3.2, I must state that the ProAudio does not work reliably on ISA machines. I checked it in combination with an Adaptec 1542 C as well as with a DPT 2021 SCSI controller at various DMA/IRQ settings. The result is always the same: Sound works quite fine for a while, but suddenly the bus freezes, the SCSI controller claims to be busy (at least the LED) and the only thing left to do is "press reset to continue" :-(((( Usually, this event happens if you don't expect it at all, e.g. at system beeps. It makes me very sad. Purchasing an EISA board is the NeXT STEP for me to do. After spending a lot of money for a ProAudio, a microphone and loudspeakers, I WANT IT GOING!!!! Maybe some folks with EISA boards could post here if sound works on their machines reliably. Regards, Markus. -- Marsu: "Es gibt tatsaechlich Leute, die ohne Computer gluecklich und zufrieden leben." -- Frankie: "Ach was, die emulieren das doch nur!" ----- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Intel aside.
Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs From: Karl_Kraft@ensuing.com Subject: Formatting an external floppy NS 3.1 Message-ID: <CHtBL2.58o@ensuing.com> Sender: karl@ensuing.com (Karl Kraft) Organization: Ensuing Technologies Inc. Date: Fri, 10 Dec 1993 09:27:02 GMT Using NeXTSTEP 3.1, I cannot format in my external PLI floppy drive. This is the message that appears in the console: --------- /usr/etc/disk -i -h oghma -l "Floppy" /dev/rsd1a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi device = /dev/rsd1a block size = 512 capacity = 1 MBytes Disk Format in progress... ***Format Complete*** writing disk label boot block extends beyond front porch -------- I looked through the last six months of the various csn groups, but could only find various posters with the same problem. Did anyone ever find a work around for this problem? -- _________ Karl Kraft Karl_Kraft@ensuing.com (NeXT mail)
From: geom2@sfb256.iam.uni-bonn.de ( Michael Moellney ) Newsgroups: comp.sys.next.bugs Subject: NFS Problems with two 3COM EtherLink III Date: 10 Dec 1993 22:15:37 GMT Organization: Applied Math, University of Bonn, Germany Distribution: world Message-ID: <2ease9$5ap@news.rhrz.uni-bonn.de> Keywords: 3COM Etherlink III, NFS Hi! I just upgraded 2 intel boxes to 3.2 and having problems with NFS. In each box there is a 3COM Etherlink III NetCard. One box exports a directory, the other mounts that directory. mounting works fine, but ... Every 2-20 sec the NFS Server doesn't respond for more than 2 Minutes... OK, it works stable, no en0: timeouts like in 3.1, but no data also. The funny thing is, using 'ping' from the server to the client seems to awake the NFS Server. When the Server hangs, the first pingtime is around 2000 ms(the machines are hooked to the same ethernetline), the 2nd time is around 1000ms, the 3rd is 2ms (thats fine) and NFS works again, for 5 seconds.. So did anybody else have this problem??? Do you have any suggestion, what's wrong??? Any hint's ?? Bye, Michael
Newsgroups: comp.sys.next.bugs From: fabien@free.fdn.org (Fabien Roy) Subject: Re: Formatting an external floppy NS 3.1 Message-ID: <1993Dec10.174505.19810@free.fdn.org> Sender: news@free.fdn.org Organization: Fabien Roy Electronic Engineering (F.R.E.E.) - Paris, France. References: <CHtBL2.58o@ensuing.com> Date: Fri, 10 Dec 1993 17:45:05 GMT In comp.sys.next.bugs article <CHtBL2.58o@ensuing.com> you wrote: > Using NeXTSTEP 3.1, I cannot format in my external PLI floppy drive. > > This is the message that appears in the console: > > --------- > /usr/etc/disk -i -h oghma -l "Floppy" /dev/rsd1a > disk name: PLI SUPER FLOPPY > disk type: removable_rw_scsi > device = /dev/rsd1a block size = 512 capacity = 1 MBytes > Disk Format in progress... > ***Format Complete*** > writing disk label > boot block extends beyond front porch > -------- > > I looked through the last six months of the various csn groups, > but could only find various posters with the same problem. > Did anyone ever find a work around for this problem? > > -- > _________ > Karl Kraft > Karl_Kraft@ensuing.com (NeXT mail) My guess: You will have to make an entry in /etc/disktab like this one ( I can't test it because i don't own a PLI Floppy) pli|PLI:\ :ty= removable_rw_scsi:nc#80:nt#2:ns#9:ss#1024:rm#300:\ :fp#96:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=odmach:z0#-1:z1#32:ro=a:\ :pa#0:sa#1344:ba#8192:fa#1024:ca#32:da#2048:ra#0:oa=space:ia:ta=4. 3BSD:aa: then run: /usr/etc/disk -t pli -i -h oghma -l "Floppy" /dev/rsd1a Cheers --Fabien --------------------------------------------------------------------- Fabien_Roy@free.fdn.org (NextMails accepted) Fabien Roy Electronic Engineering 3 rue ANDRE DANJON, 75019 PARIS, France, Tel: 33 1 4040 0206 Fax: 33 1 4040 0641
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs Subject: Re: Upgrade to 3.2 broke the keyboard! Date: 11 Dec 1993 18:11:01 +0100 Organization: Palumbian Research Labs Message-ID: <2ecuv5$3ti@marsu.tynet.sub.org> References: <2e4qqf$2dk@news.doit.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Keywords: 3.2 nextstep keyboard giddings@sadie.chem.wisc.edu (Michael Giddings) writes: >I upgraded a Toshiba 4400C (20 MB RAM/200 MB HD/486-25DX) yesterday to 3.2. >There was a little surprise: during the boot process, the CapsLock and NumLock >lights light up and the keyboard freezes. It is useable at the pre-boot >prompt, so it is not a hardware failure, but when the log in window comes up >it is completely unusable. >This configuration is listed in the 3.2 compatibility guide, so the behavior >seems strange. It happens when booted with "config=Default" as well. It >worked fine in 3.1. >Any ideas as to how to fix this, or how to "downgrade" back to 3.1 would be >appreciated. I had exactly the same problem. A friend of mine did a little kernel debugging, and he found the reason: some PC keyboards do not respond quickly enough to the kernel's initialization inquiry. The fix is simply to comment out the entire keyboard init stuff - it just works for me! gdb mach_kernel, x/30i 0x1812dc should show you the following: #Adress Opcode MustBe 001812dc pushl %ebp ---> ret ($c3) nop ($90) 001812dd movl %esp,%ebp 001812df pushl %ebx 001812e0 movb $0x01,0x001caea8 001812e7 pushl $0x64 001812e9 calll _inb 001812ee addl $0x04,%esp 001812f1 testb $0x21,%al Display the bytes with x/30b 0x1812dc, search for them with a binary editor (e.g. emacs 19.xx or even a DOS one) and change the first two bytes of the section to $c3 $90. Then copy the patched mach_kernel file to the boot disk with cp (not from Workspace Manager, which calculates the required space too big for the boot disk). Reboot - voila! Don't forget to substitute the patched kernel once again after installation, because the kernel is installed from the CD, and you have to patch this one, too. Best idea is to keep a copy of the patched kernel on a second hard disk, from which you can easily replace the CD-ROM kernel after booting from the boot disk. Good luck, Markus. -- Marsu: "Es gibt tatsaechlich Leute, die ohne Computer gluecklich und zufrieden leben." -- Frankie: "Ach was, die emulieren das doch nur!" ----- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Intel aside.
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to NEXTSTEP information on the Internet Date: 13 Dec 1993 00:31:46 -0500 Organization: Next Announcements Message-ID: <2eguo2$e4c@digifix.digifix.com> This post is made weekly, to help 'point' users to more NEXTSTEP information Topics include: comp.sys.next newsgroups related newsgroups comp.sys.next newsgroups mailing list ftp sites NeXTanswers comp.sys.next.* newsgroups -------------------------- Comp.Sys.Next.Advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. Comp.Sys.Next.Announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. Comp.Sys.Next.Bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. Comp.Sys.Next.Hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. Comp.Sys.Next.Marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. Comp.Sys.Next.Misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! Comp.Sys.Next.Programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. Comp.Sys.Next.Software This is a place to talk about [third party] software products that run on NEXTSTEP systems. Comp.Sys.Next.Sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups ------------------ Comp.Soft-Sys.Nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. Comp.Lang.Objective-C Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. Comp.Object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original Comp.Sys.Next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Getting the Newsgroups without getting News ------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe The ftp sites ------------- cs.orst.edu: The main site for North American submissions nova.cc.purdue.edu: Lots of older stuff, but very short on disk space ftp.informatik.uni-muenchen.de: In Germany. ftp.next.com: See the below ftp.next.com and NextAnswers@next.com ------------------------------------- From the document 1000_Help from ftp.next.com Welcome to the NeXTanswers information retrieval system! This system allows you to request online technical documents, drivers, and other software, which are then sent to you automatically. You can request documents by fax or Internet electronic mail, or you can transfer them by anonymous ftp. NeXTanswers is an automated retrieval system. Requests sent to it are answered electronically, and are not read or handled by a human being. NeXTanswers does not answer your questions or forward your requests. USING NEXTANSWERS BY E-MAIL To use NeXTanswers by Internet e-mail, send requests to NeXTanswers@next.com. Files are sent as NeXTmail attachments by default; you can request they be sent as ASCII text files instead. To request a file, include that file's ID number in the Subject line or the body of the message. You can request several files in a single message. You can also include commands in the Subject line or the body of the message. These commands affect the way that files you request are sent: ASCII causes the requested files to be sent as ASCII text SPLIT splits large files into 95KB chunks, using the MIME Message/Partial specification These commands return information about the NeXTanswers system: HELP returns this help file INDEX returns the list of all available files INDEX BY DATE returns the list of files, sorted newest to oldest SEARCH keywords lists all files that contain all the keywords you list (ignoring capitalization) For example, a message with the following Subject line requests three files: Subject: 2101 2234 1109 A message with this body requests the same three files be sent as ASCII text files: 2101 2234 1109 ascii This message requests two lists of files, one for each search: Subject: SEARCH Dell SCSI SEARCH NetInfo domain NeXTanswers will reply to the address in your From: line. To use a different address either set your Reply-To: line, or use the NeXTanswers command REPLY-TO <your-address> If you have any problem with the system or suggestions for improvement, please send mail to NeXTanswers-request@NeXT.com. USING NEXTANSWERS BY FAX To use NeXTanswers by fax, call (415) 780-3990 from a touch-tone phone and follow the instructions. You'll be asked for your fax number, a number to identify your fax (like your phone extension or office number), and the ID numbers of the files you want. You can also request a list of available files. When you finish entering the file numbers, end the call and the files will be faxed to you. If you have problems using this fax system, please call Technical Support at 1-800-848-6398. You cannot use the fax system outside the U.S & Canada. USING NEXTANSWERS BY ANONYMOUS FTP To use NeXTanswers by Internet anonymous FTP, connect to FTP.NEXT.COM and read the help file pub/NeXTanswers/README. If you have problems using this, please send mail to NeXTanswers-request@NeXT.com. Written by: Eric P. Scott eps@toaster.SFSU.EDU and Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs From: sengwil@duc.auburn.edu (William F. Seng) Subject: Re: Formatting an external floppy NS 3.1 Message-ID: <sengwil.931212233150@lab12.duc.auburn.edu> Sender: usenet@news.duc.auburn.edu (News Account) Organization: Auburn University, Alabama References: <CHtBL2.58o@ensuing.com> Date: Mon, 13 Dec 1993 05:31:50 GMT I had the same problem formatting a disk in my PLI external drive on my cube as well. The cheesy solution is to substitute the /usr/etc/disk program from a 3.0 release of NeXTStep. That's what I did, and everythying ran hunky dory. I just installed 3.2 on a new hard drive, and so the /usr/etc/disk that I am now testing as I speak is the one that arrived with 3.2 ..... Will it work...? (chomp...chomp....chomp......) Nope 3.2 /usr/etc/disk says exactly what 3.1 /usr/etc/disk said: /usr/etc/disk -i -h qb2 -l "WhosCalling" /dev/rsd2a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi device = /dev/rsd2a block size = 512 capacity = 1 MBytes Disk Format in progress... ***Format Complete*** writing disk label boot block extends beyond front porch So, it looks like I'll now implement the same fix as I did before - install the 3.0 version of /usr/etc/disk and be happy Hope this helps! - Bill
From: scheurer@lithnext.epfl.ch (Marco Scheurer) Newsgroups: comp.sys.next.bugs Subject: 3.2 Workspace Manager bug? Date: 13 Dec 1993 14:16:32 GMT Organization: Ecole Polytechnique Federale de Lausanne Message-ID: <2ehtg0$bg5@disuns2.epfl.ch> Hi, Is it me or is there an horrible bug in the Workspace Manager with 3.2? It seems that sometime you cannot type a new filename for a file, because it is automatically selected at more or less random interval, while you type, so you are always destroying what your are typing. I don't know what make this bug appear, but once it is here, it is for good, ie I don't know what to do to make it go away. This makes WSM useless for changing filenames! That's sad, because until then, it was pretty stable. I do not think I have seen this discussed before, so I'm wondering: did I miss it, or has nobody seen this before? One more thing: I suspect this has to do with the network, because an isolated NeXTstation does not exhibit this behavior. Looks like I should BugNeXT... --- Marco Scheurer scheurer@lithnext.epfl.ch (NeXTMail) Laboratoire d'Informatique Theorique Ecole Polytechnique Federale de Lausanne IN-Ecublens CH-1015 Lausanne (Switzerland) (+41) 21 693-2589
From: kay@nagasena Newsgroups: comp.sys.next.bugs,de.comp.sys.next Subject: 3.2 NSI Experiences Date: 12 Dec 93 10:24:32 Organization: Firestone Chaotic Group Distribution: fj Message-ID: <kay.93Dec12102432@nagasena> Mime-Version: 1.0 Content-Type: text/plain Downgrading When you use 3.2 it is necessary that you have 3.1 so that you can downgrade the system. This is what I think after 3 days using NSI 3.2 I use: 486/66 ASUS EISA, ISA, VLB 32 MB RAM ATI GUP 2 MB VLB 1 GB HD Toshiba 3401 extern Archive Viper Streamer ZyXEL Modem First of all, I couldn't boot. I never had any problems with it, now I had. He had problems to find my Adaptec 1542B. I rebooted and everything worked. Strange. Then I installed everything. SoftPC and TeX weren't installed. I did it my own. Then I rebooted so that the system can find my tape (why isn't it in the SCSI box of the Configure.app?). I got failures because of my floppy countroller. I use an Adaptec 1542B and nothing else, no onboard controller. And with 3.1 it worked fine. Now, not floppy with NSI 3.2. Very very bad. Upgrading means that all things which should not work with 3.1 but did now don't work really? Very very strange. If I mount a CD I get the following message in the console: Dec 12 09:23:05 Workspace: Mounted floppy disk at /NEXTSTEP_3.2 FOr me as a beginner, it is very confusing. So now, I have no disk When I wanted to see the performance I started BenchPress, what I like very much. The system crashes.At 100 threads testing. In 3.1 it worked properly. Reboot! And then: Can't find Adaptec at 330h! Suddenly. I didn't touch the system. Reboot! Everything ok. When the system comes up, and is registering the keyboard, I had to press return once with 3.1! Now I have to press Return twice. I am anxious to get NSI 4.0 or 5.0 later on. They I need to press is how many times! The serial drivers I am not still sure, but it looks they are not better or equal to the updated of 3.1 I read a long article of Conrad Geiger about the GNUtools which are included.... What is included is 1% of all the wonderful GNUtools. Even patch (very necessary) is not included. No new emacs. GCC 2.2.2 :-) This is really true, no joke. We have 2.5 now and we have 2.3.5 since beginning of 1993! Nothing else to say to that. I hoped to get a nearly full archive of the nearly newest GNUtools. Probably from June, but not from 1990! With emacs and so on. EMACS? I use Emacs.app with 3.1 and it worked great. With 3.2 it doesn't any more. After typing a few letters it kills itself. Who knows why? The wishes of myself also were to be able to listen to audio CDs, to see PhotoCDs and to fax. Some tell me it works, some sned me XAmode for PhotoCD ... So it works on some people, on some it doesn't (on mine). My SCSI IDs are: HD 0 Streamer 1 CDROM 6 XAmode says XAmode: Error during command-execution Audio CD kills nearly my system.... It takes hours to stop the App and come back to normal work. I bought the expensive Toshiba 3401, because I wanted to do all that. The good sides: The sound works better. The multitasking is much better than before, so I can work and listen to the sound files. Before it was incredible. The graphic performance is much better! Scrolling, moving windows and so on! SoftPC is wonderful! Since I don't need SoftPC and Sound ( although I would like) I will go back to 3.1 next week (one week left to give NSI the chance to do his work better). If all this shit arises again, I donwgrade to 3.1 and know that this is more stable and I know where the bugs are. ANd how to reproduce them! A user, who was a fanatic NS friend, who always defended NeXT and who waited like a horny cat of 3.2 and who is incredible sad now. --- Kay Schulz 08142/58727 kay@nagasena.muc.de NeXTmail accepted
From: kay@nagasena.muc.de (Kay Schulz) Newsgroups: comp.sys.next.bugs Subject: 3.2 NSI Experiences Date: 12 Dec 1993 12:23:30 +0100 Organization: Firestone Chaotic Group Message-ID: <2eeuvi$m0@nagasena.muc.de> Downgrading When you use 3.2 it is necessary that you have 3.1 so that you can downgrade the system. This is what I think after 3 days using NSI 3.2 I use: 486/66 ASUS EISA, ISA, VLB 32 MB RAM ATI GUP 2 MB VLB 1 GB HD Toshiba 3401 extern Archive Viper Streamer ZyXEL Modem First of all, I couldn't boot. I never had any problems with it, now I had. He had problems to find my Adaptec 1542B. I rebooted and everything worked. Strange. Then I installed everything. SoftPC and TeX weren't installed. I did it my own. Then I rebooted so that the system can find my tape (why isn't it in the SCSI box of the Configure.app?). I got failures because of my floppy countroller. I use an Adaptec 1542B and nothing else, no onboard controller. And with 3.1 it worked fine. Now, not floppy with NSI 3.2. Very very bad. Upgrading means that all things which should not work with 3.1 but did now don't work really? Very very strange. If I mount a CD I get the following message in the console: Dec 12 09:23:05 Workspace: Mounted floppy disk at /NEXTSTEP_3.2 FOr me as a beginner, it is very confusing. So now, I have no disk When I wanted to see the performance I started BenchPress, what I like very much. The system crashes.At 100 threads testing. In 3.1 it worked properly. Reboot! And then: Can't find Adaptec at 330h! Suddenly. I didn't touch the system. Reboot! Everything ok. When the system comes up, and is registering the keyboard, I had to press return once with 3.1! Now I have to press Return twice. I am anxious to get NSI 4.0 or 5.0 later on. They I need to press is how many times! The serial drivers I am not still sure, but it looks they are not better or equal to the updated of 3.1 I read a long article of Conrad Geiger about the GNUtools which are included.... What is included is 1% of all the wonderful GNUtools. Even patch (very necessary) is not included. No new emacs. GCC 2.2.2 :-) This is really true, no joke. We have 2.5 now and we have 2.3.5 since beginning of 1993! Nothing else to say to that. I hoped to get a nearly full archive of the nearly newest GNUtools. Probably from June, but not from 1990! With emacs and so on. EMACS? I use Emacs.app with 3.1 and it worked great. With 3.2 it doesn't any more. After typing a few letters it kills itself. Who knows why? Always after the 21st character! :-) The wishes of myself also were to be able to listen to audio CDs, to see PhotoCDs and to fax. Some tell me it works, some sned me XAmode for PhotoCD ... So it works on some people, on some it doesn't (on mine). My SCSI IDs are: HD 0 Streamer 1 CDROM 6 XAmode says XAmode: Error during command-execution Audio CD kills nearly my system.... It takes hours to stop the App and come back to normal work. I bought the expensive Toshiba 3401, because I wanted to do all that. The good sides: The sound works better. The multitasking is much better than before, so I can work and listen to the sound files. Before it was incredible. The graphic performance is much better! Scrolling, moving windows and so on! SoftPC is wonderful! Since I don't need SoftPC and Sound ( although I would like) I will go back to 3.1 next week (one week left to give NSI the chance to do his work better). If all this shit arises again, I donwgrade to 3.1 and know that this is more stable and I know where the bugs are. ANd how to reproduce them! A user, who was a fanatic NS friend, who always defended NeXT and who waited like a horny cat of 3.2 and who is incredible sad now. -- Kay Schulz 08142/58727 kay@nagasena.muc.de NeXTmail accepted
Newsgroups: comp.sys.next.bugs From: mshaler@tdocad.sps.mot.com (Michael Shaler) Subject: Re: 3.2 Workspace Manager bug? Message-ID: <1993Dec13.191908.6245@newsgate.sps.mot.com> Sender: news@newsgate.sps.mot.com Organization: sps References: <2ehtg0$bg5@disuns2.epfl.ch> Date: Mon, 13 Dec 1993 19:19:08 GMT Marco Scheurer writes Hi, Is it me or is there an horrible bug in the Workspace Manager with 3.2? It seems that sometime you cannot type a new filename for a file, because it is automatically selected at more or less random interval, while you type, so you are always destroying what your are typing. [crunch] Yep, me too, but I have yet to establish repeatable conditions for this craziness in order to report it as a true, stomp it into the ground on sight BUGNeXT heteroptera... -- Michael Shaler Tokyo Design Center Nippon Motorola Ltd. +813 3280 8245 voice +813 3440 0033 fax mshaler@tdocad.sps.mot.com [NeXTmail]
From: Charles William Swiger <infidel+@CMU.EDU> Newsgroups: comp.sys.next.bugs Subject: Re: 3.2 NSI Experiences Date: Mon, 13 Dec 1993 15:43:32 -0500 Organization: Fifth yr. senior, Chemistry, Carnegie Mellon, Pittsburgh, PA Message-ID: <Eh3BDoS00iV3I7CYV=@andrew.cmu.edu> In-Reply-To: <2eeuvi$m0@nagasena.muc.de> Excerpts from netnews.comp.sys.next.bugs: 12-Dec-93 3.2 NSI Experiences by Kay Schulz@nagasena.muc. > I read a long article of Conrad Geiger about the GNUtools which are > included.... > What is included is 1% of all the wonderful GNUtools. Even patch (very > necessary) is not included. No new emacs. > GCC 2.2.2 :-) This is really true, no joke. We have 2.5 now > and we have 2.3.5 since beginning of 1993! Nothing else to say to that. > I hoped to get a nearly full archive of the nearly newest GNUtools. > Probably from June, but not from 1990! > With emacs and so on. I hate to tell you this, but the newest versions of the GNU tools (such as gcc 2.5.5) are *beta* releases, not final production. It is perfectly reasonable for NeXT to ship stable versions of the GNU tools (meaning Emacs 18.59 rather than 19.x, and older gcc, etc) that NeXT is certain that they work. This is not much of a problem unless and until there becomes a serious feature differential between the latest GNU release and NeXT's versions, which is not the case as far as I can tell. -Chuck Charles William Swiger -- CMU...*splat*! | 1. You can't fly. --------------------------------------------+ 2. Cars are always real, even AMS & normal mail: infidel@cmu.edu | when they're not. Failing that: cs4w+@andrew.cmu.edu | 3. Police are not your friends. NeXTmail: chuck@cswiger.slip.andrew.cmu.edu | 4. Fire burns.
Newsgroups: comp.sys.next.bugs From: anderson (Ken Anderson) Subject: UUCP (white 3.2 to black 3.1) Message-ID: <1993Dec13.174649.9567@biztech.com> Keywords: UUCP Sender: news@biztech.com Organization: Biztech, Inc. Date: Mon, 13 Dec 1993 17:46:49 GMT I'm experiencing a problem transferring files via UUCP over an IP connection between white 3.2 and black 3.1. It seems that during the uucico run, the data size is WAY off (as you can see). > wmesg 'S' Y > trddata expecting 654376960 bytes > cntrl - -1 > agent biztech (12/7-08:51-790) FAILED (conversation complete) Since the sending end (3.1 black) is only sending 300 or so bytes, the receiver (3.2 white) fails with a timeout. It seems we have a big/little endian problem that wasn't caught. Anyone else experiencing this problem?
Newsgroups: comp.sys.next.bugs From: fabien@free.fdn.org (Fabien Roy) Subject: Re: 3.2 Workspace Manager bug? Message-ID: <1993Dec13.185532.27856@free.fdn.org> Sender: news@free.fdn.org Organization: Fabien Roy Electronic Engineering (F.R.E.E.) - Paris, France. References: <2ehtg0$bg5@disuns2.epfl.ch> Date: Mon, 13 Dec 1993 18:55:32 GMT In article <2ehtg0$bg5@disuns2.epfl.ch> scheurer@lithnext.epfl.ch (Marco Scheurer) writes: > Hi, > > Is it me or is there an horrible bug in the Workspace Manager with 3.2? It > seems that sometime you cannot type a new filename for a file, because it > is automatically selected at more or less random interval, while you type, > so you are always destroying what your are typing. > > I don't know what make this bug appear, but once it is here, it is for > good, ie I don't know what to do to make it go away. This makes WSM > useless for changing filenames! That's sad, because until then, it was > pretty stable. > > I do not think I have seen this discussed before, so I'm wondering: did I > miss it, or has nobody seen this before? One more thing: I suspect this > has to do with the network, because an isolated NeXTstation does not > exhibit this behavior. > > Looks like I should BugNeXT... > --- > Marco Scheurer scheurer@lithnext.epfl.ch (NeXTMail) > Laboratoire d'Informatique Theorique > Ecole Polytechnique Federale de Lausanne > IN-Ecublens > CH-1015 Lausanne (Switzerland) > (+41) 21 693-2589 Hi, This happens once when I used an external disk which was having some integrity problem. The symptoms: the external disk icon changes to regular folder. The cure: reboot and check for the correct disk icon. My guess: the WorkSpace was not aware that the disk was mounted and each time a mount was tried the name of what I was typing got selected and destroyed. Cheers :-) --Fabien --------------------------------------------------------------------- Fabien_Roy@free.fdn.org (NextMails accepted) Fabien Roy Electronic Engineering 3 rue ANDRE DANJON, 75019 PARIS, France, Tel: 33 1 4040 0206 Fax: 33 1 4040 0641
Newsgroups: comp.sys.next.bugs From: nico@imani.cam.org (Nicolas Dore) Subject: Multi-session in 3.2? Message-ID: <1993Dec14.051833.1358@imani.cam.org> Sender: nico@imani.cam.org Date: Tue, 14 Dec 1993 05:18:33 GMT Hi From the 3.2 PhotoCD.app help: > The PhotoCD standard supports appending more > images to your PhotoCD using "Multi-session" > technology. Unfortunately, multi-session drives > are currently not supported in NeXTSTEP 3.1. ^^^ ^^^ > (Currently, the driver-level changes to support > multi-session drives are vendor-specific) We will > be looking into providing this in the future. Can anyone say if this is true under 3.2 also? Thanks Ciao Nicolas Dore -- Nicolas Dore nico@imani.cam.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Le calembour est la fiente du mot qui vole." < > Victor Hugo <
Newsgroups: comp.sys.next.bugs From: wave@media.mit.edu (Michael B. Johnson) Subject: Re: Multi-session in 3.2? Message-ID: <1993Dec14.102412.26960@news.media.mit.edu> Sender: news@news.media.mit.edu (USENET News System) Organization: MIT Media Laboratory References: <1993Dec14.051833.1358@imani.cam.org> Date: Tue, 14 Dec 1993 10:24:12 GMT In article <1993Dec14.051833.1358@imani.cam.org> nico@imani.cam.org (Nicolas Dore) writes: >>Hi >> >>From the 3.2 PhotoCD.app help: >>> The PhotoCD standard supports appending more >>> images to your PhotoCD using "Multi-session" >>> technology. Unfortunately, multi-session drives >>> are currently not supported in NeXTSTEP 3.1. >> ^^^ ^^^ >>> (Currently, the driver-level changes to support >>> multi-session drives are vendor-specific) We will >>> be looking into providing this in the future. >> >>Can anyone say if this is true under 3.2 also? >> Before answering this, keep in mind that there are two things that need to be done for this to be true: you have to be using a XA drive that allows multi-session, and NeXT has to supply a driver that recognizes and talks to it. Given that the NeXT CD-ROM drive didn't have hardware support for multi-session, and I don't know of any stock traders that are clambering for multi-session photo-CD support, I doubt this made it into 3.2... I have yet to hear a good reason for taking advantage of the multi-session capability, anyway. There's no economic advantage, the way Kodak has priced things... -- --> Michael B. Johnson -- wave@media.mit.edu --> MIT Media Lab -- Computer Graphics & Animation Group --> 20 Ames St. E15-023G -- (617) 547-0563 (day office) --> Cambridge, MA 02139 -- (617) 253-0663 (night office)
From: awhite@plush.sas.upenn.edu (Andrew White) Newsgroups: comp.sys.next.bugs Subject: cdaudio on NS/i 3.2? Followup-To: comp.sys.next.bugs Date: 14 Dec 1993 14:54:17 GMT Organization: Social Science Computing, Univ. of Pennsylvania Distribution: world Message-ID: <2ekk2p$g4i@netnews.upenn.edu> Has anyone gotten NS/i 3.2 to play audio CDs? When I insert an audio CD into my NEC CDR-84 CDROM drive, I get the spinning wheel for about 20 seconds, and then a dialog box asking me to "Please eject disk". A quick look at the console shows that NS tried to read the cd: probing for DOS probing for mac probing for cdaudio So why did it not recognize the CD as cdaudio? -- Andrew White, Systems Manager : 351 McNeil Building Social Science Computing : Univ. of Pennsylvania : AWhite@McNeil.sas.upenn.edu : (215) 898-2451
Newsgroups: comp.sys.next.bugs From: nico@imani.cam.org (Nicolas Dore) Subject: Modem support in 3.2 + compresshelp? Message-ID: <1993Dec14.175402.753@imani.cam.org> Sender: nico@imani.cam.org Date: Tue, 14 Dec 1993 17:54:02 GMT Hi Just continued playing with 3.2 on Black here (got it two weeks ago), and I tried the fax drivers. In 3.0, all the supplied drivers would do with my GVC2400 is nothing. Today, I tried both the Supra and HSD. Both seem to lock the modem in non-receiving mode i.e. it hears the other modem, but doesn't say anything. This symptom carried over when I tried to poll my uucp hub: the hub was beeping all over, but my modem stayed mute. This is a step ahead, but not quite there yet. Anybody got an idea? Besides NXFax or such, I keep my money for essential stuff and faxing isn't yet. While on the subject, how come I don't get to choose the "Level_2_Fax_Modem" driver that's in /usr/lib/NextPrinter"? I only see the Interfax driver that's in there, and the HSD appeared out of nowhere (aren't those two the same, basically...). Also, where is compresshelp? It's mentionned in the release notes, but nowhere else that I see, and EPS mentioned it a few months ago when 3.1 came out. Was it taken out of 3.2? The name makes it sound usefull, since I got oevr 5Megs of help files I'd like to be able to compress... So far, 3.2 is great, BTW. Ciao, and thanks. Nicolas Dore -- Nicolas Dore nico@imani.cam.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Le calembour est la fiente du mot qui vole." < > Victor Hugo <
From: mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) Newsgroups: comp.sys.next.bugs,comp.sys.next.sysadmin Subject: is this panic fixed in 3.2? Message-ID: <MS-C.755905559.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> Date: 14 Dec 93 05:45:59 GMT Article-I.D.: Tomobiki.MS-C.755905559.1103527590.mrc Organization: University of Washington Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Has this panic been fixed in 3.2? new_posix_proc(): attempt to create proc struct for pid 7180, found existing struct; process exists This seems to have been introduced in 3.1, and happens several times a month.
Newsgroups: comp.sys.next.bugs From: flight@mathi.uni-heidelberg.de (Gregor Hoffleit) Subject: Mounting SCSI DOS partitions in NSfIP 3.2 Message-ID: <1993Dec15.003642.14201@sun0.urz.uni-heidelberg.de> Sender: news@sun0.urz.uni-heidelberg.de (NetNews) Organization: University of Heidelberg, Germany Date: Wed, 15 Dec 93 00:36:42 GMT The fstab man page in 3.1 said about the filesystem type 'dos': '... does not support SCSI hard disks'. Nevertheless there seem to be many people that have no problems mounting their SCSI DOS partitions. I was even told that the bug was in fact the man page, it should simply work. I couldn't get it work, so I waited for 3.2 and hoped that at least the 'bug in the man page' was gone. It was not. Same man page as in 3.1. See above. I've received a couple of possible solutions many of them stating that the DOS partition has to be the first or second on the drive, so I changed the partition table, so that the DOS partition IS the first on the drive. NEXTSTEP fdisk prints it out, Linux fdisk too. Could we perhaps try to collect some configuration that work, and some that don't ? For the curious, I tried e.g. mount -t dos /dev/rsd0h /mnt /mnt exists. Before mounting a floppy this yields an error msg (because the DOS.fs kernel server is not yet loaded), after mounting a floppy this slowly crashes the machine whilst disk access. Any hints, any solutions, any experiences ? Gregor | Gregor Hoffleit admin MATHInet / contact HeidelNeXT | | MAIL: Mathematisches Institut PHONE: (49)6221 56-5771 | | INF 288, 69120 Heidelberg / Germany FAX: 56-3812 | | EMAIL: flight@mathi.uni-heidelberg.de (NeXTmail) |
From: gad@eclipse.its.rpi.edu (Garance A. Drosehn) Newsgroups: comp.sys.next.bugs Subject: Re: Multi-session in 3.2? Date: 15 Dec 1993 03:38:50 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Distribution: world Message-ID: <2em0sa$qgn@usenet.rpi.edu> References: <1993Dec14.051833.1358@imani.cam.org> nico@imani.cam.org (Nicolas Dore) writes: > From the 3.2 PhotoCD.app help: > > The PhotoCD standard supports appending more images to > > your PhotoCD using "Multi-session" technology. > > Unfortunately, multi-session drives are currently > > not supported in NeXTSTEP 3.1. > ^^^ ^^^ > > Can anyone say if this is true under 3.2 also? I attached an Apple 300 CD-ROM drive to a NeXTstation running release 3.2. Multi-session support is still not available for that combination. I don't know if it's available for NS/Intel machines, or for some other multi-session CD-ROM drive, but I would tend to doubt it. -- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu ITS Systems Programmer (handles NeXT-type mail) Rensselaer Polytechnic Institute; Troy NY USA
Newsgroups: comp.sys.next.bugs From: nico@imani.cam.org (Nicolas Dore) Subject: Re: Modem support in 3.2 + compresshelp? Message-ID: <1993Dec15.003342.431@imani.cam.org> Sender: nico@imani.cam.org References: <1993Dec14.175402.753@imani.cam.org> Date: Wed, 15 Dec 1993 00:33:42 GMT Sorry to follow-up on my own post, but I found compress-help. The Modem stuff I'm still wondering about, thought... In article <1993Dec14.175402.753@imani.cam.org> nico@imani.cam.org (Nicolas Dore) writes: > Also, where is compresshelp? It's mentionned in the release notes, but > nowhere else that I see, and EPS mentioned it a few months ago when 3.1 came > out. Was it taken out of 3.2? The name makes it sound usefull, since I got > oevr 5Megs of help files I'd like to be able to compress... Ciao -- Nicolas Dore nico@imani.cam.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > "Le calembour est la fiente du mot qui vole." < > Victor Hugo <
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: stage@dla832.ubszh.net.ch (Stage) Subject: Bug in Interface Builder ? Message-ID: <CI2LLJ.38q@ubszh.net.ch> Followup-To: comp.sys.next.programmer,comp.sys.next.bugs Keywords: custom palettes, non-View custom objects, interface builder Sender: usenet@ubszh.net.ch (news) Organization: Union Bank of Switzerland Date: Wed, 15 Dec 1993 09:41:42 GMT I want to build a palette which contains a non-View object, i.e. an object I can deposit in the File window. As indicated in NeXTSTEP General Reference and the release notes, I implement the finishInstantiate method of my palette to associate my custom object with a view. When I load my palette and drag the associated view to the File window, the suitcase opens to accept it, but then Interface Builder crashes with always the same message: Workspace: New dragCompleted protocol not recognized, using old one Does anyone have the same problem or suggest a workaround. The DBKit offers a non-View object, named DBModule. In this case, everything seems to work fine. Thanks for any help, Hans -- Hans Kneubuehl EPF Lausanne kneubuhl@di.epfl.ch
From: ecesys <ECESYS@delphi.com> Newsgroups: comp.sys.next.bugs Subject: Re: cdaudio on NS/i 3.2? Date: Wed, 15 DEC 93 05:32:03 EST Organization: Delphi Internet Message-ID: <931215.19923.ECESYS@delphi.com> References: <2ekk2p$g4i@netnews.upenn.edu> Andrew: make sure the NEC is jumpered for SCSI 2. We have had good luck with NECs adn the Toshiba 3401 in our systems. Martin fossum
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: wave@media.mit.edu (Michael B. Johnson) Subject: Re: Bug in Interface Builder ? Message-ID: <1993Dec15.121216.21773@news.media.mit.edu> Keywords: custom palettes, non-View custom objects, interface builder Sender: news@news.media.mit.edu (USENET News System) Organization: MIT Media Laboratory References: <CI2LLJ.38q@ubszh.net.ch> Date: Wed, 15 Dec 1993 12:12:16 GMT In article <CI2LLJ.38q@ubszh.net.ch> stage@dla832.ubszh.net.ch writes: >>I want to build a palette which contains a non-View object, i.e. an object I can deposit in the File window. As indicated in NeXTSTEP General Reference and the release notes, I implement the finishInstantiate method of my palette to associate my custom object with a view. >> >>When I load my palette and drag the associated view to the File window, the suitcase opens to accept it, but then Interface Builder crashes with always the same message: >> >>Workspace: New dragCompleted protocol not recognized, using old one >> >>Does anyone have the same problem or suggest a workaround. The DBKit offers a non-View object, named DBModule. In this case, everything seems to work fine. >> Have you implemented: - awake - read: - write: for your custom object? Run IB under gdb to see where it's really crashing. I believe that message you're seeing just has to do with the fact that IB crashed while you were doing a drag and drop. Realize that the order of events are: load in your palette. IB sends an appropriate initFrame: to each of the subviews on the palette. If you have nonview objects, you have to tell the palette about them by associating a view object on the palette with each non-view object using: - associateObject:IBObjectPBoardType:with in the palette's finishInstantiate method. The palette then sends init to them. If you have corresponding setOutlet:sender methods, those get sent now. Then when you select a view on the palette to drag and drop, IB sends a write: to either the view or the object, depending on if the view is just acting as a handle for the object (as it is in your case). After the write: finishes, IB allocs up a new object of that type and does a read: on the stream that it just had the object write itself out to. After the read: completes, the object gets sent an awake msg to finish waking itself up. Note that init only gets called for the first instance of each object on the palette; after that it's write:, read:, and awake. The obvious mistake most people make is either forgetting to implement these or implememting them wrongly, since this may be the first time as NeXTSTEP programmers that they've had to deal with archiving objects. Hope that helps. -- --> Michael B. Johnson -- wave@media.mit.edu --> MIT Media Lab -- Computer Graphics & Animation Group --> 20 Ames St. E15-023G -- (617) 547-0563 (day office) --> Cambridge, MA 02139 -- (617) 253-0663 (night office)
From: kneubuhl@di.epfl.ch (Hans Kneubuehl, EPFL INFO 94) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Interface Builder bug? Date: 14 Dec 1993 21:13:12 GMT Organization: Ecole Polytechnique Federale de Lausanne Distribution: world Message-ID: <2ela98$793@disuns2.epfl.ch> Keywords: interface builder, custom palettes, non-View palette objects I want to build a custom palette that contains non-View objects that will be deposited in the File window. As described in the manual, I implement the finishInstantiate method of the palette class to associate my custom object with its View appearing in the palette. When I test my palette by dragging the custom object to the File window, the object suitcase opens to accept it, but subsequently Interface Builder crashes with the following message: Workspace: New dragCompleted protocol not recognized, using old one Does anyone have the same problem or suggest a workaround? The DBKit offers a DBModule object in its palette that can be dragged into the File window. In this case IB works fine. Thanks for any help, Hans -- Hans Kneubuehl EPF Lausanne kneubuhl@di.epfl.ch
From: kneubuhl@.epfl.ch (Hans Kneubuehl, EPFL INFO 94) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: debugging palettes and bundles Date: 14 Dec 1993 21:18:19 GMT Organization: Ecole Polytechnique Federale de Lausanne Distribution: world Message-ID: <2elair$793@disuns2.epfl.ch> Keywords: gdb, palettes, bundles, dynamic loading How can I use gdb to debug bundles and palettes that are dynamically loaded? I compile my bundles and palettes using the debug option, but when I start IB or another main program in gdb it doesn't have knowledge of the files loaded during run time. Thanks for any help, Hans -- Hans Kneubuehl EPF Lausanne kneubuhl@di.epfl.ch
Newsgroups: comp.sys.next.bugs From: zaphod@ctrg.rri.uwo.ca (Lance R. Bailey) Subject: hplaser IV bug Organization: University of Western Ontario Date: Wed, 15 Dec 1993 14:35:57 GMT Message-ID: <1993Dec15.143557.16834@julian.uwo.ca> Sender: news@julian.uwo.ca (USENET News System) sigh. i recently received an HP LJIv, and it has the dreadedpostscript bug in it. i seem to remember a fix for it -- anyone out there have that fix? -- Lance R. Bailey System/Network Manager Robarts Research Institute NeXT/email: zaphod@ctrg.rri.uwo.ca box: Clinical Trials Resources Group fax: +1 519 663 3789 P.O. Box 5015, 100 Perth Dr. vox: +1 519 663 3787 x4108 London, Canada N6A 5K8
Newsgroups: comp.sys.next.bugs From: yanik@planon.qc.ca (Yanik Crepeau) Subject: Re: Mounting SCSI DOS partitions in NSfIP 3.2 Message-ID: <1993Dec15.235315.376@planon.qc.ca> Sender: yanik@planon.qc.ca References: <1993Dec15.003642.14201@sun0.urz.uni-heidelberg.de> Date: Wed, 15 Dec 1993 23:53:15 GMT In article <1993Dec15.003642.14201@sun0.urz.uni-heidelberg.de> flight@mathi.uni-heidelberg.de (Gregor Hoffleit) writes: > The fstab man page in 3.1 said about the filesystem type 'dos': '... does > not support SCSI hard disks'. Nevertheless there seem to be many people > that have no problems mounting their SCSI DOS partitions. I was even told > that the bug was in fact the man page, it should simply work. > > I couldn't get it work, so I waited for 3.2 and hoped that at least the > 'bug in the man page' was gone. It was not. Same man page as in 3.1. See > above. > > I've received a couple of possible solutions many of them stating that the > DOS partition has to be the first or second on the drive, so I changed the > partition table, so that the DOS partition IS the first on the drive. > NEXTSTEP fdisk prints it out, Linux fdisk too. > > Could we perhaps try to collect some configuration that work, and some > that don't ? For the curious, I tried e.g. > > mount -t dos /dev/rsd0h /mnt > > /mnt exists. Before mounting a floppy this yields an error msg (because > the DOS.fs kernel server is not yet loaded), after mounting a floppy this > slowly crashes the machine whilst disk access. > > Any hints, any solutions, any experiences ? > > Gregor > > | Gregor Hoffleit admin MATHInet / contact HeidelNeXT | > | MAIL: Mathematisches Institut PHONE: (49)6221 56-5771 | > | INF 288, 69120 Heidelberg / Germany FAX: 56-3812 | > | EMAIL: flight@mathi.uni-heidelberg.de (NeXTmail) | That is where the fun begins. We had to face that problem some weeks ago. The BLACK hardware, can not mount any DOS-formated FIXED hard disk. It can, in theory -- I have not made any test -- mount any DOS formated removable support, including diskette, removable hard-disk, CD-ROM, Opto-Magnetic etc. etc. The INTEL hardware, is capable to mount the DOS partition of my hard disk. However, I have read many complaints of NeXT partition corrupting DOS partition or vice-versa. I did not experienced any problem with the DOS partition because I don't use it. -- Yanik Crepeau Programmer Planon Telexpertise E-Mail: yanik@planon.qc.ca (NeXT)
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: yanik@planon.qc.ca (Yanik Crepeau) Subject: Re: Bug in Interface Builder ? Message-ID: <1993Dec16.000355.438@planon.qc.ca> Sender: yanik@planon.qc.ca References: <CI2LLJ.38q@ubszh.net.ch> Date: Thu, 16 Dec 1993 00:03:55 GMT In article <CI2LLJ.38q@ubszh.net.ch> stage@dla832.ubszh.net.ch (Stage) writes: > I want to build a palette which contains a non-View object, i.e. an object I can deposit in the File window. As indicated in NeXTSTEP General Reference and the release notes, I implement the finishInstantiate method of my palette to associate my custom object with a view. > > When I load my palette and drag the associated view to the File window, the suitcase opens to accept it, but then Interface Builder crashes with always the same message: > > Workspace: New dragCompleted protocol not recognized, using old one > > Does anyone have the same problem or suggest a workaround. The DBKit offers a non-View object, named DBModule. In this case, everything seems to work fine. > > Thanks for any help, > > Hans > > -- > Hans Kneubuehl > EPF Lausanne > kneubuhl@di.epfl.ch > I have had excacly the same problem some times ago. WHen I drag the object, a new copy is created and the -read method is called. Triple check the -read method of your object. You must be aware that when you drag your pallette object, some code inside it is executed. If that code crashes, IB itself crashes. Since you begin a drag&drop session and that session is never completed, the Workspace manager writes the message above in the Console. Yanik -- Yanik Crepeau Programmer Planon Telexpertise E-Mail: yanik@planon.qc.ca (NeXT)
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Distribution: world Date: Wed, 15 Dec 1993 19:29:25 PST Message-ID: <1993Dec16.032925.346@corona.com> Newsgroups: comp.sys.next.bugs Subject: Re: cdaudio on NS/i 3.2? References: <931215.19923.ECESYS@delphi.com> From: ecesys <ECESYS@delphi.com> > make sure the NEC is jumpered for SCSI 2. > We have had good luck with NECs adn the Toshiba 3401 in our systems. > Martin fossum YES!!! At long last, the cdaudio works on my NS/I! I guess since I had a SCSI-1 cable and everything I had read indicated NEXTSTEP didn't support SCSI-2, I just sort of assumed that switch should be on SCSI 1. Silly me. But that's all water over the bridge...I'm truckin' now...with appropriate accompaniment! --- NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
Newsgroups: comp.sys.next.bugs From: Robert_La_Ferla@hot.com Subject: Re: UUCP (white 3.2 to black 3.1) Message-ID: <1993Dec15.204842.4330@hot.com> Sender: robertl@hot.com Organization: Hot Technologies References: <1993Dec13.174649.9567@biztech.com> Date: Wed, 15 Dec 1993 20:48:42 GMT Use Taylor UUCP. Source code is available for free from ftp.uu.net:/pub/networking/uucp. Robert La Ferla Hot Technologies In article <1993Dec13.174649.9567@biztech.com> anderson (Ken Anderson) writes: > I'm experiencing a problem transferring files via UUCP over an IP > connection between white 3.2 and black 3.1. It seems that during the > uucico run, the data size is WAY off (as you can see). > > > wmesg 'S' Y > > trddata expecting 654376960 bytes > > cntrl - -1 > > agent biztech (12/7-08:51-790) FAILED (conversation complete) > > Since the sending end (3.1 black) is only sending 300 or so bytes, the > receiver (3.2 white) fails with a timeout. It seems we have a big/little > endian problem that wasn't caught. > > Anyone else experiencing this problem? >
From: geom2@sfb256.iam.uni-bonn.de ( Michael Moellney ) Newsgroups: comp.sys.next.bugs Subject: 3COM Ether Link III Date: 16 Dec 1993 11:15:46 GMT Organization: Applied Math, University of Bonn, Germany Message-ID: <2epg12$bfl@news.rhrz.uni-bonn.de> Summary: Bug in Device Driver Keywords: Ether Link III, NFS, Device Driver Hi! Two days ago I ask in this group, if someone has installed NFS successful with 3COM EL III Cards? I got some answers, mostly saying to set read/write-size in Expert Options to 1024. I did this and I did it before I asked. Someone at Next send me Information, that the 3COM card is not usable for NFS! So I wonder, why in the Hardware Comp. Guide they say APPROVED!-( So I found this: 2 Intel NS/3.2, both have a 3COM Card (ISA), one serves the other. After really few NFS Transfer: NFS Server xxx not responding... Waiting doesn't help, the server dosn't wake up! 1. 'ping' from the CLIENT machine to the server machine isn't responded AT ALL! All packets were lost. 2. 'ping' from the SERVER machine to ANY OTHER machine in the net brings NFS Server to life again and pinging to the server works again! ping awakes the Ethernet card, or is it the driver?? My conclusion is: THERE IS AN INTERUPT HANDLE BUG IN THE 3COM Driver! It's no bug in NFS, because I heard on Intel Ethernet card it all works fine. And although the buffer may be small on a 3COM, under OS/2 NFS works fine with the same machines!! Now what do YOU think of it? Has anybody else seen this problem with 3COM EL III? Is my conclusion wrong ?? What else could it be?? Thanks for any hints! In the case I'm right, it's time for NeXT to fill the folder 3.2 Drivers in NeXTanswers or to show us the sorce of the 3COM EL III card driver. Bye, Michael
From: erikkay@next.com (Erik Kay) Newsgroups: comp.sys.next.bugs Subject: Re: is this panic fixed in 3.2? Date: 15 Dec 1993 18:54:26 GMT Organization: NeXT, Inc. Message-ID: <2enmh2$5e9@rosie.next.com> References: <MS-C.755905559.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> In article <MS-C.755905559.1103527590.mrc@Tomobiki-Cho.CAC.Washington.EDU> mrc@Tomobiki-Cho.CAC.Washington.EDU (Mark Crispin) writes: > Has this panic been fixed in 3.2? > new_posix_proc(): attempt to create proc struct for pid 7180, found > existing struct; process exists > > This seems to have been introduced in 3.1, and happens several times a month. Yes... we're fairly sure that this has been fixed. I can't say this with 100% certainty because it was a very difficult to reproduce (on demand at least) race condition. However, we believe that we understand the race condition and fixed the suspect code. To date, this panic has not been reported on a 3.2 system. Erik
From: pud!psl@bellcore.bellcore.com (Peter Langston) Newsgroups: comp.sys.next.bugs Subject: Need history on a 3.1 beta bug Date: 16 Dec 1993 16:42:51 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9312162202.AA00582@pud> I'm still running a 3.1 Beta (Lightning3A) on a black cube (68040) and having the problem of system hangs between booting and having the login window appear (sometimes with a tcp panic diagnostic, but often without). I've just started getting the next bugs digest, so I don't know whether this has been discussed or not (I suspect it has). My questions: 1) How can I find out what has already been said about these erratic, mysterious hangs? 2) If this hasn't been discussed to death, are others still having this problem or did it disappear with the 3.1 release version? Thanks, Peter Langston psl@acm.org
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.bugs Subject: Re: 3.2 Workspace Manager bug? Date: 15 Dec 1993 22:09:21 +0100 Organization: Palumbian Research Labs Message-ID: <2enue1$uk@marsu.tynet.sub.org> References: <2ehtg0$bg5@disuns2.epfl.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit scheurer@lithnext.epfl.ch (Marco Scheurer) writes: >Is it me or is there an horrible bug in the Workspace Manager with 3.2? It >seems that sometime you cannot type a new filename for a file, because it >is automatically selected at more or less random interval, while you type, >so you are always destroying what your are typing. I've never seen anything like that on my NS/I 3.2 since I got it on December 6. -- Marsu: "Es gibt tatsaechlich Leute, die ohne Computer gluecklich und zufrieden leben." -- Frankie: "Ach was, die emulieren das doch nur!" ----- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Intel aside.
Newsgroups: comp.sys.next.bugs From: dennis@nebulus.ampr.ab.ca (Dennis S. Breckenridge) Subject: Re: 3COM Ether Link III Keywords: Ether Link III, NFS, Device Driver References: <2epg12$bfl@news.rhrz.uni-bonn.de> Organization: "Alchemy Mindworks" Date: Fri, 17 Dec 1993 06:37:10 GMT Message-ID: <CI62Dy.399@nebulus.ampr.ab.ca> geom2@sfb256.iam.uni-bonn.de ( Michael Moellney ) writes: >Hi! ... >My conclusion is: THERE IS AN INTERUPT HANDLE BUG IN THE 3COM Driver! > It's no bug in NFS, because I heard on Intel Ethernet card it all works fine. > And although the buffer may be small on a 3COM, under OS/2 NFS works fine > with the same machines!! I don't really think it's a a true bug with the 3c509, its more a poor design on the part of the disk/ethernet teams. If the ethernet card tied the bus up too long the disk driver panics the box. I have seen this repeatedly with 3.1 >Now what do YOU think of it? Has anybody else seen this problem with >3COM EL III? Is my conclusion wrong ?? What else could it be?? Yes. The only operating system that I have at my site that CANNOT use the 3c509 is NEXTSTEP 3.1. I just got my copy of 3.2 today buy I have not tested this yet. My overall solution was to replace the 3c509 with the Intel Express 16, that NextStep runs in 8 bit mode. I suggest you do the same. -- ----------------------------------------------------------------------------- Dennis Breckenridge Microsoft Windoze. Genetic throwback from the dennis@nebulus.ampr.ab.ca natural selection of UNIX. -----------------------------------------------------------------------------
From: edmtl@alf.uib.no (Thor Legvold) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.software,comp.sys.next.misc,comp.sys.next.programmer,comp.sys.next.bugs Subject: Good/Bad points? Upgrading from 3.0 to 3.[12]. Date: 17 Dec 1993 12:34:24 +0100 Organization: University of Bergen Message-ID: <2es5g0$5fo@alf.uib.no> Hi. I have been running 3.0J for the last year, and am quite happy, despite the slowness compared with 3.0E. It's also nice to have Japanese on the Machine without having to use X11 :-) Well, I have bought 3.1E and just received 3.2E, but have hesitated in installing these releases. I have heard both positive and negative things about these releases, and am not sure that the improvement is so clear in this case. So, I'm asking the wisdom of the Net: What do I stand to gain and lose by upgrading from 3.0 to either 3.1 or 3.2? I know I'll lose Japanese environment (I haven't been able to get a hold of a 3.1/3.2 upgrade in Japanese :-(, but what other things have been removed? What has been added? What about bugs? GUI changes? IB changes? etc, etc. I would appreciate greatly any and all comments (e-mail!) regarding this upgrade decision, or any advice netters have regarding the upgrade process. Hardware: NeXT Cube 040 16MB core, HP 1.0 GB disk, NeXT CD ROM. Regards, Thor (hey - congratulate me on getting this far with vi...emacs is having problems at the moment at our site :-) -- Thor Legvold | This is the strangest life NorNeXT User Group leader | I've ever known... University of Bergen | - Jim Morrison, The Doors Norway | edmtl@fiol.uib.no (NeXTmail)
Newsgroups: comp.sys.next.programmer,comp.sys.next.software,comp.sys.next.bugs From: rashid@degas.northstar.com (Navruze Rashid) Subject: Help! No propertyValue method in DB-Kit Message-ID: <CI1FvI.HAp@northstar.com> Keywords: relationships, propertyValue method Sender: usenet@northstar.com Organization: NorthStar Technologies, inc. Date: Tue, 14 Dec 1993 18:40:29 GMT I am working on a relational database being retrieved from Sybase using relational joins between tables (relationships) to set up master-detail relationships and to retrieve these using DBRecordLists and custom DBFetchGroups. Now, here is the problem. In the DB-Kit documentation (new 3.2) as well as the Master-Detail example in the Concepts section (has anyone looked at this?) the way to retrieve a relationship is roughly as in the code here: ----------------------------------------------------------------- DBRecordList *masterDept = [[DBRecordList alloc] init]; DBRecordList *detailEmp = [[DBRecordList alloc] init]; .. DBValue *toEmpVal = [[DBValue alloc] init]; /* Create objects to store the desired entity and properties. We'll assume that db, a DBDatabase object, exists.*/ id dept = [db entityNamed:"Department"]; /* TABLE */ id toEmp = [dept propertyNamed:"toEmployee"]; /* REL'N */ .. /* Empty the List object and use it to hold the detail properties. */ [detailProps addObject:[[toEmp propertyValue] propertyNamed:"name"]; ^^^^^^^^^^^^^ ---------------------------------------------------------------------- This method does not exist within the DB-Kit. Headers or documented as a method. The program compiles then crashes when it gets to this statement with a `does not respond to - propertyValue' message. This is mentioned as the way to retrieve the entity referenced by the relationship elsewhere as well - in the DBQualifier docs. GIVE ME A BREAK How can I do this some other way? (get the entity for the relationship destination- I tried [toEmp entity] but that simply returns the base (root) entity). Maybe if NeXT worried more about providing a complete kit, people would start using it. Thanks for any comments or suggestions. Anyone been bitten by this? (Thanks, NeXT) Ruze
Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs From: cuilla@black_silk (Chris Cuilla) Subject: Re: Help! No propertyValue method in DB-Kit Message-ID: <1993Dec17.171850.10023@il.us.swissbank.com> Sender: root@il.us.swissbank.com (Operator) Organization: Swiss Bank Corporation CM&T Division References: <CI1FvI.HAp@northstar.com> Date: Fri, 17 Dec 1993 17:18:50 GMT Navruze Rashid writes > > /* Empty the List object and use it to hold the detail properties. */ > [detailProps addObject:[[toEmp propertyValue] propertyNamed:"name"]; > ^^^^^^^^^^^^^ > This method does not exist within the DB-Kit. Headers or documented > as a method. The program compiles then crashes when it gets to this > statement with a `does not respond to - propertyValue' message. > > This is mentioned as the way to retrieve the entity referenced by > the relationship elsewhere as well - in the DBQualifier docs. > > GIVE ME A BREAK > > How can I do this some other way? (get the entity for the relationship > destination- I tried [toEmp entity] but that simply returns the base > (root) entity). Maybe if NeXT worried more about providing a complete > kit, people would start using it. > Use "propertyType". This is an error that (I think) is known and aknowledged by NeXT as an error in documentation. -- Chris Cuilla --- NEXTSTEP Developer chris@its.com --------------------------------------------------------------------- "There's no such thing a as 'part-time' perfectionist."
Newsgroups: comp.sys.next.bugs From: alex@cs.umd.edu (Alex Blakemore) Subject: Re: Help! No propertyValue method in DB-Kit Message-ID: <CI75HH.uv@genoa.com> Sender: alex@genoa.com (Alex Blakemore) Organization: Genoa Software Systems References: <CI1FvI.HAp@northstar.com> Date: Fri, 17 Dec 1993 20:41:41 GMT Navruze Rashid writes > [from the dbkit concepts doc] > [detailProps addObject:[[toEmp propertyValue] propertyNamed:"name"]; > ^^^^^^^^^^^^^ > This method does not exist within the DB-Kit. its a typo, they mean propertyType. of course, the dbkit concepts doc still has this error and is still incomplete as of NS 3.2. -- Alex Blakemore alex@cs.umd.edu NeXT mail accepted
From: joe@msri.org (Joe Christy) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Weird Mail.app/NSF problem Date: 17 Dec 1993 23:15:19 GMT Organization: Lawrence Berkeley Laboratory, Berkeley CA Message-ID: <36143@dog.ee.lbl.gov> Keywords: Mail.app NSF timeout We have a user (a _VERY_ Important User) whose Mail.app disturbingly often fails to retrieve new mail. What seems to be happening is this: the NSF mount of NSF of /var/spool/mail times out for an instant so her machine doesn't see it and then remounts it. Unfortunately, Mail.app, once disappointed in its search for new mail in the temporarily unavailable /var/spool/mail/_VERY_ImportantUser, never goes back to look for it again, even when we invoke "Get New Mail" from the Utilities> menu. The only sure cure is to quit and restart Mail.app, which is not really very satisfactory. Anyone out there seen anything like this? fixes? better work-arounds? Joe -- Joe Christy | Head of Mathematical Computing |Two wrongs joe@msri.org |Mathematical Sciences Research Institute|don't make a (510)643-6069| 1000 Centennial Drive |right, but FAX 642-8609| Berkeley, CA 94720 |three lefts do
Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs From: mckelvey@fafnir.com (James W. McKelvey) Subject: Re: Formatting an external floppy NS 3.1 Message-ID: <CHyHpK.n4@fafnir.com> Sender: mckelvey@fafnir.com (James W. McKelvey) Organization: Fafnir Software, Saugus, CA, USA References: <CHtBL2.58o@ensuing.com> Date: Mon, 13 Dec 1993 04:27:19 GMT In article <CHtBL2.58o@ensuing.com> Karl_Kraft@ensuing.com writes: > Using NeXTSTEP 3.1, I cannot format in my external PLI floppy drive. > > This is the message that appears in the console: > > --------- > /usr/etc/disk -i -h oghma -l "Floppy" /dev/rsd1a > disk name: PLI SUPER FLOPPY > disk type: removable_rw_scsi > device = /dev/rsd1a block size = 512 capacity = 1 MBytes > Disk Format in progress... > ***Format Complete*** > writing disk label > boot block extends beyond front porch > -------- > > I looked through the last six months of the various csn groups, > but could only find various posters with the same problem. > Did anyone ever find a work around for this problem? > > -- > _________ > Karl Kraft > Karl_Kraft@ensuing.com (NeXT mail) > The only solution I have found is to replace your /usr/etc/disk with the 3.0 version. Apparently NeXT tried to squeeze a few more bytes out of the floppies and decreased the "front porch" to the point where the boot blocks overlapped it. And, naturally, failed to fix it for 3.2 as well. (Better explanation, anyone?) I have tried to fix this by adding a disktab entry for the floppies, derived from a properly initialized 2.88M floppy (using disk interactively, command "label"). But it never works. Here's my last attempt: PLI SUPER FLOPPY:\ :ty=removable_rw_floppy:nc#80:nt#2:ns#18:ss#1024:rm#300:\ :fp#96:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=mach_kernel:z0#-1:s1#32:ro=a:\ :pa#0:sa#2784:ba#8192:fa#1024:ca#16:da#2048:ra#0:oa=space:\ :ia:ta=4.3BSD:aa: I'd be curious to know what is wrong with this disktab entry. Of course, such an entry would not solve the problem in general, since disk must be able to initialize 1.44M and 800K floppy discs as well. -- The gentle journey jars to stop. The drifting dream is done. The long gone goblins loom ahead; the deadly, that we thought were dead, stand waiting, every one. -- Walt Kelly Jim McKelvey mckelvey@fafnir.com Relay-Version: UUL1.3; site ace.com Posting-Version: UUL1.3; site ace.com Path: uu0924!klyfix From: klyfix@ace.com (Klyfix) Newsgroups: alt.tv.mst3k Subject: Re: This is probably a dumb question... Message-ID: <1494.UUL1.3#25274@ace.com> Date: Mon, 13 Dec 93 03:30:51 EST Organization: Argus Computerized Exchange M{>In article <kiasyd-081293190136@ugl164.ccs.itd.umich.edu>, kiasyd@umich.edu M{>(Jake Baker) writes: M{>|> ...but there's no such thing. M{>|> M{>|> OK, in several episodes of MST3K (Mitchell was one, I can't remember the M{>|> others), the guys have a thing they do when someone starts listing off M{>|> names, ending with Tom saying "Chief" and Crow saying "MacCloud," M{>|> M{> Maclead is in referance to the Highlander movie or the series... Nope, it's a reference to the old McCloud series (part of the NBC Mystery Movie) starring Dennis Weaver. The voice Crow uses is an imitation of the Chief on that show. ------ --------------------------------------------------------------------------- V.S.Greene | klyfix@ace.com | "Your superior intellects are no match for our puny weapons!"-Simpson's Halloween special Relay-Version: UUL1.3; site ace.com Posting-Version: UUL1.3; site ace.com Path: uu0924!klyfix From: klyfix@ace.com (Klyfix) Newsgroups: alt.fan.mst3k Subject: Outlaw of Gor...huh? Message-ID: <1495.UUL1.3#25274@ace.com> Date: Mon, 13 Dec 93 03:30:54 EST Organization: Argus Computerized Exchange "OUtlaw", from _Outlaw of Gor_ ...urgh, what can one say? This may well be the worst Sword and Sorcery type film ever, worse than "Cave Dwellers" (Ator). I was nearly in shock at the badness of this film, worse than the reaction to "Wild, Wild, World of Batwoman". It barely needed misting...gad, the scene where the hero bends the sword was hilarious straight. But Mike and the 'bots definatly got some good licks in on this one. One puzzling thing; John Norman has sold zillions of books in the "Gor" series, but this movie is utter dreck. Maybe it works better as a novel? I've seen the guy at the Arisa SF con in Boston;l and he seems to be a fairly intelligent sort. Maybe he knows that dreck sells? Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.collecting.cards Subject: E-Sports Online! Message-ID: <421.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:04 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 Attention sports card collectors. E-Sports will trade you unwanted baseball cards at high Beckett price for on-line time on E-Sports. For complete details check out the purchase credits section on E-Sports. E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. Currently we are posting on-line credits to your account when you place or respond to a classified add. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. Check out E-Sports today. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.sport.football.college Subject: E-Sports Online Message-ID: <422.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:05 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.sport.baseball Subject: E-Sports Online Message-ID: <423.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:06 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.sport.hockey Subject: E-Sports Online Message-ID: <424.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:07 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.sport.basketball.pro Subject: E-Sports Online Message-ID: <425.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:08 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: rec.sport.football.misc Subject: E-Sports ONline Message-ID: <426.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:09 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: alt.bbs.ads Subject: E-Sports Online Message-ID: <427.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:13 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: alt.bbs Subject: E-Sports ONline Message-ID: <428.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:14 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!rubd22 From: rubd22@cris.com (Rubd22) Newsgroups: alt.bbs.lists Subject: E-Sports Online Message-ID: <429.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:15 EDT Organization: CRIS E-Sports America's On-Line Sports Connection 715-848-2508 E-Sports features forums for all professional sports teams, daily sports news, sports games including football pools and a calssified add section for sports card collectors. An entertainment section includes Mutants and Galactic Empire. There is a complete classified add section for selling, buying and trading baseball and other sports cards. The news section features game recaps, complete statistics, schedules and news articles. The news is is menu driven for easy reading. New users are given 30 minutes per day for 30 days to get acquainted with E-sports. We will take your unwanted sports cards or credit card on-line. See details on-line to trade your sports cards. Get in the game! Get on-line to E-sports Call 715-848-2508 today Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!ufinet From: ufinet@cris.com (Bill English) Newsgroups: alt.alien.visitors Subject: Where are my posts? Message-ID: <430.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:16 EDT Organization: CRIS CW>: Is the moderator for this group killing all my articles? CW>: If so, why? Worse still, I'm getting all this mail from CW>: weirdos who don't "believe" in UFOs, which is fine w/me, CW>: except they're saying that I posted something to the effect CW>: that I don't "believe" in UFOs. Let me set the record CW>: straight on that: I AM NOT A CHRISTIAN, AND UFOs ARE REAL! CW>: Would the Jesus crowd please stop cluttering up my E-mailbox. CW>: Thanx, CW>: ChuckL Yo Chuck! Could this be a government conspiracy to keep you quiet??? Bill English UFINET --- ~ OLX 2.1 TD ~ UFINET News BBS (505)682-2024 Professionalism is the Key Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!ufinet From: ufinet@cris.com (Bill English) Newsgroups: alt.alien.visitors Subject: Re: Government Alien Anno Message-ID: <431.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:18 EDT Organization: CRIS WA>C'mon. Use your old bean. What about calculators. We supposedly got WA>them as an outgrowth of chips which supposedly had to be invented WA>(necessity is the mother of invention, right) for the Appollo mission WA>or some such. And what about microwave ovens. And sattelite dishes, WA>computers, and even televsion. Most of this stuff of aliens landing WA>on earth and forming the alleged MJ-12 and all of that happened before WA>I was even BORN, and even *I* can figure out that we didn't have all WA>our modern technology back BEFORE this alleged alien landing. Sheesh. WA>-- WA>Laura Watson lkw@falcon3.att.com WA>Trying to free myself from anxiety-causing positive ion buildup. HORSE FEATHER!! I've been at this game for going on twenty years now and this has got to be the most rediculous thing I have ever heard. I am willing to acknowledge the fact that there is a government cover-up, but are we so stupid that every technological advance we have must come from aliens.. Was Einstein and Alien (Hmmmmmm....then again).... Bill English UFINET --- ~ OLX 2.1 TD ~ UFINET News BBS (505)682-2024 Professionalism is the Key Relay-Version: UUL1.3; site cris.com Posting-Version: UUL1.3; site cris.com Path: cris!ufinet From: ufinet@cris.com (Bill English) Newsgroups: soc.college Subject: White House address Message-ID: <432.UUL1.3#25345@cris.com> Date: Mon, 13 Dec 93 06:00:19 EDT Organization: CRIS Just as a matter of curiousity.....Does anyone know what Billy's address on the Internet might be....I would like to send him a bit of Email.. Bill English UFINET@CRIS.COM --- ~ OLX 2.1 TD ~ UFINET News BBS (505)682-2024 Professionalism is the Key Relay-Version: UUL1.3; site winnertech.com Posting-Version: UUL1.3; site winnertech.com Path: winner!rebecca From: rebecca@winnertech.com (rebecca schneider) Newsgroups: misc.jobs.offered,misc.jobs.contract Subject: SOFTWARE, COMMUN. & ENGR POSITIONS-CONSULTING & PERMANENT (NJ, NYC) Message-ID: <165.UUL1.3#20566@winnertech.com> Date: Fri, 10 Dec 93 16:31:09 EDT Organization: Winnertech Corporation Winnertech, in Central New Jersey, is a respected ten-year-old high-technology consulting firm, specializing in applying computer and communications technology to our clients' needs. We're looking for committed, top-flight technical people to work with our clients in the NJ/NY area. Winnertech is a member of the National Associa- tion of Computer Consultant Businesses (NACCB). We offer challenging assignments, an enjoyable, supportive environ- ment, competitive compensation, and group health, life and disability benefits. A few of our positions (noted) are permanent placements with our clients. To make it easy to reply, we have ended each Summary line with a Job No. whose first four digits are the month and day that we received the job. Please refer to these numbers in your reply. It is our policy to discuss a potential position with you before presenting your resume to a client. We will only send it with your express permission. Our clients uniformly request that we provide them with experienced people. If you don't yet have real work experience, it's unlikely we can help you. We are unable to relocate those who do not reside in the United States. We welcome comments on the readability of this posting. ------------------------------ Subject: C/UNIX Programmer Analyst - MSDOS;;1207-02 Strong C, Unix, MSDOS required to perform applications development. SQL, a relational database and C++ would be nice. Experience (yrs): 4-6 Type: Permanent placement with our client ------------------------------ Subject: Unix/C Programmer - X Windows or Open Look;Northern NJ;1206-01 Solid Unix/C, X Windows or Open Look to build graphics based applications. Informix SQL, ESQL/C or 4GL required as is experience with SW development quality methodologies. MSCS required. Experience (yrs): 3+ Type: Permanent position as a consultant ------------------------------ Subject: Unix Systems Administrator;NY City;1129-01 Perform normal systems administrations duties on an SCO machine, including network management tasks and installtion of DOS products. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: UNIX Technical Support with Drivers experience;Northern NJ;1112-01 REOPENED-Experience in developing UNIX drivers in an SMP and non-SMP environment; UNIX streams and interface standards (DDI/DDKI, SVID, TLI),ability to work in uniprocessor/multiprocessor, fault tolerant/non-fault tolerant environment. MSCS or EE Experience (yrs): 2+ Type: Permanent position as a consultant ------------------------------ Subject: Sybase APT Workbench/C Programmer;NY City;1109-01 Need programmer with 2+ years of experience with Sybase APT - Workbench and C, preferably in a VMS environment, to do front end input and some C-coding on a charge-back system. Degree required. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: Sr. UNIX Systems Administrator - Sun/Networking;NY City;1021-01 Sr. UNIX Systems Administrator with TCP/IP and Novell experience to manage UNIX area, manage production and test prototypes. Degree required. RIGHT-TO-HIRE. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: Senior Level UNIX/C Programmer Analyst w/X WINDOWS;Northern NJ;1012-01 5+ years experience with design, development and implementation in UNIX/C (must have semaphores, daemons, signals, TCP/IP sockets. Knowledge of the UNIX kernal would be nice. To work on a communications information network application. Degree nice. Experience (yrs): 5+ Type: Permanent placement with our client ------------------------------ Subject: SUN Administrator;NY City;0928-01 2 or more years of SUN Administration experience with any database experience to do scripting, programming (in C), debugging, maintenance and work with development automation tools. Degree required. Experience (yrs): 2+ Type: Permanent placement with our client ------------------------------ Subject: Senior Programmer, Sybase and Metaphor;NY City;0825-01 Senior Programmer with three years experience using Sybase and Metaphor (or DIS) to develop applications for Sybase and DB2 back-ends. Must have good communication skills. Degree preferred. Experience (yrs): 3+ Type: Permanent position as a consultant ------------------------------ Subject: Programmer Analyst - C, COBOL, TCP/IP;NY City;0824-04 Programmer Analyst with at least 3 years experience in C, COBOL and TCP/IP to develop and debug code and prepare its documentation. 4GL experience nice. Experience (yrs): 3+ Type: Permanent placement with our client ------------------------------ Subject: Manager-Applic. Dev., C, COBOL, TCP/IP, SQL;NY City;0824-05 Application development manager with at least 5 years experience in the field to manage applications using C, COBOL, TCP/IP & SQL. Also need knowledge of OS/2, DOS, Case tools & GUPTA. PC and VAX hardware environment. Degree necessary. Experience (yrs): 5+ Type: Permanent placement with our client ------------------------------ Subject: UNIX/C/Sybase Junior Programmer Analyst;Central NJ;0824-06 REVISED-Junior programmer analyst with 1+ years experience UNIX, C and Sybase to develop financial and billing applications. Will consider UNIX and INFORMIX if applicant has financial or accounting experience. BS degree nice. Client Company will sponsor. Experience (yrs): 1+ Type: Permanent placement with our client ------------------------------ Subject: Sybase Database Administrator-Strong SUN/UNIX/C;Central NJ;0810-01 DBA with strong background in SUN Workstations, UNIX/C, and thorough knowledge of Sybase SQL. Will manage transaction log, security and system back-ups, do planning and evaluation of software, code migration, and reconfiguration of server, as necessary. Statistical background helpful. Experience (yrs): 5 Type: Permanent placement with our client ------------------------------ Subject: UNIX System Administrator with OS/2;NY City;0723-02 UNIX Sys Admin w/3 years exp., some OS/2, and at least 6 mos. in a tech supt or help desk enviroment. Implement new systems, diagnose printer problems, understand & check for UNIX errors (primarily related to file systems) and write tools. Need a PROACTIVE person. Degree preferred. Experience (yrs): 3+ Type: Single-assignment consulting position ------------------------------ Subject: DB2/CICS/COBOL Programmer Analyst;;1210-01 DB2/CICS/COBOL skills needed to do general applications programming. Experience (yrs): 2+ Type: Permanent position as a consultant ------------------------------ Subject: MSA Support Specialist - Various modules;NY City;1119-01 Support Specialist with 2+ years experience with MSA in one of the following areas: general ledger, accounts payable, purchasing, inventory or human resources. Degree preferred. Experience (yrs): 2+ Type: Permanent placement with our client ------------------------------ Subject: Sr. Accountant w.G/L Redesign Exp. + M&D G/L 2.03;NY City;1026-01 Sr. accountant w/track rcd in chart-of-accounts restructuring, G/L and corporate reptg. Substantial systems bkgd, including M&D G/L 2.03; client-server experience is nice. Also preferred: CPA and Big 6 experience. New York City assignment. Experience (yrs): 5+ Type: Single-assignment consulting position ------------------------------ Subject: Senior P/A - Cullinet/IDMS/ADSO/Culprit;NY City;1008-01 Programmer with 5-plus years of experience with Cullinet's General Ledger, versions 1.0 and 1.1, IDMS, ADSO, and Culprit to work with financial systems. Degree preferred. Experience (yrs): 5+ Type: Permanent position as a consultant ------------------------------ Subject: Senior Programmer Analyst - CICS/COBOL/VSAM;NY City;0929-01 Programmer/Analyst with 4+ years of experience with COBOL/CICS and VSAM to migrate and maintain financial systems. Experience (yrs): 4+ Type: Permanent placement with our client ------------------------------ Subject: IDMS/CICS Programmer Analyst;;0831-01 Strong IDMS/CICS skills needed to do coding and testing from high level design specs. Application is accounts receivable, accounts payable. PC skills nice. Experience (yrs): 3+ Type: Permanent position as a consultant ------------------------------ Subject: IBM Mainframe COBOL Programmer - Batch & CICS;NY City;0820-02 Programmer Analyst with 2+ years experience. Batch COBOL, COBOL 2, and command-level CICS are required; DB2 is nice. Degree preferred. Experience (yrs): 2+ Type: Permanent placement with our client ------------------------------ Subject: Cobol/Sybase/Securities Programmer;NY City;0804-01 Three years exper. in fixed income analysis, portfolio performance and tuning, COBOL and SQL, pref. Sybase, to do programming, performance and tuning for securities company. Experience (yrs): 3+ Type: Permanent placement with our client ------------------------------ Subject: Technical Writer - UNIX & Sablime;Central NJ;1207-01 Excellent writing skills, familiarity with UNIX, Text Manager and Sablime required. Experience with Mechanized Loop Testing desireable. Knowledge of ISO 9000 requirements and exp. with process documentation recommended. BS degree Experience (yrs): 3+ Type: Permanent position as a consultant ------------------------------ Subject: Medical Writer;Central NJ;1111-02 Experienced medical writer with some database exposure and fluency in Word Perfect 5.2 to create and revise documents in a clinical setting. BS Required. Experience (yrs): 2+ Type: Permanent position as a consultant ------------------------------ Subject: HW/SW Integration Engr-Fiber LANs, Video Servers;Central NJ;1201-01 Engineer with both hardware and software skills to specify, evaluate, procure and integrate the equipment needed for a testbed and trial of a video communications service. Start with an empty room; end with an operational system. Exposure to fiber LANs and video servers helpful. MSEE. Experience (yrs): 3+ Type: Single-assignment consulting position ------------------------------ Subject: HW/SW Technician-Fiber LANs, Video Servers;Central NJ;1201-02 Technician with both hardware and software skills to install and integrate the equipment needed for a testbed and trial of a video communications service. Start with an empty room; end with an operational system. Exposure to fiber LANs and video servers helpful. AA/BEE degree. Experience (yrs): 3+ Type: Single-assignment consulting position ------------------------------ Subject: Voice Comm Anal.- Rolm/System 85/Intellipath 5ESS;NY City;1022-01 Voice communications analyst with 2+ years of experience with ROLM ACD, System 85, Intellipath 5ESS and CSR to interview end-users, design and program systems, update the database and interface with programmers. Degree preferred. Experience (yrs): 2+ Type: Permanent placement with our client ------------------------------ Subject: Voice Communications Technician - AT&T/System 85;NY City;1022-02 Voice communications technician with 2+ years of experience with AT&T and System 85 to work with end-users, update the database and interface with programmers. Degree preferred. Experience (yrs): 2+ Type: Permanent position as a consultant ------------------------------ Subject: Sr. Systems Engineers: Wireless Comm Products;Central NJ;0904-01 Sr Sys Engr-resp for product certification, and liaison to mfgrs of wireless data comm products for PCs/terminals. Reqd: exp. in design & test of these products, hands-on test equip (protocol analyzers). Frequent travel (some foreign). MSEE pref'd. UNIX/DOS devel. exp nice. Salary open. Experience (yrs): 4+ Type: Permanent placement with our client ------------------------------ Subject: Senior Programmer - Windows SDK;;1207-03 Solid Windows SDK background, plus C, UNIX, MSDOS to do applications development. C++ SQL, and a relational database would be nice. Experience (yrs): 3-5 Type: Permanent placement with our client ------------------------------ Subject: Project Leader - Windows SDK;;1207-04 3 years Project Management experience, plus Windows SDK, UNIX, MSDOS. A relational database, C++, SQL would be nice. Experience (yrs): 3-5 Type: Permanent placement with our client ------------------------------ Subject: FOCUS Programmer Analyst;NY City;1122-01 Strong FOCUS background including the ability to create or modify database structures and create or modify FOCEXECS for maintenance and reporting. Proficient in VM, CMS & REXX; capable of operating in a PC/LAN environment. Experience (yrs): Type: Single-assignment consulting position ------------------------------ Subject: Clinical Trials Database Manager;Southern NJ;1119-03 Solid experience in setting up Clinical Trials Database. MS degree required. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: SQL/Windows Programmer Analyst;NY City;1108-01 Highly skilled Gupta SQL/Windows programmer analyst to do design and development in a variety of applications. SYBASE SQL Server nice. Position is located in Westchester County. Experience (yrs): 5 Type: Single-assignment consulting position ------------------------------ Subject: SAS Project Manager;Northern NJ;1022-04 8+ years SAS experience in pharmaceutical industry. 2+ years supervisory background. Responsible for technical support of the site as well as a small team of statisticians. MS degree. Experience (yrs): 8+ Type: Permanent placement with our client ------------------------------ Subject: Project Manager - UNIX, Oracle, C;;1018-01 Solid project management experinece to be responsible for a staff of up to 5; time management skills. Also do design, development and maintenance of financial/brokerage applications in UNIX/C/Oracle. BS degree. Experience (yrs): 4+ Type: Permanent placement with our client ------------------------------ Subject: Powerbuilder/C Programmer Analyst;NY City;1014-01 Strong Powerbuilder and C background. Oracle or Sybase nice, micro and mini programming background (not mainframe) to work in team of 2-6 to execute projects. Financial services industry background nice. Must be personable. Experience (yrs): 3 Type: Permanent placement with our client ------------------------------ Subject: Powerbuilder Team Leader with C;NY City;1014-02 Solid Powerbuilder and C needed; Oracle or Sybase nice, micro and mini programming background (not mainframe) to monitor and organize workload to team project plans. Financial services industry background nice. Must be personable. Hands on - lead by example. Experience (yrs): 3 Type: Permanent placement with our client ------------------------------ Subject: Smalltalk Specialist. C experience helpful.;Northern NJ;0923-02 Very strong Smalltalk V or 80 plus C (nice) to replicate an application built in C. Environment is OS/2, OS/400. Experience (yrs): 3+ Type: Permanent position as a consultant ------------------------------ Subject: SAS Programmer;;0902-01 To support clinical trials, write programs for standard format- ting of reports. SAS tools, and clinical experience required, Oracle nice. BS at least. Experience (yrs): 3+ Type: Permanent placement with our client ------------------------------ Subject: Senior level Tandem Programmer/Analyst;Northern NJ;0816-02 Sr.-level Tandem P/A with at least 5 years experience in the Tandem environment. Will develop technical design specifications, test plans/ scripts; some system admin. Familiarity with the Tandem operating system and hardware architecture, good communication skills and a degree are required. Experience (yrs): 5+ Type: Permanent placement with our client ------------------------------ Subject: Tandem Programmer/Analyst-SQL, C, COBOL w/OLTP bkd;Northern NJ;0816-03 Programmer with at least 3 years experience in the Tandem envir- onment. Will develop new code and maintain existing OLTP and batch applica- tions using SQL, C and COBOL 85. Good speaking skills. Experience (yrs): 3+ Type: Permanent placement with our client ------------------------------ Subject: Sr. level SAS Programmer w/Heavy Pharmaceuticals;Central NJ;0608-01 Candidates must have 5 years of clinical R&D and NDA experience. SAS BASIC, BASE, STAT, GRAPH and CONNECT. Will develop SAS programs, produce tables, listings and graphs. WordPerfect background; experience with CANDA a plus. Experience (yrs): 5 Type: Permanent position as a consultant ------------------------------ Subject: Quality Assurance Specialist - MS Windows;NY City;1014-03 Very strong testing background to set up procedures, help select test tools and create a testing environment for MS Windows. Must have MS Windows. Manage 1-2 others. X-Windows testing background applicable. Experience (yrs): 3 Type: Permanent placement with our client ------------------------------ Subject: PC Specialist - MS-Windows - FOXPRO;NY City;1209-01 PC Specialist needed to wire and install PC's and Novell LAN, install SW packages (MS Windows, MS-Word, Access and Excel) some programming in FOXPRO. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: PC Specialist with C;NY City;1119-02 PC Specialist with at least one year of experience to do maintenance and troubleshooting; some C programming. Must have knowledge of PC packages and be able to deal with end-users. Degree preferred; experience with VAX nice. Experience (yrs): 1+ Type: Permanent placement with our client ------------------------------ Subject: LAN Administrator/PC Support - MS Windows;NY City;1118-01 LAN administrators needed to wire and set up PC's on Novel LAN and install MS-Windows, MS-Word, Access, Excel, etc. Frequent interaction with end-users. Must have at least 2 years experience; Client-Server exp. preferred - RIGHT-TO-HIRE. Experience (yrs): 2+ Type: Single-assignment consulting position ------------------------------ Subject: GUI Developer - C/MS-Windows/Powerbuilder;;1005-01 Programmer Analyst to design and develop front-end systems using C, MS-Windows and Powerbuilder. Need 3+ years of experience and a degree. Experience (yrs): 3+ Type: Permanent placement with our client ------------------------------ Subject: LAN/WAN Network Admin.- Novell, TCP/IP, E-mail;NY City;0820-01 2+ years experience with the administration of Novell LANs, and WAN, with experience in TCP/IP and electronic mail. Some mainframe and PC background. Experience (yrs): 2+ Type: Permanent placement with our client ------------------------------ Please apply to: Winnertech Corporation Voice: (908) 758-9500 75 West Front Street Fax: (908) 758-9503 Red Bank, NJ 07701 Internet: rebecca@winnertech.com (ASCII format only) Xref: adcmail comp.os.linux.admin:1243 comp.os.linux.help:7141 Newsgroups: comp.os.linux.admin,comp.os.linux.help Path: adcmail!brantk From: brantk@atlas.com (Brant Katkansky) Subject: Re: Once again, using tape drives under Linux Message-ID: <1993Dec13.124012.2341@atlas.com> Organization: Atlas Telecom Inc. References: <KAIHP.93Dec6144912@idsun3.id.dth.dk> <jcejCHqo4v.EzC@netcom.com> <1993Dec9.154009.2656@TYRELL.NET> Date: Mon, 13 Dec 1993 12:40:12 GMT In article <1993Dec9.154009.2656@TYRELL.NET> stevem@tyrell.net (Steve Miller) writes: >James CE Johnson (jcej@netcom.com) wrote: >: I've been following (most) of this discussion and keep seeing >: floppy tapes an SCSI tapes mentioned. What about just a plain >: old 1/4" cart. tape drive? > >Yeah, What about the rest of the tape drives out there. I have an >Archive VP150 Tape drive useing the VP402 controller card that >works great for DOS and SCO Unix, but I have seen no mention >of using this drive with Linux. Any ideas on setting it up? >Anyone? > >I will post a summary if this hasn't been done already. If ther >is a FAQ that I've missed please steer me in the right direction >to find it. > Quite simple to do. Modify tpqic02.h (the pathname evades me at the moment, and I'm not on my Linux box at the moment) to suit your hardware, and recompile the kernel with QIC-02 support. Works with pl13+ kernels, don't know about prior releases. It's been working fine here on an Archive VP-150e and an Archive SC-402 controller. I get better than 5MB/min backup speeds. -- --- | Real engineers don't play tennis, or any other sport which brantk@atlas.com | requires you to change clothes. Mountain climbing is okay, Atlas Telecom | and real engineers wear their climbing boots to work in Path: spi.com!BGE Message-ID: <00433.2838614519.1818@spi.com> Organization: Scientific Placement, Inc. X-Charset: MACINTOSH From: BGE@spi.com (BGE) Date: Mon, 13 Dec 1993 1:52:18 CST Subject: C++ programmers-EC and TX Newsgroups: Distribution: Job Title & Location C++ programmers-EC and TX We have 2 clients looking for applicants who have object oriented software development skills and proficiency in C++. Must have unix. In addition, one position requires expertise in RDBMS (Oracle, Sybase, SQL) and the other requires communication (IPC, sockets, DCE, etc.). MS winodws, X windows, Motif would be a plus. Qualified candidates, please send resume to: Beth Evancheck Scientific Placement, Inc., P.O. Box 71, San Ramon, CA 94583 510-733-6168 Fax: 713-496-6802 Internet: bge@scientific.com; Compuserve: 71250,3001; AppleLink:scientific; Genie: D.SMALL6; AOL: DaveSmall Formats: Ascii text via Email preferred. Macintosh or PC Word processor formats are OK via Email (binhex). Please do not send LaTex or Postscript.Fax is discouraged unless Fine Setting on your fax machine is used (to enable OCR scanning). US Mail on 3.5 inch diskette is OK too. Immigration status: You must be a U.S. or Canadian Citizen or have a Permanent Residence Visa. New graduates: Employers utilize the college placement offices to hire new graduates. They do not employ recruiting firms for this purpose. We are unable to assist recent graduates. Beth Evancheck Scientific Placement, Inc., P.O. Box 71, San Ramon, CA 94583 510-733-6168 BGE@Scientific.com -or- SCIENTIFIC@APPLELINK.APPLE.COM Path: spi.com!BGE Message-ID: <00433.2838614525.1819@spi.com> Organization: Scientific Placement, Inc. X-Charset: MACINTOSH From: BGE@spi.com (BGE) Date: Mon, 13 Dec 1993 1:53:22 CST Subject: Unix Utilities-Southeast Newsgroups: misc.jobs.offered Distribution: na Job Title & Location Unix Utilities-Southeast Unix Utilities Guru needed for client located in the Southeastern United States. Must have 4 to 8 years Unix System Programming experience. Programming in target, C, Cshell, and/or korn shell. Well versed in commands and libraries and strong background in SCO Unix and X86 standards. Nice to have exposure to SNMP and Windows. Qualified applicants, please send resume to: Beth Evancheck Scientific Placement, Inc., P.O. Box 71, San Ramon, CA 94583 510-733-6168 Fax: 713-496-6802 Internet: bge@scientific.com; Compuserve: 71250,3001; AppleLink:scientific; Genie: D.SMALL6; AOL: DaveSmall Formats: Ascii text via Email preferred. Macintosh or PC Word processor formats are OK via Email (binhex). Please do not send LaTex or Postscript.Fax is discouraged unless Fine Setting on your fax machine is used (to enable OCR scanning). US Mail on 3.5 inch diskette is OK too. Immigration status: You must be a U.S. or Canadian Citizen or have a Permanent Residence Visa. New graduates: Employers utilize the college placement offices to hire new graduates. They do not employ recruiting firms for this purpose. We are unable to assist recent graduates. Beth Evancheck Scientific Placement, Inc., P.O. Box 71, San Ramon, CA 94583 510-733-6168 BGE@Scientific.com -or- SCIENTIFIC@APPLELINK.APPLE.COM Newsgroups: rec.arts.tv.soaps Path: sadtler!rick From: rick@sadtler.com (Rick Morris) Subject: Re: DOOL: Returning Characters Message-ID: <1993Dec13.125204.29746@sadtler.com> Organization: Sadtler Research Labs References: <CHHxIB.H5G@suncad.camosun.bc.ca> <1993Dec5.141333.6186@guvax> <2e4t2qINNr5m@eccdb1.pms.ford.com> <1993Dec11.211829.1@ulkyvx.louisville.edu> Date: Mon, 13 Dec 1993 12:52:04 GMT Roo Rote: >Cher: >> >> And another comment: Didn't Steve have plastic surgery and lose the >> patch before they killed him off? --> Cher > > Yes and no. He had surgery in the spring or summer of >1989 and got a glass eye, which he wore during the church >camp thing when he played Daniel. This story, as we all >know, included good old Gail. Someone please cue Rick :-) Oh Marcus! (heheeeeeeee) >(but *no* singing!) Anyhow, he went like this for a while. >While he and Marina were in Italy after the key, he was >attacked by some of Victor's dudes. In a very graphic >(IMO) scene, one of them basically went for his bad eye and >gouged it. As much as I liked Isabella, Marina was gorgeous! Now I channel surf trying to catch those Pantine commercials... "No dear, I'm looking for ... John Wayne movies...." -Rick. -- Rick Morris Email: rick@sadtler.com Sadtler Research Labs, Philadelphia -But I speak for myself --------------------------------------------------------------- Newsgroups: rec.arts.tv.soaps Path: sadtler!rick From: rick@sadtler.com (Rick Morris) Subject: Re: DOOL: TAN: For my lovely bride-to-be Message-ID: <1993Dec13.130151.29846@sadtler.com> Organization: Sadtler Research Labs References: <2e5b3s$1fa@access.digex.net> <2e5cf6$rqv@jethro.corp.sun.com> Date: Mon, 13 Dec 1993 13:01:51 GMT My older brother wrote: > > My tastes still run toward Motown, although I am getting past > my biases and listening to R .E. M. (at someone's insistance) > and Pygmy Tribal Music (no joke - gimme gimme walla walla > gimme walla). Not sure about G'N R. I may have to > build up to that. > > toomces, who thinks Rick should stop grinning because it > was an accident that I am older. > Well, I like Benny Goodman, Harry James. I like Buddy Holly and Dion and the Bellmonts. I like the Supremes, Stevie Wonder, and Three Dog Night. I like The Who, The Strawbs, and Procol Haram. I like Black Sabbath and Blue Oyster Cult. I like Billy Ray Cyrus, Laurie Morgan, and Lucinda Williams. But R.E.M, Pygmy Tribal Music, and Guns and Roses? I feel kinda like those "Waiting for better Days" folks waiting for better Rock and Roll. But then again no one has asked me to like those things. Perhaps if the One True Love of my life said, "Oh sweetie, Dontcha just Looooooooove Pigmy Tribal Music?" I might have to pretend... -Rick. (Not in Middle Age Crisis as my older brother is...) -- Rick Morris Email: rick@sadtler.com Sadtler Research Labs, Philadelphia -But I speak for myself --------------------------------------------------------------- Newsgroups: rec.arts.tv.soaps Path: sadtler!rick From: rick@sadtler.com (Rick Morris) Subject: Re: DOOL: TAN: Birthdays (Yuck!) Message-ID: <1993Dec13.132405.177@sadtler.com> Organization: Sadtler Research Labs References: <roepk001.755382442@maroon.tc.umn.edu> <2e5ghp$rqv@jethro.corp.sun.com> Date: Mon, 13 Dec 1993 13:24:05 GMT >Suzanne M Roepke wrote: > >>Thanks for all the birthday blessings. > >>Random thoughts... >> >> ... But it just seems to me that celebrating your birth and cake >>have nothing to do with each other. And when did cake become the big sign >>of celebration? > Well, cake symbolizes the birthing ritual of a small South American tribe of Pygmies known as the Coreognos. They were discovered in 1831 by one of Toomces great-great-great grandfathers. He discovered the tribe while searching for the Amazon Potato, a potato with more spunk than the Idaho varity. He was lost in a thicket of jungle and thought all was over when he came across a clearing and saw a pygmy woman giving birth while the father ate a mixture of fauna and moss. He never found the potatoes, but he did return with a custom that lives on today - the Birthday Cake. BTW: Toomces, in Coreognosese, means No Small Potatoes. -Rick. -- Rick Morris Email: rick@sadtler.com Sadtler Research Labs, Philadelphia -But I speak for myself ---------------------------------------------------------------
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.bugs Subject: Re: 3.2 NSI Experiences Date: 18 Dec 1993 17:18:26 +0100 Organization: Palumbian Research Labs Message-ID: <2evagi$30r@marsu.tynet.sub.org> References: <Eh3BDoS00iV3I7CYV=@andrew.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Charles William Swiger <infidel+@CMU.EDU> writes: >I hate to tell you this, but the newest versions of the GNU tools (such >as gcc 2.5.5) are *beta* releases, not final production. It is >perfectly reasonable for NeXT to ship stable versions of the GNU tools >(meaning Emacs 18.59 rather than 19.x, and older gcc, etc) that NeXT is >certain that they work. This is not much of a problem unless and until >there becomes a serious feature differential between the latest GNU >release and NeXT's versions, which is not the case as far as I can tell. I don't remember details by hard, but if I remember right there are some important improvements and bug fixes included in release 2.4.x which aren't in 2.2.2. Correct me if I'm wrong. -- Marsu: "Es gibt tatsaechlich Leute, die ohne Computer gluecklich und zufrieden leben." -- Frankie: "Ach was, die emulieren das doch nur!" ----- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Intel aside.
From: mow@marsu.tynet.sub.org (Markus Wenzel) Newsgroups: comp.sys.next.bugs Subject: Re: cdaudio on NS/i 3.2? Date: 18 Dec 1993 17:46:24 +0100 Organization: Palumbian Research Labs Message-ID: <2evc50$321@marsu.tynet.sub.org> References: <2ekk2p$g4i@netnews.upenn.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit awhite@plush.sas.upenn.edu (Andrew White) writes: >Has anyone gotten NS/i 3.2 to play audio CDs? When I insert Yes. Works fine for me (since 3.2) with an old Toshiba 3201. Did you turn on "public window server" for autostarting CDPlayer.app? -- Marsu: "Es gibt tatsaechlich Leute, die ohne Computer gluecklich und zufrieden leben." -- Frankie: "Ach was, die emulieren das doch nur!" ----- Markus Wenzel System administration, Consulting, Networking mow@marsu.tynet.sub.org on... NeXTSTEP / Unix / Novell / Windows NT IRC: Marsu Intel aside.
Newsgroups: comp.sys.next.bugs From: chisel.murphy.gun.com!samurai (Darcy Brockbank) Subject: Lost threads? Message-ID: <1993Dec17.233044.17196@gun.com> Sender: samurai@gun.com Organization: Gotham Users of NeXT, inc. Date: Fri, 17 Dec 1993 23:30:44 GMT Still in 3.2: [charon] [/Users/samurai/Projects/dm/data/citicorp] ps -agux | grep mach-task samurai 18016 1.4 0.6 1.66M 200K p8 S 0:00 grep mach-task root -1 0.6 21.3 52.2M 6.81M ? U 30:45 <mach-task> root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? SW 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? S < 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? ?W< 0:00 <mach-task> root -1 0.0 0.0 0K 0K ? U 0:07 <mach-task> root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> [charon] [/Users/samurai/Projects/dm/data/citicorp] What gives? Why can't this be fixed for once and all... it's been around for over a year, and three releases now. - db
Newsgroups: comp.sys.next.bugs From: chisel.murphy.gun.com!samurai (Darcy Brockbank) Subject: Bug in ld? Message-ID: <1993Dec18.040807.17447@gun.com> Sender: samurai@gun.com Organization: Gotham Users of NeXT, inc. Date: Sat, 18 Dec 1993 04:08:07 GMT When I use the -pg flag when compiling a C program, I get the following report from ld: ld: multiple definitions of symbol _exit /lib/gcrt0.o definition of _exit in section (__TEXT,__text) /lib/libsys_s.a(exit.o) definition of absolute _exit (value 0x50023f6) I really need to do some profiling... is this a bug (ie. I won't be doing profiling until NS3.3 in 8 months) or am I missing something obvious? - darcy
From: gbol@custard.think.com (Gregory Lampshire) Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer Subject: ClipView rawScroll: bug or bad documentation? Date: 19 Dec 93 15:30:54 Organization: Thinking Machines Corporation Distribution: world Message-ID: <GBOL.93Dec19153054@custard.think.com> I installed aView as the document of a ClipView. However, aView doesn't propagate it's display message and hence drawSelf:: message to it's subviews. A traceback shows #0 -[LayeredView drawSelf::]__FP11LayeredViewP13objc_selectorPC7_NXRecti (self=0x12a30c, _cmd=0x6186899, rect=0x3fff580, count=1) at Layers.m:55 #1 0x601a740 in -[View _display::] () #2 0x601a7a6 in -[View _display::] () #3 0x60558f6 in -[ClipView rawScroll:] () #4 0x6034d66 in -[ClipView _scrollTo:] () #5 0x6062938 in -[ScrollView _doScroller:] () #6 0x502ec0e in -[Object perform:with:] () #7 0x605dd7e in -[Application sendAction:to:from:] () #8 0x60624e0 in -[Control sendAction:to:] () #9 0x6062474 in -[Scroller sendAction:to:] () #10 0x606643e in -[Scroller trackScrollButtons:] () #11 0x60648ba in -[Scroller mouseDown:] () #12 0x605ef5e in -[Window sendEvent:] () #13 0x6027d08 in -[Application sendEvent:] () #14 0x602e494 in -[Application run] () #15 0x8a6a in main (argc=1, argv=0x3fffc44) at sda_main.m:11 I am using objc++. The docs say that [aView display::] should be called not [aView _display::] which apppears to be a private message and DOES NOT call the recursive display::. This is very bad as all subviews of the document view never get display messages! Has this been seen before? gregory
Newsgroups: comp.sys.next.bugs From: dsiebert@icaen.uiowa.edu (Doug Siebert) Subject: Re: Lost threads? Message-ID: <1993Dec19.204259.19851@icaen.uiowa.edu> Sender: usenet@icaen.uiowa.edu (UseNet News daemon) Organization: Iowa Computer Aided Engineering Network, University of Iowa References: <1993Dec17.233044.17196@gun.com> Date: Sun, 19 Dec 1993 20:42:59 GMT chisel.murphy.gun.com!samurai (Darcy Brockbank) writes: >Still in 3.2: >[charon] [/Users/samurai/Projects/dm/data/citicorp] ps -agux | grep >mach-task >samurai 18016 1.4 0.6 1.66M 200K p8 S 0:00 grep mach-task >root -1 0.6 21.3 52.2M 6.81M ? U 30:45 <mach-task> >root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? SW 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? S < 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? ?W< 0:00 <mach-task> >root -1 0.0 0.0 0K 0K ? U 0:07 <mach-task> >root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >[charon] [/Users/samurai/Projects/dm/data/citicorp] >What gives? Why can't this be fixed for once and all... it's >been around for over a year, and three releases now. Is this still the same bug, or a new one? Try telnet to localhost and hit return to exit the password: prompt and then hit control-D to quit. If doing this increases the mach-task count by one each time its the same bug (a signal during a select() call leaving a mach-task behind) Ugh, I was rather hoping they'd have it fixed after over a year as well. Why does NeXT even charge for OS upgrades, they should be paying us to beta-test them! At least MS didn't make people pay for the billions of NT betas (or did they? knowing Bill Gates, they probably are the only company to ever turn a profit on a product just during the beta period ;-) ) Doug Siebert || dsiebert@isca.uiowa.edu || Defeat Usenet spool grepping! Kibo Turkey Greece Perl Watcom Mason Clinton Illuminati Fnord
Newsgroups: comp.sys.next.bugs From: lloyd@world.std.com (Christopher Lloyd) Subject: Re: Lost threads? Message-ID: <CIB6Cn.6oI@world.std.com> Organization: The World Public Access UNIX, Brookline, MA References: <1993Dec17.233044.17196@gun.com> <1993Dec19.204259.19851@icaen.uiowa.edu> Date: Mon, 20 Dec 1993 00:50:47 GMT In article <1993Dec19.204259.19851@icaen.uiowa.edu> dsiebert@icaen.uiowa.edu (Doug Siebert) writes: >chisel.murphy.gun.com!samurai (Darcy Brockbank) writes: >>Still in 3.2: > >>[charon] [/Users/samurai/Projects/dm/data/citicorp] ps -agux | grep >>mach-task >>samurai 18016 1.4 0.6 1.66M 200K p8 S 0:00 grep mach-task >>root -1 0.6 21.3 52.2M 6.81M ? U 30:45 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? SW 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S < 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? ?W< 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? U 0:07 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>[charon] [/Users/samurai/Projects/dm/data/citicorp] > >>What gives? Why can't this be fixed for once and all... it's >>been around for over a year, and three releases now. Without the proper information it is hard to tell, but it is very likely this is NORMAL. Especially on NS/FIP. <mach-tasks>'s are used for a variety of things - namely device drivers. What's the output of: "kl_util -s" ?? >Is this still the same bug, or a new one? Try telnet to localhost and hit >return to exit the password: prompt and then hit control-D to quit. If doing >this increases the mach-task count by one each time its the same bug (a signal >during a select() call leaving a mach-task behind) Ugh, I was rather hoping >they'd have it fixed after over a year as well. Why does NeXT even charge >for OS upgrades, they should be paying us to beta-test them! At least MS >didn't make people pay for the billions of NT betas (or did they? knowing >Bill Gates, they probably are the only company to ever turn a profit on a >product just during the beta period ;-) ) Yea, whatever. -- :: Christopher Lloyd :: Yrrid Incorporated :: lloyd@world.std.com :: :: boy, don't we all look _smashing_ in red. ::
Newsgroups: comp.sys.next.bugs From: byron@ocf.nms.unt.edu (Byron Goodman) Subject: AAAAHHH! Message-ID: <1993Dec18.074900.13853@news.unt.edu> Sender: usenet@news.unt.edu (UNT USENet Adminstrator) Organization: University of North Texas Date: Sat, 18 Dec 1993 07:49:00 GMT Ok.. look, I'm having a problem getting NS 3.2 for Intel processors to install on my system. I boot the floppy and loads the binary drivers and and then goes right to Next Step Mach Kernel or something to that sort and just keeps scrolling something like : thread: lost interupt -735. I forgot to write it down before I reinstalled FreeBSD from tape back on my system. I'm really frustrated. I had a 486DX2/66 with HINT chip set yesterday then went and bought a P5 MB with Optiship set. I thought the HINT chip set was the problem. I really dont understand why NS will not run on my system. There is FreeUNIX out there that preforms really well and it runs on everything. Does Next, Inc. have lousy coders? I dont want to here about you should read the HW compatibilty guide. I did, and the only I dont have that is on there is a freaken Dell or Compaq MB. I've tried 3 different motherboards and I get the same problem. All of them with different chip sets. Here is my configuration as of today. AD P5 60MHZ 24MB of 64bit Memory Adaptec 1542B with BIOS UPGRADE Diamond Viper (I tried also with several different video cards) SONY CDR-7211 CDROM LOGITECH MOUSE I do not have an ethernet card in this machine. Are there any special settings the Adaptec 1542B should be set to? I really want to run NS, but with these problems I can not recommend it to anyone. -- +--------------------------------------+--------------------------------------+ | Byron Goodman | OS/2 and FreeBSD Programmer/Advocate | | byron@ocf.nms.unt.edu | Prefers not to use Microsoft..... | +--------------------------------------+--------------------------------------+
Newsgroups: comp.sys.next.bugs From: peter@beast.math.ualberta.ca (Peter Karbaliotis) Subject: Re: Lost threads? Message-ID: <1993Dec20.164049.17904@kakwa.ucs.ualberta.ca> Sender: news@kakwa.ucs.ualberta.ca Organization: University Of Alberta, Edmonton Canada References: <1993Dec19.204259.19851@icaen.uiowa.edu> Date: Mon, 20 Dec 1993 16:40:49 GMT In article <1993Dec19.204259.19851@icaen.uiowa.edu> dsiebert@icaen.uiowa.edu (Doug Siebert) writes: >chisel.murphy.gun.com!samurai (Darcy Brockbank) writes: > > >>Still in 3.2: > >>[charon] [/Users/samurai/Projects/dm/data/citicorp] ps -agux | grep >>mach-task >>samurai 18016 1.4 0.6 1.66M 200K p8 S 0:00 grep mach-task >>root -1 0.6 21.3 52.2M 6.81M ? U 30:45 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? SW 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S < 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? ?W< 0:00 <mach-task> >>root -1 0.0 0.0 0K 0K ? U 0:07 <mach-task> >>root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> >>[charon] [/Users/samurai/Projects/dm/data/citicorp] > >>What gives? Why can't this be fixed for once and all... it's >>been around for over a year, and three releases now. > > >Is this still the same bug, or a new one? Try telnet to localhost and hit >return to exit the password: prompt and then hit control-D to quit. If doing >this increases the mach-task count by one each time its the same bug (a signal >during a select() call leaving a mach-task behind) Ugh, I was rather hoping .. I did this several times on my NeXTstation running 3.2. I only got one new <mach-task> and it disappeared as soon as I closed the Terminal window in which I did the test. I repeated the test, looking at the mach-tasks more carefully. The first time I did the telnet I got a new <mach-task>. But as soon as I did a new telnet, that <mach-task> disappeared. After hitting ^D there was another dead <mach-task>. BTW, if you want to see if those <mach-tasks> are really dead you should use the 'm' option to ps: it shows all the threads belonging to each process. Note the entry below with <no-threads>. It's one of these that appears after the telnet to localhost followed by ^D. [40]% ps amx USER PID TT %CPU STAT PRI SYSTEM USER COMMAND root -1 ? 0.0 S 10 0:45.31 0:00.00 <mach-task> root -1 ? <no threads> <mach-task> root -1 ? 0.0 S 10 0:01.18 0:00.06 <mach-task> root -1 ? 0.0 SW< 24 0:00.01 0:00.00 <mach-task> root -1 ? 0.0 S 10 0:00.01 0:00.00 <mach-task> root -1 ? 0.0 S 10 0:00.58 0:00.01 <mach-task> root 0 ? 0.0 U < 24 0:00.00 0:00.00 (kernel idle) 0.0 R N 0 14334:16.75 0:00.09 0.0 U < 24 1:22.08 0:00.00 0.0 U < 24 0:00.03 0:00.01 0.0 U < 24 1:19.72 0:02.66 0.0 U < 24 6:33.04 0:02.89 0.0 U < 24 4:39.48 0:14.65 0.0 SW< 24 0:27.61 0:00.09 0.0 U < 24 24:49.54 21:37.31 0.0 U < 24 0:14.65 0:00.48 0.0 U < 24 0:04.66 0:04.89 0.0 S < 24 0:00.00 0:00.00 0.8 S < 24 2:59.98 0:32.86 root 1 ? 0.0 SW 10 0:04.30 0:00.09 /usr/etc/init -xx root 3 ? 0.0 S 10 0:00.25 0:00.00 /usr/etc/kern_loader -n 0.0 S 10 0:01.01 0:01.06 0.0 S 10 0:00.64 0:00.46 root 21 ? 0.0 SW 10 0:00.10 0:00.00 (nmserver) 0.0 S 10 0:35.23 0:08.16 0.0 SW 10 0:11.22 0:00.78 0.0 SW 10 0:00.00 0:00.00 0.0 SW 10 0:00.00 0:00.00 0.0 S 10 0:02.06 0:00.16 0.0 SW 10 0:00.00 0:00.00 0.0 S 10 0:00.17 0:00.00 0.0 SW 10 0:00.00 0:00.00 0.0 SW 10 0:00.00 0:00.00 0.0 SW 10 0:00.00 0:00.00 root 88 ? 0.0 SW 10 0:02.21 0:00.14 /usr/etc/portmap root 93 ? 0.0 SW 10 0:02.02 0:00.09 /usr/etc/nibindd root 94 ? 0.0 SW 10 0:26.01 0:08.17 /usr/etc/netinfod local root 98 ? 0.0 S 10 0:31.49 0:10.01 (lookupd) root 107 ? 0.0 S 10 0:29.96 0:00.44 (biod) root 108 ? 0.0 S 10 0:29.28 0:00.50 (biod) root 109 ? 0.0 S 10 0:30.75 0:00.44 (biod) root 110 ? 0.0 S 10 0:30.34 0:00.42 (biod) root 119 ? 0.0 SW 10 0:26.79 0:01.20 /usr/etc/autonfsmount -tm root 128 ? 0.0 SW 10 0:03.77 0:00.06 (inetd) root 134 ? 0.0 SW 10 0:06.14 0:00.29 -accepting connections (se root 139 ? 0.0 SW 10 0:00.59 0:00.04 (lpd) 0.0 S 10 0:00.04 0:00.00 root 149 ? 0.0 SW 10 0:00.01 0:00.00 /usr/lib/lpd root 150 ? 0.0 SW 10 0:00.37 0:00.00 (pbs) root 161 ? 0.0 S 10 4:50.84 0:12.68 (rwhod) root 170 ? 0.0 S 10 2:04.57 0:03.05 update root 173 ? 0.0 S 10 0:59.40 0:08.26 (cron) root 188 ? 0.0 SWN 8 0:04.87 0:00.48 (npd) peter 11273 ? 0.0 S 10 0:01.66 0:11.91 imageserver peter 17056 ? 6.6 S 16 0:31.99 9:06.72 - console (WindowServer) 0.0 S 16 0:00.21 0:00.03 root 17057 ? 0.0 SW 16 0:20.63 9:50.53 - console (loginwindow) root 17058 ? 0.0 SW 16 0:00.03 0:00.00 - console (WindowServer) root 17400 ? 0.0 SW 10 0:00.06 0:00.00 - D38400 ttydfa (getty) peter 18119 ? 0.0 SW 16 0:00.61 0:00.06 /usr/etc/pbs -a root 18121 ? 0.0 S 17 0:01.98 0:00.84 /usr/lib/NextStep/Workspac 0.0 SW 10 0:00.04 0:00.00 0.0 SW 10 0:00.01 0:00.00 peter 18122 ? 0.0 SW 10 0:00.04 0:00.00 appkitServer 0.0 SW 10 0:00.00 0:00.00 peter 18123 ? 0.0 S 16 0:02.89 0:04.02 /usr/lib/NextStep/Workspac peter 18124 ? 0.0 SW 16 0:00.57 0:00.42 /NextApps/Preferences.app/ peter 18125 ? 0.0 SW 16 0:00.46 0:00.68 /NextApps/Mail.app/Mail -N 0.0 SWN 4 0:00.00 0:00.00 0.0 SW 10 0:00.04 0:00.00 peter 18126 ? 0.0 SW 16 0:01.00 0:01.70 /NextApps/Librarian.app/Li 0.0 SW 10 0:00.00 0:00.00 root 18127 ? 2.7 S 16 0:05.58 0:06.64 /NextApps/Terminal.app/Ter 0.2 S 10 0:00.90 0:00.07 peter 18128 ? 0.0 SWN 0 0:00.56 0:00.74 /LocalApps/BackSpace.app/B peter 18133 ? 70.7 R 7 0:37.93 15:54.58 /LocalApps/NewsGrazer.app/ 0.0 SW 10 0:02.95 0:00.21 root 2 co 0.0 S 16 0:36.61 0:09.46 (mach_init) root 83 co 0.0 S 10 0:15.35 0:02.87 /usr/etc/syslogd peter 18148 p1 0.0 S 10 0:01.28 0:00.28 -csh (csh) root 18251 p1 10.4 R 9 0:00.34 0:00.01 ps amx -- Peter Karbaliotis - peter@beast.math.ualberta.ca - NeXTmail ok X is proof that something can fill a vacuum but still suck. --- Dennis Ritchie
From: wkwong@magnus.acs.ohio-state.edu (Waihon A Kwong) Newsgroups: comp.sys.next.bugs Subject: I can't Drag....... Date: 20 Dec 1993 18:33:42 GMT Organization: The Ohio State University Distribution: usa Message-ID: <2f4r66$dn@charm.magnus.acs.ohio-state.edu> Hi, I have just rebooted my Cube with NS3.1 because I suddenly can't drag anything from the File Viewer. Other application works fine, though. In the Console, it said: Software Version 3.1 (Lightning4H) Dec 20 11:27:51 Workspace: Drag service protocol error. Dec 20 11:28:01 Workspace: Drag service protocol error. Dec 20 11:28:09 Workspace: Drag service protocol error. Dec 20 11:28:35 Workspace: Drag service protocol error. Dec 20 11:28:38 Workspace: Drag service protocol error. ......and this keeps on forever (seems to be) so I logout and reboot after 20 mins of waiting. I tried to duplicate what I did, but I can't make this happen again. Anybody have the same experience? -- //|| // @ E-mail: wkwong@magnus.acs.ohio-state.edu // || // @ wkwong@ee.eng.ohio-state.edu //==||/\\ @ // || \\ @ "If you put your mind to it, you can accompish anything!"
From: joe@msri.org (Joe Christy) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Weirder yet, Mail.app bug Date: 20 Dec 1993 20:13:04 GMT Organization: Lawrence Berkeley Laboratory, Berkeley CA Message-ID: <36172@dog.ee.lbl.gov> Keywords: weird Mail.app bug Mail.app on NS3.0 black. Last week I posted: >We have a user (a _VERY_ Important User) whose Mail.app disturbingly often >fails to retrieve new mail. > >What seems to be happening is this: the NSF mount of NSF of >/var/spool/mail times out for an instant so her machine doesn't see it and >then remounts it. Unfortunately, Mail.app, once disappointed in its search >for new mail in the temporarily unavailable >/var/spool/mail/_VERY_ImportantUser, never goes back to look for it again, >even when we invoke "Get New Mail" from the Utilities> menu. The only sure >cure is to quit and restart Mail.app, which is not really very >satisfactory. > >Anyone out there seen anything like this? fixes? better work-arounds? What actually happens is that Mail.app appears to periodically blow away /var/spool/mail/_VERY_ImportantUser, and even after I've touch'ed it back into existence, reset the ownership and modes, and even sent mail, Mail.app only found the new mail on the third relaunch cycle. Eeep! Help! -- Joe Christy | Head of Mathematical Computing |Two wrongs joe@msri.org |Mathematical Sciences Research Institute|don't make a (510)643-6069| 1000 Centennial Drive |right, but FAX 642-8609| Berkeley, CA 94720 |three lefts do
From: wmorse@erasure-sl.cc.emory.edu (William Morse) Newsgroups: comp.sys.next.bugs Subject: Re: Lost threads? Date: 20 Dec 1993 22:42:14 GMT Organization: Emory University, Dept of Math and CS Distribution: world Message-ID: <2f59o6INNied@emory.mathcs.emory.edu> References: <1993Dec17.233044.17196@gun.com> In article <1993Dec17.233044.17196@gun.com> chisel.murphy.gun.com!samurai (Darcy Brockbank) writes: > > Still in 3.2: > > [charon] [/Users/samurai/Projects/dm/data/citicorp] ps -agux | grep > mach-task > samurai 18016 1.4 0.6 1.66M 200K p8 S 0:00 grep mach-task > root -1 0.6 21.3 52.2M 6.81M ? U 30:45 <mach-task> > root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? SW 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? S < 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? ?W< 0:00 <mach-task> > root -1 0.0 0.0 0K 0K ? U 0:07 <mach-task> > root -1 0.0 0.0 0K 0K ? S 0:00 <mach-task> > [charon] [/Users/samurai/Projects/dm/data/citicorp] > > What gives? Why can't this be fixed for once and all... it's > been around for over a year, and three releases now. > > - db ------- I believe that there will always be a certain number of <mach-task>s in NS. They are even in 2.x. They appear to be kernal services below the unix layer. Thus, they have no PID. The bug in 3.1 was that there was a "leak" of these services. When you, for example, telnet out, one is created. When you kill that connection, the <mach-task> was supposed to go away. In 3.1, it did not. Now, they do. So, it appears the bug has been fixed in 3.2. William ========================================================================= Consult. / ITD :::::::::::::::::::::::::::::::::::::::: Emory Law Student ========================================================================= W
Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs From: robert@ictv.com (Robert Patrick Thille) Subject: Bug in the handling of groups under 3.2? Message-ID: <1993Dec21.011114.18571@ictv.com> Sender: usenet@ictv.com Organization: ICTV, Santa Clara, CA (408) 562-9200 Distribution: usa Date: Tue, 21 Dec 1993 01:11:14 GMT Since we are running a mixed network and we use yp for most of the password and group handling stuff, we deleted some of the groups from the NetInfo database. They no longer showed up with names in the ls and Workspace output. However, ypcat group showed them. Does anyone have a fix, besides> ypcat group | niload group / ? -- Robert Thille NeXTMail robert@ictv.com OK 660 Bair Island Rd #40 Redwood City CA 94063 However, ypcat group showed them. Does anyone have a fix, besides> ypcat group | niload group / the Mac, though I'm mostly Unix based. I've got TMON, but it's not installed. Thanks, -- Robert Thille NeXTMail robert@ictv.com OK 660 Bair Island Rd #40 Redwood City CA 94063
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to NEXTSTEP information on the Internet Date: 21 Dec 1993 00:14:36 -0500 Organization: Next Announcements Message-ID: <2f60ns$sq8@digifix.digifix.com> * new additions Two new FTP sites on the other side of the planet. This post is made weekly, to help 'point' users to more NEXTSTEP information Topics include: comp.sys.next newsgroups related newsgroups comp.sys.next newsgroups mailing list ftp sites NeXTanswers comp.sys.next.* newsgroups -------------------------- Comp.Sys.Next.Advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. Comp.Sys.Next.Announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. Comp.Sys.Next.Bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. Comp.Sys.Next.Hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. Comp.Sys.Next.Marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. Comp.Sys.Next.Misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! Comp.Sys.Next.Programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. Comp.Sys.Next.Software This is a place to talk about [third party] software products that run on NEXTSTEP systems. Comp.Sys.Next.Sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups ------------------ Comp.Soft-Sys.Nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. Comp.Lang.Objective-C Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. Comp.Object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original Comp.Sys.Next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Getting the Newsgroups without getting News ------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe The ftp sites ------------- cs.orst.edu: The main site for North American submissions nova.cc.purdue.edu: Lots of older stuff, but very short on disk space ftp.informatik.uni-muenchen.de: In Germany. terra.stack.urc.tue.nl (Dutch NEXTSTEP User Group) cube.sm.dsi.unimi.it (Italian NEXTSTEP User Group) ftp.next.com: See the below ftp.next.com and NextAnswers@next.com ------------------------------------- From the document 1000_Help from ftp.next.com Welcome to the NeXTanswers information retrieval system! This system allows you to request online technical documents, drivers, and other software, which are then sent to you automatically. You can request documents by fax or Internet electronic mail, or you can transfer them by anonymous ftp. NeXTanswers is an automated retrieval system. Requests sent to it are answered electronically, and are not read or handled by a human being. NeXTanswers does not answer your questions or forward your requests. USING NEXTANSWERS BY E-MAIL To use NeXTanswers by Internet e-mail, send requests to NeXTanswers@next.com. Files are sent as NeXTmail attachments by default; you can request they be sent as ASCII text files instead. To request a file, include that file's ID number in the Subject line or the body of the message. You can request several files in a single message. You can also include commands in the Subject line or the body of the message. These commands affect the way that files you request are sent: ASCII causes the requested files to be sent as ASCII text SPLIT splits large files into 95KB chunks, using the MIME Message/Partial specification These commands return information about the NeXTanswers system: HELP returns this help file INDEX returns the list of all available files INDEX BY DATE returns the list of files, sorted newest to oldest SEARCH keywords lists all files that contain all the keywords you list (ignoring capitalization) For example, a message with the following Subject line requests three files: Subject: 2101 2234 1109 A message with this body requests the same three files be sent as ASCII text files: 2101 2234 1109 ascii This message requests two lists of files, one for each search: Subject: SEARCH Dell SCSI SEARCH NetInfo domain NeXTanswers will reply to the address in your From: line. To use a different address either set your Reply-To: line, or use the NeXTanswers command REPLY-TO <your-address> If you have any problem with the system or suggestions for improvement, please send mail to NeXTanswers-request@NeXT.com. USING NEXTANSWERS BY FAX To use NeXTanswers by fax, call (415) 780-3990 from a touch-tone phone and follow the instructions. You'll be asked for your fax number, a number to identify your fax (like your phone extension or office number), and the ID numbers of the files you want. You can also request a list of available files. When you finish entering the file numbers, end the call and the files will be faxed to you. If you have problems using this fax system, please call Technical Support at 1-800-848-6398. You cannot use the fax system outside the U.S & Canada. USING NEXTANSWERS BY ANONYMOUS FTP To use NeXTanswers by Internet anonymous FTP, connect to FTP.NEXT.COM and read the help file pub/NeXTanswers/README. If you have problems using this, please send mail to NeXTanswers-request@NeXT.com. Written by: Eric P. Scott eps@toaster.SFSU.EDU and Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
Newsgroups: comp.sys.next.hardware,comp.sys.next.bugs,comp.sys.next.software From: mdw@sitar.jazz.att.com (Mark Wuest-nscst-tnt) Subject: 3.X Powerdown Problem Fix (was Re: Problems powering NeXTstation down...) Message-ID: <CIE0wG.H6q@cbfsb.cb.att.com> Originator: news@cbnewsg.cb.att.com Sender: news@cbfsb.cb.att.com Organization: AT&T Bell Laboratories Date: Tue, 21 Dec 1993 13:45:51 GMT Well, Art Isbell sent me email after my post in which I discussed my slab hanging when I tried to powerdown and how, coincidentally, I had to uninstall and re-install DoveFax.app to be able to Fax after upgrading to 3.1 from 2.1. He noted that one of his clients had similar problems shutting down and that it was related to the Fax modem. (In his client's case, it could not shut down if the Fax modem was enabled but physically disconnected at the time shutdown was attempted.) It was no coincidence. The Fax software was the culprit. It turns out that re-installing the Fax software also fixed my shutdown problem. It's kinda hard to pursue further at this point, but there would appear to be a bug in the NeXT upgrade software that doesn't handle Fax modems/software properly. The workaround is to uninstall and reinstall the Fax software after upgrading. We'll see what happens when I get the nerve to upgrade 3.1->3.2, but I imagine it is a 2.X->3.X problem. -- Mark Wuest mdw@sitar.jazz.att.com (NeXT Mail Ok)
Newsgroups: comp.sys.next.bugs From: zumbusch@sel-berlin.uucp (S. Zumbusch) Subject: Re: AAAAHHH! Sender: news@slbh21 Message-ID: <1993Dec21.145710.7446@slbh21> Date: Tue, 21 Dec 1993 14:57:10 GMT References: <1993Dec18.074900.13853@news.unt.edu> Organization: Alcatel SEL Berlin Hi, try the following: get a seperate floppy controller. Disable the floppy controller from the Adaptec. Try again. For some reason which I don't understand, NS don't like the floppy contr. of the Adaptec. I know it's bullshit, but that's the way they treat customers.. :o) Sascha --
From: robert@steffi.demon.co.uk (Robert Nicholson) Newsgroups: comp.sys.next.bugs Subject: GDB NS3.1 (display enumerated types?) Date: 22 Dec 1993 13:12:15 -0000 Organization: me organized? That's a joke! Message-ID: <2f9h3f$2iq@steffi.demon.co.uk> Is this a common bug? Today gdb would persistently seg fault when I tried to "display" an enum. The enum value would print fine but it wouldn't "display". -- "Buzzword Development" the new way for the 90's. Promising to deliver but not delivering what you promised.
Newsgroups: comp.sys.next.bugs From: cowboy@omega.csuohio.edu (Joe Rosenfeld) Subject: Re: GatorFTP 1.4 bug? Message-ID: <1993Dec23.115818.15214@news.csuohio.edu> Sender: news@news.csuohio.edu (USENET News System) Organization: Cleveland State University References: <1993Dec6.203244.26267@cs.yale.edu> <2e7de5$rui@vtserf.cc.vt.edu> Date: Thu, 23 Dec 1993 11:58:18 GMT The previously described problem occurs on almost every attempt to "GET" a file and in almost every FTP site I use, regardless whether it has any fancy bells and whistles or not -- | Joe Rosenfeld j.rosenfeld@csuohio.edu | Automation Librarian (216) 687-6881 [FAX] | CSU Law Library trans.csuohio.edu [ANON FTP] | NeXTMail and MIME ok
Newsgroups: comp.sys.next.bugs From: cowboy@omega.csuohio.edu (Joe Rosenfeld) Subject: Now this is interesting ... and annoying Message-ID: <1993Dec23.120141.15309@news.csuohio.edu> Sender: news@news.csuohio.edu (USENET News System) Organization: Cleveland State University Date: Thu, 23 Dec 1993 12:01:41 GMT I have noticed a change in NX Mail.app behavior from 3.0 to 3.2. On the black hardware, running 3.0, you can drag a file icon inot your NeXT mail and it stays in icon form. In 3.2, running on my white hardware, every time you drag a file icon into NeXT mail it expands out of icon file and displays the actual file. I do not like this behavior! I alos noticed no way to stop it. Does anyone know what to do to allow files in NeXT Mail in the Mail.app running on 3.2 to remain in icon form? Please email me. I will summarize if I get the answer. TIA! -- | Joe Rosenfeld j.rosenfeld@csuohio.edu | Automation Librarian (216) 687-6881 [FAX] | CSU Law Library trans.csuohio.edu [ANON FTP] | NeXTMail and MIME ok
From: charlesa@learned.co.uk Newsgroups: comp.sys.next.bugs Subject: Re: GatorFTP 1.4 bug? Date: Thu, 23 Dec 93 14:05:22 GMT Organization: EUnet GB Message-ID: <2fc8pl$5rn@marble.Britain.EU.net> References: <1993Dec6.203244.26267@cs.yale.edu> <2e7de5$rui@vtserf.cc.vt.edu> <1993Dec23.115818.15214@news.csuohio.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In article <1993Dec23.115818.15214@news.csuohio.edu>, <cowboy@omega.csuohio.edu> writes: > The previously described problem occurs on almost every attempt to > "GET" a file and in almost every FTP site I use, regardless whether it > has any fancy bells and whistles or not > Me too. I tried it on Intel. C.
Newsgroups: comp.sys.next.misc,comp.sys.next.bugs.alt.internet.talk-radio From: macrae@geo.ucalgary.ca (Andrew MacRae) Subject: Re: Playing Sun .au files on a NeXT Message-ID: <Dec23.200456.30109@acs.ucalgary.ca> Sender: macrae@pandora.geo.ucalgary.ca Date: Thu, 23 Dec 1993 20:04:56 GMT References: <2f7crd$4cv@marble.Britain.EU.net> Organization: Geology & Geophysics Dept, University of Calgary, Canada Followup-To: comp.sys.next.bugs [note change in newsgroups and followup] charlesa@learned.co.uk writes: >I'm trying to play Internet Talk Radio files on a NeXT 3.1. ITR files are >distributed as Sun .au file formats, which I understand is closely associated >with the NeXT's .snd format. >If I rename the .au file to .snd, my NeXT will >play about the first 20 seconds, then freeze tight - like power down, crash >and burn. Does anybody know a way to get these files to play on a NeXT >without such spectacular side effects?? That is weird. I noticed the same effect with a _specific_ sound file on a Sun Sparc 2. The sound would play almost to completion, and then a garbled whine was emitted, and the machine would crash and reboot. It only happened for one file, but it was reproducable. The implication is that certain sound files (for no good reason) will crash the machine when played. It is a remote possibility, but maybe this is an example of the same effect? The NeXT and Sun sound formats are almost identical. Maybe they have a similar bug? (I know, very speculative!) Can you play the same sound files on a Sun with no ill effects? What tool are you using to play the sounds? Did you try "sndplay" from the command-line? If it is reproducable with standard tools, you should probably send the sound file to bugnext, if it isn't too big. -Andrew macrae@pandora.geo.ucalgary.ca or: macrae@geo.ucalgary.ca
Newsgroups: comp.sys.next.bugs From: cowboy@trans.csuohio.edu (Joe Rosenfeld) Subject: Re: Now this is interesting ... and annoying Message-ID: <1993Dec23.224725.18589@news.csuohio.edu> Sender: news@news.csuohio.edu (USENET News System) Organization: Cleveland State University Law Library References: <1993Dec23.120141.15309@news.csuohio.edu> Date: Thu, 23 Dec 1993 22:47:25 GMT Joe Rosenfeld (cowboy@omega.csuohio.edu) wrote: : I have noticed a change in NX Mail.app behavior from 3.0 to 3.2. On : the black hardware, running 3.0, you can drag a file icon inot your : NeXT mail and it stays in icon form. : In 3.2, running on my white hardware, every time you drag a file icon : into NeXT mail it expands out of icon file and displays the actual : file. I do not like this behavior! I alos noticed no way to stop it. : Does anyone know what to do to allow files in NeXT Mail in the : Mail.app running on 3.2 to remain in icon form? : Please email me. I will summarize if I get the answer. : TIA! Well, I have limited this to EPS and TIFF files only. They tend to expand anyway, so I guess no really untoward is going on. REgards and happy holidays.
From: pkron@corona.com (Peter Kron) Organization: Corona Design, Inc., Seattle, WA Distribution: world Date: Thu, 23 Dec 1993 21:20:14 PST Message-ID: <1993Dec24.052014.261@corona.com> Newsgroups: comp.sys.next.bugs Subject: Parallel port broken in 3.2 NS/I? Since 3.1 came out in May, I have been reliably printing to my HP DeskJet 550C using the configuration available on the archives and Ghostscript 2.6. Since upgrading to 3.2, however, printing is barely usable. If I'm lucky I can print a full page without some character getting dropped, breaking the data protocol and causing the printer to spew out pages of smileys and hearts in the finest DOS fashion. Nothing in the configuration has changed other than 3.2, so I have to conclude that the parallel port driver broke. (Well, the serial port works...2 out of 3 ain't bad?) It seems related to end of page/new page, for it never fails at the top of the page, only as it approaches the bottom. And the chances of success go up greatly if one page is printed at a time. The same pages printed as a range will certainly fail. Anyone else experiencing this or have any clues? Thanks --- NeXTMail:Peter_Kron@corona.com Corona Design, Inc. P.O. Box 51022 Seattle, WA 98115-1022
From: Mark Crispin <mrc@Ikkoku-Kan.Panda.COM> Newsgroups: comp.sys.next.bugs Subject: FAX won't render some PostScript? Date: Thu, 23 Dec 1993 23:56:21 -0800 Organization: University of Washington Message-ID: <MS-C.756719781.377401575.mrc@Ikkoku-Kan.Panda.COM> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII A project is in place to have a pair of NeXTs in a *highly* visible application that depends upon the FAX software functioning properly. The FAX support in NEXTSTEP would be ideal for this application; in fact, a slab and a cube have been purchased for this effort. Unfortunately, a problem has come up which threatens to derail the entire effort. Certain valid PostScript fails with ``invalid restore'' as being the only diagnostic given. Just about everything else is perfectly happy to render this PostScript, including NEXTSTEP to the screen or a NeXT printer. There is no indication of which restore is causing it to choke or any other context which would assist in debugging the problem. Matters are at the do-or-die stage. If a solution can't be found soon, the most likely outcome will be to punt on using NeXTs -- something being advocated by certain individuals (not me) on the grounds that the hardware is dead and NeXT Inc. may be next to die -- and use some other system. If so, it'll be a damn shame, and wouldn't look too good to have to punt on NEXTSTEP because of a bug. Whereas, the alternate would be that golly gee, these ``obsolete'' computers were put into service because they were the best solution for the problem. NeXT won't talk to you unless you give them a VISA number, and there is an objection to paying to be told ``we don't know the answer''. Nor can it wait until a new release; this application requires a plug & play solution. These systems are running 3.0. If it can be definitely confirmed that this is some problem fixed in 3.1 or 3.2, money could be generated to get the upgrade. Money can't, however, be generated to get a useless tracking number. So...anyone have any information that might salvage this project?
Newsgroups: comp.sys.next.bugs From: rpomeroy@aunext1.amd.com (Ron Pomeroy x(Coop)) Subject: Re: FAX won't render some PostScript? Message-ID: <CIJrIF.373@dvorak.amd.com> Sender: news@dvorak.amd.com (Usenet News) Organization: Advanced Micro Devices, Austin TX References: <MS-C.756719781.377401575.mrc@Ikkoku-Kan.Panda.COM> Distribution: usa Date: Fri, 24 Dec 1993 16:08:39 GMT In article <MS-C.756719781.377401575.mrc@Ikkoku-Kan.Panda.COM> Mark Crispin <mrc@Ikkoku-Kan.Panda.COM> writes: >>A project is in place to have a pair of NeXTs in a *highly* visible >>application that depends upon the FAX software functioning properly. The FAX >>support in NEXTSTEP would be ideal for this application; in fact, a slab and a >>cube have been purchased for this effort. >> >>Unfortunately, a problem has come up which threatens to derail the entire >>effort. Certain valid PostScript fails with ``invalid restore'' as being the >>only diagnostic given. Just about everything else is perfectly happy to >>render this PostScript, including NEXTSTEP to the screen or a NeXT printer. >>There is no indication of which restore is causing it to choke or any other >>context which would assist in debugging the problem. >> >>Matters are at the do-or-die stage. If a solution can't be found soon, the >>most likely outcome will be to punt on using NeXTs -- something being >>advocated by certain individuals (not me) on the grounds that the hardware is >>dead and NeXT Inc. may be next to die -- and use some other system. >> >>If so, it'll be a damn shame, and wouldn't look too good to have to punt on >>NEXTSTEP because of a bug. Whereas, the alternate would be that golly gee, >>these ``obsolete'' computers were put into service because they were the best >>solution for the problem. >> >>NeXT won't talk to you unless you give them a VISA number, and there is an >>objection to paying to be told ``we don't know the answer''. Nor can it wait >>until a new release; this application requires a plug & play solution. >> >>These systems are running 3.0. If it can be definitely confirmed that this is >>some problem fixed in 3.1 or 3.2, money could be generated to get the upgrade. >>Money can't, however, be generated to get a useless tracking number. >> >>So...anyone have any information that might salvage this project? Sounds like you need a PostScript degugging/development environment. I seem to recall Adobe used to sell such a beast for the NeXT. Unfortunately, I can't seem to locate my 3rd party catalog (looks like someone nik'ed it). Someone want to look it up ? -- Ronald Pomeroy Advanced Micro Devices CAM Applications Group rpomeroy@aunext1.amd.com
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.software,comp.sys.next.sysadmin From: andrew@stone.com (Andrew Stone) Subject: WARNING: NS 3.2 and DataPhile 2.0 incompatibilities & workarounds Message-ID: <1993Dec24.175209.801@stone.com> Keywords: DataPhile 3.2 Sender: andrew@stone.com Organization: Stone Design Corp Date: Fri, 24 Dec 1993 17:52:09 GMT DataPhile 2.0 has serious problems running on NEXTSTEP 3.2. Since DataPhile 2.0 shipped before NS 3.2, this was totally unpredictable. Even the person who made the change to the IXKIT was unaware of its adverse effects on ALL applications dependent upon the indexing kit. Stone Design and Pangea have isolated the main problem that is responsible for corrupting databases and destroying views. Basically any view or text field or entry list larger than 8K in size will trigger the bug. NeXT is aware of the problem, knows that it is theirs, and we await their fix. In the meantime, we have made available a patch program, PatchDP, for DataPhile 2.0 that allows it to use the 3.1 shared libraries rather than the ones in 3.2. This circumvents most of the problems, but we would still encourage you to take precautions, such as exporting regularly and often, until DataPhile 2.1 is released Q1 94. If you decide to use DP2.0 unpatched on NS3.2, review your databases for the potential problem areas mentioned above before logging out. In particular, the Cities entry list provided in your DataPhileAux.pkg should not be used. Also, follow the instructions for fixing finds in SEARCHING_DP. Basically, we recommend that you should either not upgrade to NS 3.2, or patch DP 2.0. The PatchDP program is available on the Internet at the following ftp site: ftp.cs.unm.edu, in directory pub/stone/DataPhile/NS_3.2-DataPhile_Workarounds.tar.Z sum NS_3.2-DataPhile_Workarounds.tar.Z 28557 65 If you cannot ftp, send email to info@stone.com with the subject "Send Patch - ASCII" or "Send Patch - NeXTMAIL" We are on holiday until January 3, 1994; but we will fill requests for the patch during the holidays. May '94 be Happy and Bug Free! -- ||<<->>||<<==>>||<<++>>||<<?>>||<<+>>||<<-->>||<<==>>||<<+>>|| !! Andrew Stone !! (505) 345-4800 !! !! andrew@stone.com <> Stone Design Corp !! ||<<->>||<<==>>||<<++>>||<<?>>||<<+>>||<<-->>||<<==>>||<<+>>||
From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.bugs Subject: Re: FAX won't render some PostScript? Message-ID: <1438@rtbrain.rightbrain.com> Date: 25 Dec 93 03:06:39 GMT References: <MS-C.756719781.377401575.mrc@Ikkoku-Kan.Panda.COM> Sender: glenn@rightbrain.com Mark Crispin writes > Unfortunately, a problem has come up which threatens to derail the entire > effort. Certain valid PostScript fails with ``invalid restore'' as being the > only diagnostic given. It's hard for us to help with the problem without seeing the PS code, but here's a guess.... The code may not be fully compliant with the document structuring conventions, and the fax code may be reordering the pages. Alternatively, there may be a bug in the fax code that incorrectly reads some of the comments in the structuring conventions. Experiment: try paging both through the PS file both forward and backward in Preview. That should help ensure its page independence. Experiment: try stripping all %% comments out of the file, and/or changing the first line to simply "%!", to see if the fax implemention will render it correctly. Question: where did the PS come from? Which application? Are there any embedded files, weird fonts, or other "interesting" things about it? -- Glenn Reid glenn@rightbrain.com Woodside, California Shameless Plug: buy my book, "Thinking in PostScript"
Newsgroups: comp.sys.next.bugs From: mckelvey@fafnir.com (James W. McKelvey) Subject: Formatting External Floppies - 3.2 Message-ID: <CIKAnn.EDF@fafnir.com> Sender: mckelvey@fafnir.com (James W. McKelvey) Organization: Fafnir Software, Saugus, CA, USA Date: Fri, 24 Dec 1993 23:02:10 GMT NeXT has finally put the "official" answer to formatting external floppies to NeXTanswers. Since there has been some discussion of this topic recently, I'm posting it below. Note that the official solution requires a shell, and root access. It seems to squeeze a few more bytes out of the floppies. The unofficial solution, as posted before, is to use the 3.0 version of /usr/etc/disk. PLI External SCSI Floppy Drive format boot block extends beyond front porch Q: When I try to format a floppy disk with my external SCSI floppy drive, it fails and shows an alert panel that says "Cannot initialize disk. See console for errors." In the console I see this message if it is a new unformatted disk: /usr/etc/disk -i -h localhost -l "UntitledDisk" /dev/rsd1a Target 5: MEDIA ERROR; block 0H retry 1 Target 5: MEDIA ERROR; block 0H retry 2 Target 5: MEDIA ERROR; block 0H retry 3 Target 5: MEDIA ERROR; block 0H retry 4 Target 5: MEDIA ERROR; block 0H retry 5 Target 5: MEDIA ERROR; block 0H retry 6 Target 5: MEDIA ERROR; block 0H retry 7 Target 5: MEDIA ERROR; block 0H retry 8 Target 5: MEDIA ERROR; block 0H retry 9 sd1 (5,0): sense key:0x3 additional sense code:0x12 SCSI Block in error = 0 (no valid label) Read of sector 0 failed If the disk have been formatted and you try to re-initialize the disk, you will see this message in the console: /usr/etc/disk -i -h localhost -l "UntitledDisk" /dev/rsd1a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi device = /dev/rsd1a block size = 512 capacity = 1 MBytes Disk Format in progress... ***Format Complete*** writing disk label boot block extends beyond front porch How can I initialize floppy disks. A: This assumes your external SCSI floppy drive is at sd1. You must be logged in as, or su'd to root. (You type the things in bold...) localhost:18# sdform /dev/rsd1a device = /dev/rsd1a block size = 512 capacity = 1 MBytes ***FORMATTING THIS DISK CAUSES ALL DISK DATA TO BE LOST*** This will take approximately 5 minutes. Do you wish to proceed? (Y/anything) Y Disk Format in progress... ***Format Complete*** localhost:19# disk /dev/rsd1a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi Disk utility disk> label label information: print, write? write enter host name: localhost enter disk label: UntitledDisk writing disk label disk> quit localhost:20# newfs /dev/rsd1a setting optimization for space with minfree less than 10 Warning: 12 sector(s) in last cylinder unallocated /dev/rsd1a: 1392 sectors in 78 cylinders of 2 tracks, 9 sectors 1.4Mb in 5 cyl groups (16 c/g, 0.29Mb/g, 64 i/g) super-block backups (for fsck -b#) at: 16, 320, 592, 896, 1168, localhost:21# disk -e /dev/rsd1a disk name: PLI SUPER FLOPPY disk type: removable_rw_scsi localhost:22# Valid: 3.1, 3.2 68K QAxx [xx will be replaced by the unique QAP number] -- The gentle journey jars to stop. The drifting dream is done. The long gone goblins loom ahead; the deadly, that we thought were dead, stand waiting, every one. -- Walt Kelly Jim McKelvey mckelvey@fafnir.com
From: dave@truth.asg.arlut.utexas.edu (David Slotnick) Newsgroups: comp.sys.next.bugs Subject: DPSDoUserPathWithMatrix() bug Date: 27 Dec 1993 01:53:36 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <2flf70$98h@geraldo.cc.utexas.edu> There is a documented bug in DPSDoUserPathWithMatrix() which causes a DPS error if numCoords and/or numOps are large (~10,000-20,000). Unfortunately, I'm writing a mission critical contouring application which ABSOLUTELY REQUIRES me to specify user paths with at least this many segments. Does anyone know of a workaround? I would greatly appreciate any helpful information you could provide! Please respond via e-mail. Thanks! -- *** David Slotnick *** Applied Research Laboratories *** dave@truth.asg.arlut.utexas.edu NeXTmail desired and appreciated
From: sanguish@digifix.com Newsgroups: comp.sys.next.announce,comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.advocacy,comp.sys.next.hardware,comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.programmer,comp.sys.next.marketplace Subject: Quick Guide to NEXTSTEP information on the Internet Date: 27 Dec 1993 00:13:44 -0500 Organization: Next Announcements Message-ID: <2flqu8$tl@digifix.digifix.com> This post is made weekly, to help 'point' users to more NEXTSTEP information Topics include: comp.sys.next newsgroups related newsgroups comp.sys.next newsgroups mailing list ftp sites NeXTanswers comp.sys.next.* newsgroups -------------------------- Comp.Sys.Next.Advocacy This is the "why NEXTSTEP is better (or worse) than anything else in the known universe" forum. It was created specifically to divert lengthy flame wars from .misc. Comp.Sys.Next.Announce Announcements of general interest to the NeXT community (new products, FTP submissions, user group meetings, commercial announcements etc.) The NEXTSTEP FAQs are posted here monthly as well. This is a moderated newsgroup, meaning that you can't post to it directly. Submissions should be e-mailed to next-announce@digifix.com where the moderator (Scott Anguish) will screen them for suitability. Comp.Sys.Next.Bugs A place to report verifiable bugs in NeXT-supplied software. Material e-mailed to Bug_NeXT@NeXT.COM is not published, so this is a place for the net community find out about problems when they're discovered. This newsgroup has a very poor signal/noise ratio--all too often bozos post stuff here that really belongs someplace else. It rarely makes sense to crosspost between this and other c.s.n.* newsgroups, but individual reports may be germane to certain non-NeXT- specific groups as well. Comp.Sys.Next.Hardware Discussions about NeXT-label hardware and compatible peripherals, and non-NeXT-produced hardware (e.g. Intel) that is compatible with NEXTSTEP. In most cases, questions about Intel hardware are better asked in comp.sys.ibm.pc.hardware. Questions about SCSI devices belong in comp.periphs.scsi. This isn't the place to buy or sell used NeXTs--that's what .marketplace is for. Comp.Sys.Next.Marketplace NeXT stuff for sale/wanted. Material posted here must not be crossposted to any other c.s.n.* newsgroup, but may be crossposted to misc.forsale.computers.workstation or appropriate regional newsgroups. Comp.Sys.Next.Misc For stuff that doesn't fit anywhere else. Anything you post here by definition doesn't belong anywhere else in c.s.n.*--i.e. no crossposting!!! Comp.Sys.Next.Programmer Questions and discussions of interest to NEXTSTEP programmers. This is primarily a forum for advanced technical material. The NEXTSTEP programmer FAQs are posted here. Generic UNIX questions belong elsewhere (comp.unix.questions), although specific questions about NeXT's implementation or porting issues are appropriate here. Note that there are several other more "horizontal" newsgroups (comp.lang.objective-c, comp.lang.postscript, comp.os.mach, comp.protocols.tcp-ip, etc.) that may also be of interest. Comp.Sys.Next.Software This is a place to talk about [third party] software products that run on NEXTSTEP systems. Comp.Sys.Next.Sysadmin Stuff relating to NeXT system administration issues; in rare cases this will spill over into .programmer or .software. related Newsgroups ------------------ Comp.Soft-Sys.Nextstep Like comp.sys.next.software and comp.sys.next.misc combined. Exists because NeXT is a software-only company now, and comp.soft-sys is for discussion of software systems with scope similar to NEXTSTEP. Comp.Lang.Objective-C Technical talk about the Objective-C language. Implemetations discussed include NeXT, Gnu, Stepstone, etc. Comp.Object Technical talk about OOP in general. Lots of C++ discussion, but NeXT and Objective-C get quite a bit of attention. At times gets almost philosophical about objects, but then again OOP allows one to be a programmer/philosopher. (The original Comp.Sys.Next no longer exists--do not attempt to post to it.) Exception to the crossposting restrictions: announcements of usenet RFDs or CFVs, when made by the news.announce.newgroups moderator, may be simultaneously crossposted to all c.s.n.* newsgroups. Getting the Newsgroups without getting News ------------------------------------------- Thanks to Michael Ross at antigone.com, the main NEXTSTEP groups are now available as a mailing list digest as well. next-nextstep-d next-advocacy-d next-announce-d next-bugs-d next-hardware-d next-marketplace-d next-misc-d next-programmer-d next-software-d next-sysadmin-d (For a full description, send mail saying LISTS to <digestif@antigone.com>). The subscription syntax is essentially the same as LISTSERV's. To subscribe, send a message to <digestif@antigone.com> saying: SUB Listname YourName Example: SUB next-hardware-d John Doe The ftp sites ------------- cs.orst.edu: The main site for North American submissions nova.cc.purdue.edu: Lots of older stuff, but very short on disk space ftp.informatik.uni-muenchen.de: In Germany. ftp.next.com: See the below ftp.next.com and NextAnswers@next.com ------------------------------------- From the document 1000_Help from ftp.next.com Welcome to the NeXTanswers information retrieval system! This system allows you to request online technical documents, drivers, and other software, which are then sent to you automatically. You can request documents by fax or Internet electronic mail, or you can transfer them by anonymous ftp. NeXTanswers is an automated retrieval system. Requests sent to it are answered electronically, and are not read or handled by a human being. NeXTanswers does not answer your questions or forward your requests. USING NEXTANSWERS BY E-MAIL To use NeXTanswers by Internet e-mail, send requests to NeXTanswers@next.com. Files are sent as NeXTmail attachments by default; you can request they be sent as ASCII text files instead. To request a file, include that file's ID number in the Subject line or the body of the message. You can request several files in a single message. You can also include commands in the Subject line or the body of the message. These commands affect the way that files you request are sent: ASCII causes the requested files to be sent as ASCII text SPLIT splits large files into 95KB chunks, using the MIME Message/Partial specification These commands return information about the NeXTanswers system: HELP returns this help file INDEX returns the list of all available files INDEX BY DATE returns the list of files, sorted newest to oldest SEARCH keywords lists all files that contain all the keywords you list (ignoring capitalization) For example, a message with the following Subject line requests three files: Subject: 2101 2234 1109 A message with this body requests the same three files be sent as ASCII text files: 2101 2234 1109 ascii This message requests two lists of files, one for each search: Subject: SEARCH Dell SCSI SEARCH NetInfo domain NeXTanswers will reply to the address in your From: line. To use a different address either set your Reply-To: line, or use the NeXTanswers command REPLY-TO <your-address> If you have any problem with the system or suggestions for improvement, please send mail to NeXTanswers-request@NeXT.com. USING NEXTANSWERS BY FAX To use NeXTanswers by fax, call (415) 780-3990 from a touch-tone phone and follow the instructions. You'll be asked for your fax number, a number to identify your fax (like your phone extension or office number), and the ID numbers of the files you want. You can also request a list of available files. When you finish entering the file numbers, end the call and the files will be faxed to you. If you have problems using this fax system, please call Technical Support at 1-800-848-6398. You cannot use the fax system outside the U.S & Canada. USING NEXTANSWERS BY ANONYMOUS FTP To use NeXTanswers by Internet anonymous FTP, connect to FTP.NEXT.COM and read the help file pub/NeXTanswers/README. If you have problems using this, please send mail to NeXTanswers-request@NeXT.com. Written by: Eric P. Scott eps@toaster.SFSU.EDU and Scott Anguish sanguish@digifix.com Additions from: Greg Anderson (Greg_Anderson@afs.com) and Michael Pizolato (Michael_Pizolato@afs.com)
From: glenn@rightbrain.com (Glenn Reid) Newsgroups: comp.sys.next.bugs Subject: Re: DPSDoUserPathWithMatrix() bug Message-ID: <1439@rtbrain.rightbrain.com> Date: 27 Dec 93 07:51:18 GMT References: <2flf70$98h@geraldo.cc.utexas.edu> Sender: glenn@rightbrain.com David Slotnick writes > There is a documented bug in DPSDoUserPathWithMatrix() which > causes a DPS error if numCoords and/or numOps are large > (~10,000-20,000). Unfortunately, I'm writing a mission > critical contouring application which ABSOLUTELY REQUIRES me > to specify user paths with at least this many segments. First, you must convince us (me) that you really have a condition that "absolutely requires" you to have this many segments in your user paths. I have been looking at PostScript stuff for a long time, and I've never yet seen such a case. The workaround for this documented bug is, of course, to use fewer segments in your path, and we can perhaps help with that workaround if you describe the problem more fully, so we can appreciate (and work around) this absolute requirement. -- Glenn Reid glenn@rightbrain.com Woodside, California Shameless Plug: buy my book, "Thinking in PostScript"
From: dave@truth.asg.arlut.utexas.edu (David Slotnick) Newsgroups: comp.sys.next.bugs Subject: Re: DPSDoUserPathWithMatrix() bug Date: 27 Dec 1993 15:48:46 GMT Organization: The University of Texas at Austin, Austin, Texas Message-ID: <2fn04u$s8b@geraldo.cc.utexas.edu> >> There is a documented bug in DPSDoUserPathWithMatrix() which >> causes a DPS error if numCoords and/or numOps are large >> (~10,000-20,000). Unfortunately, I'm writing a mission >> critical contouring application which ABSOLUTELY REQUIRES me >> to specify user paths with at least this many segments. > >First, you must convince us (me) that you really have a condition >that "absolutely requires" you to have this many segments in your >user paths. I have been looking at PostScript stuff for a long >time, and I've never yet seen such a case. The workaround for >this documented bug is, of course, to use fewer segments in your >path, and we can perhaps help with that workaround if you describe >the problem more fully, so we can appreciate (and work around) >this absolute requirement. Here I was all prepared to post a firm statement of my needs, when in the middle of constructing the post I came upon a way to subdivide the path! Thanks, Glenn, for forcing me to rethink the problem! --- *** David Slotnick *** Applied Research Laboratories *** dave@truth.asg.arlut.utexas.edu NeXTmail desired and appreciated -- *** David Slotnick *** Applied Research Laboratories *** dave@truth.asg.arlut.utexas.edu NeXTmail desired and appreciated
From: haker@whitewater.chem.wisc.edu (M Haker) Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer Subject: DriverKit and out-of-line messaging:still causing problems Date: 28 Dec 1993 01:50:02 GMT Organization: Division of Information Technology Message-ID: <2fo3ca$i7@news.doit.wisc.edu> Hello all again, I've got a functioning 3.2 driver for an Analog to Digital data aquisition (DAQ) board, or so I thought. The driver functions asyncronously. A user control/monitor program connects to the driver, sends it a mach_port on which it will receive data blocks, configures the driver for a DAQ session, arms the board for external triggers, then launches a thread to sit on the data port waiting for incoming messages of dataBlocks or status messages. My current problem is that no matter how I setup my mach message, for some reason it only maps the first page (8192 bytes) of my drivers data buffer into my user program. And sometimes it fails to map the buffer even though the msg_send was sucessful. I didn't realize I had a problem until I got past the simple tests and really gave my driver a moderate DAQ task (a single trigger block of 64kb of data in 1 sec). QUESTIONS: 1) Does the msg_simple=FALSE and msg_type_inline=FALSE handle all the details of mapping the vm pages between the two tasks, or do you have to also use the vm_write command to do the mapping as in the /NextDeveloper/Examples/Unix/LKSOutOfLineData example? Mine seemed to work fine up to a single vm page without any vm_write or vm_read, and it doesn't seem to solve this problem. 2) Are out-of-line data blocks limited to single vm pages, or can you out-of-line a pointer to as big a region as can be allocated? 3) Does the msg_type_name and msg_type_size fields in the msg_type_t type really do anything special, or could you always use MSG_TYPE_BYTE, 8 and just adjust the msg_type_number to correspond to the number of bytes in a data block? 4) Is there anything special about the KernelIOTask in regard to this between task mapping of vm regions? Here's how my driver allocates it's data buffer: (vm_allocate also worked) r = vm_statistics(kern_serv_kernel_task_port(), &vm_stats); threadData->bufferSize = threadData->samplesPerTrigger * sizeof(unsigned short); numPages = (threadData->bufferSize)/(vm_stats.pagesize)+2; IOLog(" ORIGbufferSize=%d numPages=%d\n" ,threadData->bufferSize,numPages); threadData->bufferSize = numPages * vm_stats.pagesize; IOLog(" NEWbufferSize=%d\n",threadData->bufferSize); threadData->mallocPtr = IOMalloc(threadData->bufferSize); if(!IOIsAligned(threadData->mallocPtr, vm_stats.pagesize)) { IOLog(" buffer not page aligned\n"); threadData->dataBuffer = IOAlign(unsigned short*, threadData->mallocPtr, vm_stats.pagesize); } else { IOLog(" buffer is already aligned\n"); threadData->dataBuffer = threadData->mallocPtr; } IOLog(" allocated buffer %d\n",(int)threadData->dataBuffer); here is the message structure I'm using: typedef struct { msg_header_t header; msg_type_t t1; int frameNum; int dataCount; /* No. of shorts in *data */ msg_type_t t2; unsigned short *data; } data_msg_t; and here is the code for creating the message and sending it out: dmsg->header.msg_type = MSG_TYPE_NORMAL; dmsg->header.msg_local_port = NULL; dmsg->header.msg_remote_port = threadData->dataPort; dmsg->header.msg_id = msgID; dmsg->header.msg_size = sizeof(data_msg_t); dmsg->t1.msg_type_name = MSG_TYPE_INTEGER_32; dmsg->t1.msg_type_size = 32; dmsg->t1.msg_type_number = 2; dmsg->t1.msg_type_inline = TRUE; dmsg->t1.msg_type_longform = FALSE; dmsg->t1.msg_type_deallocate = FALSE; dmsg->frameNum = threadData->frameNum; dmsg->dataCount = threadData->dataCount; if(msgID==DATA_BLOCK) { dmsg->header.msg_simple = FALSE; dmsg->t2.msg_type_name = MSG_TYPE_INTEGER_16; dmsg->t2.msg_type_size = 16; dmsg->t2.msg_type_number = threadData->dataCount; dmsg->t2.msg_type_inline = FALSE; dmsg->t2.msg_type_longform = FALSE; dmsg->t2.msg_type_deallocate = FALSE; dmsg->data = threadData->dataBuffer; } else { dmsg->header.msg_simple = TRUE; } r= msg_send((msg_header_t*)dmsg, MSG_OPTION_NONE,0); Thanks for any help, and please email responses. Michael Haker dept. Chemistry, UW-Madison haker@whitewater.chem.wisc.edu
From: M.Crawford@dcs.shef.ac.uk (Malcolm Crawford) Newsgroups: comp.sys.next.bugs Subject: Re: DPSDoUserPathWithMatrix() bug Date: 28 Dec 1993 09:32:57 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9312281534.AA00738@dcs.shef.ac.uk> Since Glenn seems to have told Dave the same thing I guessed at I feel a bit more confident about sending out my suggestion, with a wodge of code... I'd appreciate any comments, corrections etc... :-) [originally to Dave] I'm not very well informed on this stuff, but I'd guess the "bug" is simply due to memory limits in the display server... the "workaround" is to put in a check to see if the limit for ops or pts has been reached: if it has then throw the code at the server and restart. There's no harm in this, the only side-effect is that the user might get a bit flustered if contours appear in waves rather than "growing" or all appearing at once. It might also be worth noting that DPSDoUserPath(), whist very useful for quick on-screen drawing, produces horrendous PS if you're saving an image -- all those pts and ops just get translated directly... 100 100 moveto 110 110 lineto 120 100 lineto etc. This creates BIG .ps files. If you're planning on saving PS it might be worth creating a second set of routines to run if NX_PRINTING [end] Alternatively, if you know you'll be printing to a Level 2 printer, you could use the following wrap in place of DPSDoUserPath() /* * defineps PSWUserPath (float numstring pts[numPts]; int numPts; * char ops[numOps]; int numOps; char *op) * [pts (ops)] op * endps */ which will generate more compact PostScript code. Here's a code fragment which I hope should show the relationship between the two. #ifdef USE_DPSDoUserPath bbox[0] = minX; bbox[1] = minY; bbox[2] = maxX; bbox[3] = maxY; #endif i = j = 0; #ifdef USE_PSWUserPath pts[i++] = minX; pts[i++] = minY; pts[i++] = maxX; pts[i++] = maxY; ops[j++] = dps_setbbox; #endif /* * set up first point */ pts[i++] = firstDrawPoint; pts[i++] = theData[firstDrawPoint]; ops[j++] = dps_moveto; /* * main loop */ for (x = firstDrawPoint +1; x < (lastDrawPoint + 1) ; x++) { pts[i++] = x; pts[i++] = data[x]; ops[j++] = dps_lineto; if (i > MAX_UPATHPTS) { /* * if points limit reached, write out the path so far... */ #ifdef USE_DPSDoUserPath DPSDoUserPath(pts, i, dps_float, ops, j, bbox, dps_ustroke); #endif ifdef USE_PSWUserPath PSWUserPath(pts, i, ops, j, "ustroke"); #endif /* * ... and restart */ i = j = 0; #ifdef USE_PSWUserPath pts[i++] = minX; pts[i++] = minY; pts[i++] = maxX; pts[i++] = maxY; ops[j++] = dps_setbbox; #endif pts[i++] = x; pts[i++] = data[x]; ops[j++] = dps_moveto; } } /* * finish up */ #ifdef USE_DPSDoUserPath DPSDoUserPath(pts, i, dps_float, ops, j, bbox, dps_ustroke); #endif #ifdef USE_PSWUserPath PSWUserPath(pts, i, ops, j, "ustroke"); #endif Acknowledgement and disclaimer -- much of this was stolen from the Purple book and various NeXT doc sources... bugs are more likely to be mine: use at your own risk! :-) Have fun, mmalcolm.
Newsgroups: comp.sys.next.bugs From: pablo@acsu.buffalo.edu (Juan P. Abonia) Subject: Formatting, BuildDOS and Mac Floppies Message-ID: <CIr5x5.HDD@acsu.buffalo.edu> Sender: nntp@acsu.buffalo.edu Organization: UB Date: Tue, 28 Dec 1993 16:03:05 GMT -- J. Pablo Abonia University at Buffalo BITNET: pablo@sunybcs.BITNET Roswell Park Cancer Institute Internet: pablo@cs.Buffalo.EDU UUCP: ...!{watmath,boulder,decvax,rutgers}!sunybcs!pablo
From: doko@cs.tu-berlin.de (Matthias Klose) Newsgroups: comp.sys.next.bugs Subject: NS3.x UserManager Date: 28 Dec 1993 16:31:25 GMT Organization: TU Berlin Fachbereich Informatik Message-ID: <2fpn0v$afo@news.cs.tu-berlin.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit When I try to add a group named 'users' I get the message that this name already exists (but it doesn't). This only happens with this special name. Bug or feature? Matthias
Control: cancel <CIr5x5.HDD@acsu.buffalo.edu> Newsgroups: comp.sys.next.bugs From: pablo@acsu.buffalo.edu (Juan P. Abonia) Subject: cmsg cancel <CIr5x5.HDD@acsu.buffalo.edu> Message-ID: <CIrA9C.J0B@acsu.buffalo.edu> Sender: nntp@acsu.buffalo.edu Organization: UB References: <CIr5x5.HDD@acsu.buffalo.edu> Date: Tue, 28 Dec 1993 17:36:47 GMT <CIr5x5.HDD@acsu.buffalo.edu> was cancelled from within trn. -- J. Pablo Abonia University at Buffalo BITNET: pablo@sunybcs.BITNET Roswell Park Cancer Institute Internet: pablo@cs.Buffalo.EDU UUCP: ...!{watmath,boulder,decvax,rutgers}!sunybcs!pablo
Newsgroups: comp.sys.next.bugs From: pablo@acsu.buffalo.edu (Juan P. Abonia) Subject: Formatting, BuildDOS and Mac Floppies Message-ID: <CIrABx.J2t@acsu.buffalo.edu> Sender: nntp@acsu.buffalo.edu Organization: UB Date: Tue, 28 Dec 1993 17:38:20 GMT I have been trying to use BuildDOS to format several 1.44 floppies. Every time that I insert a floppy I receive the message "Wrong Disk", followed by an immediate ejection (NextStation Color running 2.0). These floppies have already been formatted under DOS. Could that be causing the problem? Also the FAQ indicates thatI should be able to format, read and write to Mac disks. It then directs me to my user's manual which seems to be oblivious about Mac Floppies. Am I missing something simple here? -- J. Pablo Abonia University at Buffalo BITNET: pablo@sunybcs.BITNET Roswell Park Cancer Institute Internet: pablo@cs.Buffalo.EDU UUCP: ...!{watmath,boulder,decvax,rutgers}!sunybcs!pablo
Newsgroups: comp.sys.next.bugs From: pablo@acsu.buffalo.edu (Juan P. Abonia) Subject: Fax problems Message-ID: <CIrAnB.J9J@acsu.buffalo.edu> Sender: nntp@acsu.buffalo.edu Organization: UB Date: Tue, 28 Dec 1993 17:45:10 GMT Hello, I'm trying to set up a Faxmodem on a NextStation Color. I'm using a ZOOM Faxmodem VFX v32bis (14400). It is a Class 2 Fax and it is hooked up to Serial port B. Right now I'm using it for Kermit and have set all the different AT settings accordingly. Whenever I try to use the FAX capabilities I end up with a message that the FAX software has failed. It then goes on to tell me to reboot the machine and try again. I have used both the Interfax and Class 2 drivers with the same result. Currently I using NeXT OS v2.0. Any ideas? Pablo -- J. Pablo Abonia University at Buffalo BITNET: pablo@sunybcs.BITNET Roswell Park Cancer Institute Internet: pablo@cs.Buffalo.EDU UUCP: ...!{watmath,boulder,decvax,rutgers}!sunybcs!pablo
From: zaphod!tpg@csn.org (Terry Gliedt) Newsgroups: comp.sys.next.bugs Subject: Fax problems Date: 28 Dec 1993 19:40:27 -0600 Organization: UTexas Mail-to-News Gateway Sender: daemon@cs.utexas.edu Message-ID: <9312282335.AA00218@csn.org> >Hello, I'm try to set up a Faxmodem on a NextStation Color.... >.... >Currently I using NeXT OS 2.0 I think you will find that 2.0 is your most likely problem. There are lots of serial problems in 2.0 which were fixed in 2.1. I was able to make a Zoom modem work with some Fax software on 2.1 and on 3.0. Since you are on 2.0, you should be able to upgrade for free to 2.1. The problem will be to find a set of 2.1 diskettes or a 2.1 system to upgrade from. ============================================================================= Terry Gliedt zaphod!tpg@csn.org
Newsgroups: comp.sys.next.bugs From: bugni@cs.washington.edu (Paul F Bugni) Subject: BIOS values lost/ DMA transfer speed Message-ID: <1993Dec29.190814.27456@beaver.cs.washington.edu> Sender: news@beaver.cs.washington.edu (USENET News System) Organization: Computer Science & Engineering Dept., Univ. of Washington, Seattle Date: Wed, 29 Dec 93 19:08:14 GMT Sender: Followup-To: Distribution: Organization: Computer Science & Engineering, U. of Washington, Seattle Keywords: After turning off the machine (intel) drive a is set to NOT INSTALLED and the time and date are reset to somewhere in 1980. Is this simply a battery issue o or is Next playing a part? In reguards to problems I've been having with lockups occuring when trying to install anything from the CD-ROM, I've been advised to slow the DMA transfer speed. I don't find this available in CMOS. Where might this be adjusted? Thanks, please respond (ASCII) to bugni@cs.washington.edu
Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer From: gerben@rna.indiv.nluug.nl Subject: POSIX in 3.2 Message-ID: <1993Dec30.080057.368@rna.indiv.nluug.nl> Sender: gerben@rna.indiv.nluug.nl (Gerben Wierda) Organization: G.R.O.S.S. Date: Thu, 30 Dec 1993 08:00:57 GMT According to a post in comp.soft-sys.nextstep: > "* Building POSIX applications is now supported. To compile POSIX 1003.1 > conforming source, specify the -posix flag to cc. Note that POSIX kernel > interfaces are not supported for NEXTSTEP applications." > Is that compile-time or run-time? I can understand that you cannot mix header file setups. But suppose I make a separate class, which interface does not need -posix (but whose implementation does). Can I use that class in a NS app? If not, than this is as stupid as NT's POSIX: Unusable. -- Gerben Wierda [NeRD:7539] gerben@rna.indiv.nluug.nl "If you don't know where you are going, any road will take you there." From the Talmud(?), rephrased in Lewis Carroll, "Alice in Wonderland".
Newsgroups: comp.sys.next.bugs From: Neil Greene <Neil@bMD.com> Subject: 3.2; Adaptor Oracle: Problems connecting to Oracle6 Message-ID: <1993Dec30.145407.2213@bMD.com> Sender: neil@bMD.com Organization: benchMark Developments, Inc. (Lex., KY) Date: Thu, 30 Dec 1993 14:54:07 GMT When attempting to connect to an Oracle v6.x.x.x database instance consisting of uppercase and lowercase characters, the Oracle adaptor fails to make the connection. Apparently, the adapter is mangling connect strings consisting of uppercase and lowercase characters. SQL*Plus connections from all machines work using the same SQL*Net connect parameters. However, attempts to connect via the Oracle Adaptor fail. -- Neil Greene benchMark Developments, Inc. [NeXT VAR] 2040 Regency Road, Suite C Lexington, KY 40503 Phone: 606-231-6599 / Fax: 606-254-4864 Email: Neil@bMD.com [NeXTmail] -- Neil Greene benchMark Developments, Inc. [NeXT VAR] 2040 Regency Road, Suite C Lexington, KY 40503 Phone: 606-231-6599 / Fax: 606-254-4864
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.