This is Bugs-12.gz in view mode; [Up]
Newsgroups: comp.sys.next.bugs From: dsr@lns598.lns.cornell.edu Sender: btr@trenet.com Date: 30 Nov 1996 22:04:34 EST Control: cancel <32a0c8c4.17335814@nntp.cts.com> Subject: cmsg cancel <32a0c8c4.17335814@nntp.cts.com> no reply ignore Message-ID: <cancel.32a0c8c4.17335814@nntp.cts.com> Spam cancelled by dsr@lns598.lns.cornell.edu original subject was Be a Beta Tester!
From: shess@one.net (Scott Hess) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 5 Dec 96 09:50:15 Organization: Is a sign of weakness Distribution: world Message-ID: <SHESS.96Dec5095015@slave.one.net> References: <585ri8$qb6@news.doit.wisc.edu> In-reply-to: giddings@menominee.chem.wisc.edu's message of 5 Dec 1996 06:54:00 GMT In article <585ri8$qb6@news.doit.wisc.edu>, giddings@menominee.chem.wisc.edu (Michael Giddings) writes: Another piece of evidence is that I did a complete text search of the *entire* hard drive for "/bin/rm -rf" and OpenWrite *does* contain that string (and not many other apps do). The last nail is the following, posted earlier by Christopher Wolf in c.s.n.bugs: >There is a bug in OpenWrite having to do with renaming a chapter >in a book which will wipe out all the files in your home >directory. A coworker of mine was bitten by it just a couple of >weeks ago. Sounds like this may have happened to you. Boy, that is _truly_ scary. Using system() or popen() to execute simple informative commands like "hostinfo" is bad enough. Using it to execute destructive commands is pretty bad - unforgivable in a program you're going to distribute. It's not like unlink() and rmdir() are really _that_ tough to use. Recursive directory deletion using kernel calls is certainly not a walk in the park, but I've written it enough times that I know it's about eight orders of magnitude simpler than a word processor :-). OTOH, OpenWrite was not written at Lighthouse, so fortunately this doesn't implicate other programs they've written. Later, -- scott hess <shess@one.net> (606) 578-0412 http://w3.one.net/~shess/ <I plan to become so famous that people buy tapes of me reading source code>
From: cwolf@wolfware.com (Christopher Wolf) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Trojan horse or bug? (This is scary!!!!!) Date: 6 Dec 1996 03:38:16 GMT Organization: Best Internet Communications Message-ID: <5884f8$q95@nntp1.best.com> References: <584i3p$30ao@news.doit.wisc.edu> <585djv$sd3@nntp1.best.com> <58706j$a8e@bignews.shef.ac.uk> In-Reply-To: <58706j$a8e@bignews.shef.ac.uk> On 12/05/96, mmalcolm crawford wrote: >On 12/05/96, Christopher Wolf wrote: > >> There is a bug in OpenWrite having to do with renaming a chapter in a book >> which will wipe out all the files in your home directory. A coworker of >> mine was bitten by it just a couple of weeks ago. Sounds like this may >> have happened to you. >> >WHAT??!! > >I can hardly believe this. > >*If true* (I'd like to see some sort of confirmation) this is appalling... >not so much for the fact that the bug exists (although that such a malicious >bug should exist is bad enough), but rather for the fact that as far as I'm >aware no announcement has been made. Can I prove it or document it? No - I personally don't ever have the need to use OpenWrite so I haven't worried about it. I've seen two people have the exact same thing happen to them though (they were rearranging/renaming chapters in a book in OpenWrite and most/all of their home directory files were deleted). When it happened to my co-worker several other people in our company commented that the had seen the same thing happen to them (we have LOTS of NeXTSTEP systems and site licenses for most of the Lighthouse apps) so I assumed this was already "common knowledge." >Not impressed at all, > >mmalc. --
From: jsamson@istar.ca (Jean-Paul C. Samson) Newsgroups: comp.sys.next.bugs Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 6 Dec 1996 04:36:43 GMT Organization: iSTAR Internet Incorporated Message-ID: <5887sr$ni@news.istar.ca> References: <585ri8$qb6@news.doit.wisc.edu> <SHESS.96Dec5095015@slave.one.net> In-Reply-To: <SHESS.96Dec5095015@slave.one.net> >OTOH, OpenWrite was not written at Lighthouse, so fortunately this >doesn't implicate other programs they've written. Well, I have troubles with Concurrence 2 incorrectly saving files. My first and last experience with the product involved producing some overheads. When I tried to reload the file, some text and other information I typed in was missing. I reinserted the material, saved, loaded and guess what--the same stuff had disappeared again. So Concurrence doesn't save/load correctly. I think I can blame Lighthouse for that one, since I believe they wrote that application. Ever since, I've used FrameMaker to do my overheads... -- -===================================================================- Jean-Paul C. Samson -=- jsamson@istar.ca -=- NeXTmail & MIME welcome -============- http://www.cs.ualberta.ca/~jeanpaul/ -=============- -===================================================================-
From: pete@ohm.york.ac.uk (-bat.) Newsgroups: comp.sys.next.bugs Subject: Re: Corrupt serial output under 4.0 ? Date: 30 Nov 1996 19:29:09 GMT Organization: The University of York, UK Message-ID: <57q1u5$17r@netty.york.ac.uk> References: <57hkou$gov@digdug.pswtech.com> robin@pswtech.com (Robin Wilson) writes: > What do you get when you use "tip" or other programs designed to read/write > serial ports? (I'm not suggesting that you should be able to use 'cat' -- > just as a debugging tool I'd like to know if this is related to how 'cat' > opens the serial device file descriptor, vs. a program that knows about flow > control and the like. Your problem could be related to flow control as well. Same problems with tip, cat, kermit and dd - it's definitely the serial port. The flow control is identical to that I used under 3.3 - the ,machines haventchanges I just upgraded the O.S. They also work fine when booted under DOS/Windows/NT - sigh. i guess I'm the only one who's got this problem then :-(
From: root@sucre.unice.fr (Operator) Newsgroups: comp.sys.next.bugs Subject: Kernel Trap with PRO200 under 4.0 Date: 6 Dec 1996 14:48:00 GMT Organization: University of Nice Sophia-Antipolis Message-ID: <589bn0$9kp@malibu.unice.fr> Hello, We have a clone Pentium PRO 200 with 4 ultra wide scsi hard drives of 2Go under 4.0 and a lots of NextStation under 3.3 and every day there is a kernel trap with messages like : Frame 7b7bf5c called by 1454d5 args 6086de0 01 11 Frame 7b7bf94 called by 1514cd args fffffffff 11 1 .. We change all the devices (network card, video card,...even motherboard) and we have the same problem, has anyone got a idea ? Thanks Stephane Maurel maurel@doublon.unice.fr.
From: jens (Jens Breitenborn) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 5 Dec 1996 17:10:48 GMT Organization: Universitaet Bremen, Germany Distribution: world Message-ID: <586vmo$89b@kohl.informatik.uni-bremen.de> References: <585ri8$qb6@news.doit.wisc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Cc: giddings@menominee.chem.wisc.edu In <585ri8$qb6@news.doit.wisc.edu> Michael Giddings wrote: > WARNING: Potential bug that may cause data serious data loss (everything in > your home directory)! > > [....] > > ***I would recommend that people refrain from using any of the book related > features of OpenWrite, and possibly refrain from using it at all, until there > is a definitive response from Lighthouse regarding this potential bug**** > > Unfortunately, this may be the final blow that causes me to go over to > Windoze and use MS-Word. Sad, I hope it doesn't come to that but it may . . > . > > Michael Giddings (my .signature got lost too) > I am using OpenWrite for a long time now. During the last 6 month I've written two mid-size book documents (my diploma thesis ~230 pages in 12 chapters and a manual ~ 150 pages in 11 chapters) using OpenWrite 2.1. Of course there are some (minor) bugs in OpenWrite - but I've never experience that kind of nightmare that you have described (Yes, I have renamed chapters several times ± and I've just tested it again without losing any files.) Which version of OpenWrite/OS do you use ? -- -------------------------------------------------------------------- Jens Breitenborn mailto:jensb@MeVis.Uni-Bremen.DE http://WWW.MeVis.Uni-Bremen.de/~jensb
From: giddings@menominee.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 6 Dec 1996 23:31:20 GMT Organization: University of Wisconsin, Madison Distribution: world Message-ID: <58aac8$14r2@news.doit.wisc.edu> References: <585ri8$qb6@news.doit.wisc.edu> <586vmo$89b@kohl.informatik.uni-bremen.de> Cc: jens In <586vmo$89b@kohl.informatik.uni-bremen.de> Jens Breitenborn wrote: > > I am using OpenWrite for a long time now. During the last 6 month I've > written two mid-size book documents (my diploma thesis ~230 pages in > 12 chapters and a manual ~ 150 pages in 11 chapters) using OpenWrite 2.1. > Of course there are some (minor) bugs in OpenWrite - but I've never > experience that kind of nightmare that you have described (Yes, I have > renamed chapters several times ± and I've just tested it again > without losing any files.) > > Which version of OpenWrite/OS do you use ? > > > I was using version 2.1. However, the woman I talked to at Lighthouse said she thought it affected all versions back to 1.x. BTW - Lighthouse has publicly acknowledged that this bug DOES exist, I think they posted to c.s.n.software or something like that. I'd say you're very lucky it never struck you, luckier than I was. -- Michael Giddings giddings@chem.wisc.edu giddings@barbarian.com (608)258-1699 or (608) 692-2851 http://www.barbarian.com
From: jray@bigmac.ag.ohio-state.edu (John Ray) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.programmer Subject: Apache 1.2b1 - can anyone compile this on OS 4.0? Date: 4 Dec 1996 13:44:37 GMT Organization: The Ohio State University Message-ID: <jray-0412960848000001@140.254.80.2> Hello, I've been absolutely pleased w/ the previous Apache distributions - of course, I was compiling them under NS 3.3 (Intel). Unfortunately, the combination of OpenStep 4.0 and Apache 1.2b1 doesn't seem to be too happy together. (Fails almost immediately, even if using Apaches REGEX implementation) Any successes? Thanks a bunch, John
From: aisbell@ix.netcom.com (Art Isbell) Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: 4 Dec 1996 16:43:47 GMT Organization: Netcom Distribution: world Message-ID: <5849o3$79o@dfw-ixnews6.ix.netcom.com> References: <57um4p$kat@leonie.object-factory.com> Erik Doernenburg <erik@object-factory.com> wrote: > > I've used the upgrader application that comes with OpenStep for Mach to do > the following: (1) upgrade from 3.3 to 4.0 on NeXT hardware and (2) upgrade > from 4.0 to 4.1 on Intel hardware. In both cases the upgrade worked but it > made *every single binary* on the machine triple-fat, eventhough both > installations were single-architecture installations; m68k and i486 resp. > > Did anybody encounter the same problem or did the upgrade work properly for > you? Or is everybody avoiding to upgrade? So that's why I lost considerable free space when I upgraded from OS 4.0 to 4.1!! I, too, have triple-fat binaries after the upgrade :-( Too bad Xanthus Stripper no longer works on OS apps. -- Art Isbell NeXT/MIME Mail: aisbell@ix.netcom.com Trego Systems Voice/Fax: +1 408 335 2515 CaseServ: OPENSTEP Voice Mail: +1 408 335 1154 managed care solutions US Mail: Felton, CA 95018-9442
From: kiwi@buran.fb10.tu-berlin.de (Axel Habermann) Newsgroups: comp.sys.next.bugs Subject: Re: Kernel Trap with PRO200 under 4.0 Date: 7 Dec 1996 14:15:05 GMT Organization: Technical University Berlin, Germany Message-ID: <58bu59$rt0@brachio.zrz.TU-Berlin.DE> References: <589bn0$9kp@malibu.unice.fr> Operator <root@sucre.unice.fr> wrote: : Hello, : We have a clone Pentium PRO 200 with 4 ultra wide scsi hard drives of 2Go : under 4.0 and a lots of NextStation under 3.3 and every day there is a : kernel trap with messages like : : Frame 7b7bf5c called by 1454d5 args 6086de0 01 11 : Frame 7b7bf94 called by 1514cd args fffffffff 11 1 : .. : We change all the devices (network card, video card,...even motherboard) : and we have the same problem, has anyone got a idea ? Have you changed components between different brands or just replaced one card against another instance of the same brand. I once had kernel traps on a regular basis due to a buggy network driver. On another occasion it was a faulty harddisk making the scsi driver crash. It was hard to diagnose though (involved remote kernel debugging) You should give complete specs of the systems crashing, maybe it reminds someone of something.... -- 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: giddings@menominee.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Trojan horse or bug? (This is scary!!!!!) Date: 4 Dec 1996 19:06:33 GMT Organization: University of Wisconsin, Madison Distribution: world Message-ID: <584i3p$30ao@news.doit.wisc.edu> This morning I was trying to save a document from WriteUp, and noticed that the folder I was trying to save to had disappeared. So I had a look at the File Viewer and noticed that a whole lot of the files in my home directory were MISSING! I also noticed that the disk was chugging away on something. I quickly started a terminal and did a ps aux. **There was a /bin/rm -rf process running under my user id**, which I promptly killed. Unfortunately, it had already removed 3/4 of my files (and nothing seems to have been touched outside my home directory). I couldn't determine what had spawned the process (I had already killed it), and it was attached to no terminal. THIS IS SCARY!!! Either it is a serious bug in one of the programs I was running (OpenWrite, WriteUp, LaunchBar, Backspace, Diagram2) OR it is some kind of trojan horse. There is no way I could have done this accidentally because there was no terminal window at the time. HAS ANYONE SEEN THIS BEFORE? Whatever caused this is VERY bad news. Here is a list of things that I was doing or had recently done on the system that were out of the ordinary, in case any of these things ring any bells: 1. Had for the first time started working with OpenWrite Books, and was in the process of creating a book. 2. I was running WriteUp, which I don't normally use, to try to save a document from it as RTFD. 3. I had unplugged the floppy drive from the computer (I've done this before with no problems). 4. Yesterday I had de-installed then reinstalled the PCMCIA and Xircom ethernet drivers 5. I recently installed LaunchBar and WideScreen, though WideScreen was not being run at the time. 6. I recently sent some negative mail to my NeXT sales rep about NeXT's pricing, and customer treatment (NeXT gets revenge!!) WHATEVER HAPPENED HERE IS VERY BAD NEWS. Please, if you've *ever* seen anything like this post here or send email to me. -- Michael Giddings giddings@chem.wisc.edu giddings@barbarian.com (608)258-1699 or (608) 692-2851 http://www.barbarian.com
From: Bartley R Troyan <bt26+@andrew.cmu.edu> Newsgroups: comp.sys.next.bugs Subject: Re: Apache 1.2b1 - can anyone compile this on OS 4.0? Date: Wed, 4 Dec 1996 17:07:06 -0500 Organization: Carnegie Mellon, Pittsburgh, PA Message-ID: <wmdTM_y00iWn0BmZA0@andrew.cmu.edu> References: <jray-0412960848000001@140.254.80.2> In-Reply-To: <jray-0412960848000001@140.254.80.2> Nope, I couldn't get it to compile under 3.3 either... I posted a message several days ago to comp.infosystems.www.servers.unix, and got no response. I believe the REGEX implementation is the problem, but whatever NeXT's builtin REGEX support is, it doesn't work with 1.2b1 either... If anybody gets it to compile under 3.3 please let me know what you did... THanks Bart Excerpts from netnews.comp.sys.next.bugs: 4-Dec-96 Apache 1.2b1 - can anyone c.. by John Ray@bigmac.ag.ohio- > > I've been absolutely pleased w/ the previous Apache distributions - of > course, I was compiling them under NS 3.3 (Intel). Unfortunately, the > combination of OpenStep 4.0 and Apache 1.2b1 doesn't seem to be too happy > together. (Fails almost immediately, even if using Apaches REGEX > implementation) > > Any successes? > > Thanks a bunch, > John --- Bartley Troyan BLaCKSMITH, Inc. bart@BLaCKSMITH.com (NeXTmail/MIME)
From: andrew_abernathy@omnigroup.com Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: 4 Dec 1996 22:12:54 GMT Organization: Omni Development, Inc. Message-ID: <584t16$i86@gaea.titan.org> References: <57um4p$kat@leonie.object-factory.com> <5849o3$79o@dfw-ixnews6.ix.netcom.com> aisbell@ix.netcom.com (Art Isbell) wrote: > So that's why I lost considerable free space when I upgraded from OS 4.0 > to 4.1!! I, too, have triple-fat binaries after the upgrade :-( Too bad > Xanthus Stripper no longer works on OS apps. Interesting. It didn't do it to me - my 4.0 to 4.1 install left all my apps Intel-only. --- andrew_abernathy@omnigroup.com - NeXTmail & MIME ok
From: Timothy Luoma <luomat@peak.org> Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Trojan horse or bug? (This is scary!!!!!) Followup-To: comp.sys.next.sysadmin Date: Wed, 4 Dec 1996 14:20:53 -0800 Organization: The PEAK FTP site for OpenStep & NeXTStep Message-ID: <Pine.SUN.3.95.961204141731.13846C-100000@kira> References: <584i3p$30ao@news.doit.wisc.edu> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII To: giddings@whitewater.chem.wisc.edu In-Reply-To: <584i3p$30ao@news.doit.wisc.edu> I have been running LaunhBar 24/7 since it came out and have had no such experience. I am sure it is not WideScreen either. I am beginning to think that there is someone out there trying to bring trojan horses to NeXTStep. I have found /bin/sh setuid root twice now. However, I am not using OpenWrite or WriteUp, so I can't say they are connected. I rather expect it is something else TjL
From: randyj@lowana.sbs.ohio-state.edu (Randy Jackson) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 8 Dec 1996 00:26:09 GMT Organization: The Ohio State University Message-ID: <58d1v1$9ts@charm.magnus.acs.ohio-state.edu> References: <585ri8$qb6@news.doit.wisc.edu> <586vmo$89b@kohl.informatik.uni-bremen.de> <58aac8$14r2@news.doit.wisc.edu> In-Reply-To: <58aac8$14r2@news.doit.wisc.edu> >BTW - Lighthouse has publicly acknowledged that this bug DOES exist, I think >they posted to c.s.n.software or something like that. > Ok, I am no programming guru, but I'd say that this bug ought to be extremely easy to purge! Come on, what would it take to find the line that has the rm command and modify it? I'd say a new version of OpenWrite could and should be made available immediately if all this is true. Lighthouse? -- Randy Jackson, Associate Professor ,_ o __o Geography, The Ohio State University / //\, _`\<,_ 1036 Derby Hall, 154 North Oval Mall \>> | (*)/ (*) Columbus OH 43210-1361 \\, FAX (614) 292 6213 randyj@lubra.sbs.ohio-state.edu
From: randyj@lowana.sbs.ohio-state.edu (Randy Jackson) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Re: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 8 Dec 1996 00:31:37 GMT Organization: The Ohio State University Message-ID: <58d299$9vh@charm.magnus.acs.ohio-state.edu> References: <585ri8$qb6@news.doit.wisc.edu> <586vmo$89b@kohl.informatik.uni-bremen.de> <58aac8$14r2@news.doit.wisc.edu> <58d1v1$9ts@charm.magnus.acs.ohio-state.edu> In-Reply-To: <58d1v1$9ts@charm.magnus.acs.ohio-state.edu> Posted the following before seeing Lighthouse's response. Looks like a new release will be forthcoming. Thanks, LH. rj On 12/07/96, Randy Jackson wrote: > >>BTW - Lighthouse has publicly acknowledged that this bug DOES >exist, I think >>they posted to c.s.n.software or something like that. >> > > >Ok, I am no programming guru, but I'd say that this bug ought to >be extremely easy to purge! Come on, what would it take to find the >line that has the rm command and modify it? I'd say a new version >of OpenWrite could and should be made available immediately if all >this is true. > >Lighthouse? > > > > >-- > Randy Jackson, Associate Professor ,_ o > __o Geography, The Ohio State University / //\, > _`\<,_ 1036 Derby Hall, 154 North Oval Mall \>> | >(*)/ (*) Columbus OH 43210-1361 \\, > FAX (614) 292 6213 randyj@lubra.sbs.ohio-state.edu > -- Randy Jackson, Associate Professor ,_ o __o Geography, The Ohio State University / //\, _`\<,_ 1036 Derby Hall, 154 North Oval Mall \>> | (*)/ (*) Columbus OH 43210-1361 \\, FAX (614) 292 6213 randyj@lubra.sbs.ohio-state.edu
From: cwolf@wolfware.com (Christopher Wolf) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs Subject: Re: Trojan horse or bug? (This is scary!!!!!) Date: 5 Dec 1996 02:55:59 GMT Organization: Best Internet Communications Message-ID: <585djv$sd3@nntp1.best.com> References: <584i3p$30ao@news.doit.wisc.edu> In-Reply-To: <584i3p$30ao@news.doit.wisc.edu> On 12/04/96, Michael Giddings wrote: >This morning I was trying to save a document from WriteUp, and noticed that >the folder I was trying to save to had disappeared. So I had a look at the >File Viewer and noticed that a whole lot of the files in my home directory >were MISSING! > >THIS IS SCARY!!! Either it is a serious bug in one of the programs I was >running (OpenWrite, WriteUp, LaunchBar, Backspace, Diagram2) OR it is some >kind of trojan horse. There is no way I could have done this accidentally >because there was no terminal window at the time. > >HAS ANYONE SEEN THIS BEFORE? Whatever caused this is VERY bad news. > >Here is a list of things that I was doing or had recently done on the system >that were out of the ordinary, in case any of these things ring any bells: >1. Had for the first time started working with OpenWrite Books, and was in >the process of creating a book. There is a bug in OpenWrite having to do with renaming a chapter in a book which will wipe out all the files in your home directory. A coworker of mine was bitten by it just a couple of weeks ago. Sounds like this may have happened to you. >WHATEVER HAPPENED HERE IS VERY BAD NEWS. Please, if you've *ever* seen >anything like this post here or send email to me. > >-- >Michael Giddings >giddings@chem.wisc.edu >giddings@barbarian.com >(608)258-1699 or (608) 692-2851 >http://www.barbarian.com > > --
From: aisbell@ix.netcom.com (Art Isbell) Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: 5 Dec 1996 03:36:51 GMT Organization: Netcom Distribution: world Message-ID: <585g0j$rsp@dfw-ixnews6.ix.netcom.com> References: <57um4p$kat@leonie.object-factory.com> <5849o3$79o@dfw-ixnews6.ix.netcom.com> <584t16$i86@gaea.titan.org> andrew_abernathy@omnigroup.com wrote: > > aisbell@ix.netcom.com (Art Isbell) wrote: > > So that's why I lost considerable free space when I upgraded from OS 4.0 > > to 4.1!! I, too, have triple-fat binaries after the upgrade :-( Too bad > > Xanthus Stripper no longer works on OS apps. > > > Interesting. It didn't do it to me - my 4.0 to 4.1 install left all my apps > Intel-only. Mine was a m68k upgrade, so maybe this is a m68k-specific bug. I recouped about 55 MB of disk space by thinning all executables and frameworks. -- Art Isbell NeXT/MIME Mail: aisbell@ix.netcom.com Trego Systems Voice/Fax: +1 408 335 2515 CaseServ: OPENSTEP Voice Mail: +1 408 335 1154 managed care solutions US Mail: Felton, CA 95018-9442
From: giddings@menominee.chem.wisc.edu (Michael Giddings) Newsgroups: comp.sys.next.software,comp.sys.next.bugs,comp.sys.next.sysadmin Subject: Warning: Potential *nasty* bug in OpenWrite (Was: Trojan Horse or Bug?) Date: 5 Dec 1996 06:54:00 GMT Organization: University of Wisconsin, Madison Distribution: world Message-ID: <585ri8$qb6@news.doit.wisc.edu> WARNING: Potential bug that may cause data serious data loss (everything in your home directory)! Earlier today I posted a message after a bunch of files had been wiped out on my hard drive by a "/bin/rm -rf" process that I could not figure out the source of. I was running OpenWrite using the Books feature, rearranging chapters at the time this occurred. At the time I didn't suspect OpenWrite was the cause, so later in the day I resumed work on my *backup* system (kept synchronized with RDIST). As soon as I started working with chapters I had a system panic, due to freeing a freed inode or some such thing. Upon re-boot a bunch of files were missing in my home directory on this system (though the panic seems to have stopped it early enough so it didn't destroy as many as it did this morning). This brought me to start suspecting OpenWrite. Another piece of evidence is that I did a complete text search of the *entire* hard drive for "/bin/rm -rf" and OpenWrite *does* contain that string (and not many other apps do). The last nail is the following, posted earlier by Christopher Wolf in c.s.n.bugs: >There is a bug in OpenWrite having to do with renaming a chapter in a book which >will wipe out all the files in your home directory. A coworker of mine was >bitten by it just a couple of weeks ago. Sounds like this may have happened to >you. Though I cannot currently prove that OpenWrite was the cause (and I'm not about to risk trying it again), at this point I *highly* suspect it has caused data in my accounts on two separate systems to be destroyed (this while my graduate prelim is due in less than 24 hours!) ***I would recommend that people refrain from using any of the book related features of OpenWrite, and possibly refrain from using it at all, until there is a definitive response from Lighthouse regarding this potential bug**** Unfortunately, this may be the final blow that causes me to go over to Windoze and use MS-Word. Sad, I hope it doesn't come to that but it may . . . Michael Giddings (my .signature got lost too)
From: Patrick Stein <jolly@joker.ppp.cis.uni-muenchen.de> Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: 9 Dec 1996 17:32:42 GMT Organization: CIS Uni-Muenchen Distribution: world Message-ID: <58hifq$d3@joker.ppp.cis.uni-muenchen.de> References: <57um4p$kat@leonie.object-factory.com> <5849o3$79o@dfw-ixnews6.ix.netcom.com> Cc: aisbell@ix.netcom.com In prospect of all the people that are now writing scripts to thin out those binaries, here's one. It should get called like : find /bin -exec Thinner.perl m68k {} \; find /NextApps -exec Thinner.perl m68k {} \; I even used find / -fstype 4.3 -exec Thinner.perl m68k {} \; It worked on my black hardware - you might have to change the %magiccookies hash on littleendian architectures. #!/usr/bin/perl %supportedarchitectures = ( 'i386','i386','m68k','m68k','hppa','hppa','sparc','sparc'); $architecture = shift(@ARGV); $supportedarchitectures{$architecture} || die "Don't know architecture $architecture\n"; %magiccookies = ( 0xCAFEBABE,'cafebabe' ); while ( $filename = shift(@ARGV) ) { if( -f $filename ) { if( open(FILE,$filename) ) { if( 8 == read(FILE,$magictest,8) ) { (@stats)=stat(FILE); $fatuid = $stats[4]; $fatgid = $stats[5]; $fatmode = $stats[2]; $fatatime = $stats[8]; $fatmtime = $stats[9]; close(FILE); if( $magiccookies{unpack('N',$magictest)} ) { print STDERR "File $filename seems to be multiarch.\n"; system 'lipo','-thin',$architecture,'-output',$filename.'.'.$architecture, $filename; if( -f $filename.'.'.$architecture ) { print STDERR "Can't change file date \n" if ! utime $fatatime, $fatmtime, $filename.'.'.$architecture ; print STDERR "Can't change file mods \n" if ! chmod $fatmode, $filename.'.'.$architecture ; print STDERR "Can't change file user \n" if ! chown $fatuid, $fatgid, $filename.'.'.$architecture ; system '/bin/mv', '-f', $filename.'.'.$architecture, $filename; } } } else { print STDERR "Can't read $filename - ignoring file\n"; close(FILE); } } else { print STDERR "Can't open $filename - ignoring file \n"; } } }
From: lynne@lighthouse.com (Lynne Fitzpatrick Angeloro) Newsgroups: comp.sys.next.bugs Subject: BUG in OpenWrite-Response from Lighthouse Design Date: 9 Dec 1996 23:45:22 GMT Organization: Best Internet Communications Message-ID: <58i8ai$dqi@nntp1.best.com> Hi all, Well, here is the definitive on this issue: YES, we have just identified a bug in OpenWrite that can POTENTIALLY delete your home directory. We have finally been able to nail down a specific recipe for repeating this problem and it has just been fixed. We anticipate a new release available to all OpenWrite 2.x users will be available by the middle of next week-check our ftp site ftp://ftp.lighthouse.com some time after Wednesday. In the mean time, here is WHAT *NOT* TO DO: - Do NOT rename chapters after importing them into a book. Rename your file BEFORE importing into the book. Regards, Lynne. -- Lynne Fitzpatrick Angeloro Manager Education & Services Lighthouse Design, Ltd. a Sun Microsystems, Inc. Business 2929 Campus Drive San Mateo, CA 94403-2534
From: Jochen Richter <jr@sade.schiele-ct.de> Newsgroups: comp.sys.next.bugs Subject: Nameserver requests under OS4.1 Date: Tue, 10 Dec 1996 19:13:11 +0100 Organization: S.a.d.e. Message-ID: <32ADA837.1708@sade.schiele-ct.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, after upgrading from NS3.3 to OS4.1 I have the problem that my nameserver that is on a host on the other side of a WAN connection is called all the time, i.e. when opening a shell in Terminal.app, when typing a su command, when opening a database in Tiffany etc. This is very annoying and was never working like that under 3.3. Can it be avoided. Any help very much appreciated. Jochen Richter
Newsgroups: comp.sys.next.bugs Organization: Antigone Press gateway, San Francisco Return-Path: <luomat@nerc.com> Message-ID: <199612101330.IAA09201@nerc.com> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) From: Timothy J Luoma <luomat@nerc.com> Date: Tue, 10 Dec 96 08:29:58 -0500 Subject: Re: Upgrader4.app: Triple-fat installations only? Cc: comp-sys-next-bugs@antigone.com, aisbell@ix.netcom.com Organization: Princeton Theological Seminary Responding To: Patrick Stein <jolly@joker.ppp.cis.uni-muenchen.de> Original Date: 9 Dec 1996 17:32:42 GMT Message-ID: > In prospect of all the people that are now writing scripts to thin > out those binaries, here's one. It should get called like : > find /bin -exec Thinner.perl m68k {} \; > find /NextApps -exec Thinner.perl m68k {} \; > I even used find / -fstype 4.3 -exec Thinner.perl m68k {} \; > It worked on my black hardware - you might have to change the > %magiccookies hash on littleendian architectures. > > > > #!/usr/bin/perl > %supportedarchitectures = ( > 'i386','i386','m68k','m68k','hppa','hppa','sparc','sparc'); There's also i486. I don't know why, but there are two arch types for Intel. Just to make things interesting, I guess. TjL -- Tj Luoma (luomat@peak.org) http://www.next.peak.org/~luomat
From: shess@one.net (Scott Hess) Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: 11 Dec 96 04:38:32 Organization: Is a sign of weakness Message-ID: <SHESS.96Dec11043832@slave.one.net> References: <199612101330.IAA09201@nerc.com> In-reply-to: Timothy J Luoma's message of Tue, 10 Dec 96 08:29:58 -0500 In article <199612101330.IAA09201@nerc.com>, Timothy J Luoma <luomat@nerc.com> writes: There's also i486. I don't know why, but there are two arch types for Intel. Just to make things interesting, I guess. Basically, there is an assembly code used in the byte-swapping macros which causes this to happen. If you don't use them, you get to be i386. If you do use them, you get to be i486, all without any effort on your part. Indeed, the apps I have which ended up i486 were compiled with -arch i386. What's odd is that NeXT even called it i386 in the first place. As far as I know, no version of NeXTSTEP runs on a 386 machine. Perhaps the development versions did, but do we care? :-). Later, -- scott hess <shess@one.net> (606) 578-0412 http://w3.one.net/~shess/ <I plan to become so famous that people buy tapes of me reading source code>
From: Student@gc.maricopa.edu (A. Student) Newsgroups: comp.sys.next.bugs Subject: Re: Nameserver requests under OS4.1 Date: 11 Dec 1996 18:33:36 GMT Organization: Glendale Community College Message-ID: <58muq0$7lh@nntp.dist.maricopa.edu> References: <32ADA837.1708@sade.schiele-ct.de> Mime-Version: 1.0 Hello! In article <32ADA837.1708@sade.schiele-ct.de>, jr@sade.schiele-ct.de says... > >Hi, > >after upgrading from NS3.3 to OS4.1 I have the problem that my >nameserver that is on a host on the other side of a WAN connection is >called all the time, i.e. when opening a shell in Terminal.app, when >typing a su command, when opening a database in Tiffany etc. This is >very annoying and was never working like that under 3.3. Can it be >avoided. >Any help very much appreciated. > >Jochen Richter
Newsgroups: comp.sys.next.bugs,control From: news@news.msfc.nasa.gov Message-ID: <cancel.58nces$f2l@hil-news-svc-5.compuserve.com> Control: cancel <58nces$f2l@hil-news-svc-5.compuserve.com> Subject: cmsg cancel <58nces$f2l@hil-news-svc-5.compuserve.com> no reply ignore Organization: Semi-Automatic Chain Letter Remover Date: Wed, 11 Dec 1996 22:26:36 GMT Sender: invest@goldbergservices.com ignore Make Money Fast post canceled by news@news.msfc.nasa.gov. Make Money Fast has been posted thousands of times, enough to qualify as cancel-on-sight spam. The chain letter scheme it describes is illegal in many countries. For example, see: http://www.usps.gov/websites/depart/inspect/chainlet.htm
Control: cancel <58nc2d$bv1u@usenet1w.prodigy.net> From: Subscribe2@Juno.com Newsgroups: comp.sys.next.bugs Subject: cmsg cancel <58nc2d$bv1u@usenet1w.prodigy.net> Message-ID: <Can_58nc2d$bv1u@usenet1w.prodigy.net> Date: Wed, 11 Dec 96 22:20:03 GMT Cancelled - doesn't fit Prodigy(r) "Terms of Use" Questions to admin@prodigy.com
From: schulhof@aol.com Newsgroups: comp.sys.next.bugs Subject: test Date: Wed, 11 Dec 1996 17:53:02 Message-ID: <58nohq$bap@news1-alterdial.uu.net> this is only a test, john do you see this.
From: lynne@lighthouse.com (Lynne Fitzpatrick Angeloro) Newsgroups: comp.sys.next.bugs Subject: New version of OpenWrite 2.1-8 is now available Date: 12 Dec 1996 04:40:35 GMT Organization: Best Internet Communications Message-ID: <58o2c3$5c3@nntp1.best.com> Hi all, The new version of OpenWrite 2.1-8 is now available from our ftp site: ftp://ftp.lighthouse.com/pub/products/OpenWrite/ This version fixes the "deleting home directory files" bug identified late last week. NOTE: OpenWrite is a LARGE app, and our site is going to be pretty busy for the next week or so, so be patient and try to download late at night if you are having trouble getting connected. Best Regards, Lynne Angeloro -- Lynne Fitzpatrick Angeloro Manager Education & Services Lighthouse Design, Ltd. a Sun Microsystems, Inc. Business 2929 Campus Drive San Mateo, CA 94403-2534
From: Someone <Someone@home.thinking.about.you.com> Newsgroups: comp.sys.next.bugs Subject: Your GOD Loves You - YES YOU! Date: Thu, 12 Dec 1996 02:57:36 PST Organization: GTE Intelligent Network Services, GTE INS Message-ID: <1212199602573684566764825368Someone@home.thinking.about.you.com> I hope that you know your GOD loves you, no matter what GOD you believe in. Thank your GOD for life and ask your GOD to let you live as your GOD would want you to. When we look closely at GOD we begin to realize that we all believe in the same GOD, we may see GOD in different ways, but GOD will always be GOD. There can only be one GOD, and that one GOD loves us all, and wants nothing but the best for us. If your in doubt, just remember GOD works in mysterious ways, there is a reason for everything... God thank you. Someone
Newsgroups: comp.sys.next.bugs From: dsr@lns598.lns.cornell.edu Sender: Someone <Someone@home.thinking.about.you.com> Date: 12 Dec 1996 10:34:11 EST Control: cancel <1212199602573684566764825368Someone@home.thinking.about.you.com> Subject: cmsg cancel <1212199602573684566764825368Someone@home.thinking.about.you.com> no reply ignore Message-ID: <cancel.1212199602573684566764825368Someone@home.thinking.about.you.com> Spam cancelled by dsr@lns598.lns.cornell.edu original subject was Your GOD Loves You - YES YOU!
Message-ID: <32B1D641.25A1@nmaa.org> Date: Fri, 13 Dec 1996 14:18:41 -0800 From: Daniel Fahey <dansources@nmaa.org> Organization: DanSources Technical Services Inc. MIME-Version: 1.0 Newsgroups: comp.sys.next.bugs,comp.sys.next.hardware,comp.sys.next.marketplace,comp.sys.next.misc,comp.sys.next.programmer,comp.sys.next.advocacy,comp.sys.next.,announce,comp.sys.next.software,comp.sys.next.sysadmin,comp.soft-sys.nextstep,comp.lang.objective-c Subject: Corba and Next Developers Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit HELLO CORBA and NEXT Developers: We are seeking a bunch of contract C++, Corba, Object Oriented and OpenStep Developers for a large and long telecommunications program located in the Washington, DC. area. Our client is developing most of their systems in OpenStep and merging the legacy systems with C++ and CORBA compliance. There are Senior to Junior Developer positions with as little as one year NEXT or CORBA experience. Training is available for those who need to upgrade to OpenStep. If you are interested, please email your resume. The best way to send is to Attach as a Word or Wordperfect file, or just Paste it to the Email. If your know any friends please pass this information to them. We have a excellent team of people and the customer is cool to work with. This project is hot and we need good people. Thank you for your time and patience. Sincerely, Dan Fahey
From: mpaque@wco.com (Mike Paquette) Newsgroups: comp.sys.next.bugs Subject: Re: Upgrader4.app: Triple-fat installations only? Date: Fri, 13 Dec 1996 19:26:31 GMT Organization: Electronics Service, Unit No. 16 Message-ID: <58sali$7e5@news.wco.com> References: <199612101330.IAA09201@nerc.com> Timothy J Luoma <luomat@nerc.com> wrote: >Responding To: Patrick Stein <jolly@joker.ppp.cis.uni-muenchen.de> [munch] >> #!/usr/bin/perl >> %supportedarchitectures = ( >> 'i386','i386','m68k','m68k','hppa','hppa','sparc','sparc'); >There's also i486. I don't know why, but there are two arch types >for Intel. >Just to make things interesting, I guess. That's the assembler and linker being clever. When assembling code for a particular architecture, by default the assembler tags the object file with the lowest processor in it's list that supports the opcodes in that file. If a module uses nothign but i386 opcodes, it's tagged for the i386. If a module uses a 486 opcode, then it gets tagged for the i486. The linker tags it's output to be the most restrictive type found among it's input files. The kernel's exec code checks the tags in the Mach-O header to make sure that an executable will run on the processor. None of this is much of a problem on the Intel platforms, where the 486 and it's instruction set are the minimum for NEXTSTEP. It actually is a problem for a few programmers on the m68k machines. If a program uses an opcode like MOVE16, then the program is tagged as 68040 specific, and won't run on 68030 machines. Programmers have worked around this by checking the processor type before using the 68040 opcodes (typically checked at startup, diddling 68040 function pointers as needed.) and marking the program type as 68030, so it still runs on older cubes. Mike Paquette -- I don't speak for my employer, and they don't speak for me. mpaque@wco.com mpaque@next.com NeXT business mail only, please
From: doyle@aps.org (Mark Doyle) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.programmer Subject: cmsg cancel <58na0n$fon@sun20.ccd.bnl.gov> Control: cancel <58na0n$fon@sun20.ccd.bnl.gov> Date: 11 Dec 1996 21:47:15 GMT Organization: Brookhaven National Laboratory Message-ID: <58na53$fon@sun20.ccd.bnl.gov> cancel
From: doyle@aps.org (Mark Doyle) Newsgroups: comp.sys.next.sysadmin,comp.sys.next.bugs,comp.sys.next.programmer Subject: cmsg cancel <58na0n$fon@sun20.ccd.bnl.gov> Control: cancel <58na0n$fon@sun20.ccd.bnl.gov> Date: 11 Dec 1996 21:47:23 GMT Organization: Brookhaven National Laboratory Message-ID: <58na5b$fon@sun20.ccd.bnl.gov> cancel
From: Ones-And-Zeros@Prodigy.net Newsgroups: comp.sys.next.bugs Subject: ! MASS POST Was Here (rhpgsj) Date: Sat, 14 Dec 96 12:31:39 GMT Organization: Ones And Zeros, Corp. Message-ID: <58u6nc$7a1m@usenet1w.prodigy.net> MASS POST, by Ones And Zeros, will let you post to as many newsgroups as you want! To find out more about this exciting new program, visit a business newsgroup. (This ad was sent to thousands of newsgroups!) (veadqs)
From: Ones-And-Zeros@Prodigy.net Newsgroups: comp.sys.next.bugs Organization: Ones And Zeros, Corp. Message-ID: <cancel.58u6nc$7a1m@usenet1w.prodigy.net> Control: cancel <58u6nc$7a1m@usenet1w.prodigy.net> Subject: cmsg cancel <58u6nc$7a1m@usenet1w.prodigy.net> Date: 14 Dec 1996 19:52:59 GMT Spam deleted
Control: cancel <58u6nc$7a1m@usenet1w.prodigy.net> From: Ones-And-Zeros@Prodigy.net Newsgroups: comp.sys.next.bugs Subject: cmsg cancel <58u6nc$7a1m@usenet1w.prodigy.net> Message-ID: <Can_58u6nc$7a1m@usenet1w.prodigy.net> Date: Sat, 14 Dec 96 12:31:39 GMT Commercial SPAM Questions to news@prodigy.com
Newsgroups: comp.sys.next.bugs From: tomi@shinto.nbg.sub.org (Thomas Engel) Subject: OPENSTEP 4.0 color handling broken ? Message-ID: <E2I6Ls.8x@shinto.nbg.sub.org> Sender: news@shinto.nbg.sub.org Organization: STEPeople's home (A NUGI member) Date: Mon, 16 Dec 1996 11:01:03 GMT Hi, I am a little puzzled about 4.0's colorhandling. Someone reported that under 8Bit the colors look different then in 3.3 days which I can't comment upon... BUT what I just realized is that there must be another mystery in 4.0 even when running of 32Bit hardware (NeXTdimension). I opened an RTFD file in Edit (3.3app) and TextEdit (4.0app) and suddenly realized that the same image looked completely!! different within the 4.0 app. Now opening the EPS image inside Preview (3.3app) and Draw (4.0app) cause exactly the same results. But not all images look really different...only the blueish EPS image..not the yellowish TIFF image. I can not imagine that the DPS engine is causing the trouble since 3.3 and 4.0 apps should work through the same DPS. So all I can figure is that some part of the new NSEPSImageRep handling is buggy. This puts another aspect on using 4.0 with 4.0 app for publishing. Currently it only affects Stone Designs Create 4.0 since no other publishing tools seem to have been ported on top of the Openstep frameworks...sadly this bug makes it impossible for Create 4.0 users to guarantee that the on screen colors are correct. Comments ? Aloha Tomi
Newsgroups: comp.sys.next.bugs,control From: news@news.msfc.nasa.gov Message-ID: <cancel.594c1b$ebj@oolong.memphis.edu> Control: cancel <594c1b$ebj@oolong.memphis.edu> Subject: cmsg cancel <594c1b$ebj@oolong.memphis.edu> no reply ignore Organization: Semi-Automatic Chain Letter Remover Date: Mon, 16 Dec 1996 21:10:32 GMT Sender: InfiNet ignore Make Money Fast post canceled by news@news.msfc.nasa.gov. Make Money Fast has been posted thousands of times, enough to qualify as cancel-on-sight spam. The chain letter scheme it describes is illegal in many countries. For example, see: http://www.usps.gov/websites/depart/inspect/chainlet.htm
From: mkienenb@arsc.edu (Mike Kienenberger) Newsgroups: comp.sys.next.bugs Subject: long filenames crash file matching code in csh Date: 16 Dec 1996 21:55:49 GMT Organization: Arctic Region Supercomputing Center Message-ID: <594gh5$70b@news.alaska.edu> FYI: Hardware Configuration: Processor: SPARC (Generic) Primary memory: 32.00 MB Hostname: ice Software Version 3.3risc (Rose2L) Having a long filename crashes the csh with "Floating exception" when you use control-d to print a list of matching files. Here's an example (as root, but the same problem occurred using non-root accounts). After I deleted the file "ftp:__ftp.nmr.embl-heidelberg.de_pub_next_Images_People_tomi.shinto.nbg.sub. org.tiff", the problem no longer occurred. ice:1# ls -l /tmp lrwxrwxrwx 1 root 11 Feb 15 1995 /tmp -> private/tmp@ ice:2# ls -lt /private/tmp total 453 -rw------- 1 mkienenb 2518 Dec 16 11:59 console.log drwx------ 2 mkienenb 1024 Dec 16 11:38 mkienenb/ -rw-r--r-- 1 mkienenb 0 Dec 16 11:23 ftp:__ftp.nmr.embl-heidelberg.de_pub_next_Images_People_tuparev.koala.tiff -rw-r--r-- 1 mkienenb 1198 Dec 16 10:51 http:__www.nerc.com_~luomat_Timothy_J_Luoma-X-Face.tiff -rw-r--r-- 1 mkienenb 0 Dec 16 10:48 ftp:__ftp.nmr.embl-heidelberg.de_pub_next_Images_People_tomi.shinto.nbg.sub.o rg.tiff drwxr-xr-x 2 mkienenb 1024 Dec 16 05:45 TickleServices/ -rw-r--r-- 1 root 15896 Dec 16 00:54 log_mg.ttydfa drwxr-xr-x 3 mkienenb 1024 Dec 13 17:53 O_Alexandra.0.82.NIHS_bs/ drwxr-xr-x 3 mkienenb 1024 Dec 13 16:00 O_topv0.3.NIHS_bs/ -rw-r--r-- 1 mkienenb 419976 Dec 13 15:29 O_ls-lR -rw-r--r-- 1 mkienenb 1754 Dec 13 15:21 OpenWrite.2.1.8.README drwxr-xr-x 3 mkienenb 1024 Dec 13 11:55 O_Relnotes_961213/ -r--r--r-- 1 mkienenb 0 Dec 13 11:23 .reallyignorethis.term drwxrwxrwx 2 mkienenb 1024 Dec 13 10:51 .X11-unix/ ice:3# ls -l /tmp/<CONTROL-D> Floating exception --- Mike Kienenberger Arctic Region Supercomputing Center Systems Analyst (907) 474-6842 mkienenb@arsc.edu http://www.arsc.edu
Newsgroups: comp.sys.next.bugs From: tom@icgned.nl (Tom Hageman) Subject: Re: OPENSTEP 4.0 color handling broken ? Message-ID: <E2KALn.9uy@icgned.nl> Sender: news@icgned.nl Organization: IC Group References: <E2I6Ls.8x@shinto.nbg.sub.org> Date: Tue, 17 Dec 1996 14:22:35 GMT tomi@shinto.nbg.sub.org (Thomas Engel) wrote: >I am a little puzzled about 4.0's colorhandling. > >Someone reported that under 8Bit the colors look different then in 3.3 days >which I can't comment upon... > >BUT what I just realized is that there must be another mystery in 4.0 even >when running of 32Bit hardware (NeXTdimension). > > >I opened an RTFD file in Edit (3.3app) and TextEdit (4.0app) and suddenly >realized that the same image looked completely!! different within the 4.0 >app. > >Now opening the EPS image inside Preview (3.3app) and Draw (4.0app) cause >exactly the same results. > >But not all images look really different...only the blueish EPS image..not >the yellowish TIFF image. [...] >Comments ? From the 4.x AppKit release notes: "The default NSCMYKAdjust is now YES by default. This basically enables the WindowServer's ability to use an enhanced algorithm for rendering device-dependent CMYK colors on an RGB device, resulting in a greater accuracy in the on-screen appearance of CMYK colors. Applications can turn this off by registering this default with a NO value at startup time." (The corresponding 3.x default NXCMYKAdjust is NO by default. Hence the apparent difference in behaviour between 3.x and 4.x apps.) Hope this helps, Tom. -- __/__/__/__/ Tom Hageman <tom@basil.icce.rug.nl> [NeXTmail/Mime OK] __/ __/_/ IC Group <tom@icgned.nl> (work) __/__/__/ "Ed is the standard text editor" __/ _/_/ -- Unix Programmer's Manual
From: jrudd@cygnus.com (John Rudd) Newsgroups: comp.sys.next.bugs Subject: Re: OPENSTEP 4.0 color handling broken ? Date: 17 Dec 1996 18:19:53 GMT Organization: Cygnus Support Message-ID: <596o89$gpk@majipoor.cygnus.com> References: <E2I6Ls.8x@shinto.nbg.sub.org> <E2KALn.9uy@icgned.nl> Cc: tom@icgned.nl In <E2KALn.9uy@icgned.nl> Tom Hageman wrote: > tomi@shinto.nbg.sub.org (Thomas Engel) wrote: > >I am a little puzzled about 4.0's colorhandling. > > > >Someone reported that under 8Bit the colors look different then in 3.3 days > >which I can't comment upon... > > > >BUT what I just realized is that there must be another mystery in 4.0 even > >when running of 32Bit hardware (NeXTdimension). > > > > > >I opened an RTFD file in Edit (3.3app) and TextEdit (4.0app) and suddenly > >realized that the same image looked completely!! different within the 4.0 > >app. > > > >Now opening the EPS image inside Preview (3.3app) and Draw (4.0app) cause > >exactly the same results. > > > >But not all images look really different...only the blueish EPS image..not > >the yellowish TIFF image. > [...] > >Comments ? > > From the 4.x AppKit release notes: > > "The default NSCMYKAdjust is now YES by default. This basically enables the > WindowServer's ability to use an enhanced algorithm for rendering > device-dependent CMYK colors on an RGB device, resulting in a greater > accuracy in the on-screen appearance of CMYK colors. > > Applications can turn this off by registering this default with a NO value > at startup time." > > (The corresponding 3.x default NXCMYKAdjust is NO by default. Hence the > apparent difference in behaviour between 3.x and 4.x apps.) > > Hope this helps, > Tom. > > Is there any way that we, as users, can turn it off? -- John "kzin" Rudd jrudd@cygnus.com (ex- kzin@email.sjsu.edu) =========Intel: Putting the backward in backward compatible.============ Spammers: I charge you for my time, disk, and bandwidth if you post off- topic solicitations for money in the groups I read. $500/post/group.
From: sef@kithrup.com Newsgroups: comp.sys.next.bugs Subject: cmsg cancel <597opd$k94@crawler.dlc.fi> Date: 18 Dec 1996 04:56:48 GMT Control: cancel <597opd$k94@crawler.dlc.fi> Message-ID: <cancel.597opd$k94@crawler.dlc.fi> Sender: jorge@mailloop.com Spam cancelled by sef@kithrup.com
Newsgroups: comp.sys.next.bugs Organization: Antigone Press gateway, San Francisco Return-Path: <luomat@nerc.com> Message-ID: <199612171526.KAA02913@nerc.com> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) In-Reply-To: cbce108ffaaa098848bf9ae1539c4823 - From: Timothy J Luoma <luomat@nerc.com> Date: Tue, 17 Dec 96 10:26:16 -0500 Subject: Re: long filenames crash file matching code in csh Cc: comp-sys-next-bugs@antigone.com References: cbce108ffaaa098848bf9ae1539c4823 - Organization: Princeton Theological Seminary Responding To: mkienenb@arsc.edu (Mike Kienenberger) Original Date: 16 Dec 1996 21:55:49 GMT > Having a long filename crashes the csh with "Floating exception" > when you use control-d to print a list of matching files. If you have 3.3, now would be a good time to learn ZSH, which is already installed, and which does not have any such silly little bugs. There are some bugs, to be sure, but they are not something the average user would normally come across, in my experience TjL ps -- hey, that's my X-Face in your /tmp ;-) -- Tj Luoma (luomat@peak.org) / http://www.next.peak.org/~luomat *** I will be out of town from Dec 19th - Dec 31st ***
Newsgroups: comp.sys.next.bugs From: tom@icgned.nl (Tom Hageman) Subject: Re: OPENSTEP 4.0 color handling broken ? (No, it's a feature...) Message-ID: <E2LqJ7.ECx@icgned.nl> Sender: news@icgned.nl Organization: IC Group References: <E2I6Ls.8x@shinto.nbg.sub.org> <E2KALn.9uy@icgned.nl> <596o89$gpk@majipoor.cygnus.com> Date: Wed, 18 Dec 1996 09:04:19 GMT jrudd@cygnus.com (John Rudd) wrote: >In <E2KALn.9uy@icgned.nl> Tom Hageman wrote: >> From the 4.x AppKit release notes: >> >> "The default NSCMYKAdjust is now YES by default. This basically enables the >> WindowServer's ability to use an enhanced algorithm for rendering >> device-dependent CMYK colors on an RGB device, resulting in a greater >> accuracy in the on-screen appearance of CMYK colors. >> >> Applications can turn this off by registering this default with a NO value >> at startup time." >> >> (The corresponding 3.x default NXCMYKAdjust is NO by default. Hence the >> apparent difference in behaviour between 3.x and 4.x apps.) >> >> Hope this helps, >> Tom. >> >> > >Is there any way that we, as users, can turn it off? Of course :-) defaults write NSGlobalDomain NSCMYKAdjust NO to turn it off for all OS4.x applications, or defaults write <appName> NSCMYKAdjust NO to turn it off for individual apps. RTFM defaults. -- __/__/__/__/ Tom Hageman <tom@basil.icce.rug.nl> [NeXTmail/Mime OK] __/ __/_/ IC Group <tom@icgned.nl> (work) __/__/__/ "Ed is the standard text editor" __/ _/_/ -- Unix Programmer's Manual
Newsgroups: comp.sys.next.programmer,comp.sys.next.software,comp.sys.next.bugs From: js@euler.han.de (Juergen Sell) Subject: Paper Sizes hardcoded - where? Message-ID: <E2M9LI.ALs@euler.han.de> Sender: js@euler.han.de (Juergen Sell) Organization: Ink Unknown Date: Wed, 18 Dec 1996 15:56:06 GMT Hi, sorry for the crossposting but this has bothered me again and again. Besides Next knows about it and seems to have known for some releases but has failed to porvide a bugfix. During my efforts to create PS output in the size of A0 or larger I stumbled across a dumb hardcoded limit (in the previewer (only?)). It cannot display documents somewhat larger than A3 but for such docs displays only the lower left (or right?) fraction. Since I will not use some of the doc sizes supported (all US sizes for me) I'd like to change their definition to represent the desired A0 and A00 sizes I need. Now I wonder where this is hardcoded? Initially I suspected the postscript package - either it is not there or I was not able to find it. So maybe it is somewhere in one of those shlibs? Since I do not even know in what unit (cm or Point or ?) the various sizes are stored internally it is most difficult to search for a representation of implicit doc sizes. Another thing that comes to mind: Using cm as unit, the print layout panel displays some round-off errors, second - the print layout panel 'knows' supported sizes. So it is either stored in the corresponding shlib or the code loads it dynamically? Any insights most welcome. Having DPS as a native windowing system _and_ a hardcoded limitation in formatsize has been annoying, to say the least. Thanks, Juergen --- AnsweringMachine +49 511 92455-50 Fon -51 Fax -52 NeXTMail welcome = What time do we live in when revolution reminds us of soap powder, = when spontaneity and freedom get associated with instant coffee, = when a politician's idea of social change is changing names = when a country posing as super know-how factory cuts expenses on education?
Newsgroups: comp.sys.next.bugs From: tomi@shinto.nbg.sub.org (Thomas Engel) Subject: Re: OPENSTEP 4.0 color handling broken ? Message-ID: <E2MMI3.CF@shinto.nbg.sub.org> Sender: news@shinto.nbg.sub.org Organization: STEPeople's home (A NUGI member) References: <E2I6Ls.8x@shinto.nbg.sub.org> <E2KALn.9uy@icgned.nl> Date: Wed, 18 Dec 1996 20:34:50 GMT tom@icgned.nl (Tom Hageman) wrote: > tomi@shinto.nbg.sub.org (Thomas Engel) wrote: > From the 4.x AppKit release notes: > > "The default NSCMYKAdjust is now YES by default. This basically enables the > WindowServer's ability to use an enhanced algorithm for rendering > device-dependent CMYK colors on an RGB device, resulting in a greater > accuracy in the on-screen appearance of CMYK colors. > > Applications can turn this off by registering this default with a NO value > at startup time." > > (The corresponding 3.x default NXCMYKAdjust is NO by default. Hence the > apparent difference in behaviour between 3.x and 4.x apps.) Yes this is exactly the solution. Thanx. Oddly my EPS image really had CMYK colors even though I can't understand why I used CMYK for this partikular silly image...hmm. I remember reading the NXCMYKAdjust note in the release notes but I was not aware of the "huge" differences this would cause. Is there any mayor drawback of having CMYK adjust turned on ??? There might be a performance penalty but IMHO the release notes should make it more clear. Now I have set the GLOBALs NXCMYKAdjust in the 3.3 database to YES and things are perfectly fine. Sorry NeXT engineering...wasn't your bug. Aloha Tomi P.S. Andy and others pointed me to the AppKit fix for 4.0 with 3.33 EPS import...but that was not part of this problem.
From: Thomas.Tschannen@ivi.admin.ch Newsgroups: comp.sys.next.bugs Subject: Mail.app, forwarded MIME Mails get small Fonts Date: 19 Dec 1996 14:28:33 GMT Organization: BFI, Bern (Switzerland) Message-ID: <59bjeh$2a7@fwsrva.bfi.admin.ch> Keywords: mail mime font Some (not all) of our users have this problem: If they forward a MIME encoded mail the forwarded mail will have fonts of a smaller size than the original mail. Here is part of the original mail: You wrote: <bigger><bigger>K=F6nnen Sie=20 </bigger></bigger><smaller>diese </smaller><bigger><bigger> mail an=20 <bigger>tt weiterleiten </bigger></bigger></bigger> ? and here part of the forwarded mail: <smaller><smaller>You wrote: </smaller></smaller>K=F6nnen Sie=20 <smaller><smaller><smaller>diese </smaller></smaller></smaller> mail an=20 <bigger>tt weiterleiten </bigger><smaller><smaller> ? Is there a solution to this problem ? We're running NeXTSTEP 3.3 and Mail.app 3.3e (v118.2(e1.3)) Thank you very much for your help, Thomas
From: mpaque@wco.com (Mike Paquette) Newsgroups: comp.sys.next.bugs Subject: Re: OPENSTEP 4.0 color handling broken ? Date: Sat, 21 Dec 1996 21:30:36 GMT Organization: Electronics Service, Unit No. 16 Message-ID: <59hksc$85n@news.wco.com> References: <E2I6Ls.8x@shinto.nbg.sub.org> <E2KALn.9uy@icgned.nl> <E2MMI3.CF@shinto.nbg.sub.org> tomi@shinto.nbg.sub.org (Thomas Engel) wrote: >Yes this is exactly the solution. Thanx. Oddly my EPS image really had CMYK >colors even though I can't understand why I used CMYK for this partikular >silly image...hmm. >I remember reading the NXCMYKAdjust note in the release notes but I was not >aware of the "huge" differences this would cause. One interesting thing to try is to examine a pure cyan swatch with the CMYK adjust on and off. It really looks much better with it on. >Is there any mayor drawback of having CMYK adjust turned on ??? There might >be a performance penalty but IMHO the release notes should make it more >clear. Not really. The WindowServer is smart about caching recently used color conversions. Process artwork using CMYK typically has a small number of colors re-used in a number of places. >Now I have set the GLOBALs NXCMYKAdjust in the 3.3 database to YES and things >are perfectly fine. Sorry NeXT engineering...wasn't your bug. Kewl... Mike Paquette -- I don't speak for my employer, whoever it is, and they don't speak for me. mpaque@wco.com mpaque@next.com NeXT business mail only, please
From: InfiNet Newsgroups: comp.sys.next.bugs Subject: important--you must read this! Date: Mon, 16 Dec 1996 22:38:50 GMT Organization: The University of Memphis Message-ID: <594c1b$ebj@oolong.memphis.edu> Take five minutes to read this and it WILL change your life. The Internet has grown tremendously. It doubles in size every 4 months. think about it. You see those 'Make.Money.Fast' posts more and more. That's ... because it WORKS! So I thought, all those new users might make it work. And I decided to try it out, a few months ago. Besides, whats $5.00, I spend more than that in the morning on my way to work on coffee and cigs for the day. So I sent in my money and posted. Everyone was calling it a scam, but there are SO many new users from AOL, Netcom, etc. they will join in and make it work for you. Well, two weeks later, I began recieving bucks in the mail! I couldn't believe it! Not just a little, I mean big bucks! At first only a few hundred dollars, then a week later, a couple of thousand, then BOOM. By the end of the fourth week, I had recieved nearly $47,000.00. It came from all over the world. And every bit of it perfectly legal and on the up and up. I've been able to pay off all my bills and still had enough left over for a nice vacation for me and my family. Not only does it work for me, it works for other folks as well. Markus Valppu says he made $57,883 in four weeks. Dave Manning claims he made $53,664 in the same amount of time. Dan Shepstone says it was only $17,000 for him. Do I know these folks? No, but when I read how they say they did it, it made sense to me. Enough sense that I'm taking a similar chance with $5 of my own bucks. Not a big chance, I admit--but one with incredible potential, because $5 is all anyone ever invests in this system. Period. That's all Markus, Dave, or Dan invested, yet their $5 netted them tens of thousands of dollars each, in a safe, legal, completely legitimate way. Here's how it works in 3 easy steps: STEP 1. Invest your $5 by writing your name and address on five seperate piecesof paper along with the words: "PLEASE ADD ME TO YOUR MAILING LIST." (In this way, you're not just sending a dollar to someone; you're paying for a legitimate service.) Fold a $1 bill, money order, or bank note inside each paper, and mail them by standard U. S. Mail to the following five addresses: 1- Natalie Jansen Lancveldlaan 18 5671 CN Nuenen Holland 2- Victor Chen 2021 Hearst Ave Berkeley, CA. 94709 3- Steve Boltinghouse 1009 Bird St. Hannibal, MO 63401 4- Sean T. Stevenson 14933 Blackwood Lane White Rock, BC CANADA V4B 2A8 5- B. Bradley 284 Deloach Memphis, TN 38111 USA STEP 2. Now remove the top name from the list, and move the other names up.This way, #5 becomes #4 and so on. Put your name in as the fifth one on the list. STEP 3. Post the article to at least 250 newsgroups. There are at least 19000 newsgroups at any given moment in time. Try posting to as many newsgroups as you can. Remember the more groups you post to, the more people will see your article and send you cash! STEP 4. You are now in business for yourself, and should start seeing returns within 7 to 14 days! Remember, the Internet is new and huge. There is no way you can lose. Now here is how and why this system works: Out of every block of 250 posts I made, I got back 5 responses. Yes, thats right,only 5. You make $5.00 in cash, not checks or money orders, but real cash with your name at #5. Each additional person who sent you $1.00 now also makes 250 additional postings with your name at #4, 1000 postings. On average then, 50 people will send you $1.00 with your name at #4,....$50.00 in your pocket! Now these 50 new people will make 250 postings each with your name at #3 or 10,000 postings. Average return, 500 people= $500. They make 250 postings each with your name at #2= 100,000 postings=5000 returns at $1.00 each=$5,000.00 in cash! Finally, 5,000 people make 250 postings each with your name at #1 and you get a return of $60,000 before your name drops off the list.And that's only if everyone down the line makes only 250 postings each! Your total income for this one cycle is $55,000. From time to time when you see your name is no longer on the list, you take the latest posting you can find and start all over again. The end result depends on you. You must follow through and repost this article everywhere you can think of. The more postings you make, the more cash ends up in your mailbox. It's too easy and too cheap to pass up!!! So thats it. Pretty simple sounding stuff, huh? But believe me, it works. There are millions of people surfing the net every day, all day, all over the world. And 100,000 new people get on the net every day. You know that, you've seen the stories in the paper. So, my friend, read and follow the simple instructions and play fair. Thats the key, and thats all there is to it. Print this out right now so you can refer back to this article easily. Try to keep an eye on all the postings you made to make sure everyone is playing fairly. You know where your name should be. If you're really not sure or still think this can't be for real, then don't do it. But please print this article and pass it along to someone you know who really needs the bucks, and see what happens. REMEMBER....HONESTY IS THE BEST POLICY.YOU DON'T NEED TO CHEAT THE BASIC IDEA TO MAKE THE BUCKS! GOOD LUCK TO ALL, AND PLEASE PLAY FAIR AND YOU WILL WIN AND MAKE SOME REAL INSTANT FREE CASH! *** By the way, if you try to deceive people by posting the messages with your name in the list and not sending the bucks to the people already included, you will not get much. I know someone who did this and only got about $150 (and that's after two months). Then he sent the 5 bills, people added him to their lists, and in 4-5 weeks he had over $10,000! TRY IT AND YOU'LL BE HAPPY !!!!!!!!!!
From: Qoute-A-Day@juno.com Newsgroups: comp.sys.next.bugs Subject: Good Quotes (bluNpY) Date: Sat, 28 Dec 96 01:27:44 GMT Organization: Qoute A Day Message-ID: <5a1t3t$11di@useneta1.news.prodigy.com> Every day, we at Quote-A-Day e-mail an interesting quote to people on the Internet. The quotes are inspirational, witty and insightful. We don’t charge for this service and we hope you’ll want to be a part of it. If you would like to join our mailing, send e-mail to Subscribe2@Juno.com And put your name in the body of the message. Later, if you like, you can stop receiving this mailing by sending e-mail to Unsubscribe2@Juno.com (bluNpY)
Control: cancel <5a1t3t$11di@useneta1.news.prodigy.com> From: Qoute-A-Day@juno.com Newsgroups: comp.sys.next.bugs Subject: cmsg cancel <5a1t3t$11di@useneta1.news.prodigy.com> Message-ID: <Can_5a1t3t$11di@useneta1.news.prodigy.com> Date: Sat, 28 Dec 96 01:27:44 GMT Cancelled - doesn't fit Prodigy(r) "Terms of Use" Questions to admin@prodigy.com
From: root@bytewarecafe.com Newsgroups: comp.sys.next.bugs Subject: 32meg 70ns 72pin EDO simm for $140 Date: 31 Dec 1996 20:41:48 GMT Organization: bytewarecafe.com Message-ID: <5abtqc$82f@newman.pcisys.net> We are a new site on the internet and we can supply your hardware needs. As a promotion to get our name out to you, we are running a special promotion on 32Meg simms. For a very limited time, we are selling 32Meg/70ns EDO simms for just 140+shipping and handling, delivered to your door within 2-3 days. Just go to our site www.bytewarecafe.com and fill out the necessary information about yourself and your credit card information. Goto the products list and choose the memory item. From here, select the memory you want and click on the invoice button to see your total charges. If you wish to browse the other hardware categories, feel free to browse for as long as you wish. If you wish to buy anything else, just select that item from that category. If you are satisfied with your selection(s) and your personal information is correct, click on the submit order button. The bytewarecafe.com server will respond with an order number and a time stamp. You will need these two numbers for any future correspondences with bytewarecafe.com Your order will be prepared and delivered to your door within 2-3 days. Thank you.
From: root@bytewarecafe.com Newsgroups: comp.sys.next.bugs Subject: 32meg 70ns 72pin EDO simm for $140 Date: 31 Dec 1996 20:41:49 GMT Organization: bytewarecafe.com Message-ID: <5abtqd$82f@newman.pcisys.net> We are a new site on the internet and we can supply your hardware needs. As a promotion to get our name out to you, we are running a special promotion on 32Meg simms. For a very limited time, we are selling 32Meg/70ns EDO simms for just 140+shipping and handling, delivered to your door within 2-3 days. Just go to our site www.bytewarecafe.com and fill out the necessary information about yourself and your credit card information. Goto the products list and choose the memory item. From here, select the memory you want and click on the invoice button to see your total charges. If you wish to browse the other hardware categories, feel free to browse for as long as you wish. If you wish to buy anything else, just select that item from that category. If you are satisfied with your selection(s) and your personal information is correct, click on the submit order button. The bytewarecafe.com server will respond with an order number and a time stamp. You will need these two numbers for any future correspondences with bytewarecafe.com Your order will be prepared and delivered to your door within 2-3 days. Thank you.
These are the contents of the former NiCE NeXT User Group NeXTSTEP/OpenStep software archive, currently hosted by Marcel Waldvogel and Netfuture.ch.