The collected works of robespierre - Page 6

The CM2086A3SG (D) version is nice because it supports stereo display (using STR_BOT or STR_TOP). It would be perfect for a Personal IRIS or Power Series. The ones I have owned were the (C) version, which unfortunately is not specified for stereo display. I did find that it was possible to use it with a resolution completely different from its fixed-frequency intended purpose. The monitor is spec'd for 1280x1024@60, but it will also sync at 1024x768@72, and I used it like that for months. There was a bit of nonlinearity that couldn't be eliminated, but I could get a stable, complete picture without tweaking anything too hard.
Another curious thing about these monitors (and others like the Sony GDM-19xx series) is that the body molding has raised contours for 8 front bezel pots, even though there are only 2 (brightness, contrast). the others would be cut out and populated by controls for vertical and horizontal size and convergence if the customer required them.

I don't mean to quibble, but what do you mean "address lines"? that is not part of the parallel scsi interface.
edit: on a SCA connector there are 4 ID pins, but these are not bussed, they are part of enclosure services.

SDI inputs won't be found on gear in the consumer channel, period.
Some video players do use it internally and can be modified to output SDI. (generally by parallel to serial conversion)
you should be able to find a reasonable deal on broadcast gear that's coming off lease, like the Barco LC40 or the Sony LMD which both have HD-SDI input options.

I found some old notes I made about using SCA connectors with ribbon cables, and there is an AMP/TE Connectivity part number: 1734098-8. This is not labelled as SCA but it looks very similar and might be compatible. It mounts to a ribbon cable.

I've never seen a 68030 NeXT slab. Do they really exist?

I never suspected that Apple's multicolor iMac experiment was thought up to separate "collectors" from their money, but this is strong evidence

I think that's right... at the Computer History Museum there's a display of the control module from a Minuteman rocket, it's a huge wire loom that fills a 4' wide airframe. I think they had to invent glass epoxy laminates (CEM-3 etc) to come up with a circuit board that was reliable enough for the Apollo program.
PCBs were harder to repair than point-to-point as long as they used through-hole technology. surface mount made a huge improvement to reliability and rework (and assembly!) is much easier with the correct tools.

I found a reference that claims Ray Rebels was a plug-in that was renamed "3D Extreme Effects".
There was a contemporary plug-in called Minerva that was rechristened "SI Custom Effects".

some competing home computers (like the Commodore 64, Atari 8-bit, TI 99/4A, PCjr, or ZX Spectrum) had a cartridge port and could use software on ROM chips in cartridges. The Apple ][ series never had that. All Apple software is disk-based, with the exception of some early programs that loaded from cassette tape. The floppy disks use a GCR modulation that is incompatible with PC floppy drives. So to transfer files to a IIgs, you can use a Macintosh with 800KB floppies, or use LocalTalk, or transfer files over a serial link using sz/rz.

http://apple2online.com/index.php?p=1_2 ... re-Library
https://archive.org/details/apple-ii-disk-collection
http://apple2.callapple.org/links.html

late edit: I forgot one other way. If you have both an Apple II "SuperDrive controller" and the G7287 External FDHD Drive, you can use 1.4 MB ProDOS, or (on GS System 6 and up) HFS, floppies that can be written from a Mac or PC. Apple switched from GCR to MFM modulation on HD floppies so compatibility is easier. There were compatible versions of the controller and drive from other companies like Applied Engineering. Other methods using (generally expensive) 3rd party hardware exist...

There is also a program called ADTPro ( http://adtpro.sourceforge.net/ ) that runs on a modern computer and provides data to the Apple II over the serial port (or the cassette port for older Apples). This is not as good as LocalTalk but has some of the same advantages.

You can also edit bootptab to customize the files available to each client.

something like WAIS may have had fewer holes, but the problem is we really don't know. security isn't that easy, what you actually need is proof-by-construction that the system is secure, and this means you have do everything from scratch using secure operations. no library convenience allowed.

the interactions between WWW browsers and routers are even more insidious than you paint it:
https://www.defcon.org/images/defcon-18 ... outers.pdf
Don't use routers that allow configuration from the browser.

I wonder if there isn't simply a way to use the c99 preprocessor with the C++ compiler? they should be more or less independent.

LD_PRELOAD is often used to emend the runtime behavior of such libraries. The advantage here is that you don't need to reverse engineer the target library much at all. Just dl_load it under a different name, call it, and fiddle with the return value all you want.

I could be wrong about this, but I don't think soft power-on works with the compact macs (at least it doesn't work with the SE/30). When the power switch is set to off, they really are off. But based on your message that it makes a whining sound when you plug in the lead, this appears not to apply to the color classic? Either way, I don't think I would plug parts in with power applied, because they were not designed to support that. I remember using a powerbook 180c where even pulling out the battery while the machine was on could fry something.
Some of these machines have a small button near the battery that is used to reset the microcontroller. It could also point to a battery problem, try removing the lithium battery for a minute and then replacing it.

Just to add some extra flavor, I had a PPC clone mac that wouldn't soft-start if the power key was hit quickly, it spun the fans for a bit and then stopped. You had to hold the key in for almost a second, and it was like this when new. The kind of thing that could be very frustrating to diagnose if you didn't think to try holding the key in.
There is also a technique to force a mac to boot without a PRAM battery: turn it on and then use the reset switch. If there is no reset switch you can sometimes mimic the effect by quickly flipping the power off and on. Looks like there's an unpopulated S1 on that board, hmm.

In the image "WP_20140918_19_32_19_Pro.jpg", you can see an empty square labeled "S1". This is where the PRAM reset switch would go if they had populated it.

fuggeddaboutit....

now that's eclectic. love the Metropolis figure.

please, the politically correct term is PTSD.

in OSX you still can't interact with the GUI from any thread except the main one....
I guess that means it's still primitive

Yes, we already know that you favor a "See Figure 1" approach to system usability. You really don't need to say it in every post.

and yet you can confuse the windowserver enough that the keyboard is useless...

that's a result of /bin/sh being a link to it. Only a few non-critical init scripts use it directly.
try

hamei, sites like that aren't made for humans. They're made by and for machines, to SEO certain search terms with links to and from other useless sites.

For any (sufficiently powerful) formal system, there will always be a true statement that it can't prove... this has implications for spam classifiers.

The Mac Plus can only use external hard disks. You can use a (stone-age) HD20, or a SCSI disk that supports narrow single-ended mode, which is a similar situation to old SGIs.

When emulating a computer, there is usually no upper limit to the amount of CPU consumed.
The emulator works on a "best-effort" basis, and runs the virtual CPU as fast as it can. This is not related to the useful work on the virtual CPU, since it probably busy-waits for something to happen (interrupts). In hardware you would keep the clock running all the time, and be ready to service an interrupt as soon as it happened. The only way to limit the (useless) consumption of host CPU resources is to engineer a completely new virtual "device" that does not exist in the original hardware at all, which stops the clock and everything else until something happens. This almost always requires a new device driver in the emulated OS.

sgifanatic wrote: I see. I saw a really nice mac+ on eBay, a little too late. This one also has a cd rom hooked up, along with a ram.upgrade and something called a 'fanny mac'. I need to read up on the plus so I can make a list of things I need to get it fully operational.

that is a box with a fan that would be installed on an early mac (512K or Plus). The machines used convection cooling only, so some people used "system savers" which were externally attached fans. The catch is that it is no longer silent.

You can only run up to System 7.5.5 on a Plus, and support for HFS+ became available in System 8.1. So you're limited to original HFS's support for drive volumes, which if I recall correctly is 2GB per volume. Even at that size, HFS is pretty wasteful with space: each fork gets allocated a multiple of 32KB space on the volume. Since most Mac files have two forks, it will be wasting an average of 32KB per file.
Back when they were deployed it was common to use third-party disk formatting tools, because the Drive Setup utility was so limited.
Silver Lining, Remus, Lido, and FWB were popular ones.

edit: another thing worth knowing about the Plus is that it emits a powerful magnetic field from the left side. Don't put any magnetic media near there.

foetz wrote:

robespierre wrote:

Code: Select all

$ sudo -s
# chmod -x /bin/bash
# ln -f /bin/ksh /bin/sh

fuggeddaboutit....

i did the same on osx but with zsh. might work for linux, too

In fact, osx can't boot using ksh. But zsh does seem to work.
(None of the system scripts in osx use bash)

i use tcsh as a login shell, but i've never liked it for scripts. just a dim feeling that it wasn't very clean. when i had to write some scripts to recover a lost file, i used ksh.

webweave wrote: http://www.ebay.com/itm/NEW-Barco-Creator-by-Paperback-Book-English-Free-Shipping-/191185097599
Someone has made a book on Creator, the description sounds kind of odd. Wish I still had my Barco training binders.

"High quality content by wikipedia articles!"
no, this is just typical spamware publishing. move along, nothing to see here...

this is a classic "led down the garden path" situation, which you do need to have some programming ability to notice.

you concluded that "It's something stupid related to pipes and processes"; in other words, that the statement "x=1" was not affecting the value of x, because it (surprisingly) executes in a different process. this is an unwarranted assumption, since it might not have affected x simply by never executing at all.


ls: quux: No such file or directory

for those who "do a lot of shell scripting" and are led astray by such basic mistakes, the greater danger may not be their choice of shell, but letting them near computers to begin with.


is a newline, because line is empty.


and

and
work as expected. the read runs without spawning a subshell; where it differs from other shells is in its handling of stdin: by default, if stdin is not a terminal, read doesn't wait for its input, but returns immediately if there is no data.

Alver wrote: I have ultrix running in SIMH on Linux (ULTRIX V4.0 (Rev. 161) - and yes, SIMH exists on OSX as well) and it doesn't consume 100% CPU. It all comes down to how the emulator implements the idle instructions of the emulated OS/chip. I'm far from an expert on how these things get implemented, but rest assured, I've made sure none of my emulated VAXen had the 100% CPU issue before setting them loose 24/7. :D

Indeed, it is a rare CPU that has "idle instructions". That isn't how hardware works: Even when the system is waiting "idle" for an event, it is still running code, and it still needs to update counters/timers.

See these links for some insight into how brittle and unreliable the heuristics used by SIMH are:
http://github.com/simh/simh/issues/80
http://www.mail-archive.com/simh@traili ... 01231.html
This approach is very VAX-like. "We've got so many instructions, we'll never have to use each one more than once!" Expecting it to work on a more rational architecture is a pipe dream.

maybe the write-protect sensor is stuck?

Those tests were all done using "sh (AT&T Labs Research) 1993-12-28 p". the point is that even "ksh93" does not run the example as expected.

I think that the behavior of bash/dash is informed by POSIX.2:

Additionally, each command of a multi-command pipeline is in a subshell environment; as an extension, however, any or all commands in a pipeline may be executed in the current environment.

They interpret it to require that the behavior as respects variable assignment be as if the command was executed in a subshell, even though it is not.

those Sony low-cost CDROMs are unbearably slow, although they do seem reasonably reliable.

I don't think the VW 320/540 were ever supplied with Linux. You got NT or W2K only.
Apart from the CPU, the rest of the machine was an SGI design, so it's not accurate to call it just a PC.
I haven't had a burning desire to own one, but they are an interesting historical artifact.

those old demos were very low resolution, and never show more than a dozen polygons. they make it seem like more than it is using tricks that manipulate the display format (like "smooth scrolling" and colormap animation). I remember being really impressed by some of those effects back in the early '90s, like "plasma". the first time you see it, it looks amazing. but in actual fact, it's a static image, only the colormap is changing.
But, hey, whatever floats your boat. That "Type R" sticker really does make it go faster, right?