This is Bugs-09.gz in view mode; [Up]
Newsgroups: comp.sys.next.bugs From: Nitezki@NiDat.sub.org (Peter Nitezki) Subject: Virtual memory management went mad Message-ID: <Dx0HI4.87@nidat.sub.org> Sender: nitezki@nidat.sub.org (Peter Nitezki) Organization: private site of Peter Nitezki, Kraichtal, Germany Date: Sat, 31 Aug 1996 16:51:39 GMT This happened twice in about half a year: There is a slab (mono, 20MB, 1+4GB disk, CD/ROM, 4mmDAT, NS 3.3) sitting beside my desk acting mainly as a server for my TurboColor (NetInfo, NFS, NNTP, Taylor-UUCP, NXFax, SafetyNet, and the like). There is almost no interactive task running on it besides a workspace where I'm logged in as "root" to monitor operations. Somewhere during the night something went wrong and when I came in the other morning the Console on the server was frantically scrolling with a line saying (if I remember correctly): v-node_swapout failure errno = 28 and the system was eating away the swap partition at a rate of 100MB and more per hour. My attempts to fix some of the more severe consequences of this failure needed about a dozen reboots until suddenly the eating away at the swap partition stopped completely and now I'm obviously left with a system that lives on real memory only. The swapfile never grows anymore, not even to the lowat-size, albeit there is 250MB free space on the root partition. Last time I only came to see the final state of this mess, and I had no other chance to mend it than reinstall the OS from scratch. Is there anybody who can explain this situation or even better: rescue me from the tedious procedure of reconstructing the whole system? -- Peter Nitezki | Nitezki@NiDat.sub.org # Blessed art thou who knoweth Staarenbergstr. 44 | Tel.: +49 7251 62495 # not about the pleasure and D-76703 Kraichtal | Fax : +49 7251 69215 # delight of being hooked GERMANY | E-mail defunct, sorry # up to the Net. Peter 1,3-5
From: Anthony Cordeiro <ren@netscape.com> Newsgroups: comp.sys.next.bugs Subject: Font panel bug in Terminal.app Date: Fri, 30 Aug 1996 17:09:04 -0700 Organization: i.dont.speak.for.netscape.com Message-ID: <322782A0.6494@netscape.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit If there's a good 'known bug archive' for NS 3.3 floating around out there, please point me to it and I'll look for myself. In the meantime, has anyone else running 3.3 on black hardware noticed that if you have a large number of fonts installed (in my case /LocalLibrary/Fonts), trying to open the font panel within Terminal.app effectively hoses both Terminal and File Manager? A couple other people I've talked to have noticed the same problem; I'm wondering if there's a fix for it, or if it's a known bug, or what. Granted, it's not particularly vital a feature, but it's somewhat odd. Maybe it's time to buy Stuart. :) --Ren
From: Garance A Drosehn <gad@eclipse.its.rpi.edu> 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: Re: Asking a favor Date: 3 Sep 1996 02:40:21 GMT Organization: Rensselaer Polytechnic Institute, Troy NY, USA Message-ID: <50g5ql$11g@usenet.rpi.edu> References: <01bb9798$69b121e0$331543a4@lullaby> "Duncan Idaho" <everblue@ucla.edu> wrote: > I'm looking to utilize the Recycler animation in NeXTSTEP in a > Windoze app I'm currently working on. Unfortunately I sold my > copy a while back so I have to get the bitmaps from someone else. "Utilize", as in "copy" and "use without permission"? My guess is that you'll be treading on some copyright issues that you should not be treading on. What makes you think you have the right to use those images for some application you're writing? --- Garance Alistair Drosehn = gad@eclipse.its.rpi.edu Senior Systems Programmer (MIME & NeXTmail capable) Rensselaer Polytechnic Institute; Troy NY USA
From: "Duncan Idaho" <everblue@ucla.edu> 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: Re: Asking a favor Date: 4 Sep 1996 03:01:34 GMT Organization: University of California, Los Angeles Message-ID: <01bb99ca$41ed87f0$871443a4@lullaby> References: <01bb9798$69b121e0$331543a4@lullaby> <50g5ql$11g@usenet.rpi.edu> Actually, it's for personal use.
From: aisbell@ix.netcom.com (Art Isbell) Newsgroups: comp.sys.next.bugs Subject: PB Makefiles: Cannot redefine nextstep-specific.make macros Date: 4 Sep 1996 03:14:15 GMT Organization: Netcom Distribution: world Message-ID: <50is67$let@dfw-ixnews6.ix.netcom.com> I filed the following bug report with NeXT. Maybe someone will find my workaround at least a starting point to a fix: Macros defined in nextstep-specific.make are included in common.make after Makefile.preamble has been included in Makefile so that their redefinition is no longer possible. This makes the use of flex instead of lex not possible by merely redefining LEX in Makefile.preamble as under NS 3.x. The following patches seem to fix this problem but have been poorly tested so other problems are likely: *** commonOrig.make Fri Aug 9 13:26:16 1996 --- common.make Tue Sep 3 17:15:57 1996 *************** *** 29,37 **** SUPPORTFILES = Makefile $(ICONHEADER) $(APPICON) $(DOCICONS) # What OS are we running on? ! -include $(MAKEFILEDIR)/platform.make ! include $(MAKEFILEDIR)/$(PLATFORM_OS)-specific.make # Use the OS-specific versions of some variables, if they exist. --- 29,37 ---- SUPPORTFILES = Makefile $(ICONHEADER) $(APPICON) $(DOCICONS) # What OS are we running on? ! #-include $(MAKEFILEDIR)/platform.make ! #include $(MAKEFILEDIR)/$(PLATFORM_OS)-specific.make # Use the OS-specific versions of some variables, if they exist. *** platformOrig.make Fri May 3 18:04:59 1996 --- platform.make Tue Sep 3 17:15:35 1996 *************** *** 1 **** --- 1,3 ---- PLATFORM_OS = nextstep + + include $(MAKEFILEDIR)/$(PLATFORM_OS)-specific.make -- Art Isbell NeXT/MIME Mail: aisbell@ix.netcom.com Trego Systems Voice/Fax: +1 408 335 2515 CaseServ: NEXTSTEP/OpenStep Voice Mail: +1 408 335 1154 managed care solutions US Mail: Felton, CA 95018-9442
From: aisbell@ix.netcom.com (Art Isbell) Newsgroups: comp.sys.next.bugs Subject: depend target is broken in OS/Mach 4.0 Date: 4 Sep 1996 03:29:44 GMT Organization: Netcom Distribution: world Message-ID: <50it38$let@dfw-ixnews6.ix.netcom.com> I've heard precious few complaints about this serious problem. Maybe no OS developers maintain "make" dependencies which will likely lead to serious bugs. Or maybe most OS developers recompile everything when any change is made, something that's impractical for large projects. I can't imagine that anyone is maintaining dependencies manually, especially on large projects. Maybe everyone's figured out the problem, but no one told me :-) The OS Developer Makefiles are even more complex than before, but new hooks are provided in addition to the old Makefile.p{re,ost}amble. I've taken advantage of the new common.make.postamble hook to fashion a less-broken "depend" target. I don't believe that the "depend" target is the problem, but the ".bproj.depend .subproj.depend .tproj.depend" transformation rule is missing. I can understand why. Trying to devise one with the even more complex project architecture isn't easy. Place the attached common.make.postamble file in your favorite directory and read the comments in the attached file. The "depend" target has been removed from PB as well as support for adding targets, so the depend target must be build from a shell in the top-level project directory just like in the bad old days :-) % gnumake depend # Place this file in LOCAL_MAKEFILEDIR and define LOCAL_MAKEFILEDIR in # the top-level Makefile.preamble. # Assumes that "ProjectHeaders" is the name of the top-level directory to which # project headers are exported. ..bproj.depend .subproj.depend .tproj.depend: @(cd `basename $<`; \ sym_dir=`echo $(SYM_DIR) | sed '/^[^/]/s:^:../:'` ; \ proj_spec_cflags=`echo $(PROJECT_SPECIFIC_CFLAGS) | sed 's:ProjectHeaders:../ProjectHeaders:'` ; \ $(MAKE) depend "NAME = $*" \ "SYM_DIR = $$sym_dir/$<" \ "PROJECT_SPECIFIC_CFLAGS = $$proj_spec_cflags" \ "LOCAL_MAKEFILEDIR = $(LOCAL_MAKEFILEDIR)" ) depend:: .less_broken.Makefile.dependencies $(SUBPROJECTS:.subproj=.depend) $(BUNDLES:.bproj=.depend) $(TOOLS:.tproj=.depend) ..less_broken.Makefile.dependencies:: $(CLASSES) $(MFILES) $(CFILES) $(CCFILES) $(CAPCFILES) $(CAPMFILES) $(CXXFILES) $(CPPFILES) $(INITIAL_TARGETS) @($(RM) -f Makefile.dependencies ; \ if [ "`$(ECHO) $(CLASSES) $(MFILES) $(CFILES) $(CCFILES) $(CAPCFILES) $(CAPMFILES) $(CXXFILES) $(CPPFILES) | wc -w`" != " 0" ] ; then \ cmd="$(CC) -MM $(PROJECT_SPECIFIC_CFLAGS) $(PROPOGATED_CFLAGS) -I$(SYM_DIR) $(CLASSES) $(MFILES) $(CFILES) $(CCFILES) $(CAPCFILES) $(CAPMFILES) $(CXXFILES) $(CPPFILES)" ; \ echo "$$cmd > Makefile.dependencies" ; $$cmd > Makefile.dependencies || ($(RM) -f Makefile.dependencies ; exit 1) ; \ fi ) -- Art Isbell NeXT/MIME Mail: aisbell@ix.netcom.com Trego Systems Voice/Fax: +1 408 335 2515 CaseServ: NEXTSTEP/OpenStep Voice Mail: +1 408 335 1154 managed care solutions US Mail: Felton, CA 95018-9442
From: "Claude A. Rogers III" <car3@magicnet.net> Newsgroups: comp.sys.next.bugs Subject: Canon printer problems! Date: 4 Sep 1996 18:18:20 GMT Organization: MagicNet, Inc. Message-ID: <322DC794.6395@magicnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I have a Canon BJ-200ex printer. Recently, I upgraded my mother board from a 486 to a pentium 133mghz. Since the change my printer will not print properly. It prints jargon diagonally across the page. I have reloaded my Windows 95 software, reloaded my printer software. Downloaded the latest drivers from the Canon web site and checked my connections from the parallel port to the PRN1 connection. None of these things have solved the problem. I have e-mailed Canon twice, but they do not repsond. I called them by phone and I was left on indefinite hold. If anyone has any suggestions, please e-mail me or reply to this newsgroup. Thank you, Claude
From: jut@ukrv.de (J.-U. Thieme) Newsgroups: comp.sys.next.bugs Subject: Re: Canon printer problems! Date: 4 Sep 1996 20:59:47 GMT Organization: Technical University Berlin, Germany Message-ID: <50kqk3$68k@brachio.zrz.TU-Berlin.DE> References: <322DC794.6395@magicnet.net> Cc: car3@magicnet.net In <322DC794.6395@magicnet.net> "Claude A. Rogers III" wrote: > Hi, > > I have a Canon BJ-200ex printer. Recently, I upgraded my mother board > from a 486 to a pentium 133mghz. Since the change my printer will not > print properly. It prints jargon diagonally across the page. I have > reloaded my Windows 95 software, reloaded my printer software. > Downloaded the latest drivers from the Canon web site and checked my > connections from the parallel port to the PRN1 connection. None of these > things have solved the problem. I have e-mailed Canon twice, but they do > not repsond. I called them by phone and I was left on indefinite hold. > > If anyone has any suggestions, please e-mail me or reply to this > newsgroup. > > Thank you, > Claude > Your problem is your sense of direction :-)) This is comp.sys.next.bugs !!! NeXT is´nt guilty of Win95 and your problems with this. CIAO JUT -- -------------------------------------------------------------- - Dipl.-Ing. (FH) J.- U. Thieme - -------------------------------------------------------------- - send to : jut@ukrv.de or jut@rz.charite.hu-berlin.de - - -> NeXTMail & PGP welcome <- - - phone : +49 30 450 66127 - - fax: +49 30 450 66937 - -------------------------------------------------------------- - location : virchow-hospital in berlin (germany) - --------------------------------------------------------------
From: wolfgang@wi.WHU-Koblenz.de (Wolfgang Roeckelein) Newsgroups: comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs,de.comp.sys.next,comp.unix.solaris,alt.sys.sun,comp.sys.sun.admin,comp.sys.sun.managers,comp.sys.sun.misc Subject: problem with nis/nis+ with NeXTstep 3.3/Solaris 2.5.1 Date: 5 Sep 1996 08:14:00 GMT Organization: University of Regensburg, Germany Distribution: inet Message-ID: <50m248$i4q@rrzs3.uni-regensburg.de> Hi, I am having a severe problem with my nis/nis+ setup: Server: Solaris 2.5.1, nis+ in nis compatability mode client: NeXTstep 3.3, nis and netinfo When I login to nextstep with a nis account, the group gets not set, and I wind up in wheel. On the Solaris console the following error is printed: Sep 3 22:50:58 rrws27 nisd[92]: WARNING: db_query::db_query: bad index Sep 3 22:50:58 rrws27 nisd[92]: No table /var/nis/data/group.org_dir for object group.org_dir.lehner.wiwi.uni-regensburg.de., status = 4 Note that: logins on the Solaris machine are ok, ypcat passwd and ypcat group are ok, I can chgrp a file to the offending group and it shows correctly with ls -lg. The + line in /etc/passwd and /etc/group on the NeXT side is there. On the Solaris side: # showrev -p Patch: 103663-01 Obsoletes: Packages: SUNWcsu, SUNWhea Patch: 103594-03 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu Patch: 103630-01 Obsoletes: Packages: SUNWcsu, SUNWcsr Patch: 103680-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu Patch: 103683-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWcsu Patch: 103817-01 Obsoletes: Packages: SUNWcsu Patch: 103582-01 Obsoletes: Packages: SUNWcsr Patch: 103743-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWfns Patch: 103686-01 Obsoletes: , Requires:, 103663-01 Packages: SUNWnisu On the NEXTstep side: 3.3 patch 1 What is causing this? Can anybody help me? Thank you very much in advance, Wolfgang --- Dipl.-Wirtsch.Inf. Voice: +49 941 943 3205 Wolfgang Roeckelein Fax: +49 941 943 4986 Uni Regensburg E-Mail: roeckelein@wi.whu-koblenz.de Universitaetsstr. 31 Wolfgang.Roeckelein@wiwi.uni-regensburg.de D-93053 Regensburg (MIME and NeXTmail ok) Germany WWW: http://www.whu-koblenz.de/~wolfgang/ GCM/B d-- s: a- C++ US+++$ UX+++ P+ L E? W++ N++ w-- O-(++) M+ !V PS++ PE Y+ PGP(++) t+ 5? X? R+ tv b++ DI D++ G e+++>++++ h+ r++>% y? (Geek Code V3.x)
Newsgroups: comp.sys.next.bugs From: bbsady@midway.uchicago.edu (bryce) Subject: DNS problems Message-ID: <Dx917A.7GM@midway.uchicago.edu> Sender: news@midway.uchicago.edu (News Administrator) Organization: The University of Chicago Date: Thu, 5 Sep 1996 07:37:58 GMT how do i get DNS to work? (i'm very new to this). networking is fine if i go by number, but i'd rather use DNS. any possibility? bryce -- ()-() Bryce B. Sady (o o) http://student-www.uchicago.edu/users/bbsady /\o/\ Classical Studies, the College, the University of Chicago
Newsgroups: comp.sys.next.bugs From: bbsady@midway.uchicago.edu (bryce) Subject: remote printing problems Message-ID: <Dx919o.7L3@midway.uchicago.edu> Sender: news@midway.uchicago.edu (News Administrator) Organization: The University of Chicago Date: Thu, 5 Sep 1996 07:39:24 GMT should there be an /etc/printcap on my NeXTStation? i want to print to a remote spool... any idea how to do this? the print app only lets me modify local printers... i must be doing something wrong :-( bryce -- ()-() Bryce B. Sady (o o) http://student-www.uchicago.edu/users/bbsady /\o/\ Classical Studies, the College, the University of Chicago
Newsgroups: comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs From: bbsady@midway.uchicago.edu (bryce) Subject: postscript font printing problem Message-ID: <DxA7GE.MAq@midway.uchicago.edu> Sender: news@midway.uchicago.edu (News Administrator) Organization: The University of Chicago Date: Thu, 5 Sep 1996 22:50:38 GMT i have a font (Sgreek) which edits just fine on my NeXT and shows up beautifully on my screen. to print it, i save it as a postscript file, and take it to a computer to be printed with lpr (it's a Sun, not a NeXT), and all the fonts show up fine except Sgreek which shows up as helvetica for the keystrokes i used in Sgreek. any ideas? bryce -- ()-() Bryce B. Sady (o o) http://student-www.uchicago.edu/users/bbsady /\o/\ Classical Studies, the College, the University of Chicago
From: mmalcolm crawford <m.crawford@shef.ac.uk> Newsgroups: comp.sys.next.misc,comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: postscript font printing problem Date: 5 Sep 1996 23:31:31 GMT Organization: University of Sheffield, UK Message-ID: <50nnsj$ikp@bignews.shef.ac.uk> References: <DxA7GE.MAq@midway.uchicago.edu> In-Reply-To: <DxA7GE.MAq@midway.uchicago.edu> On 09/06/96, bryce wrote: > i have a font (Sgreek) which edits just fine on my NeXT and shows up > beautifully on my screen. to print it, i save it as a postscript file, > and take it to a computer to be printed with lpr (it's a Sun, not a NeXT), > and all the fonts show up fine except Sgreek which shows up as helvetica > for the keystrokes i used in Sgreek. > > any ideas? > Are you saving the file "with fonts for chosen printer" (cf the pop-up menu in the Print/Save panel)? If not, and the computer you're printing to doesn't have the font, it won't print out properly. Best wishes, mmalc. --
From: jorr@math.unl.edu (John L. Orr) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.lang.java.misc,comp.lang.java.setup Subject: Java on co-Xist Date: Sat, 07 Sep 1996 00:03:58 GMT Organization: Netcom Message-ID: <50qe1v$mr5@dfw-ixnews10.ix.netcom.com> I am trying to view applets with the JDK appletviewer running on a SPARC Solaris 2.5 machine. The appletviewer works fine on the Solaris machine, but crashes when I try to view its output on a remote (NeXTStep) machine using co-Xist (an X client for NeXTStep). Has anyone had any experience with viewing Java applets in co-Xist, or any other NeXTStep-based client? Many thanks for any and all help, John L. Orr jorr@math.unl.edu
From: jq@papoose.quick.com (James E. Quick) Newsgroups: comp.sys.next.bugs Subject: Re: DNS problems Date: 9 Sep 1996 08:24:04 -0400 Organization: PHCS Message-ID: <511294$bsl@papoose.quick.com> References: <Dx917A.7GM@midway.uchicago.edu> In article <Dx917A.7GM@midway.uchicago.edu>, bryce <bbsady@midway.uchicago.edu> wrote: >how do i get DNS to work? (i'm very new to this). networking is fine if >i go by number, but i'd rather use DNS. any possibility? You need to do a couple of things. 1. Create a file /etc/resolv.conf, containing 2 lines domain YOUR.DO.MAINNAME nameserver 999.999.999.999 2. If their are multiple subnets, and you have a router on your subnet which understands how to route everywhere else, then have routed install a default route to this host. add net 255.255.255 gateway 999.999.999.999 passive 3. Finally, modify /etc/hostconfig so that the ROUTER line reads: ROUTER=-ROUTED- Example, imagine that I am in the example.config.com my hostname is ns.example.config.com my IP is 172.16.1.125 an omniscient router on my subnet is my IP is 172.16.1.2 nameserver for the example.config.com domain is at 172.16.21.8 resolv.conf contains domain easy.config.com nameserver 172.16.21.8 gateways contains net 255.255.255 gateway 172.16.1.2 hostconfig has the router line ROUTER=-ROUTED- Note that in this example the name server is on a different subnet. We would not be able to use it unless we had help from the router specified in the gateways file. This is, of course, a gross oversimplification of network configuration. But if there is a router on the local subnet, this is pretty much all you need. (Also note that routes are important on the other end too. For instance, the name server has to know the route back to your subnet before this can work. -- ___ ___ | James E. Quick jq@quick.com / / / | Private HealthCare Systems NeXTMail O.K. \_/ (_\/ | Systems Integration Group (617) 895-3343 ) | "I don't think so," said Rene Descartes. Just then, he vanished.
Newsgroups: comp.sys.next.bugs From: Bob Griffin <rgriffin@techsol.com> Subject: Problem with OpenStep 4.0 Serial Ports Content-Type: text/plain; charset=us-ascii Message-ID: <32344628.27AB@techsol.com> Sender: news@pfizer.com (News Admin) Content-Transfer-Encoding: 7bit Organization: Technology Solutions Inc. Mime-Version: 1.0 Date: Mon, 9 Sep 1996 16:30:32 GMT I upgraded from NextStep 3.3 to 4.0 recently on Intel hardware. My 3.3 apps that open "/dev/cua" and "/dev/cub" (i.e. COM1,COM2) have crashed, such as my fax software. It seems that the device names are now treated as invalid. I wrote a little C program to open the ports and I still get an open failure. Maybe I missed something in the documentation. Any help would be appreciated. Thanks.
From: steve@blacksmith.com (Steven Meyer) Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Serial ports and 3.3 black - bug? Date: 9 Sep 1996 15:11:04 -0400 Organization: BLaCKSMITH Inc. Message-ID: <511q48$59b@chutney.BLaCKSMITH.com> I've been tracking down a problem I've had with Taylor uucp for awhile now, and I've figured out my problem. Questions are, does this happen for everyone, and is it in fact a bug, or am I misreading something? Here's the basic situation. It appears that opening a process's control terminal when that terminal is a serial port _and that port is not already open under its proper name_, wedges the port in that direction, until it is opened under its proper name. The purpose here is to diassociate the process from its control terminal. However, it appears that the only way to do so is to open /dev/tty and send the right ioctl; even if you know the right device, by its proper name, and have an open descriptor to it, you can't send the ioctl to that, you need to use /dev/tty. The short program below demonstrates the problem. Basically, it diassociates from its terminal, opens /dev/cufb and /dev/ttyb alternately, then opens /dev/tty, then tries to open /dev/ttyb again. Once /dev/cub is the control terminal, and /dev/tty is opened (and closed), you can never open /dev/ttyb. As a matter of fact, no process will be able to open /dev/ttyb until some process has opened /dev/cub. Interestingly enough, it does work if you bracket the open of /dev/tty with open/close of /dev/cub. That is, open /dev/cub open /dev/tty close /dev/cub send ioctl to /dev/tty close /dev/tty does work. But that requires knowing what your current control terminal is, and the whole point of the /dev/tty synonym, as I understand it, is not to have to know. So, could anyone running 3.3 black: 1) Compile up this little program and run it (probably as root, to get access to the ports) and let me know if they get "Device busy: Second open of ttyb" as I do. I ask this, because I'm the only person I know who has this problem with Taylor uucp, so I'm wondering if I'm the only person this happens to. 2) Explain why this is proper behavior, if it is. Thanks. Steve Meyer smeyer@blacksmith.com ===================== #import <libc.h> int main(int argc, char**argv) { int o; /* Detach from ttypx */ o = open ("/dev/tty", O_RDONLY); if (o >= 0) { ioctl (o, TIOCNOTTY, 0); close (o); } /* Open cub - becomes control terminal */ o = open("/dev/cub", O_RDONLY); if (o >= 0) close (o); else perror("First open of cub"); /* Open ttyb - becomes control terminal */ o = open("/dev/ttyb", O_RDONLY); if (o >= 0) close (o); else perror("First open of ttyb"); /* Open cub - becomes control terminal. Note if we try to use the ioctl here, it will return success, but the not actually succeed in detaching. */ o = open("/dev/cub", O_RDONLY); if (o >= 0) close (o); else perror("Second open of cub"); /* Detach from cub using /dev/tty - will leave no control terminal, but also munges port - see next open. Sending the ioctl or not doesn't matter; it's the open of /dev/tty which causes the problem. */ o = open ("/dev/tty", O_RDONLY); if (o >= 0) { int io; io = ioctl (o, TIOCNOTTY, 0); if (io != 0) perror("ioctl"); close (o); } else perror("Open of /dev/tty"); /* Open ttyb - would become control terminal if successful. Fails with "Device busy" */ o = open("/dev/ttyb", O_RDONLY); if (o >= 0) close (o); else perror("Second open of ttyb"); exit(0); } -- Steve Meyer BLaCKSMITH, Inc. smeyer@blacksmith.com (NeXTMail accepted)
From: Charles William Swiger <cs4w+@andrew.cmu.edu> Newsgroups: comp.sys.next.bugs,comp.sys.next.programmer Subject: Re: Serial ports and 3.3 black - bug? Date: Mon, 9 Sep 1996 18:34:48 -0400 Organization: Fifth yr. senior, Computer Science, Carnegie Mellon, Pittsburgh, PA Message-ID: <cmB9i8600WBOA5VUVF@andrew.cmu.edu> References: <511q48$59b@chutney.BLaCKSMITH.com> In-Reply-To: <511q48$59b@chutney.BLaCKSMITH.com> Excerpts from netnews.comp.sys.next.programmer: 9-Sep-96 Serial ports and 3.3 black .. by Steven Meyer@blacksmith. > So, could anyone running 3.3 black: > > 1) Compile up this little program and run it (probably as root, to get > access to the ports) and let me know if they get "Device busy: Second > open of ttyb" as I do. Yes, I get that message as well. > 2) Explain why this is proper behavior, if it is. Beats me. I've managed to avoid needing to understand the deeper mysteries of the tty(4) terminal interface. :-) -Chuck Charles Swiger | cs4w@andrew.cmu.edu | standard disclaimer ----------------+---------------------+--------------------- I know you're an optimist if you think I'm a pessimist.
From: batmon@abico.com.tw (Mon-Sen Yang) Newsgroups: comp.sys.next.bugs Subject: Install NeXT to a Notebook computer Date: Tue, 10 Sep 1996 03:57:53 GMT Organization: j%nki~w€RJ3M-26XPLZ8L-BFGD44CT-1EA6BC82 Message-ID: <512scj$99n@netnews.hinet.net> Hi, I am planing to install OpenStep or NeXTStep v3.3 to a notebook computer. The notebook is P586/100, 16MB RAM with 1GB EIDE HD. I also use an Adaptec SlimSCSI card to attach my CD-ROM. The problem is when I use the boot-up disk and set the CD-ROM driver to Adaptec PCMCIA 6x60 Card, HD to EIDE driver;, it only found my HD and said there is no SCSI device or CD-ROM. I did check with NeXTanswers and it says NeXT does support Adaptec SlimSCSI card. Is there any other driver I have to load or any procedure I have to do for NeXT to be able to find the Slim SCSI card??
From: ash@now.ch (Michael Aeschbach) Newsgroups: comp.sys.next.bugs Subject: Re: Problem with OpenStep 4.0 Serial Ports Date: Tue, 10 Sep 1996 10:25:49 GMT Organization: NOW GmbH, Baar, Switzerland Sender: news@now.ch Message-ID: <DxIIB1.HGo.0.astra@now.ch> References: <32344628.27AB@techsol.com> Cc: rgriffin@techsol.com In <32344628.27AB@techsol.com> Bob Griffin wrote: > I upgraded from NextStep 3.3 to 4.0 recently on Intel hardware. My 3.3 > apps that open "/dev/cua" and "/dev/cub" (i.e. COM1,COM2) have crashed, > such as my fax software. It seems that the device names are now treated > as invalid. I wrote a little C program to open the ports and I still get > an open failure. Maybe I missed something in the documentation. Any help > would be appreciated. Thanks. > I had a same problem and installed the TTY Port Server (v4.00) with the Configurer (Add Other Devices). Now it works. Regards, Michael
From: Ernest Aleixandre Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.marketplace,comp.sys.next.misc,comp.sys.next.programmer Control: cancel <514f8o$a1e@fin.firstnations.ca> Subject: cmsg cancel <514f8o$a1e@fin.firstnations.ca> Date: 10 Sep 96 19:57:51 GMT Organization: First Nations Network Inc. Message-ID: <cancel.514f8o$a1e@fin.firstnations.ca> Article cancelled by news@service3.uky.edu.
From: gvandyk@icon.co.za Newsgroups: comp.sys.next.bugs Subject: Re: Install NeXT to a Notebook computer Date: 11 Sep 1996 05:07:46 GMT Organization: E.S. Systems cc (Financial Systems Development) Message-ID: <515hf2$h51@hermes.is.co.za> References: <512scj$99n@netnews.hinet.net> In-Reply-To: <512scj$99n@netnews.hinet.net> On 09/10/96, Mon-Sen Yang wrote: >Hi, > >I am planing to install OpenStep or NeXTStep v3.3 to a notebook >computer. The notebook is P586/100, 16MB RAM with 1GB EIDE HD. I >also use an Adaptec SlimSCSI card to attach my CD-ROM. The problem is >when I use the boot-up disk and set the CD-ROM driver to Adaptec >PCMCIA 6x60 Card, HD to EIDE driver;, it only found my HD and said >there is no SCSI device or CD-ROM. I did check with NeXTanswers and >it says NeXT does support Adaptec SlimSCSI card. Is there any other >driver I have to load or any procedure I have to do for NeXT to be >able to find the Slim SCSI card?? > > > Yes, There is another procedure that you must follow. I sat with same problem 2 weeks ago and in pure frustration looked futher in NeXTanswers. There is a directory (don't know exact position now) on NeXTanswers where you can find floppyImages. You need to make a different Boot Disk for Installing Next using PCMCIA devices. Use the PCCard Installation Image to create a Bootable next floppy. You also need to create the Additional Drivers Disk image. Use these 2 Disks you have created to Install NextStep on a Notebook computer using PCMCIA devices -- Regards, Gerrit van Dyk email: gvandyk@icon.co.za (NeXTMail welcome) E.S. Systems cc The OBJECT is the ADVANTAGE
From: paul@plsys.co.uk (Paul Lynch) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.lang.java.misc,comp.lang.java.setup Subject: Re: Java on co-Xist Date: 11 Sep 1996 10:38:33 GMT Organization: P & L Systems, Ltd. Message-ID: <5164r9$epo@ironhorse.plsys.co.uk> References: <50qe1v$mr5@dfw-ixnews10.ix.netcom.com> Cc: jorr@math.unl.edu In <50qe1v$mr5@dfw-ixnews10.ix.netcom.com> "John L. Orr" wrote: > I am trying to view applets with the JDK appletviewer running on a > SPARC Solaris 2.5 machine. The appletviewer works fine on the Solaris > machine, but crashes when I try to view its output on a remote > (NeXTStep) machine using co-Xist (an X client for NeXTStep). > > Has anyone had any experience with viewing Java applets in co-Xist, or > any other NeXTStep-based client? We do it all the time with Cub'X from a SPARC running Solaris 2.5. No problems at all. Paul -- Paul Lynch (NeXTmail) paul@plsys.co.uk Tel: (01494)432422 P & L Systems Fax: (01494)432478 http://www.plsys.co.uk/~paul
From: jsturm@zenacomp.zenacomp.com (Jeff Sturm) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.lang.java.misc,comp.lang.java.setup Subject: Re: Java on co-Xist Followup-To: comp.sys.next.software,comp.sys.next.bugs,comp.lang.java.misc,comp.lang.java.setup Date: 11 Sep 1996 13:30:54 -0400 Organization: ZenaComp Inc. Message-ID: <516t0e$9r6@zenacomp.zenacomp.com> References: <50qe1v$mr5@dfw-ixnews10.ix.netcom.com> <5164r9$epo@ironhorse.plsys.co.uk> Paul Lynch (paul@plsys.co.uk) wrote: : In <50qe1v$mr5@dfw-ixnews10.ix.netcom.com> "John L. Orr" wrote: : > I am trying to view applets with the JDK appletviewer running on a : > SPARC Solaris 2.5 machine. The appletviewer works fine on the Solaris : > machine, but crashes when I try to view its output on a remote : > (NeXTStep) machine using co-Xist (an X client for NeXTStep). : > : > Has anyone had any experience with viewing Java applets in co-Xist, or : > any other NeXTStep-based client? : We do it all the time with Cub'X from a SPARC running Solaris 2.5. No : problems at all. Hmm... what color model is supported by co-Xist? Does it have 8-bit color? Not all X server configuations are yet supported by the JDK, I seem to remember. Try xdpyinfo from an xterm window, and see what it says about co-Xist. -- Jeff Sturm ZenaComp Incorporated jsturm@zenacomp.com
Newsgroups: comp.sys.next.bugs From: as@asci.fdn.fr (Antoine Schmitt) Subject: faxcleanup fails, crashes and looses my received faxes Message-ID: <1996Sep11.215701.9467@asci.fdn.fr> Sender: as@asci.fdn.fr Organization: Antoine Schmitt - Paris, France. Date: Wed, 11 Sep 1996 21:57:01 GMT I am having a big problem with my fax software. The software is standard from NeXT. Here is what happens: - Incoming fax call, modem picks up - Fax is received - modem hangs up, says no error - I receive mail saying I have a new fax and should run FaxReader - I run FaxReader and there is nothing. This has happened from two different callers now, so I am starting to worry. More insight: it seems that some cleanup command is run on the fax file in the spool directory /usr/spool/NeXTFaxes/laura_fax. This cleanup command fails, and deletes the file. >From my console: %> laura_fax: activity on port Tue Sep 10 10:53:39 1996 %> laura_fax: wait for connect %> laura_fax: ring 1 %> laura_fax: answer call %> laura_fax: incoming fax call %> laura_fax: CONNECT FAX ----------NXFax Driver Version 1.04.1---------- %> laura_fax: Tue Sep 10 10:53:53 1996 %> laura_fax: fax call %> laura_fax: from %> laura_fax: negotiated capabilities %> laura_fax: low resolution %> laura_fax: 9600 bps %> laura_fax: 1728 pixels per line %> laura_fax: 0 ms scan time %> laura_fax: receive fax %> laura_fax: negotiated capabilities %> laura_fax: low resolution %> laura_fax: 9600 bps %> laura_fax: 1728 pixels per line %> laura_fax: 0 ms scan time %> laura_fax: Tue Sep 10 10:53:58 1996 %> laura_fax: page 1 %> laura_fax: receive fax %> laura_fax: hangup[0]: No errors. %> laura_fax: receive finished %> laura_fax: Tue Sep 10 10:54:34 1996 %> laura_fax: receive time 00:36 %> laura_fax: call complete --------------------------------------------- %<LaunchHelpers_000364f0>% /usr/lib/NextPrinter/faxcleanup -Q -X -s -c 1 /usr/spool/NeXTFaxes/laura_fax/Sep_10_1996_10:53:58 !! %<LaunchHelpers_000364f0>% /usr/lib/NextPrinter/faxcleanup: abnormal termination code, 2 Last line from the file /usr/spool/NeXTFaxes/laura_fax/log: R 09/10/96 10:53 1pg 0:36 OK. rm=" " I have used my fax software for a year now and I started having problems a few month ago, but it is starting to become worse and worse. I have installed nothing new around this time. My system is: NS 3.3 on Black HW. Zyxel 1496E modem with NXFax software. Below is a answer from the Black&White people, who where very helpful, but in the end I still dont have a solution, since they dont. Anyone can help ? Thanks ! Antoine -- ________________________________________________________ Antoine Schmitt, ASCI - Paris, France as@asci.fdn.fr - NeXT and MIME mail welcome From: Black and White Sales <sales@bandw.com> Date: Mon, 8 Apr 96 12:34:44 -0400 To: Antoine Schmitt <uunet!asci.fdn.fr!as@uunet.uu.net> Subject: Re: NXFax tech support question Hello Antoine, Unfortunately, you have run into the faxcleanup problem. If you have received a fax, but it does not appear in the FaxReader, the following information may help you resolve the problem. Possible Cause #3 -- The NEXTSTEP faxcleanup program failed Fax data received by NXFax is converted into a fax file by a NEXTSTEP program called faxcleanup. Although faxcleanup nearly always works reliably, we have occasionally received reports of it failing to do its job properly. If faxcleanup should fail to execute for some reason, it may leave spool files named in the following manner in /usr/spool/NeXTFaxes/<your_modem_name>: Jan_05_1995_12:59:32.001 Jan_05_1995_12:59:32.002 If you see these files after a fax has been received, you can be sure that faxcleanup failed or was interrupted as might occur in a power failure. If you don't see these files, but you received mail saying a fax had come in and/or you see an entry for a received fax in the FaxReader log, faxcleanup may have failed after already removing the spool files, but before creating the fax file. If you have not rebooted your machine since the fax came in, check the workspace console to see if there are any error messages from faxcleanup. Unfortunately, if the fax is not in /usr/spool/NeXTFaxes/<your_modem_name>, then it simply is not on your system. The best you can do is to send a fax back to the sender (assuming their number is reported in the FaxReader log) and ask them to re-send. Again, faxcleanup is part of NEXTSTEP and this kind of problem is extremely rare, but is mentioned here for completeness. ---- If faxcleanup should fail to execute for some reason, it will leave spoolfiles named in the following manner in /usr/lib/NeXTFaxes/<your_modem_name>: Jan_05_1995_12:59:32.001 Jan_05_1995_12:59:32.002 In this case you simply have to be sure that a matching .fax file exists. For this example, you can cd to the directory where the spoolfiles are located (you must have root permissions to do this) and issue the command: touch Jan_05_1995_12:59:32.fax where the file name you provide is the same as the spool file name minus the page extensions. Then you can give the command /usr/lib/NextPrinter/faxcleanup <n> Jan_05_1995_12:59:32 where <n> is the number of pages. This will decode the files and build the combined fax file, but will not remove the spool files. ---- Since the problem just started happening you might want to think about what has changed on your system recently. One other suggestion that appears to help this situation is to do an operating system upgrade in case some of the system files have been corrupted. Regards, ---------------------------------------------------------- Janice Kenyon nxfax_support@bandw.com Black & White Software, Inc. NeXTMail OK Bridge Street Marketplace 802-496-8500 Waitsfield, VT 05673-1210 802-496-5112 (fax) Automated Help nxfax_help@bandw.com ---------------------------------------------------------- -- ________________________________________________________ Antoine Schmitt, ASCI - Paris, France
From: svail@next.com (Scott Vail) Newsgroups: comp.sys.next.bugs Subject: Re: Install NeXT to a Notebook computer Date: 11 Sep 1996 06:49:56 GMT Organization: NeXT Software, Inc. Message-ID: <515nek$8n0@news.next.com> References: <512scj$99n@netnews.hinet.net> In article <512scj$99n@netnews.hinet.net> batmon@abico.com.tw (Mon-Sen Yang) writes: > Hi, > > I am planing to install OpenStep or NeXTStep v3.3 to a notebook > computer. The notebook is P586/100, 16MB RAM with 1GB EIDE HD. I > also use an Adaptec SlimSCSI card to attach my CD-ROM. The problem is > when I use the boot-up disk and set the CD-ROM driver to Adaptec > PCMCIA 6x60 Card, HD to EIDE driver;, it only found my HD and said > there is no SCSI device or CD-ROM. I did check with NeXTanswers and > it says NeXT does support Adaptec SlimSCSI card. Is there any other > driver I have to load or any procedure I have to do for NeXT to be > able to find the Slim SCSI card?? > Make sure you are using the latest version of the PCMCIA, PCIC, and AHA-6x60 SCSI drivers, all of which can be found on NextAnswers. See "http://www.next.com/NeXTanswers/NABrowse?/NEXTSTEP/Intel_Configuration_In formation/Drivers" for more details on acquiring these drivers or getting floppy disk images for Nextstep installation. --Scott -- This is not official NeXT stuff, so ignore me if you want. http://www.next.com/~svail/ "Our intent is to flood the market with free Internet software and squeeze Netscape until they run out of cash." -- Microsoft on fair competition in the Internet market
From: larryy@dove.mtx.net.au (larry youngberry) Newsgroups: comp.sys.next.bugs Subject: Static device resource conflict Date: Sat, 14 Sep 1996 06:04:59 GMT Organization: Microtronics Information Systems Message-ID: <51dlc6$6bf@curlew.mtx.net.au> Hi, Does anyone know what the problem could be and how to cure it on my computer. It appears on the start up screen, it does not appear to be causing troubles, that I know of. Regards, Larry
Newsgroups: comp.sys.next.bugs From: Nitezki@NiDat.sub.org (Peter Nitezki) Subject: Re: faxcleanup fails, crashes and looses my received faxes Message-ID: <DxpzD3.81@nidat.sub.org> Sender: nitezki@nidat.sub.org (Peter Nitezki) Organization: private site of Peter Nitezki, Kraichtal, Germany References: <1996Sep11.215701.9467@asci.fdn.fr> Date: Sat, 14 Sep 1996 11:17:27 GMT In article <1996Sep11.215701.9467@asci.fdn.fr> as@asci.fdn.fr (Antoine Schmitt) writes: > I am having a big problem with my fax software. The software is standard > from NeXT. Here is what happens: > - Incoming fax call, modem picks up > - Fax is received > - modem hangs up, says no error > - I receive mail saying I have a new fax and should run FaxReader > - I run FaxReader and there is nothing. > This has happened from two different callers now, so I am starting to > worry. Does this mean you have a modem that works with plain NEXTSTEP drivers? I thought there is none left from the old days and that almost everyone now runs NXFax? Might just be that the protocol only works to a certain extent but that there are no valid data in the queue. -- Peter Nitezki | Nitezki@NiDat.sub.org # Blessed art thou who knoweth Staarenbergstr. 44 | Tel.: +49 7251 62495 # not about the pleasure and D-76703 Kraichtal | Fax : +49 7251 69215 # delight of being hooked GERMANY | E-mail defunct, sorry # up to the Net. Peter 1,3-5
From: Bernhard Scholz <scholz@informatik.tu-muenchen.de> Newsgroups: comp.sys.next.bugs Subject: CDPlayer and OS4.0 Date: Thu, 19 Sep 1996 14:05:42 +0200 Organization: Technische Universitaet Muenchen, Germany Distribution: world Message-ID: <Pine.HPP.3.95.960919140346.18454D-100000@hphalle0.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Since upgrading to OS4.0 CDPlayer.app refuses to work with my system. It states: can't find CD-ROM. Unfortunatly OmniCD continues to work, and now starts up automatically to replace CDPlayer. Any suggestions why this happens? I like the fast-forward/backward buttons from CDPlayer which OmniCD is lacking. Greetings, Bernhard. -- Bernhard Scholz (IRC: Boerny) scholzb@pst.informatik.uni-muenchen.de http://peanuts.leo.org/ http://www.leo.org/~scholz/
From: Bernhard Scholz <scholz@informatik.tu-muenchen.de> Newsgroups: comp.sys.next.bugs Subject: Sound.app and OS4.0 Date: Thu, 19 Sep 1996 14:07:38 +0200 Organization: Technische Universitaet Muenchen, Germany Distribution: world Message-ID: <Pine.HPP.3.95.960919140551.18454E-100000@hphalle0.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Everytime I doulbe click a .snd file to load it, Sound.app starts up as usual, but can't load the sound. This happens with any sound. If I choose "Open..." I can load the /NextLibrary/Sound/ files, but it still fails with larger sound files (50MB or more) (on a 64MB machine) Greetings, Bernhard. -- Bernhard Scholz (IRC: Boerny) scholzb@pst.informatik.uni-muenchen.de http://peanuts.leo.org/ http://www.leo.org/~scholz/
From: Bernhard Scholz <scholz@informatik.tu-muenchen.de> Newsgroups: comp.sys.next.bugs Subject: Warning: NEXTIME trashing filesystem Date: Tue, 24 Sep 1996 14:28:29 +0200 Organization: Technische Universitaet Muenchen, Germany Distribution: world Message-ID: <Pine.HPP.3.95.960924141616.8092A-100000@hphalle0.informatik.tu-muenchen.de> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello, Ok, it sounds more serious than it eventually is. I didn't test it too intensivly and didn't bug@next because I want to know other experiences before doing so: The situation: - Running OS4.0 - I'm working with 'Openere.app' all day: no problems - copying and deleting files to and from the root's /tmp directory: no problem. No the wired cause: - Selecting a compressed quicktime movie runs Opener as usually and decrunches fine (I expect there is no error here) - I double click the movie and it launches NEXTIME. - I can play the movie etc. - I do repeat the procedure for more quicktime movies. The whole time I'm watching my swapfile and the free space on the root device (there is my /tmp and Opener decrunches the files to /tmp/O_xxx). After e.g. allocating about 100MB of diskspace due to decrunching, I deleted all quicktimes from /tmp, but only about 50MB are reclaimed!!! The swapfile didn't grow, so where are the lost MBs? It get's even worse: rebooting doesn't work now.. The system isn't able to shutdown the system, it simply can't umount root!!!!! Of course everytime I reboot, root is fsck'ed, which is quite annoying. I tried it several times and this always occurs if I run NEXTIME, no problems occur if I don't run it. Anybody experienced something equal? Greetings, Bernhard. P.S.: there is another bug in NEXTIME 4.0 which causes the sound to break when I deactivate the NEXTIME window. In some circumstances it isn't possible to play sound again: it is always stopped after a certain period of time (I expect it to be a buffering problem) and only restarting NEXTIME helps. Of course the NEXTIMESound.driver is installed. I'm using an non-PnP SB16, 16Bit & 8 Bit DMA mode. -- Bernhard Scholz (IRC: Boerny) scholzb@pst.informatik.uni-muenchen.de http://peanuts.leo.org/ http://www.leo.org/~scholz/
From: kiwi@buran.fb10.tu-berlin.de (Axel Habermann) Newsgroups: comp.sys.next.bugs Subject: Re: Warning: NEXTIME trashing filesystem Date: 24 Sep 1996 21:03:39 GMT Organization: Technical University Berlin, Germany Distribution: world Message-ID: <529ibb$4e0@brachio.zrz.TU-Berlin.DE> References: <Pine.HPP.3.95.960924141616.8092A-100000@hphalle0.informatik.tu-muenchen.de> Bernhard Scholz <scholz@informatik.tu-muenchen.de> wrote: [...] : It get's even worse: rebooting doesn't work now.. The system isn't able to : shutdown the system, it simply can't umount root!!!!! : Of course everytime I reboot, root is fsck'ed, which is quite annoying. : I tried it several times and this always occurs if I run NEXTIME, no : problems occur if I don't run it. : Anybody experienced something equal? 'sndplay'ing a very large file has the same effect on 3.3 (unability to reclaim the space by unlinking the file, no clean shutdown). Perhaps a problem with memory-mapping large files? -- Axel Habermann kiwi@buran.fb10.tu-berlin.de Fon:+49 30 45478986 Fax:4542296 Die Dateien, in denen die Programmdokumentation enthalten ist, haben normalerweise die Endung ".c", -- Kristian Koehntopp
From: Bernhard Scholz <scholz@informatik.tu-muenchen.de> Newsgroups: comp.sys.next.bugs Subject: Re: Warning: NEXTIME trashing filesystem Date: Wed, 25 Sep 1996 11:16:37 +0200 Organization: Technische Universitaet Muenchen, Germany Distribution: world Message-ID: <Pine.HPP.3.95.960925105842.18580A-100000@hphalle0.informatik.tu-muenchen.de> References: <Pine.HPP.3.95.960924141616.8092A-100000@hphalle0.informatik.tu-muenchen.de> <529ibb$4e0@brachio.zrz.TU-Berlin.DE> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII In-Reply-To: <529ibb$4e0@brachio.zrz.TU-Berlin.DE> On 24 Sep 1996, Axel Habermann wrote: > Bernhard Scholz <scholz@informatik.tu-muenchen.de> wrote: > [...] > : Anybody experienced something equal? > > 'sndplay'ing a very large file has the same effect on 3.3 > (unability to reclaim the space by unlinking the file, no > clean shutdown). > > Perhaps a problem with memory-mapping large files? > I'm going to believe so, although I upgraded my system to 96MB RAM (because it was simply sooo cheap) and no swapping occured, this might really be a memory mapping problem. ... On the other hand, maybe there is something wrong with my disk. Yesterday I lost all may Quantum drives' disk space (4.5GB) containing the premastered Peanuts CD-ROM, due to an kernel panic. Fsck wasn't able to restore the drive (unexpected inconsitencies) so I have to reinstall the whole system, which will take at least two days *sigh* :-( I never had such a big bang with NS3.3, so should I learn something? Maybe the problem reoccurs, maybe not... Greetings, Bernhard.
From: far@ix.netcom.com(Felipe A. Rodriguez) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Q:NeXT and Fujitsu 2513 MO (3.5" 640mb MO Solutions) Date: 25 Sep 1996 11:55:28 GMT Organization: Netcom Message-ID: <52b6jg$hlv@dfw-ixnews3.ix.netcom.com> In case anyone is curious a Fujistsu M2513A is a 3.5" Direct Overwrite MO drive capable of storing 640mb (2048 b/s media). Great drive! The following was posted here a while ago: > In comp.sys.next.sysadmin article <4q3dd0$qam@ra.ibr.cs.tu-bs.de> > you wrote: > > > >Hallo! > >I'v brought a Fujitsu 2513 MO and want to use a Medium with > blocksize of 2048 > >Byte! > >1.: > >If I want to use the Medium, the Console output is: > >"Note: This device's > >block size (2048) is too big to coerce to DEV_BSIZE (1024). You > won't be > >able to use it with software versions earlier then Release 3.0" > >2.: > >If I want to formatted a Medium with 512 Byte blocksize the Output is: > >"Device Init Panel - Cannout select the default (choosing NeXT instead) > >->can't write label -- diskunusable !: I/O error" > > > >Can anybody help me with that Problems and can someone tell me whitch > >Program must be updated! > > > >I'm use Next Release 3.3 on an Intel Prozessor! Recently, these drives became available in the US. Although I did not get the exact errors, I did experience similar difficulties. The problem mentioned above probably arises from the device driver getting confused when using the 2513 with both 512 and 2048 b/s media. Use one or the other during any given session. Otherwise, once this occurs I've needed to reboot to get things back in order. Workspace initializer/BuildDisk do not properly initialize the media for this drive. The workaround involves disktab entries and a small program which covers for newfs. For some reason disk and newfs produce different results using the same disktab entry. On the 230mb media I needed to double the sa value when using disk instead of newfs. The following disktab entries have been working for me, although, they could probably stand some tweaking. # # Fujitsu 640mb 3.5" MO SCSI M2513A-2048 # # M2513A-640|M2513A-2048|M2513A-640-2048|FUJITSU M2513A-640-2048:\ :ty=removable_rw_scsi:nc#808:nt#2:ns#192:ss#2048:rm#3600:\ :fp#80:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=mach_kernel:z0#16:z1#48:ro=a:\ :pa#0:sa#310272:ba#8192:fa#2048:ca#16:da#4096:ra#5:oa=time:\ :ia:ta=4.3BSD:aa: # # Fujitsu 230mb 3.5" MO SCSI M2513A-512 # # M2513A-230|M2513A-512|FUJITSU M2513A 1000 -512|FUJITSU M2513A 1000-512:\ :ty=removable_rw_scsi:nc#348:nt#2:ns#320:ss#512:rm#3600:\ :fp#320:bp#0:ng#0:gs#0:ga#0:ao#0:\ :os=mach_kernel:z0#64:z1#192:ro=a:\ :pa#0:sa#223002:ba#8192:fa#1024:ca#16:da#4096:ra#5:oa=time:\ :ia:ta=4.3BSD:aa: With just these disktab entries you can initialize the 2513 from the command line. I wrote the following short program so that I could use Workspace/Buildisk to initialize disks. If anyone has a more elegant solution I would like to hear about it. //***************************************************************************** // // newfs cover -- newfsCover.c // // When placed at /usr/etc/newfs this program will cover for and // subsequently call newfs.org (the system supplied original). // This is just a quick hack to allow Workspace manager to properly // initialize a Fujitsu M2513A 3.5" 640mb MO drive. The system // supplied newfs miscalculates its values with this drive. // // This hack was necessary because I was unable to get BuildDisk // or the Workspace initializer to take my disktab otherwise. // // Using: // // 1. cc newfsCover.c -o newfs // 2. mv /usr/etc/newfs /usr/etc/newfs.org // 3. copy this newfs cover to /usr/etc/newfs. // 4. Append the M2513A disktab entries to your /etc/disktab // // Bugs: // // The M2513A is capable of using a variety of media, this program // should be extended to support these by looking at the label info // written down by disk. Currently, this program only supports two // media types: 640-2048 and 230-512 which must be defined in disktab. // // When using different block size media the driver can get confused, // it may be possible to reset it using this thing. // // It might be better if this program covered for disk instead of newfs // // This code is hereby placed into the public domain. Use at your own risk. // // Felipe A. Rodriguez 9/23/96 far@ix.netcom.com // //***************************************************************************** #import <sys/param.h> #import <signal.h> #import <bsd/dev/disk.h> #import <bsd/dev/scsireg.h> #import <libc.h> #import <stdlib.h> #import <sys/file.h> #import <sys/disktab.h> main(int argc, char *argv[]) { int fd; static struct drive_info di; char Path[MAXPATHLEN + 1]; strncpy(Path, *argv++, MAXPATHLEN); strncat(Path, ".org ", MAXPATHLEN - strlen(Path)); while(*argv) { if(**argv == '/') { fd = open(*argv, O_RDWR, 0); ioctl(fd, DKIOCINFO, &di); // get info about device printf("drive type name -- %s\n", di.di_name); close(fd); } strncat(Path, *argv++, MAXPATHLEN - strlen(Path)); strncat(Path, " ", MAXPATHLEN - strlen(Path)); } // if an M2513A and disktab not already specified on commLine if(strstr(di.di_name, "M2513A") && (!strstr(Path, "M2513A"))) { printf("Fujitsu M2513A drive, media block size of %d\n", di.di_devblklen); if(di.di_devblklen == 512) strncat(Path, "M2513A-230", MAXPATHLEN - strlen(Path)); else strncat(Path, "M2513A-640", MAXPATHLEN - strlen(Path)); } printf("%s", Path); printf("%s", "\n"); system(Path); // call the real newfs exit(0); } -- Felipe A. Rodriguez # Francesco Sforza became Duke of Milan from Agoura Hills, CA # being a private citizen because he was # armed; his successors, since they avoided far@ix.netcom.com # the inconveniences of arms, became private (NeXTmail preferred) # citizens after having been dukes. (MIMEmail welcome) # --Nicolo Machiavelli
From: Constantin Szallies <szallies@energotec.de> Newsgroups: comp.sys.next.bugs Subject: Bugs in OpenStep Conversion Date: 26 Sep 1996 13:12:44 GMT Organization: Tech Net GmbH Message-ID: <52dvgc$13t@ddfservb.technet.net> I noticed the following two bugs in the Openstep conversion scripts: 1) Any method using (const char*) instead of (const char *) in not included in the StringMethods file produced by the preprocess step. Work-a-round: In /NextDeveloper/OpenStepConversion/UtilityScripts/ shellscripts Replace: /usr/bin/egrep 'char \*|NXAtom' $allMethodsFile > $optionalString by /usr/bin/egrep 'char\*|char \*|NXAtom' $allMethodsFile > $optionalString 2) If a method head in the implementation file ends with a ";" character, the optional string convertion script doesn't work. For example this doesn't work: - (const char *)lotNrTxt; { return ""; } Work-a-round: None? ??????????????????????????????? Are there some more bugs one should know ? ??????????????????????????????? -- Constantin Szallies, Energotec GmbH szallies@energotec.de 49211-9144018
Newsgroups: comp.sys.mac.games,comp.sys.next.bugs,comp.sys.next.misc,comp.sys.northstar,comp.windows.x.pex,hepnet.conferences From: dsr@lns598.lns.cornell.edu Sender: GetFree@mail.com Date: 26 Sep 1996 20:35:37 EDT Control: cancel <3242D9EC.7D93@mail.com> Subject: cmsg cancel <3242D9EC.7D93@mail.com> Message-ID: <cancel.3242D9EC.7D93@mail.com> Spam/MMF cancelled by dsr@lns598.lns.cornell.edu original subject was BEYOND TECHNOLOGY
From: Charles William Swiger <cs4w+@andrew.cmu.edu> Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: netinfo woes--help please--more info Date: Fri, 27 Sep 1996 12:47:01 -0400 Organization: Carnegie Mellon, Pittsburgh, PA Message-ID: <EmH0I5m00Uzx01sLct@andrew.cmu.edu> References: <52fnjm$mt5@news.tamu.edu> <52gi0p$hn0@crcnis3.unl.edu> In-Reply-To: <52gi0p$hn0@crcnis3.unl.edu> Excerpts from netnews.comp.sys.next.sysadmin: 27-Sep-96 Re: netinfo woes--help plea.. by Rex Dieter@math.unl.edu > The "official" and "proper" thing to do is to set the machines hostname to > be a FQDN (Fully Qualified Domain Name), > hostname = yhost.mysubdomain.mydomain I agree, but there are (or at least were) major problems doing so under NEXTSTEP. I've been a NEXTSTEP sysadmin for years now, and I have _never_ been able to get NetInfo and FQDNs to work together. It hasn't worked under NS 2.1, 2.2, 3.0, 3.2, or 3.3. I even addressed the following question to NeXT's Premium Technical Support, but they were unable to provide an answer. Cal Thixton of NeXT said that he had once gotten it working, but it had proven to be so difficult that he could not remember what had to be done, so he recommended not using FQDNs with NEXTSTEP. I would greatly appreciate it if someone from NeXT would give us a coherent explanation of why this is such a problem. =============================================================== Message-Id: <199509141845.OAA23859@tertius.res.cmu.edu> From: Charles Swiger <chuck@its.com> Date: Thu, 14 Sep 95 14:45:32 -0400 To: its_psst@next.com Subject: FQDN hostname problems Hello, How can I give my machine a fully-qualified domain name (FQDN) under NEXTSTEP? Background: ----------- It appears that portions of NeXT's software simply cannot handle a canonical hostname in the form of a FQDN. An example would be naming my machine "tertius.res.cmu.edu" instead of just "tertius". For example, one major problem that occurs if I name my machine "tertius.res.cmu.edu" instead of "tertius" is the pasteboard server fails with a "pasteboard server error -102" message to the console whenever I try to do drag-n-drop or cut-copy-paste. (There appear to have been other problems in NetInfo as well, but a NEXTSTEP system with the pasteboard not working is effectively unusable, so I have not investigated in more detail.) What's wrong with not using FQDN's? Well, you break the following invariant: gethostbyname(gethostname()) == gethostbyaddr(primary_interface_address) ...so every application such as mail readers, newsreaders, sendmail, and so forth has to contain a few hundred of lines of fairly involuted code to reliably determine what the real FQDN of the machine is. Having to use an unqualified hostname to get the pbs and NetInfo working has also historically resulted in a large number of NeXT systems who send email or post to newsgroups as "user@tertius" instead of "user@tertius.res.cmu.edu". -Chuck Charles Swiger | cs4w@andrew.cmu.edu | standard disclaimer ----------------+---------------------+--------------------- I know you're an optimist if you think I'm a pessimist.
From: thedrjay@aol.com (The Dr Jay) Newsgroups: comp.sys.next.bugs Subject: Re: NS Crashed :-( Date: 27 Sep 1996 22:12:11 -0400 Organization: America Online, Inc. (1-800-827-6364) Sender: root@newsbf02.news.aol.com Message-ID: <52i1hr$pbp@newsbf02.news.aol.com> References: <4rh1bd$gr@turbocat.snafu.de> f you read the manual for the Asus mother board you will find it clearly states for a 100 MHz Pentium CPU to use 60 Ns RAM. I have seen a lot of systems with 70 Ns ram used when 60 Ns RAM was specified. Most of the times they work without problems, but not always. Whether it works depends on the memory manufactures tolerances. Most of the better manufactures 70 Ns ram will test out at 60 Ns when checked with a SIMM tester at ambient temperature. This insures that they will meet the 70 Ns specification at higher operating temperature (performance of semiconductors degrade at higher temperatures). Some inferior manufactures don’t factor in temperature, and will mark there chips at 70 Ns that test OK at ambient temperature leaving no margin for degradation form heat. Also there are a lot of remarked chips on the market most of times they where sold for use in none critical applications like toys (due to being low-grade seconds), or where remarked from 80 Ns to 70 Ns (at this time the only current use in computers for 80 Ns ram is printers mostly). Because of this care must be taken when buying RAM to insure you get memory that meets specifications for your system, and is from a reputable supplier.
From: rdieter@math.unl.edu (Rex Dieter) Newsgroups: comp.sys.next.bugs Subject: Re: netinfo woes--help please--more info Date: 30 Sep 1996 14:27:32 GMT Organization: University of Nebraska--Lincoln Message-ID: <52olcl$n59@crcnis3.unl.edu> References: <EmH0I5m00Uzx01sLct@andrew.cmu.edu> In article <EmH0I5m00Uzx01sLct@andrew.cmu.edu> Charles William Swiger <cs4w+@andrew.cmu.edu> writes: > Excerpts from netnews.comp.sys.next.sysadmin: 27-Sep-96 Re: netinfo > woes--help plea.. by Rex Dieter@math.unl.edu > > The "official" and "proper" thing to do is to set the machines hostname > > to be a FQDN (Fully Qualified Domain Name), > > hostname = yhost.mysubdomain.mydomain > > I agree, but there are (or at least were) major problems doing so under > NEXTSTEP. I've been a NEXTSTEP sysadmin for years now, and I have > _never_ been able to get NetInfo and FQDNs to work together. It hasn't > worked under NS 2.1, 2.2, 3.0, 3.2, or 3.3. Umm... That's odd, because I've had it working successfully for almost 2 years here while I've been sysadmin, and we are using both 3.2 and 3.3. I WAS careful to put aliases to the old variants of the hostnames in NetInfo (just in case). -- Rex Dieter Computer System Manager Department of Mathematics and Statistics University of Nebraska Lincoln
From: Charles William Swiger <cs4w+@andrew.cmu.edu> Newsgroups: comp.sys.next.bugs Subject: Re: netinfo woes--help please--more info Date: Mon, 30 Sep 1996 14:49:30 -0400 Organization: Carnegie Mellon, Pittsburgh, PA Message-ID: <EmI1MuK00UzxQ27LZ5@andrew.cmu.edu> References: <EmH0I5m00Uzx01sLct@andrew.cmu.edu> <52olcl$n59@crcnis3.unl.edu> In-Reply-To: <52olcl$n59@crcnis3.unl.edu> Excerpts from netnews.comp.sys.next.bugs: 30-Sep-96 Re: netinfo woes--help plea.. by Rex Dieter@math.unl.edu >> I agree, but there are (or at least were) major problems doing so under >> NEXTSTEP. I've been a NEXTSTEP sysadmin for years now, and I have >> _never_ been able to get NetInfo and FQDNs to work together. It hasn't >> worked under NS 2.1, 2.2, 3.0, 3.2, or 3.3. > > Umm... That's odd, because I've had it working successfully for almost 2 > years here while I've been sysadmin, and we are using both 3.2 and 3.3. I > WAS careful to put aliases to the old variants of the hostnames in NetInfo > (just in case). Question: in /etc/hostconfig, is 'HOSTNAME' set to a FQDN? -Chuck Charles Swiger | cs4w@andrew.cmu.edu | standard disclaimer ----------------+---------------------+--------------------- I know you're an optimist if you think I'm a pessimist.
From: eric@skatter.USask.Ca Newsgroups: comp.sys.next.programmer,comp.sys.next.bugs Subject: Printf %g format still broken in OPENSTEP 4.0 Date: 30 Sep 1996 19:10:49 GMT Organization: University of Saskatchewan Message-ID: <52p5vp$1sq@tribune.usask.ca> I just upgraded my machine (486DX2/66) to OPENSTEP 4.0. One of the first things I tried was my printf `%g' format test program: #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; } Here's the output after compiling the program on NEXTSTEP 4.0: Expect 0.00123: 0.001 Expect 123: 123.457 Expect 123.5: 123.4567 Expect 1e+03: 999.6 I can hardly believe this. It is now *SEVEN YEARS* since I first reported this bug (in NextStep 1.0). I have reported this error in every subsequent release up to and including NEXTSTEP 3.3. In May, 1994 I received mail from NeXT saying that this would be fixed in 4.0. Looks like they missed it again. Every other time I have posted an article about this bug I have received mail saying that the behaviour of the NeXT printf is correct. To try and forestall these replies I include the following: 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 test program: >> >> format "%.3g" .001234567 >> >> ==== Result was: >> 0.001 >> ---- Result should have been: >> 0.00123 The zero's in 0.00123 are *not* significant. Score 1 against NeXT. >> >> format "%.3g" 999.6 >> >> ==== Result was: >> 999.6 >> ---- Result should have been: >> 1e+03 >> The format calls for 3 SIGNIFICANT DIGITS. Rounding 999.6 to three significant digits leaves 1000, 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 Phone: (306) 966-6308 University of Saskatchewan FAX: (306) 966-6058 Saskatoon, Canada. NeXTMail accepted.
From: dmd@asimov.oit.umass.edu (Daniel M. Drucker) Newsgroups: comp.sys.next.bugs Subject: Librarian crashes Date: 30 Sep 1996 15:22:33 -0400 Organization: University of Massachusetts, Amherst Message-ID: <52p6lp$c0@asimov.oit.umass.edu> If I run Librarian and click on my home directory icon, it always crashes while doing the index. The machine must be hard-power-cycled; alt-numluck doesn't work. This is 3.3 U+D on a Cyrix P166+ with 32mb. -- [ Daniel M. Drucker / dmd@3e.org ] dreams windblown and scattered among the grass and sand
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.