robespierre wrote:
magnet for dreamers and crackpots.
this.
_________________
The collected works of kjaer - Page 3
this.
_________________
You're not "forced" to do anything. If the state of the computer industry annoys you that much, either learn to love it or find something else to do. I hear art majors get a lot of arse. Maybe you could try that for a while.
_________________
The only thing you can do when the battery has gone flat and you get the 161 error, is to boot the reference diskette and get the CMOS settings set, or go into BASIC. It doesn't matter if you have an OS on the hard drive or not. It will never be looked at, because until the settings are set the computer doesn't even know it has a hard drive.
_________________
IBM does not publish benchmark results.
duck wrote:
it seems that IRIX' traceroute uses ICMP packets instead of the traditional UDP
Since when has anything but ICMP been "traditional" for traceroute?!
_________________
you're right, I got confused about where the TTL field that traceroute needs to work actually comes from.
_________________
Got some brochures and a FAQ from a DroidWorks 4/85 press kit up on the site. Not super info-dense, and not SGI-related, but cool anyway; these systems were driven by early Suns. On the basis of the high-res color SunView display shown in the EditDroid brochure, I think it must have been a VME Sun-2, rather than a Multibus one (the earlier models were supposedly driven by 100Us) since the only multibus color framebuffer for Sun (the cgone) has a display area of only 640x480 pixels (the framebuffer itself is 640x512).
Was there an earlier computerized editing suite for film or video?
http://www.typewritten.org/Articles/#DroidWorks
Was there an earlier computerized editing suite for film or video?
http://www.typewritten.org/Articles/#DroidWorks
Judging by my installation, it's about
1. 373 MB resources (203 MB in lens profiles, 147 MB in camera profiles, a handful of localization, and 234 PNG files that aren't even as big as one HFS+ block, which contain UI elements),
2. 230 MB plugins (23 reasonably sized ones to do things like Location, Facebook, Email, Flickr, Web export, crash reporting, and tether mode for Canon, Leica, and Nikon cameras, plus a 190 MB "layout toolkit", whatever that is -- looks like maybe for arranging hardcopy output), and
3. 330 MB "Support" (the most dubious of the three -- 193 MB of "DynamicLinkMediaServer" (wtf), 75 MB "TypeSupport", and a handful of other smaller... supports).
Plus ~90 MB in frameworks (52 at an average size of about 1.5 MB each). Camera Raw looks the biggest (perhaps because there are so many variations) at 16 MB.
In the old days, this would have been sixteen or twenty totally separate programs, from several different companies. Leica would have had their own program to deal with its camera raw format, that wouldn't have worked with or the same as Canon's or Nikon's equivalent, and if I wanted to switch from Nikon to Canon (or vice versa) I would have had to throw away a lot of software as well. I don't long for those days, because I have work to do. There's a lot of shit to support to be "modern". Be found this out the hard way, and never even got much past the halfway mark.
1. 373 MB resources (203 MB in lens profiles, 147 MB in camera profiles, a handful of localization, and 234 PNG files that aren't even as big as one HFS+ block, which contain UI elements),
2. 230 MB plugins (23 reasonably sized ones to do things like Location, Facebook, Email, Flickr, Web export, crash reporting, and tether mode for Canon, Leica, and Nikon cameras, plus a 190 MB "layout toolkit", whatever that is -- looks like maybe for arranging hardcopy output), and
3. 330 MB "Support" (the most dubious of the three -- 193 MB of "DynamicLinkMediaServer" (wtf), 75 MB "TypeSupport", and a handful of other smaller... supports).
Plus ~90 MB in frameworks (52 at an average size of about 1.5 MB each). Camera Raw looks the biggest (perhaps because there are so many variations) at 16 MB.
In the old days, this would have been sixteen or twenty totally separate programs, from several different companies. Leica would have had their own program to deal with its camera raw format, that wouldn't have worked with or the same as Canon's or Nikon's equivalent, and if I wanted to switch from Nikon to Canon (or vice versa) I would have had to throw away a lot of software as well. I don't long for those days, because I have work to do. There's a lot of shit to support to be "modern". Be found this out the hard way, and never even got much past the halfway mark.
_________________
icecubecheddarmilk wrote:
Howdy
I recently acquired an old R5k O2, and it suffers from the famous thrown gear problem in the CD drive unit. I've pulled apart the machine and I have the CD drive and the little white gear, but I can't figure out where it actually goes in the mechanism. I've searched the forums but the posts I came across didn't tell me where it should be. Can someone please help me? I'll take a couple of photos if that helps.
I recently acquired an old R5k O2, and it suffers from the famous thrown gear problem in the CD drive unit. I've pulled apart the machine and I have the CD drive and the little white gear, but I can't figure out where it actually goes in the mechanism. I've searched the forums but the posts I came across didn't tell me where it should be. Can someone please help me? I'll take a couple of photos if that helps.
if it's the pinion I'm thinking of, it's press-fit over the tray motor spindle.
If it's come off because it's split, putting it back on is likely insufficient to restore the drive to operation.
_________________
I don't think Warp 4 includes a power-off on shutdown. It just does exactly what you observe.
Would that be the x86 1400 or the m68k 1400? If the latter I will fly to Germany and
swim
home with it if I have to.
_________________
Nobody was asking for this, but since I have been playing around with it recently, I ran this benchmark (maybe we should call it the "dhumbstone"?) in a Lisp Listener on my TI microExplorer. It scored 37 seconds, for n=50000. I don't even want to think about how long I'd be waiting for n=50000000.
Well, probably something approaching 37000 seconds actually. So, around 10 hours. That doesn't sound like very much fun.
I'm just curious enough to compare it with the "compiled" option, where you can have an application run standalone in the Mac OS without the full Lisp system running (but using the microExplorer CPU). I should see if I can learn how to even do that.
Well, probably something approaching 37000 seconds actually. So, around 10 hours. That doesn't sound like very much fun.
I'm just curious enough to compare it with the "compiled" option, where you can have an application run standalone in the Mac OS without the full Lisp system running (but using the microExplorer CPU). I should see if I can learn how to even do that.
OpenGenera on Linux is the same as Alpha, except with the VLM hacked to run on x86-64 linux instead of Alpha OSF. My smallest Alpha is a DS20e (that still weighs 100+ lbs.), half the PCI cards in it aren't supported in DU4, and I was never able to get OG2 to run on Tru64 v5. Frankly, OG2 in a Linux VM makes anything else really difficult to recommend.
limited function maintenance shell, this is unix 101. no 'ls' -> use 'echo *'. make the shell do the work.
um. what is the question here? that access to environment variables in DOS is case sensitive? I don't understand the problem.
geo wrote: mmm how about the Genera under Alpha? i think that was the latest setup from Symbolics right? do you have such setup?
n=50000000 with OpenGenera 2 on Alpha DS20e (2x EV67 667 MHz)
Interpreted = 3752
Compiled = 6
geo wrote: hmm was wondering how a standalone Lisp machine would perform this..
I'm going to pull out my 3620 in the next couple days and start it as a project. I'll let you know eventually.
No new benchmark results (though I thought about installing Macintosh Common Lisp on the IIfx and comparing that to the MacIvory II. maybe in the spring.) but I have been jerking around with bringing up color on the NuVista+. There is some stub support for it in Genera 8.3, but it's not complete enough to actually work. So I hacked a patch together, borrowing the sync programs from the NuVista source. I think the timings are maybe not quite correct for the NuVista+ because I've got no color in any of the video modes, and the "hires" (31kHz) mode needs some pretty serious sync processing before any display will play ball. It'd be nice to find a copy of the Mac driver disks so I could extract the timing values from the "official" NuVista+ sync programs, and see if it makes any difference in the displays output from Genera.
But it does work. I haven't looked into any of the S-Graphics packages yet, though the color demos are (however) mildly amusing.
But it does work. I haven't looked into any of the S-Graphics packages yet, though the color demos are (however) mildly amusing.
Finger Of God and Spheres definitely do. The hardware pan and zoom works, but is not very smooth. I'm not sure if this is a limitation of the NuVista or of the MacIvory (or NuBus for that matter). The only thing that doesn't seem to work is color map animation. But it might. I'm not sure what it's supposed to look like. I have a 3650 with full color, but it needs attention before I can play with it and compare to NuVista.
The NuVista and NuVista+ really only do broadcast resolution.
The NuVista and NuVista+ really only do broadcast resolution.
I actually took some photos of the other demos too, just didn't upload them.
Shel's son Eric informed me this morning that Shel passed away on Sunday.
IIRC it should just pull straight out the front of the drive. If it's really "stuck", though, the gear train is probably bound, which can happen with split pinion as the teeth will no longer mesh near the split. The parts are resilient enough to withstand a reasonable amount of forcing.
The ADVC-300 isn't really a TBC.
I vaguely recall being here with my 5364 when I first started with it... but there was nothing wrong, it was just waiting for me to do something specific that I can't remember now. I will have to dig mine out from the shop to try again and see if I can remember something.
There were no "special" machines for front-ending a 5364. You could use any machine that meets the (trivial) requirements.
There were no "special" machines for front-ending a 5364. You could use any machine that meets the (trivial) requirements.
What makes you sure it's a 50z? I see nothing to distinguish it from a plain 50, or even a 70.
No.
setuid is dangerous on any shell script, not just those with csh. but csh is also poor for programming.
http://www-uxsup.csx.cam.ac.uk/misc/csh.html
On another note, I'm always amazed when an experienced UNIX user claims program x can't do y, when what he really means is, he never bothered to find out how. Most frequently, I encounter this around vi ("but I NEED vim to copy & paste!"), but... csh has always had command line history.
http://www-uxsup.csx.cam.ac.uk/misc/csh.html
On another note, I'm always amazed when an experienced UNIX user claims program x can't do y, when what he really means is, he never bothered to find out how. Most frequently, I encounter this around vi ("but I NEED vim to copy & paste!"), but... csh has always had command line history.
The ksh source was opened by AT&T maybe five or six years ago. Before that it was free for end-user download since the end of the '90s approximately, though the build environment was not entirely friendly.
IMO it'd have shown a more savvy touch to have had him as "boris@kremvax".
http://www.ebay.com/itm/111547545918
No connection to the seller, except I bought something else from him recently and noticed he's had it listed for a while. Power supply looks like a relatively easy replacement, and I can't think of another SPARC laptop off the top of my head which has SBus slots?
No connection to the seller, except I bought something else from him recently and noticed he's had it listed for a while. Power supply looks like a relatively easy replacement, and I can't think of another SPARC laptop off the top of my head which has SBus slots?
Yes, it appears to be an MCO.
isn't this the same uwm that was the default window manager prior to X11R4? why can't you just download it from x.org?
I just spent two months in the X11R2, X11R3, and X11R4 source. the uwm code isn't included with R4 (maaaaaaybe in contrib/, I didn't spend a lot of time in that part). the source from x.org is the straight release, it's not "athenaized" unless the official distribution was. R3 builds and runs (except the server binary---oy, compiler bugs) on RT 4.3BSD, so there's nothing wrong with the source.
smj wrote: Anyway - X11R2, R3 and R4 on ROMP, eh? How long did that R3 build take?Reminds me of setting up X11 builds to run over the weekend back in '89-91...
R3 took something like 6 hours, then another 4 to run 'make install', because it keeps rebuilding everything (thanks for learning how to use make, guys). Despite RT BSD supposedly being a native target for R2, it didn't even build. This was apparently well known even in the day; you had to use the IBM distribution of R2 on the RT if you want it to, you know, actually work.
I came to X11 originally in the R4/R5 transition days, by which time X11 was pretty well sorted out. The exercise gave me a new appreciation for the complaints in the UHH which I'd always taken as exaggerated for comic effect, and made me remember that shitty software written by infinite monkeys isn't a new feature of the free software movement.
If anybody knows where to find a copy of the MIT contributed patches to Xibm server in the R3 distribution that used to be at ftp://expo.lcs.mit.edu/contrib/ibm-rt.r3-fixes.tar.Z which actually make the thing, well, work , I'd be beyond thrilled to hear about it. It'd be dated approximately May 25, 1989, and contain the server/ddx/ibm/ tree.
Inconvenient software wasting time is a long way from boilers exploding and killing people. Things improve when people are of a mind to get together and improve them.
foetz wrote: this might be trivial but i couldn't get it done
i have an old workshop cd from 1994 in mint condition but i can't mount it ... anywhere. tried on solaris with all options i could think of. then tried on linux with the different ufs options and whatnot; no dice. tried no options at all - same result.
i have that cd twice and had the same problem with both and both are in great condition so i don't think they're broken or so.
so is there any trick to mount them? according to the booklet just -t ufs should do it but it doesn't
For a start, -t only works on Solaris 1.x. You need -F for Solaris 2.x. Second, are you sure it's a ufs FS, and not hsfs? If it is ufs, it probably has a Sun disk label, which would suggest you need to mount a slice other than s2, and may explain why linux can't cope with it.
I tried an assortment of workshop discs I have here. only one of them was ufs (V5N1 for Solaris 1.x). All the rest were hsfs, including V5N1 for Solaris 2.x, V3N1 for x86, and V6N1 for SPARC.
I don't know the provenance of your disc, but perhaps the booklet is for some other one. Did you try mounting it as hsfs?
I don't know the provenance of your disc, but perhaps the booklet is for some other one. Did you try mounting it as hsfs?
tingo wrote: For cases like this, when you don't exactly know what you have in your hands, the disktype utility is handy.
Good point, I forgot Solaris has 'fstyp -v'.
change /etc/nsswitch.conf so hosts: has files first, before anything else, and make sure the local hostname and IP appear in /etc/hosts. then fix /etc/resolv.conf to list a name server that you can actually communicate with (or remove it if you don't have any name server).
nsswitch.conf is also where you can remove references to NIS.
nsswitch.conf is also where you can remove references to NIS.
If you want the tapes imaged, that's something I can do for you if you're willing to ship them to me. I suppose in that case I should also verify my TK50s are still working, since it's been a while. Most of the tapes I've been transferring these days have been QIC.