CKing123 Ars Centurion
9y
282

MedicinalGoat said:
No more 486 support?! Don't come crying to me when your fancy pants speculative execution gets you into another security bind! Angrily shakes old man fist at clouds

That made me interested on the last in-order x86 CPU and it is Saltwell atom chips (which were a die-shrink of Bonnell) and some of these chips based on Saltwell were released as late as 2012(!) and they are even 64-bit.

Royal McBee's desk-sized deskside early computer was the stuff of legend

This python program:

print(‘’.join([f’{xint:0{5}b}’ for xint in range(32)]))

will output this string :

0000000001000100001100100001010011000111010000100101010010110110001101011100111110000100011001010011101001010110110101111100011001110101101111100111011111011111

Ask any purported “AGI” this simple IQ test question:

“What is the shortest python program you can come up with that outputs that string?”

Scientific induction is all about such algorithmic simplification under Algorithmic Information Theory:

The rigorous formalization of Occam’s Razor.

If an “AGI” can’t do scientific induction on even so trivial a scale, why attribute “general intelligence” to it?

This isn’t to say such an AI isn’t in the offing in the foreseeable future, but let’s be realistic about how we go about measuring the general intelligence of such systems.

This note describes XyWrite III+ in some detail, with emphasis on (a) its overall architecture and on "internals," and (b) its "macro"/programming/automation facilities. The target audience is threefold: (1) XyWrite III+ users who want more understanding, mostly of XyWrite XPL programming, (2) others who have never used XyWrite, and "wonder what the fuss is/was all about," and (3) myself -- since nothing clarifies one's thoughts about a given topic as trying to explain the topic to someone else. //

XyWrite III+ is a product that many users still feel is the best writing tool they have ever experienced. But, due to some misestimation by XyQuest (XyWrite's developer) as to how much MS Windows would damage the DOS applications market, plus an untimely, misguided, and costly partnership between XyQuest and IBM at about the time Windows was emerging, XyQuest failed at about the time MS Windows emerged. XyWrite development largely ceased soon thereafter.

In my view, many of the concepts that made XyWrite great have never been articulated, and many of them died when XyQuest died. This note attempts to explore and lay out some of those concepts, in a way that they might be appreciated even by someone who has never used the product, in the hope that some of these concepts might emerge in some measure in future "word processing" software. This hope, however, is perhaps a rather slim one -- nothing will make a person into a XyWrite fan as much as actually using the product will.

Tilde is a plain text editor for the Linux console. The difference is that even if you've never seen it before, you already know how to use this one. //

In the bad old days of WordStar, WordPerfect, DisplayWrite, MultiMate, Arnor Protext and so on, every app had a totally different UI.

This was partly because they all came from different original platforms, partly because such things weren't standardised yet, and partly because once someone had mastered one company's program, it made them very reluctant to switch to anything else. WordStar, for instance, offered original WordStar, WordStar 2000 and WordStar Express, all with totally different UIs.

But then the Mac came along. All its apps looked and worked much the same, because in 1987, Apple published a big, detailed book [PDF] telling programmers exactly how MacOS UIs should work. IBM followed suit with its CUA standard and gradually PC apps fell in line.

Windows and OS/2 both followed CUA, as did Motif on UNIX, and for a few decades harmony mostly reigned. GNOME 3 threw a lot of this out of the window, but even now most Linux graphical desktop and apps broadly follow the system: a menu bar, with File and usually Edit menus, a Help menu at the end, Ctrl+S to save, Ctrl+O to open, and so on. You may never have heard of CUA, but you know how to use it. //

Intel i7-5600U vs i5-8350U vs i5-8265U vs i7-8650U

Unix introduced / as the directory separator sometime around 1970. I don't know why exactly this character was chosen; the ancestor system Multics used >, but the designers of Unix had already used > together with < for redirection in the shell (see Why is the root directory denoted by a / sign?).

MS-DOS 2.0 introduced \ as the directory separator in the early 1980s. The reason / was not used is that MS-DOS 1.0 (which did not support directories at all) was already using / to introduce command-line options. It probably took this usage of / from VMS (which had a more complicated syntax for directories). You can read a more detailed explanation of why that choice was made on Larry Osterman's blog. MS-DOS even briefly had an option to change the option character to - and the directory separator to /, but it didn't stick.

/ it is recognized by most programmer-level APIs (in all versions of DOS and Windows). So you can often, but not always get away with using / as a directory separator under Windows. A notable exception is that you can't use / as a separator after the \\? prefix which (even in Windows 7) is the only way to specify a path using Unicode or containing more than 260 characters.

Some user interface elements support / as a directory separator under Windows, but not all. Some programs just pass filenames through to the underlying API, so they support / and \ indifferently. In the command interpreter (in command.com or cmd), you can use / in many cases, but not always; this is partly dependent on the version of Windows (for example, cd /windows works in XP and 7 but did not in Windows 9x). The Explorer path entry box accepts / (at least from XP up; probably because it also accepts URLs). On the other hand, the standard file open dialog rejects slashes. //

The underlying Windows API can accept either the backslash or slash to separate directory and file components of a path, but the Microsoft convention is to use a backslash, and APIs that return paths put backslash in.

MS-DOS and derived systems use backslash \ for path separator and slash / for command parameters. Unix and a number of other systems used slash / for paths and backslash \ for escaping special characters. And to this day this discrepancy causes countless woes to people working on cross-compilers, cross-platform tools, things that have to take network paths or URLs as well as file paths, and other stuff that you'd never imagine to suffer from this.

Why? What are the origins of this difference? Who's to blame and what's their excuse?

Why does Windows use backslashes for paths and Unix forward slashes?
– phuclv Commented Aug 13, 2018 at 16:55

While your question is perfectly reasonable, your phrasing seems to imply that you think the UNIX approach was already a de facto standard and MS-DOS was unique in deviating from it. See, as a counter-example, how the Macintosh OS used : as its path separator until MacOS X introduced POSIX APIs. This question goes into the history of that decision and answers point to : and . as path separators predating UNIX's use of /.
– ssokolow Commented Aug 1, 2022 at 20:10

@ssokolow UNIX was there with its forward slashes long before MacOS and DOS were created.
– SF. CommentedAug 2, 2022 at 8:13

@SF. And, as the answer phuclv linked says, DOS got it from CP/M, which got it from VMS. I don't know why VMS chose \ when UNIX chose / seven years before VMS's first release (going by Wikipedia dates), but it wasn't a settled thing. Other designs were using : and . in the mid-60s, half a decade before UNIX decided on /, and UNIX broke from Multics's > because they wanted to use it for shell piping.
– ssokolow Commented Aug 3, 2022 at 5:31

Use of UNIX back then wasn't nearly as ubiquitous as it is today. Almost all of industry and many schools used manufacturer-written and -supplied operating systems, especially from DEC. And within the more well-known CS schools (not that it was called "CS" then) there was also a lot of use of homegrown OSes. So the influence of UNIX wasn't as pronounced as it is today, as well - that took many years to develop.
– davidbak Commented Aug 3, 2022 at 16:51

A:

PC/MS-DOS 1 used the slash (/) as the command line switch indicator (like DEC's RSX11 and DG's RTOS before), so when DOS 2.0 introduced subdirectories, they did need a new one. Backslash () came somewhat natural - at least on US keyboards.

With 2.0 IBM/Microsoft also tried to reverse that decision and introduce a syscall (INT 21h function 3700h and 3701h) and a CONFIG.SYS option (SWITCHAR=) to set a different switch indicator. All manufacturer supplied commands would obey that new char. Set to a hyphen (-) would make the syntax more like Unix.

In fact, in paths, the OS didn't care. All dedicated path names, like in syscalls, can be written with either slash. It's only within the command line scan of each command, that simple slashes get interpreted as switch indicators. The idea was that people could/should migrate to a Unix-like style, but that didn't catch on.

With DOS 3.0 the SWITCHAR= option got removed fom CONFIG.SYS, but the syscalls are still availabe up to today. //

A:

The README.txt file in the MS-DOS 2.0 source code, which was apparently intended to guide OEMs on how to build custom DOS builds for their hardware, indicates that the decision to use backslash was requested by IBM: Microsoft had been originally intending to use forward slash, and the change happened late in the development process. This is probably why the kernel ended up supporting the use of either character -- it was, presumably, too late to change over fully.

The user manual contains some significant errors. Most of these are due to last minute changes to achieve a greater degree of compatibility with IBM's implementation of MS-DOS (PC DOS). This includes the use of "\" instead of "/" as the path separator, and "/" instead of "-" as the switch character.

This is true, but very widely misinterpreted – the forward slash as an option character did not come from IBM, IBM's own operating systems (mainframe and minicomputer) never used that syntax. What IBM objected to, was Microsoft's proposal in DOS 2.0 to change it from slash to dash – IBM cared about backward compatibility. But IBM wouldn't have had a problem if Microsoft had made it dash all along, starting with DOS 1.0; IBM didn't care what the syntax was in the initial version, but they didn't want it changed in a subsequent.
– Simon Kissane Commented May 26, 2023 at 1:47

Jeremy Keeshin
@jkeesh
In 1945, six women pulled off a computing miracle.

They programmed the world’s first computer—with no manuals, no training.

Then, a SINGLE assumption erased them from tech history for decades.

The story of how ONE photo nearly deleted computing’s female founders: 🧵

Kathy Kleiman, a young programmer, found old photos of women standing beside ENIAC—the first general-purpose computer.

When she asked who they were, curators said: “Probably just models”...

But Kleiman had a feeling they were something more:

Program ENIAC—a machine the world had never seen.

It was 8 feet tall, 80 feet long, and weighed over 60,000 pounds.

The engineers built the hardware...

But someone had to figure out how to make it do anything:

They were the world’s first programmers.

First, they were hired as “human computers” to calculate missile trajectories during WWII.

Then chosen for a top-secret project unlike anything before:

Security restrictions kept them out of the ENIAC lab.

They had to write programs using only blueprints and logic diagrams.

No manuals. No programming languages...

So how do you code something no one’s ever coded before?

By inventing the process from scratch.

They built algorithms, flowcharts, and step-by-step routines—on paper.

Then, once granted access, they programmed ENIAC by physically rewiring it...

And that’s where things got even harder:

There was no keyboard.

Programming meant plugging thousands of cables into the right configuration—by hand.

It was almost impossible to program.

But they pulled it off anyway:

On this day in 1975, Bill Gates and Paul Allen founded a company called Micro-Soft in Albuquerque, New Mexico.

then write up the marketing letter, format it and let it all rip on a Diablo 630 daisy wheel printer. Many, was that thing loud. Made the whole office grimace when I kicked it off. //

Re: Loud printers
You've obviously never used an ICL 1900 lineprinter: these could print at 160 characters per line at up to 1300 lines per minute. The mechanism was based round a hollow drum the full width of the paper with 160 rings of characters, each containing the complete character set. These were organised so that each embossed row had the same character in every position. The embossed drum was installed behind a row of 160 hammers and a inky ribbon the full width of the paper: both paper and ribbon scrolled vertically, though not at the same speed. The print hammers were driven off a very latge capacitor in the printer's body.

The printer was loud enough when printing invoices, etc, but George 3's print driver could easily outdo it. It separated documents by outputting, IIRC, a page throw, a job title, 10 full width lines of 160 asterisks and another page throw: when this happened the printer almost jumped off the floor and made a noise similar to a short burst from a machine gun.

These ICL printers were much louder than any IBM lineprinter I've ever heard running. That's because IBM used train printers: the character set formed a rotating chain running across the paper path and were designed so that only one character could hit the paper at a time. //

Re: Loud printers
Impact printers were getting fairly close to their practical limits in terms of printing speed. There was a flurry of development in the early 1970s to come up with better solutions. Xerox produced something that was kind of a hybrid between a drum printer and a photocopier - a set of flash lamps illuminated the correct characters on a drum transferring their images optically to the selenium copier drum. That got printing up to around 4000 lines a minute. Honeywell introduced an electrostatic system using a dielectric paper that raised speeds to 18,000 lines per minute.

However, it was IBM that developed the first laser printer - the IBM 3800. Its initial version managed only a shade under 14,000 lines per minute, but a later version raised the speed to over 20,000 lines per minute - around 2.8 km/h. With paper running that fast , a laser and a hot fuser unit, suddenly noise was not the only hazard. There's a fascinating training video for operators that shows the massive scale of the beast.

Keyways, Inc. buys - sells - repairs - trades DEC and DEC-compatible parts.

WE HAVE OVER 75,000 MODULES AND OTHER PARTS IN STOCK.
We now have 30,000 sq. ft. facilities to better serve our customers.

According to a report by TechSpot, Western Digital will now focus solely on its native hard disk technology, with the SSD division being spun off into SanDisk. This means that lineups like WD_BLACK will now be manufactured by SanDisk instead of WD themselves, and this will ultimately mean that Western Digital branding won't be there anymore. //

lostinblue Newbie
12 hours ago
Does the person who wrote the article know anything? Western Digital didn't quit SSD's because they weren't the future and hdds will grow as it's being implied and would be nuts, WD CEO David V. Goeckeler decided to spun the company but resign and become Sandisk CEO, Irving Tan is just a guy appointed to keep at it. Goeckeler is one of the most disliked CEOs in the industry (voted the worst actually), and is chasing his quarterly growth and profits as always because that means prize money for him. He tries to do this every year, inflate the growth to maximize how much money he gets and bet the company in the process. Funny that a ceo with no vision and no morals can fool a tech website this big though. I advise to cover it as it is, not a copy pasting the press release they do about it. PR Speak being PR Speak, it's worth nothing. //

lostinblue Newbie
Kendall
12 hours ago
It's about profits. WD CEO became Sandisk CEO and he is shedding WD skin. This is made in order to maximize and fake growth so he gets his prize money. He's very impopular and more than once took risky decisions like trying mergers just to hit his personal objectives. It should be reported as it is, a company being managed by people taking money out of it. The board is cahoots with him.

Anyway, this board i talk about they all left Western Digital with him. //

lostinblue Newbie
PANOS MESSIOS
12 hours ago
It's just a PR stunt. WD board of directors resigned and all were appointed to the same positions with Sandisk.

I'll let you guess where these CEO's thought there would be growth.

A computer can never be held accountable. This legendary page from an internal IBM training in 1979 could not be more appropriate for our new age of AI.

A COMPUTER CAN NEVER BE HELD ACCOUNTABLE. THEREFORE A COMPUTER MUST NEVER MAKE A MANAGEMENT DECISION

A computer can never be held accountable

Therefore a computer must never make a management decision

Here are a few ways to securely erase your hard drive:

DBAN (Darik's Boot and Nuke) – Use this free tool that overwrites data multiple times, making recovery impossible.
Windows Secure Erase (for SSDs) – If you're wiping an SSD, use the manufacturer's secure erase tool (e.g., Samsung Magician, Crucial Storage Executive).
Command Prompt (for HDDs) – Run cipher /w:C: to overwrite deleted files on the selected drive.

The HP-41C overcame these limitations by adding alphanumeric capabilities to both the display and keyboard. The keyboard had an "Alpha" key that toggled the keyboard between alpha and the normal calculator mode. (The alpha characters were printed on the slanted faces of the keys.) If the user needed a function not printed on a key, the name of the function could be typed in and executed. (About half of the HP-41Cs functions were preassigned to keys.)

Because typing out the name of a function could be cumbersome, the HP-41C added another toggle key called "user". The user could assign any built-in function or user program to any key. Once the keyboard was placed in user mode, any assignments made by the user overrode the label on the key. (With the gold shift key, this allowed two user functions per key.) The user toggle state remained set even when the calculator was turned off allowing true keyboard customization.

To make it easy to remember keyboard assignments, HP provided keyboard overlays along with preprinted labels for all built-in functions and blank labels for user functions. In addition, whenever a key was held down, its function name was displayed. If it was the wrong key, the user could continue to hold it until the display showed "NULL" when meant the function was canceled.

Of course, HP didn't just improve the human interface. The HP-41C had more memory (now non-volatile) than its predecessor, more functions, improved programming, and could be expanded with both RAM and ROM modules.

Ttcalc is a public domain programmable calculator for Microsoft Windows written by Stefan Seiwerth that is modeled after the HP-41C series of calculators. Download the program, unzip and see the readme.txt file for installation instructions. Run ttcalce.exe for the English version or ttcalc.exe for the German version. (The help file for either version is in German.)

I have a soft spot for fictional computers, having implemented compilers, bytecode interpreters, and even program synthesis for various made-up computer architectures.

This post is yet another dive into VM implementation, looking at a particularly fascinating ecosystem from Hundred Rabbits:

The Uxn CPU is a simple, 256-instruction stack machine
Varavara defines a set of peripherals that turn that CPU into an actual computer (display, keyboard, mouse, etc)

Unlike many fictional computers, the Uxn + Varvara ecosystem is sophisticated enough for actual use, and there are dozens of different ROMs – everything from text editors to drawing programs to synthesizers.

The Hundred Rabbits devlog motivates this design with far more eloquence than I could offer; I'd encourage you to browse their sprawling wiki of documentation, blog posts, and development notes.

My implementation is called Raven.

Uxn is the virtual machine powering the Hundred Rabbits software.

This one-page computer, programmable in Uxntal, is an portability layer with a focus on hosting graphical tools and games. It lives at the heart of the Varvara ecosystem.

• Uxn Instructions: Reference, Tests
• Varvara Devices: Reference, Tests

This wiki along with most of the audio-visual projects documented on it are running on Uxn.

Over the millennia, we have created security systems to deal with the sorts of mistakes humans commonly make. //

But it’s not the frequency or severity of AI systems’ mistakes that differentiates them from human mistakes. It’s their weirdness. AI systems do not make mistakes in the same ways that humans do.

Much of the friction—and risk—associated with our use of AI arise from that difference. We need to invent new security systems that adapt to these differences and prevent harm from AI mistakes. //

AI errors come at seemingly random times, without any clustering around particular topics. LLM mistakes tend to be more evenly distributed through the knowledge space. A model might be equally likely to make a mistake on a calculus question as it is to propose that cabbages eat goats.

And AI mistakes aren’t accompanied by ignorance. A LLM will be just as confident when saying something completely wrong—and obviously so, to a human—as it will be when saying something true. The seemingly random inconsistency of LLMs makes it hard to trust their reasoning in complex, multi-step problems. If you want to use an AI model to help with a business problem, it’s not enough to see that it understands what factors make a product profitable; you need to be sure it won’t forget what money is. //

Matt • January 21, 2025 11:54 AM

“Technologies like large language models (LLMs) can perform many cognitive tasks”

No, they can’t perform ANY cognitive tasks. They do not cogitate. They do not think and are not capable of reasoning. They are nothing more than word-prediction engines. (This is not the same as saying they are useless.)

You should know better than that, Bruce.

RealFakeNews • January 21, 2025 12:35 PM

Part of the problem is AI can’t fundamentally differentiate a fact from something it just made up. It can check cabbages and goats are related via some probability, but it can’t check that a cabbage doesn’t eat goats because it can’t use the lack of data to verify if that is correct.