#68000

[classictechnology]

Commodore Amiga 500

Title : Commodore Amiga 500, De nieuwe computergeneratie Publisher : Commodore B.V. Language : Dutch Year : Somewhere in the 1980’s Subject : Amiga 500 See https://www.homecomputermuseum.nl/collectie/commodore/amiga-500-2/ for more information

[textbookdedications]

Microprocessor Systems Design 2ed. - 68000 Family Hardware, Software and Interfacing

by Alan Clements

[outragedtortilla]

spooky ghost ???

[commodorez]

Various Japanese computers from thegirlg33k - VCF Midwest 18

[faggottonystark]

just read a Really good time loop fic and now its 2am and i need to reevaluate my life choicdz

[formula-fun]

Hi!!!!!!

So happy that you have found time to write again!

By now I have reread the story too many times so I have been trying to “force” your two amazing stories on my best friend in hopes of finding someone to scream together (I have successfully dragged her across most of the fandoms I have dabbled in) and she was very excited when I explained the plot and showed her my too-long asks on your tumblr to her 🤣

Of course she would love them as much as I do, and she would be running out of excuses for wips (hahahaha) when it looks like the final chapters might be happening!

Very very excited! Thank you so much for taking the time to write! 😘

Hey hey!!!

Aww thanks so much!! I know its not for everyone and wips sometimes arent everyones cup of tea either but i hope she likes it if she gives it a try!! ive had the wildest month in the world so im only now starting to clean them up, but really hoping to have them up soon before school gets crazy again <3

leaving a snippet here for you since i love it so so much but am unfortunately about to cut it!

In Brazil Max doesn’t even bother pretending he wants to use his own hotel room. Charles has only been settled for fifteen minutes when a polite knock rings through the room, and when he opens the door it’s to the sight of Max standing in front of it, tapping away on his phone, his backpack slung precariously over the handle of the suitcase resting beside him.

“Is the WiFi working for you?” he asks in lieu of a greeting, wandering past Charles when Charles steps aside.

“I don’t know,” Charles says, amused. “I just got here.”

“Oh. Same.” He flops backward onto the bed, his knees hanging over the edge, not looking up when his suitcase finally overbalances and falls to the floor with a clatter. He drops his phone somewhere over his head, stretching his arms until they shake. He looks lazy and content, easy with the way he’s made a place for himself in Charles’ space, like he knows he’s always welcome. Charles wants to get on the bed and crawl toward him, one palm on his sternum, and see what his mouth feels like against Charles’ upside down.

He swallows hard.

“Do you want to order room service?” Max asks him.

They have places to be. Charles is pretty sure they do, anyway. They always do. He and Max have been apart for barely ten hours. It’s not long enough to miss someone; not at all.

He lets Max pick up the menu and narrate it aloud to him, halfheartedly debating each item while Charles systematically empties his suitcase across the entirety of the room. Max finally toes his shoes off and slides backward to sit against the headboard, picking up the phone and fiddling with the cord as he orders them a ninety dollar pizza and a seventy dollar fruit tray and a fifteen dollar bottle of sparkling water, and then mumbles something about putting it on his room’s tab instead of Charles’, even though their teams foot the bills anyway. As soon as the phone thunks down into the cradle Charles drops the shirt he was pretending to fold and turns to crawl onto the bed and curl into Max’s side.  

Max’s hand settles on his waist, heavy and warm. “They said fifteen minutes,” Max tells him. His eyes are wide and soft.

Charles shakes his head. “That’s fine,” he answers. His chest feels too big—too full. Max is looking at him with a gentle kind of happiness, and when Charles thinks about him seeking Charles out and living in his space he feels too much. He doesn’t know what to do with it all.

He cups his face and kisses him in greeting, finally—means to keep it short and sweet, but Max pulls him closer immediately. It’s stupid; it shouldn’t feel the way it does, when they’ve barely been apart a day. It doesn’t matter.

He relaxes into Max’s hold a little too much, half-sprawled across his lap and unbalanced because of it. Max just rolls them until they’re laying sideways, their heads at the foot of the bed, kissing lazily all the while. Time turns soft and elastic, everything else drifting away, Charles caught somewhere in all the things they’re pressing against each other’s lips: hello’s and how are you’s and I missed you’s and I love you’s.

When a woman comes with the room service cart Charles has to get up and let her in with wobbly legs, his lips tingling. He winces behind her back when he registers her alpha scent as she passes him, a stark contrast to the happy tangle of Charles and Max’s scents that’s taken all of half an hour to permeate the room. There’s no way she doesn’t notice it, but she doesn’t say a word. Max gives her a bashful red-lipped smile and a tip that’s double the cost of their food, and Charles resists the urge to put his face in his hands.

[ui-alcoholic]

Amiga 1000

The Amiga1000 was introduced in the summer of 1985 and was the first machine in the Amiga family. Commodore acquired the technology through the acquisition of the Amiga company, which was originally developed by engineers Jay Miner and Larry Kaplan who had left Atari.

The goal was to develop a gaming platform with graphics and sound capabilities ahead of its time. This goal was achieved, but in the process, they created a complete computer instead of a game console.

The technical side of things went well enough, but financial problems meant they had to look for an investor, and ended up with Commodore.

The Amiga 1000 was a true multimedia computer. The 7MHz Motorola 68000 (PAL/7.09MHz PAL NTSC/7.16MHz) and 256kB of memory were roughly equivalent to those offered by the competition. In contrast, the 8-bit stereo sound and outstanding color graphics were well ahead of its contemporaries. However, neither the PC, Atari ST, nor even the Apple Macintosh had a multitasking operating system (AmigaOS). (although until the advent of faster machines, this was a disadvantage rather than an advantage) Read more about the story here: Geekometery - Jay Miner & The Amiga Computer

Check these out too if you are interested in retro computing

the iconic "Amiga ball" which seemed like a fantastic thing at the time.

A1000 cover sheet signed by the team members

A1000 in the Stranger Things 4

[mayra-quijotescx]

I've already made my views on staying in H**st*n known, so I feel like the nightmare I had last night with floodwater seeping in through all four walls of the apartment and filling the room while Meli and I were trapped inside was excessive and frankly entirely uncalled for

[gamemories]

[pop-squeak]

jesus

[gryphills]

I don't have the energy to write an actual reply rn but oh my god. Post with 68,000 notes saying "flash animation isn't bad, it's Puppet animation that's bad 95% of the time" and everyone's like "yeah flash animation can be good" as if the majority of 2D stuff isn't puppets/builds (flash or not)

Tell me you don't know anything about animation without telling me you don't know anything about animation.

Like. Puppet animation isn't "95% bad" - Most of the shit you see is "puppets". The only time you notice it looks shitty is when it's cheaper animation w high quotas.

The only 2D stuff that isn't builds is like. Klaus. And student films.

[merinsedai]

What. The. Fuck?

what an absolute git of a random event.

[mllebleue]

Violence is an ambiguous and amorphous thing. Physical violence is obvious (you can’t really miss being hit in the face), but it is not the only kind of violence. And although oppression through physical, say military, means is easy to identify, oppression does not necessarily require the use of fists or a baton to occur.

In his book Violence, Peace and Peace Research, Norwegian political scientist Johan Galtung, a prominent scholar in peace studies, outlines three different types of violence: direct, structural and cultural violence.

Direct violence includes actions taken by an actor against a subject, such hitting, maiming, killing, imprisoning. So aggression in all forms. It also includes the act of insulting a person, demeaning a person, shouting at a person, and all the acts of micro-aggression that we have begun to collectively recognize.

Structural violence is at its core social injustice, which is defined as injustice and inequality built into the very structure of society, resulting in unequal power and imbalanced life chances. Systemic racism is structural violence.

Structural violence, therefore, refers to all of the institutional and societal means by which a social group is curtailed, isolated, repressed and oppressed, such as socioeconomic marginalization, for example. Systematic refusal of care on a specific social group is structural violence. Notably, all the societal means that oppress by “keeping the underdogs on the outside, will impede mobilization.” (p. 38) Meaning that the inability to resist is integral to structural violence.

Cultural violence exists in any and every aspect of a culture that can be used to legitimize violence in its direct or structural forms. It’s the value systems, the ideas, the prejudices, the stories, the jokes, the slurs, the nicknames to refer to a marginalized or oppressed group. Fat phobia. Ableism.

Most importantly, Galtung underscores that the three types of violence function together, integrated, justifying, feeding and self-fulfilling each other, in a system in which “cultural violence makes direct and structural violence look and feel right, or at least not wrong.” (p. 39) Cultural and structural violence make it so that direct (physical) violence seems unavoidable, inevitable, even preferred and justified.

To sum up with an exagerated hypothetical example, when a Donald Trump supporter starts screaming in the face of person of colour marching in a Black Lives Matter protest, the slurs he uses are cultural violence, his screaming and physical posturing are direct violence and the cops who look on and do nothing are exercising structural violence. The fact that Black Lives Matter demonstrations happen, on the one hand, and are repressed by armed, militarized forces on the other hand are both examples of how structural violence impedes mobilization and resistance.

I’ve got my tumblr inbox turned off so I really have to commend the person who actually emailed me to let me know they don’t like the things I’ve posted about the UnitedHealth CEO being murdered on their commitment to their beliefs.

But seen as how you emailed me from a dud email that appears to be bouncing back replies and I really wanted to address something you said to me about violence begetting violence:

My migraine medication, the medication I was given for my debilitating neurological disease that has gotten so bad I spent most of this year actively suicidal, costs $1300 a month.

My insurance covered it. But only because my doctors office went to fucking war for me because I’m a high anaphylaxis risk for the drugs the insurance wanted me to try.

Because that’s the thing.

My doctors knew, based on my documented medical history, I likely wouldn’t be a good fit for the “first line” of preventative migraine drugs, but because of insurance, I had to be given drugs that were contradictory to my other life threatening conditions, because otherwise insurance wouldn’t cover anything else.

I failed them. Spectacularly and with an anaphylactic reaction to one of them. And I was still warned insurance would fight me because I hadn’t tried the remaining drug they wanted me to try.

A drug which I would have to take in an ER waiting room because my mast cell disease is unpredictable but insurance wouldn’t cover in-patient treatment to let me try it safely under medical supervision.

Is that not violence?

Were all the times I was denied coverage for vital and necessary procedures that could have prevented my disabilities from worsening not violence?

Maybe not in the sense you mean. But I assure you it felt very much like violence to me.

Do I condone murder? No, obviously. But I’m also sick and tired of people pretending that what is happening to the American people every day isn’t eugenics through class warfare.

Violence begets violence.

It sure fucking does.

Maybe these insurance companies should have thought of that first.

[sarcasticdolphin]

Chapters: 1/1 Fandom: Elisabeth - Levay/Kunze Rating: Mature Warnings: Creator Chose Not To Use Archive Warnings Relationships: Rudolf von Österreich-Ungarn | Rudolf Crown Prince of Austria/Der Tod | Death (Elisabeth) Characters: Rudolf von Österreich-Ungarn | Rudolf Crown Prince of Austria, Der Tod | Death (Elisabeth) Additional Tags: Rudolf and Tod spending some time together, that is basically all this fic is, just some kind of disturbing fluff, and I wanted to write a little more on Tod's wings Series: Part 11 of Mirrorverse Summary:

It took two and a half months, in the end, but Rudolf did return to Mayerling.

[techav]

On Multitasking

Sharing a Computer with Friends

The Motorola 68030 was a decently powerful microprocessor for its day. It is a fully 32-bit processor with 16 general-purpose registers, separate instruction & data caches, memory management unit, 18 addressing modes, over 100 instructions, pipelined architecture, and was available rated up to 50MHz. It was used in computers by Apple, Amiga, NeXT, Sun, Atari, and saw further life embedded in devices such as printers, oscilloscopes, and network switches. It was the kind of microprocessor used for desktop publishing, 3D CAD & animation, photo & video editing, etc.

In short, the 68030 is a microprocessor that can do some serious work. That's part of why I like it so much. It's a real workhorse chip but as far as 32-bit microprocessors go, it's dead simple to build with.

But running a single quick & simple BASIC program hardly seems like an adequate exercise for such a capable chip.

There is a prevailing claim that the 68000 architecture was heavily inspired by that of the PDP-11 or VAX minicomputers — powerhouses of the previous generation of computing. These machines ran entire businesses, at times servicing many simultaneous users. Surely the 68030 with similar capabilities but significantly faster instruction throughput than the decade-older machines would be more than capable of handling such a workload.

As I've mentioned before, one of my end goals for my 68030 projects is to run a proper operating system. Something like System V, BSD, or Linux; a true multi-user system befitting of the 68k's architectural heritage. My programming skills are limited, and getting such a complex project running is still outside my reach. But I am learning, and slowly inching myself closer to that goal.

Recently I built an expansion card for my Wrap030 project to add another four serial ports to it. In the context of the old minicomputers, another serial port means another terminal, which means the ability to serve one more user. My new 4-port serial card should give me the ability to add four new user terminals.

If only I had software capable of doing so.

Excluding symmetric multiprocessing and today's multi-core behemoths, supporting multiple user processes on a single computer processor means dividing time between them. The computer will run one user's program for a little while, then stop and run another user's program for a little while. Do this fast enough and neither user might ever notice that the computer is paying attention to someone else — especially since the computer spends much of its time just waiting for user input.

There are a few ways to accomplish this, but the simplest is to just make sure that every user program is written to cooperate with the others and periodically yield to the next user program ("Cooperative Multitasking"). A good time to do this is whenever the program needs to wait for input from the user or wait for a device to be ready to accept output.

Enhanced BASIC (68k EhBASIC), which I have been running on all of my 68k computer builds, was written in such a way that lends itself well to this sort of cooperative multitasking. It runs a tight loop when waiting for input or output, and while running a BASIC program, it stops at the end of each line to see if the user has pressed Ctrl-C to stop the program. This means that EhBASIC never goes too long without needing to check in with slow I/O devices. All that would needed is a simple kernel to set things up and switch to another user's processes whenever each time one of them is waiting for I/O.

So I set about creating such a minimal multi-user kernel. On startup, it initializes hardware, sets up some data tables for keeping track of what each user program is doing, loads BASIC into RAM, then starts running BASIC for that first user. Whenever a user process needs to read data from or write data to its terminal, it asks the kernel to handle that I/O task for it. The kernel will save the state of the user program to the data table it set up in the beginning, then switch to the next user to let it run until it too asks for assistance with an I/O task.

The kernel works through all user processes round-robin until it loops back around to the first user. After restoring the state of the user's process the kernel will service the I/O task that user process had originally requested, and return to let that user process run for a little while again. So all of the other user processes get their chance to run while one is waiting on data, and each process makes sure to allow the others a chance to run for a while when they are in the middle of running their own program.

I was able to throw together a quick proof of concept using the EASy68K simulator. What followed was days of catching all of the tiny mistakes I made, such as saving register A0 to the memory location reserved for register A1, overwriting the value previously saved for A1 and effectively losing both in the process — an error which resulted in BASIC printing only the first three characters of its startup header followed by a long string of null characters.

Debugging was tricky. I was starting from the bottom. No standard library, no existing structure or frameworks to rely on. The kernel process relied on the very same registers the user programs were using. Any changes to register contents by the kernel would affect the user processes. I ended up adding assembly macros to print short statements and register contents to the kernel console to try to get some insight into what was happening. I was able to track when registers came out of the user context save/restore process different than when they went in to find where I had bugs in that process.

This was a challenging project resulting in nearly a thousand lines of very low-level 68k assembly code, all of which I wrote and rewrote multiple times before figuring everything out. I've written small pieces of assembly code over the years, but none which required such deep dives into the CPU documentation to discern fine details of how the chip operates. I got there eventually though and now I have an 8MHz 68030 homebrew computer with 2MB of RAM that can run four BASIC programs simultaneously.

I'm going to need more terminals.