Search
1000 results for “alt_graph”
-
The huge irony is that Pinterest kept censoring my book covers -- which, you know, I'm just the narrator, the authors pick the covers -- so while I was busy making bland alt graphics to post on Pinterest, I thought I'd post some writing books there as a kind of loss leader to safely build traffic...and then Pinterest went and censored the writing books, too. 😂
Excuse me as I sing along with MJ.
-
CW: re: punctuation woes
@vicorva I think my preference for single double quotes might have something to do with how I tend to use the same character for single quotes and apostrophes, and thus you could end up in situations where there would be an apostrophe right before a single closing quote: 'That's James'', which would look weirder to me than "That's James'". I guess I I could solve this by using grave accent and backticks, so you'd have `That's James'´, but that would take too much conscious typing and use of the alt-graph key.
In Dutch I grew up using quotes where the first one is more like double lying commas, such as 🙸That's James'🙷 or „That's James'” or ones that are hanging but tilted towards the word, such as ‟That's James'”, though those are even harder to type unless I use my phone. ;)
(Also, I dont think a trailing apostrophe is actually a thing in Dutch.)My use of quotes might also be heavily influenced by programming though, where single quotes strings are usually not parsed by the programming language, while those in double quotes can often contain variables. Nested quotes of the same type also mean you need to escape them with a backslash, which means I tend to use double quotes for strings so I don't have to worry about apostrophes breaking my string.
When I quote a text, I tend to wrap it in «double angle quotation marks», so I don't have to worry about nested quotes of any kind confusing people where my quote ends and the quotee's quote starts. :)
In my #FiXaNotes browser extension I do have a section with all sorts of quotation marks in case I need to mix and match though.
#quotation #FiXaThoughts #writing #FiXatoWrites #FiXatoCreative
-
@smurthys The control systems for most particle accelerators and other large #physics experiments are built on C++. It might sound like a niche application, but it’s a surprisingly large ecosystem of libraries, services and device drivers for controlling some of the world’s largest machines.
https://www.tango-controls.org
https://epics-controls.org
https://doocs.desy.de
#cpp
#acceleratorphysics -
@smurthys The control systems for most particle accelerators and other large #physics experiments are built on C++. It might sound like a niche application, but it’s a surprisingly large ecosystem of libraries, services and device drivers for controlling some of the world’s largest machines.
https://www.tango-controls.org
https://epics-controls.org
https://doocs.desy.de
#cpp
#acceleratorphysics -
@smurthys The control systems for most particle accelerators and other large #physics experiments are built on C++. It might sound like a niche application, but it’s a surprisingly large ecosystem of libraries, services and device drivers for controlling some of the world’s largest machines.
https://www.tango-controls.org
https://epics-controls.org
https://doocs.desy.de
#cpp
#acceleratorphysics -
@smurthys The control systems for most particle accelerators and other large #physics experiments are built on C++. It might sound like a niche application, but it’s a surprisingly large ecosystem of libraries, services and device drivers for controlling some of the world’s largest machines.
https://www.tango-controls.org
https://epics-controls.org
https://doocs.desy.de
#cpp
#acceleratorphysics -
@smurthys The control systems for most particle accelerators and other large #physics experiments are built on C++. It might sound like a niche application, but it’s a surprisingly large ecosystem of libraries, services and device drivers for controlling some of the world’s largest machines.
https://www.tango-controls.org
https://epics-controls.org
https://doocs.desy.de
#cpp
#acceleratorphysics -
Yamaha
Japan Technology
Many of you only know Yamaha from a few of their skillsets.
Yes I said skillsets not products.
Yamaha has specialists in many fields
They create wonderful things in the fields of
- Music
- instruments
- woodwinds
- brass
- trumpet
- tuba
- saxophone
- bass
- alto
- tenor
- sopraan
- sopranino
- strings
- Bass Guitars
- acoustic
- electric
- Guitars
- violins
- ContraBass
- cello
- recorders
- Audio
- tape decks (Pro Open Reel)
- turntables
- cassette decks
- radios
- receivers
- transceivers
- Pro Audio
- Mixing console
- multiple channel
- from 8 to 32 analog
- FOH mixing console
- stage mixing console
- compressor
- limiter
- equalizer
- microphones
- dynamic
- condenser
- PA speakers
- passive
- active
- floor monitors
- FOH speaker systems (full sets)
- passive
- active
- subwoofer
- studio monitor
- amplifiers
- class B
- class D
- Bass guitar enclosures
- Bass amp heads
- guitar enclosures
- guitar amp heads
- Display systems
- [data]
- Mechanics
- engines
- motorcycles
- RD 400 2 stroke Daytona
- mopeds
With the subjects I just mentioned I only covered the surface of what Yamaha specialists can produce with their skillsets
If you purchase a Yamaha Grand Piano, Yamaha goes so far that when you've chosen it (in person!) they deliver install, secure and tune your grand piano, so your experience is similar to what their musicians and technical building experts have (had) when building and playing the Grand.
Yamaha has perfectionists who live and work by the principle of Kysen. They will tune and tweak their sublime work so it becomes even more sublime. Yamaha specialists gurus and experts do this in all fields that Yamaha is in.
Images & photographs
As you see I've included photographs of an 8 channel Yamaha portable mixing system, designed for micro live performance, with a build in two channel class D amplifier, and a set of dual driver speakers / monitors, which I use when I need balanced physical PA speaker output, that my sets of headphones cannot produce, in the studio, simply because the physics in combination with the acoustics prohibits such output.
The system is tuned to the space, thus is small.
It delivers a balanced flat sound up to 90dB of SPL in the this closed real world setting, if needed (though that is rare)
This level has been measured (and is regularly done). I do this to make sure I don't overload my ears with dB thus damaging my precious engineering organsYamaha in my personal and Pro live
Yamaha plays an important role in my professional PA live.
- I have mixing consoles made by them, which blow all others just plain out of the water, when I chose those Yamaha consoles.Note 1
- microphones
- dynamic
- condenser
- speaker systems
- full range
- monitors (floor)
- subwoofers
In my musical live Yamaha plays an important role too. I have instruments ranging from the humble recorder to
- string instruments
- brass
- many others, too many to specify here
Note 1
Naturally I have specialized mixers from other brands which do an excellent job. Yamaha does not make those, so I have no fields of comparable parametersZ
#Yamaha #instruments #technology #mathematics #physics #brass #trumpet #trombone #saxophone #alt #tenor #bass #sopranino #sopraan #string #piano #bass #cello #doublebass #woodwinds #flute #Audio #PA #console #mixer #speaker #passive #active #amp #compressor #limiter #eq #equalizer #parametric #graphic #analog #digital 🎶 ##Retro #Legacy #current #Analog
-
HAPPY #FUNDFRIDAY 🌻
RULES - pls read them! Lets keep this space safe from getting susp*nded 🙂
❤ 1 post per person
❤ repost/like other requests
❤ use ALT text for images
❤ no hateful/bigoted language (automatic block)
❤ repost the thread
❤ no graphic images#mutualaid #MutualAidRequest #MutualAidSavesLives #MutualAidBoost #disabled #bipoc #trans #lgbtqia #lgbtq #poverty #houseless #directaid #kofi #urgentmutualaid #chronicillness
-
HAPPY #FUNDFRIDAY 🌻
RULES - pls read them! Lets keep this space safe from getting susp*nded 🙂
❤ 1 post per person
❤ repost/like other requests
❤ use ALT text for images
❤ no hateful/bigoted language (automatic block)
❤ repost the thread
❤ no graphic images#mutualaid #MutualAidRequest #MutualAidSavesLives #MutualAidBoost #disabled #bipoc #trans #lgbtqia #lgbtq #poverty #houseless #directaid #kofi #urgentmutualaid #chronicillness #MutualAidThread
-
HAPPY #FUNDFRIDAY 🌻
RULES - pls read them! Lets keep this space safe from getting susp*nded 🙂
❤ 1 post per person
❤ repost/like other requests
❤ use ALT text for images
❤ no hateful/bigoted language (automatic block)
❤ repost the thread
❤ no graphic images#mutualaid #MutualAidRequest #MutualAidSavesLives #MutualAidBoost #disabled #bipoc #trans #lgbtqia #lgbtq #poverty #houseless #directaid #kofi #urgentmutualaid #chronicillness #MutualAidThread
-
HAPPY #FUNDFRIDAY 🌻
RULES - pls read them! Lets keep this space safe from getting susp*nded 🙂
❤ 1 post per person
❤ repost/like other requests
❤ use ALT text for images
❤ no hateful/bigoted language (automatic block)
❤ repost the thread
❤ no graphic images#mutualaid #MutualAidRequest #MutualAidSavesLives #MutualAidBoost #disabled #bipoc #trans #lgbtqia #lgbtq #poverty #houseless #directaid #kofi #urgentmutualaid #chronicillness #MutualAidThread
-
HAPPY #FUNDFRIDAY 🌻
RULES - pls read them! Lets keep this space safe from getting susp*nded 🙂
❤ 1 post per person
❤ repost/like other requests
❤ use ALT text for images
❤ no hateful/bigoted language (automatic block)
❤ repost the thread
❤ no graphic images#mutualaid #MutualAidRequest #MutualAidSavesLives #MutualAidBoost #disabled #bipoc #trans #lgbtqia #lgbtq #poverty #houseless #directaid #kofi #urgentmutualaid #chronicillness #MutualAidThread
-
@Jeffrey D. Stark I know that decision tree, and it doesn't really work for my original images because it's limited to what you'd usually find on professional/commercial static websites or blogs with a very small choice of kinds of images.
Let's take this image as an example here. It was the first image I've described in detail. I'm not going to link to that description because it's hopelessly outdated and probably terribly lacking at only a bit over 13,000 characters, and the image does not have a descriptive alt-text yet. It's an old shame, so-to-speak.
Does the image contain text?
Let's say, what the image shows within its borders has 22 bits of text on it, for any definition of text. This could count as yes.
However, of these 22 bits of text, only three are legible in the image as it is, at the resolution at which I've uploaded it: three times a capital M. As I've said, for any definition of text. The other 19 are so small that they're illegible, or they are so small that they can't be identified as text, or they're so tiny that they're invisible at this resolution. The big black sign in the middle with the yellow writing on it has a tree in front of it.
Is it still a yes because, while it isn't readable, there still is text?
Is it a yes for the three capital Ms?
Is it a no because the text does not show itself as text in this image at this resolution? So technically speaking, with the exception of the three capital Ms, there is no text in this image because where there's text in the original, there's just some blurry mush that does not qualify as text in the image as shown?
Or is it a no because I can't transcribe it anyway if I can't read it? Fun fact: I have transcribed all this text. 100% verbatim. And provided translations for everything that isn't English. So "you can't read it anyway" doesn't count because I can read it.
Now comes the kicker: If we pick yes because there is text in the image, the decision tree implies that it is an image of text and nothing else, and that the image-describing process is over after transcribing the text. This wouldn't even work with an image macro.
Does the image contribute meaning to the current page or context?
Does this question even work in this case?
Let's say the post in question is about the world where the image was taken shutting down soon and my avatar in this world disappearing. Because it was when I first posted this image. It's just meant to be a last farewell.
It doesn't add any extra information. This is not a post in a professional commercial or scientific or technological blog. So, does the image contribute meaning, yes or no?
If so:- It's not "a simple graphic or a photograph". It's a digital 3-D rendering, and it's anything but simple.
- It's not "a graph or complex piece of information". Complex, yes. But it isn't a graph, and it isn't a piece of information of the kind you'd have on a scientific website.
- I don't think it "shows content that is redundant to real text nearby".
Is the image purely decorative or not intended for users?
That's debatable. On professional websites and blogs, this question may make sense. In social media where nobody adds decorative images to posts, it doesn't. In the Fediverse which has way higher accessibility standards than 𝕏 or Facebook or Tumblr or Threads or Bluesky or LinkedIn, it makes even less sense.
Is the image’s use not listed above or it’s unclear whatalttext to provide?
Probably.
The top of the article is already a dead give-away: This guide is not meant for social media. Not for the big commercial silos, and even less for the Fediverse where Mastodon re-defines what makes an image description good. Not even two dozen people in the world use social media that support HTML<img>tags in posts.
While professional Web accessibility experts will throw their hands up into the air in utter outrage over 250 characters of alt-text because it's too long, Mastodon users celebrate alt-text that's four times as long.
So this is a case where a whole bunch of edge-cases unhandled by the WAI meet in one place:- A situation in which not the audience comes to the content, but the content comes to the audience without the audience necessarily explicitly seeking out this kind of content.
- Social media with possibilities that vastly exceed those of the big commercial silos, especially regarding character count, while at the same time mostly not supporting full HTML.
- An audience which has defined its own accessibility "rules". Including blind or visually-impaired people who do want to know what something in an image looks like, even if the WAI alt-text guidelines forbid describing it.
- Content that has never been taken into consideration by any alt-text/image description guide out there. Ever.
Trying to force this into the WAI or WCAG guidelines is akin to trying to push a square peg into a round hole that was drilled by people who think all pegs are round.
I mean, as you've just seen, I can't even clearly answer any of the questions in the decision tree.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #WebAccessibilityInitiative #WAI #WCAG #A11y #Accessibility -
@Jeffrey D. Stark I know that decision tree, and it doesn't really work for my original images because it's limited to what you'd usually find on professional/commercial static websites or blogs with a very small choice of kinds of images.
Let's take this image as an example here. It was the first image I've described in detail. I'm not going to link to that description because it's hopelessly outdated and probably terribly lacking at only a bit over 13,000 characters, and the image does not have a descriptive alt-text yet. It's an old shame, so-to-speak.
Does the image contain text?
Let's say, what the image shows within its borders has 22 bits of text on it, for any definition of text. This could count as yes.
However, of these 22 bits of text, only three are legible in the image as it is, at the resolution at which I've uploaded it: three times a capital M. As I've said, for any definition of text. The other 19 are so small that they're illegible, or they are so small that they can't be identified as text, or they're so tiny that they're invisible at this resolution. The big black sign in the middle with the yellow writing on it has a tree in front of it.
Is it still a yes because, while it isn't readable, there still is text?
Is it a yes for the three capital Ms?
Is it a no because the text does not show itself as text in this image at this resolution? So technically speaking, with the exception of the three capital Ms, there is no text in this image because where there's text in the original, there's just some blurry mush that does not qualify as text in the image as shown?
Or is it a no because I can't transcribe it anyway if I can't read it? Fun fact: I have transcribed all this text. 100% verbatim. And provided translations for everything that isn't English. So "you can't read it anyway" doesn't count because I can read it.
Now comes the kicker: If we pick yes because there is text in the image, the decision tree implies that it is an image of text and nothing else, and that the image-describing process is over after transcribing the text. This wouldn't even work with an image macro.
Does the image contribute meaning to the current page or context?
Does this question even work in this case?
Let's say the post in question is about the world where the image was taken shutting down soon and my avatar in this world disappearing. Because it was when I first posted this image. It's just meant to be a last farewell.
It doesn't add any extra information. This is not a post in a professional commercial or scientific or technological blog. So, does the image contribute meaning, yes or no?
If so:- It's not "a simple graphic or a photograph". It's a digital 3-D rendering, and it's anything but simple.
- It's not "a graph or complex piece of information". Complex, yes. But it isn't a graph, and it isn't a piece of information of the kind you'd have on a scientific website.
- I don't think it "shows content that is redundant to real text nearby".
Is the image purely decorative or not intended for users?
That's debatable. On professional websites and blogs, this question may make sense. In social media where nobody adds decorative images to posts, it doesn't. In the Fediverse which has way higher accessibility standards than 𝕏 or Facebook or Tumblr or Threads or Bluesky or LinkedIn, it makes even less sense.
Is the image’s use not listed above or it’s unclear whatalttext to provide?
Probably.
The top of the article is already a dead give-away: This guide is not meant for social media. Not for the big commercial silos, and even less for the Fediverse where Mastodon re-defines what makes an image description good. Not even two dozen people in the world use social media that support HTML<img>tags in posts.
While professional Web accessibility experts will throw their hands up into the air in utter outrage over 250 characters of alt-text because it's too long, Mastodon users celebrate alt-text that's four times as long.
So this is a case where a whole bunch of edge-cases unhandled by the WAI meet in one place:- A situation in which not the audience comes to the content, but the content comes to the audience without the audience necessarily explicitly seeking out this kind of content.
- Social media with possibilities that vastly exceed those of the big commercial silos, especially regarding character count, while at the same time mostly not supporting full HTML.
- An audience which has defined its own accessibility "rules". Including blind or visually-impaired people who do want to know what something in an image looks like, even if the WAI alt-text guidelines forbid describing it.
- Content that has never been taken into consideration by any alt-text/image description guide out there. Ever.
Trying to force this into the WAI or WCAG guidelines is akin to trying to push a square peg into a round hole that was drilled by people who think all pegs are round.
I mean, as you've just seen, I can't even clearly answer any of the questions in the decision tree.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #WebAccessibilityInitiative #WAI #WCAG #A11y #Accessibility -
@Jeffrey D. Stark I know that decision tree, and it doesn't really work for my original images because it's limited to what you'd usually find on professional/commercial static websites or blogs with a very small choice of kinds of images.
Let's take this image as an example here. It was the first image I've described in detail. I'm not going to link to that description because it's hopelessly outdated and probably terribly lacking at only a bit over 13,000 characters, and the image does not have a descriptive alt-text yet. It's an old shame, so-to-speak.
Does the image contain text?
Let's say, what the image shows within its borders has 22 bits of text on it, for any definition of text. This could count as yes.
However, of these 22 bits of text, only three are legible in the image as it is, at the resolution at which I've uploaded it: three times a capital M. As I've said, for any definition of text. The other 19 are so small that they're illegible, or they are so small that they can't be identified as text, or they're so tiny that they're invisible at this resolution. The big black sign in the middle with the yellow writing on it has a tree in front of it.
Is it still a yes because, while it isn't readable, there still is text?
Is it a yes for the three capital Ms?
Is it a no because the text does not show itself as text in this image at this resolution? So technically speaking, with the exception of the three capital Ms, there is no text in this image because where there's text in the original, there's just some blurry mush that does not qualify as text in the image as shown?
Or is it a no because I can't transcribe it anyway if I can't read it? Fun fact: I have transcribed all this text. 100% verbatim. And provided translations for everything that isn't English. So "you can't read it anyway" doesn't count because I can read it.
Now comes the kicker: If we pick yes because there is text in the image, the decision tree implies that it is an image of text and nothing else, and that the image-describing process is over after transcribing the text. This wouldn't even work with an image macro.
Does the image contribute meaning to the current page or context?
Does this question even work in this case?
Let's say the post in question is about the world where the image was taken shutting down soon and my avatar in this world disappearing. Because it was when I first posted this image. It's just meant to be a last farewell.
It doesn't add any extra information. This is not a post in a professional commercial or scientific or technological blog. So, does the image contribute meaning, yes or no?
If so:- It's not "a simple graphic or a photograph". It's a digital 3-D rendering, and it's anything but simple.
- It's not "a graph or complex piece of information". Complex, yes. But it isn't a graph, and it isn't a piece of information of the kind you'd have on a scientific website.
- I don't think it "shows content that is redundant to real text nearby".
Is the image purely decorative or not intended for users?
That's debatable. On professional websites and blogs, this question may make sense. In social media where nobody adds decorative images to posts, it doesn't. In the Fediverse which has way higher accessibility standards than 𝕏 or Facebook or Tumblr or Threads or Bluesky or LinkedIn, it makes even less sense.
Is the image’s use not listed above or it’s unclear whatalttext to provide?
Probably.
The top of the article is already a dead give-away: This guide is not meant for social media. Not for the big commercial silos, and even less for the Fediverse where Mastodon re-defines what makes an image description good. Not even two dozen people in the world use social media that support HTML<img>tags in posts.
While professional Web accessibility experts will throw their hands up into the air in utter outrage over 250 characters of alt-text because it's too long, Mastodon users celebrate alt-text that's four times as long.
So this is a case where a whole bunch of edge-cases unhandled by the WAI meet in one place:- A situation in which not the audience comes to the content, but the content comes to the audience without the audience necessarily explicitly seeking out this kind of content.
- Social media with possibilities that vastly exceed those of the big commercial silos, especially regarding character count, while at the same time mostly not supporting full HTML.
- An audience which has defined its own accessibility "rules". Including blind or visually-impaired people who do want to know what something in an image looks like, even if the WAI alt-text guidelines forbid describing it.
- Content that has never been taken into consideration by any alt-text/image description guide out there. Ever.
Trying to force this into the WAI or WCAG guidelines is akin to trying to push a square peg into a round hole that was drilled by people who think all pegs are round.
I mean, as you've just seen, I can't even clearly answer any of the questions in the decision tree.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #WebAccessibilityInitiative #WAI #WCAG #A11y #Accessibility -
@Jeffrey D. Stark I know that decision tree, and it doesn't really work for my original images because it's limited to what you'd usually find on professional/commercial static websites or blogs with a very small choice of kinds of images.
Let's take this image as an example here. It was the first image I've described in detail. I'm not going to link to that description because it's hopelessly outdated and probably terribly lacking at only a bit over 13,000 characters, and the image does not have a descriptive alt-text yet. It's an old shame, so-to-speak.
Does the image contain text?
Let's say, what the image shows within its borders has 22 bits of text on it, for any definition of text. This could count as yes.
However, of these 22 bits of text, only three are legible in the image as it is, at the resolution at which I've uploaded it: three times a capital M. As I've said, for any definition of text. The other 19 are so small that they're illegible, or they are so small that they can't be identified as text, or they're so tiny that they're invisible at this resolution. The big black sign in the middle with the yellow writing on it has a tree in front of it.
Is it still a yes because, while it isn't readable, there still is text?
Is it a yes for the three capital Ms?
Is it a no because the text does not show itself as text in this image at this resolution? So technically speaking, with the exception of the three capital Ms, there is no text in this image because where there's text in the original, there's just some blurry mush that does not qualify as text in the image as shown?
Or is it a no because I can't transcribe it anyway if I can't read it? Fun fact: I have transcribed all this text. 100% verbatim. And provided translations for everything that isn't English. So "you can't read it anyway" doesn't count because I can read it.
Now comes the kicker: If we pick yes because there is text in the image, the decision tree implies that it is an image of text and nothing else, and that the image-describing process is over after transcribing the text. This wouldn't even work with an image macro.
Does the image contribute meaning to the current page or context?
Does this question even work in this case?
Let's say the post in question is about the world where the image was taken shutting down soon and my avatar in this world disappearing. Because it was when I first posted this image. It's just meant to be a last farewell.
It doesn't add any extra information. This is not a post in a professional commercial or scientific or technological blog. So, does the image contribute meaning, yes or no?
If so:- It's not "a simple graphic or a photograph". It's a digital 3-D rendering, and it's anything but simple.
- It's not "a graph or complex piece of information". Complex, yes. But it isn't a graph, and it isn't a piece of information of the kind you'd have on a scientific website.
- I don't think it "shows content that is redundant to real text nearby".
Is the image purely decorative or not intended for users?
That's debatable. On professional websites and blogs, this question may make sense. In social media where nobody adds decorative images to posts, it doesn't. In the Fediverse which has way higher accessibility standards than 𝕏 or Facebook or Tumblr or Threads or Bluesky or LinkedIn, it makes even less sense.
Is the image’s use not listed above or it’s unclear whatalttext to provide?
Probably.
The top of the article is already a dead give-away: This guide is not meant for social media. Not for the big commercial silos, and even less for the Fediverse where Mastodon re-defines what makes an image description good. Not even two dozen people in the world use social media that support HTML<img>tags in posts.
While professional Web accessibility experts will throw their hands up into the air in utter outrage over 250 characters of alt-text because it's too long, Mastodon users celebrate alt-text that's four times as long.
So this is a case where a whole bunch of edge-cases unhandled by the WAI meet in one place:- A situation in which not the audience comes to the content, but the content comes to the audience without the audience necessarily explicitly seeking out this kind of content.
- Social media with possibilities that vastly exceed those of the big commercial silos, especially regarding character count, while at the same time mostly not supporting full HTML.
- An audience which has defined its own accessibility "rules". Including blind or visually-impaired people who do want to know what something in an image looks like, even if the WAI alt-text guidelines forbid describing it.
- Content that has never been taken into consideration by any alt-text/image description guide out there. Ever.
Trying to force this into the WAI or WCAG guidelines is akin to trying to push a square peg into a round hole that was drilled by people who think all pegs are round.
I mean, as you've just seen, I can't even clearly answer any of the questions in the decision tree.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #WebAccessibilityInitiative #WAI #WCAG #A11y #Accessibility -
@Jeffrey D. Stark I know that decision tree, and it doesn't really work for my original images because it's limited to what you'd usually find on professional/commercial static websites or blogs with a very small choice of kinds of images.
Let's take this image as an example here. It was the first image I've described in detail. I'm not going to link to that description because it's hopelessly outdated and probably terribly lacking at only a bit over 13,000 characters, and the image does not have a descriptive alt-text yet. It's an old shame, so-to-speak.
Does the image contain text?
Let's say, what the image shows within its borders has 22 bits of text on it, for any definition of text. This could count as yes.
However, of these 22 bits of text, only three are legible in the image as it is, at the resolution at which I've uploaded it: three times a capital M. As I've said, for any definition of text. The other 19 are so small that they're illegible, or they are so small that they can't be identified as text, or they're so tiny that they're invisible at this resolution. The big black sign in the middle with the yellow writing on it has a tree in front of it.
Is it still a yes because, while it isn't readable, there still is text?
Is it a yes for the three capital Ms?
Is it a no because the text does not show itself as text in this image at this resolution? So technically speaking, with the exception of the three capital Ms, there is no text in this image because where there's text in the original, there's just some blurry mush that does not qualify as text in the image as shown?
Or is it a no because I can't transcribe it anyway if I can't read it? Fun fact: I have transcribed all this text. 100% verbatim. And provided translations for everything that isn't English. So "you can't read it anyway" doesn't count because I can read it.
Now comes the kicker: If we pick yes because there is text in the image, the decision tree implies that it is an image of text and nothing else, and that the image-describing process is over after transcribing the text. This wouldn't even work with an image macro.
Does the image contribute meaning to the current page or context?
Does this question even work in this case?
Let's say the post in question is about the world where the image was taken shutting down soon and my avatar in this world disappearing. Because it was when I first posted this image. It's just meant to be a last farewell.
It doesn't add any extra information. This is not a post in a professional commercial or scientific or technological blog. So, does the image contribute meaning, yes or no?
If so:- It's not "a simple graphic or a photograph". It's a digital 3-D rendering, and it's anything but simple.
- It's not "a graph or complex piece of information". Complex, yes. But it isn't a graph, and it isn't a piece of information of the kind you'd have on a scientific website.
- I don't think it "shows content that is redundant to real text nearby".
Is the image purely decorative or not intended for users?
That's debatable. On professional websites and blogs, this question may make sense. In social media where nobody adds decorative images to posts, it doesn't. In the Fediverse which has way higher accessibility standards than 𝕏 or Facebook or Tumblr or Threads or Bluesky or LinkedIn, it makes even less sense.
Is the image’s use not listed above or it’s unclear whatalttext to provide?
Probably.
The top of the article is already a dead give-away: This guide is not meant for social media. Not for the big commercial silos, and even less for the Fediverse where Mastodon re-defines what makes an image description good. Not even two dozen people in the world use social media that support HTML<img>tags in posts.
While professional Web accessibility experts will throw their hands up into the air in utter outrage over 250 characters of alt-text because it's too long, Mastodon users celebrate alt-text that's four times as long.
So this is a case where a whole bunch of edge-cases unhandled by the WAI meet in one place:- A situation in which not the audience comes to the content, but the content comes to the audience without the audience necessarily explicitly seeking out this kind of content.
- Social media with possibilities that vastly exceed those of the big commercial silos, especially regarding character count, while at the same time mostly not supporting full HTML.
- An audience which has defined its own accessibility "rules". Including blind or visually-impaired people who do want to know what something in an image looks like, even if the WAI alt-text guidelines forbid describing it.
- Content that has never been taken into consideration by any alt-text/image description guide out there. Ever.
Trying to force this into the WAI or WCAG guidelines is akin to trying to push a square peg into a round hole that was drilled by people who think all pegs are round.
I mean, as you've just seen, I can't even clearly answer any of the questions in the decision tree.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #WebAccessibilityInitiative #WAI #WCAG #A11y #Accessibility -
I've described all my images since I've learned about alt-texts, and I put more effort and knowledge into them than anyone on Mastodon; CW: long (almost 8,700 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, character limit meta Artikel ansehen Zusammenfassung ansehen
@David Mitchell :CApride: Now listen here.
Ever since I've learned about alt-texts and image descriptions, I've described all my images. And unlike most Mastodon users, I've improved my image-describing further and further.
Whenever I learned something new about image descriptions, be it a rule, a guideline, a good practice or a Mastodon preference, I used this new knowledge in new image descriptions and declared all my previous image descriptions obsolete. And I've learned a lot over the years.
I've learned from Mastodon that if explanations are necessary to understand an image, they must be delivered immediately with the image post. Ever since, I've explained everything in my images that needs explaining. And since all my image posts are about extremely obscure niche topics, they need a whole lot of explanations.
I've learned from a physically disabled Mastodon user that not everyone can access alt-texts. She, for example, can't. Thus, explanations in the alt-text are lost to her. I've learned from her that explanations go into the post text. I've put all my explanations into the post text ever since.
I've learned from Mastodon that Mastodon tends to love long, detailed image descriptions. Considering how obscure the contents of my original images are and how nobody knows what anything in them looks like if they don't see it, I came to the conclusion that someone somewhere out there might need full, detailed descriptions. I've given my original images full, detailed descriptions ever since.
I've learned from various sources that alt-text must only describe what's important within the context of a post. But judging from my observations of Mastodon, its culture and its love for long alt-texts override this rule. If someone wants to know about all the small details in your images, the context doesn't matter. Thus, how detailed my image descriptions are depends on whether or not I have to expect someone being curious about the details.
I've learned by experimentation that Mastodon truncates long external alt-texts from outside at the 1,500-character mark. Also, Hubzilla (where I am) can only display so many characters of alt-text, and alt-text cannot be scrolled. Since the audience of my alt-texts is pretty much exclusively on Mastodon, I've put the full, long, detailed image descriptions into the post text.
I've learned from a blog post that alt-texts must never contain line breaks. Line breaks in alt-texts have a nasty side-effect for screen reader users: After each line break, screen readers assume that they're reading a new alt-text for a new image. And they start whatever they consider an individual image alt-text with something like, "Graphic." Thus, I write all my alt-texts as one single paragraph.
I've learned from another blog post, as well as personal experience with various Fediverse server applications, that alt-texts must never contain the double quotes commonly found on keyboards. Different frontends may misbehave in different ways, some fail very ungracefully. Thus, I no longer use these quotes in my alt-texts.
I've learned from Mastodon that even if there is an image description in the post text, there must always be an accurate and sufficiently detailed image description in the alt-text regardless. Otherwise you risk being sanctioned. I have described all my original images twice ever since: with a long and fully detailed description in the post text and a shorter description in the alt-text.
I've learned from blog posts and websites about alt-texts that text in images must be transcribed verbatim. However, nowhere that I've seen this rule written down, I've seen it mention text that's unreadable in the image while the author knows what's written there. My conclusion is that there is no exception for these texts. I tend to have many such texts. Thus, I transcribe all bits and pieces of text within the borders of my images if I have a way to read them. And I usually have.
I've learned from other blog posts about alt-texts that colours must not only be mentioned in image descriptions, but they must also be described. After all, blind people cannot be expected to know what e.g. Burgundy red is. Also, dimensions must be given not simply in absolute measures, but relatively to what else is in the image or to something that everyone is familiar with, namely the human body. Unfortunately, I've learned that so recently that I only have one original image post in which I make use of these techniques; hence, all my older original image posts count as obsolete.
I've learned from yet elsewhere that races must not be mentioned, and genders must not be assumed. I abide by both when describing meme images. My original images, on the other hand, never contain actual human beings. Whenever I show an avatar, it's always one of my avatars whose gender I have personally defined, and these avatars can't really emulate real-life human phenotypes.
Most of the above has never been taken into consideration by anyone on Mastodon. I'm literally the only one in the Fediverse who takes describing images to such levels.
But I go beyond alt-texts and image descriptions.
I've learned from Mastodon that if there's something, anything in a post of yours that might disturb anyone in some way, the post requires a Mastodon-style content warning that mentions in which way the post is disturbing. Here on Hubzilla, that's a summary. It's the same thing, and Hubzilla had summaries before Mastodon had CWs.
From observing both Mastodon and the Web outside the Fediverse, I've compiled a list of potentially triggering topics. Even excluding national/state/provincial/regional politics, I've gathered 111 of these so far. I do my best to include each one whenever necessary. On top of that, I add CWs for many things I post about because I guess I go onto people's nerves when I post about them (the Fediverse, alt-text, image descriptions, hashtags, character limits, quote-posts, actual quote-posting etc.).
However, Hubzilla is not a Twitter wannabe. It's more like Facebook or blogging software. It only offers a summary (Mastodon: CW) field for posts and DMs, but not for comments (it has two different editors for when you reply and when you don't). I could try to add a summary (Mastodon: CW) using a pair of BBcode tags, and I've done so here, but I know from personal experience that the summary tags do not translate to a Mastodon CW in comments. I'd add an individual CW to each one of my comments, but Mastodon users will neither get an actual CW nor understand that I've tried.
So I double almost all my CW'd topics up with an appropriate set of hashtags. This is in line with the culture where I am: Here on Hubzilla and in its whole software family, we don't force poster-side CWs upon each other. Instead, we have them automatically generated for ourselves, reader-side, tailored to our individual needs. But this requires keywords to trigger the automated hiding of content behind CWs.
Also, I know just what may disturb people. The best example is eye contact. You think that eye contact can only be triggering in full-face portraits of a person looking directly at the viewer? Wrong! It's triggering if there's at least one eye in the image. I've been told that some people in the autistic spectrum can detect an eye in an image if it's only a tiny fraction of a pixel. I have to expect this to extend to other potentially triggering things as well.
Thus, if it's potentially triggering and somewhere within the borders of one of my images, even if it's hardly discernible or completely invisible to the neurotypical, I still consider the whole image potentially triggering, and I treat the image and the whole post as such.
In fact, I've stopped posting potentially triggering images here on Hubzilla altogether. That's because Hubzilla has no way of making Mastodon blank an image out. And not long ago, Mastodon's CWs only hid the post text, but not the images belonging to a post. I can't rule out that certain Mastodon apps still behave this way. So I can't even use CWs to hide a triggering image. This is why I only ever post images on (streams) now: (streams) makes Mastodon blank images out when a post contains one or two certain hashtags.
Again, nobody on Mastodon goes even only nearly that far.
Please tell me in which ways exactly this is still insufficient.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta -
I've described all my images since I've learned about alt-texts, and I put more effort and knowledge into them than anyone on Mastodon; CW: long (almost 8,700 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, character limit meta View article View summary
@David Mitchell :CApride: Now listen here.
Ever since I've learned about alt-texts and image descriptions, I've described all my images. And unlike most Mastodon users, I've improved my image-describing further and further.
Whenever I learned something new about image descriptions, be it a rule, a guideline, a good practice or a Mastodon preference, I used this new knowledge in new image descriptions and declared all my previous image descriptions obsolete. And I've learned a lot over the years.
I've learned from Mastodon that if explanations are necessary to understand an image, they must be delivered immediately with the image post. Ever since, I've explained everything in my images that needs explaining. And since all my image posts are about extremely obscure niche topics, they need a whole lot of explanations.
I've learned from a physically disabled Mastodon user that not everyone can access alt-texts. She, for example, can't. Thus, explanations in the alt-text are lost to her. I've learned from her that explanations go into the post text. I've put all my explanations into the post text ever since.
I've learned from Mastodon that Mastodon tends to love long, detailed image descriptions. Considering how obscure the contents of my original images are and how nobody knows what anything in them looks like if they don't see it, I came to the conclusion that someone somewhere out there might need full, detailed descriptions. I've given my original images full, detailed descriptions ever since.
I've learned from various sources that alt-text must only describe what's important within the context of a post. But judging from my observations of Mastodon, its culture and its love for long alt-texts override this rule. If someone wants to know about all the small details in your images, the context doesn't matter. Thus, how detailed my image descriptions are depends on whether or not I have to expect someone being curious about the details.
I've learned by experimentation that Mastodon truncates long external alt-texts from outside at the 1,500-character mark. Also, Hubzilla (where I am) can only display so many characters of alt-text, and alt-text cannot be scrolled. Since the audience of my alt-texts is pretty much exclusively on Mastodon, I've put the full, long, detailed image descriptions into the post text.
I've learned from a blog post that alt-texts must never contain line breaks. Line breaks in alt-texts have a nasty side-effect for screen reader users: After each line break, screen readers assume that they're reading a new alt-text for a new image. And they start whatever they consider an individual image alt-text with something like, "Graphic." Thus, I write all my alt-texts as one single paragraph.
I've learned from another blog post, as well as personal experience with various Fediverse server applications, that alt-texts must never contain the double quotes commonly found on keyboards. Different frontends may misbehave in different ways, some fail very ungracefully. Thus, I no longer use these quotes in my alt-texts.
I've learned from Mastodon that even if there is an image description in the post text, there must always be an accurate and sufficiently detailed image description in the alt-text regardless. Otherwise you risk being sanctioned. I have described all my original images twice ever since: with a long and fully detailed description in the post text and a shorter description in the alt-text.
I've learned from blog posts and websites about alt-texts that text in images must be transcribed verbatim. However, nowhere that I've seen this rule written down, I've seen it mention text that's unreadable in the image while the author knows what's written there. My conclusion is that there is no exception for these texts. I tend to have many such texts. Thus, I transcribe all bits and pieces of text within the borders of my images if I have a way to read them. And I usually have.
I've learned from other blog posts about alt-texts that colours must not only be mentioned in image descriptions, but they must also be described. After all, blind people cannot be expected to know what e.g. Burgundy red is. Also, dimensions must be given not simply in absolute measures, but relatively to what else is in the image or to something that everyone is familiar with, namely the human body. Unfortunately, I've learned that so recently that I only have one original image post in which I make use of these techniques; hence, all my older original image posts count as obsolete.
I've learned from yet elsewhere that races must not be mentioned, and genders must not be assumed. I abide by both when describing meme images. My original images, on the other hand, never contain actual human beings. Whenever I show an avatar, it's always one of my avatars whose gender I have personally defined, and these avatars can't really emulate real-life human phenotypes.
Most of the above has never been taken into consideration by anyone on Mastodon. I'm literally the only one in the Fediverse who takes describing images to such levels.
But I go beyond alt-texts and image descriptions.
I've learned from Mastodon that if there's something, anything in a post of yours that might disturb anyone in some way, the post requires a Mastodon-style content warning that mentions in which way the post is disturbing. Here on Hubzilla, that's a summary. It's the same thing, and Hubzilla had summaries before Mastodon had CWs.
From observing both Mastodon and the Web outside the Fediverse, I've compiled a list of potentially triggering topics. Even excluding national/state/provincial/regional politics, I've gathered 111 of these so far. I do my best to include each one whenever necessary. On top of that, I add CWs for many things I post about because I guess I go onto people's nerves when I post about them (the Fediverse, alt-text, image descriptions, hashtags, character limits, quote-posts, actual quote-posting etc.).
However, Hubzilla is not a Twitter wannabe. It's more like Facebook or blogging software. It only offers a summary (Mastodon: CW) field for posts and DMs, but not for comments (it has two different editors for when you reply and when you don't). I could try to add a summary (Mastodon: CW) using a pair of BBcode tags, and I've done so here, but I know from personal experience that the summary tags do not translate to a Mastodon CW in comments. I'd add an individual CW to each one of my comments, but Mastodon users will neither get an actual CW nor understand that I've tried.
So I double almost all my CW'd topics up with an appropriate set of hashtags. This is in line with the culture where I am: Here on Hubzilla and in its whole software family, we don't force poster-side CWs upon each other. Instead, we have them automatically generated for ourselves, reader-side, tailored to our individual needs. But this requires keywords to trigger the automated hiding of content behind CWs.
Also, I know just what may disturb people. The best example is eye contact. You think that eye contact can only be triggering in full-face portraits of a person looking directly at the viewer? Wrong! It's triggering if there's at least one eye in the image. I've been told that some people in the autistic spectrum can detect an eye in an image if it's only a tiny fraction of a pixel. I have to expect this to extend to other potentially triggering things as well.
Thus, if it's potentially triggering and somewhere within the borders of one of my images, even if it's hardly discernible or completely invisible to the neurotypical, I still consider the whole image potentially triggering, and I treat the image and the whole post as such.
In fact, I've stopped posting potentially triggering images here on Hubzilla altogether. That's because Hubzilla has no way of making Mastodon blank an image out. And not long ago, Mastodon's CWs only hid the post text, but not the images belonging to a post. I can't rule out that certain Mastodon apps still behave this way. So I can't even use CWs to hide a triggering image. This is why I only ever post images on (streams) now: (streams) makes Mastodon blank images out when a post contains one or two certain hashtags.
Again, nobody on Mastodon goes even only nearly that far.
Please tell me in which ways exactly this is still insufficient.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta -
I've described all my images since I've learned about alt-texts, and I put more effort and knowledge into them than anyone on Mastodon; CW: long (almost 8,700 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, character limit meta Artikel ansehen Zusammenfassung ansehen
@David Mitchell :CApride: Now listen here.
Ever since I've learned about alt-texts and image descriptions, I've described all my images. And unlike most Mastodon users, I've improved my image-describing further and further.
Whenever I learned something new about image descriptions, be it a rule, a guideline, a good practice or a Mastodon preference, I used this new knowledge in new image descriptions and declared all my previous image descriptions obsolete. And I've learned a lot over the years.
I've learned from Mastodon that if explanations are necessary to understand an image, they must be delivered immediately with the image post. Ever since, I've explained everything in my images that needs explaining. And since all my image posts are about extremely obscure niche topics, they need a whole lot of explanations.
I've learned from a physically disabled Mastodon user that not everyone can access alt-texts. She, for example, can't. Thus, explanations in the alt-text are lost to her. I've learned from her that explanations go into the post text. I've put all my explanations into the post text ever since.
I've learned from Mastodon that Mastodon tends to love long, detailed image descriptions. Considering how obscure the contents of my original images are and how nobody knows what anything in them looks like if they don't see it, I came to the conclusion that someone somewhere out there might need full, detailed descriptions. I've given my original images full, detailed descriptions ever since.
I've learned from various sources that alt-text must only describe what's important within the context of a post. But judging from my observations of Mastodon, its culture and its love for long alt-texts override this rule. If someone wants to know about all the small details in your images, the context doesn't matter. Thus, how detailed my image descriptions are depends on whether or not I have to expect someone being curious about the details.
I've learned by experimentation that Mastodon truncates long external alt-texts from outside at the 1,500-character mark. Also, Hubzilla (where I am) can only display so many characters of alt-text, and alt-text cannot be scrolled. Since the audience of my alt-texts is pretty much exclusively on Mastodon, I've put the full, long, detailed image descriptions into the post text.
I've learned from a blog post that alt-texts must never contain line breaks. Line breaks in alt-texts have a nasty side-effect for screen reader users: After each line break, screen readers assume that they're reading a new alt-text for a new image. And they start whatever they consider an individual image alt-text with something like, "Graphic." Thus, I write all my alt-texts as one single paragraph.
I've learned from another blog post, as well as personal experience with various Fediverse server applications, that alt-texts must never contain the double quotes commonly found on keyboards. Different frontends may misbehave in different ways, some fail very ungracefully. Thus, I no longer use these quotes in my alt-texts.
I've learned from Mastodon that even if there is an image description in the post text, there must always be an accurate and sufficiently detailed image description in the alt-text regardless. Otherwise you risk being sanctioned. I have described all my original images twice ever since: with a long and fully detailed description in the post text and a shorter description in the alt-text.
I've learned from blog posts and websites about alt-texts that text in images must be transcribed verbatim. However, nowhere that I've seen this rule written down, I've seen it mention text that's unreadable in the image while the author knows what's written there. My conclusion is that there is no exception for these texts. I tend to have many such texts. Thus, I transcribe all bits and pieces of text within the borders of my images if I have a way to read them. And I usually have.
I've learned from other blog posts about alt-texts that colours must not only be mentioned in image descriptions, but they must also be described. After all, blind people cannot be expected to know what e.g. Burgundy red is. Also, dimensions must be given not simply in absolute measures, but relatively to what else is in the image or to something that everyone is familiar with, namely the human body. Unfortunately, I've learned that so recently that I only have one original image post in which I make use of these techniques; hence, all my older original image posts count as obsolete.
I've learned from yet elsewhere that races must not be mentioned, and genders must not be assumed. I abide by both when describing meme images. My original images, on the other hand, never contain actual human beings. Whenever I show an avatar, it's always one of my avatars whose gender I have personally defined, and these avatars can't really emulate real-life human phenotypes.
Most of the above has never been taken into consideration by anyone on Mastodon. I'm literally the only one in the Fediverse who takes describing images to such levels.
But I go beyond alt-texts and image descriptions.
I've learned from Mastodon that if there's something, anything in a post of yours that might disturb anyone in some way, the post requires a Mastodon-style content warning that mentions in which way the post is disturbing. Here on Hubzilla, that's a summary. It's the same thing, and Hubzilla had summaries before Mastodon had CWs.
From observing both Mastodon and the Web outside the Fediverse, I've compiled a list of potentially triggering topics. Even excluding national/state/provincial/regional politics, I've gathered 111 of these so far. I do my best to include each one whenever necessary. On top of that, I add CWs for many things I post about because I guess I go onto people's nerves when I post about them (the Fediverse, alt-text, image descriptions, hashtags, character limits, quote-posts, actual quote-posting etc.).
However, Hubzilla is not a Twitter wannabe. It's more like Facebook or blogging software. It only offers a summary (Mastodon: CW) field for posts and DMs, but not for comments (it has two different editors for when you reply and when you don't). I could try to add a summary (Mastodon: CW) using a pair of BBcode tags, and I've done so here, but I know from personal experience that the summary tags do not translate to a Mastodon CW in comments. I'd add an individual CW to each one of my comments, but Mastodon users will neither get an actual CW nor understand that I've tried.
So I double almost all my CW'd topics up with an appropriate set of hashtags. This is in line with the culture where I am: Here on Hubzilla and in its whole software family, we don't force poster-side CWs upon each other. Instead, we have them automatically generated for ourselves, reader-side, tailored to our individual needs. But this requires keywords to trigger the automated hiding of content behind CWs.
Also, I know just what may disturb people. The best example is eye contact. You think that eye contact can only be triggering in full-face portraits of a person looking directly at the viewer? Wrong! It's triggering if there's at least one eye in the image. I've been told that some people in the autistic spectrum can detect an eye in an image if it's only a tiny fraction of a pixel. I have to expect this to extend to other potentially triggering things as well.
Thus, if it's potentially triggering and somewhere within the borders of one of my images, even if it's hardly discernible or completely invisible to the neurotypical, I still consider the whole image potentially triggering, and I treat the image and the whole post as such.
In fact, I've stopped posting potentially triggering images here on Hubzilla altogether. That's because Hubzilla has no way of making Mastodon blank an image out. And not long ago, Mastodon's CWs only hid the post text, but not the images belonging to a post. I can't rule out that certain Mastodon apps still behave this way. So I can't even use CWs to hide a triggering image. This is why I only ever post images on (streams) now: (streams) makes Mastodon blank images out when a post contains one or two certain hashtags.
Again, nobody on Mastodon goes even only nearly that far.
Please tell me in which ways exactly this is still insufficient.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta -
I've described all my images since I've learned about alt-texts, and I put more effort and knowledge into them than anyone on Mastodon; CW: long (almost 8,700 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, alt-text meta, image description meta, character limit meta Artikel ansehen Zusammenfassung ansehen
@David Mitchell :CApride: Now listen here.
Ever since I've learned about alt-texts and image descriptions, I've described all my images. And unlike most Mastodon users, I've improved my image-describing further and further.
Whenever I learned something new about image descriptions, be it a rule, a guideline, a good practice or a Mastodon preference, I used this new knowledge in new image descriptions and declared all my previous image descriptions obsolete. And I've learned a lot over the years.
I've learned from Mastodon that if explanations are necessary to understand an image, they must be delivered immediately with the image post. Ever since, I've explained everything in my images that needs explaining. And since all my image posts are about extremely obscure niche topics, they need a whole lot of explanations.
I've learned from a physically disabled Mastodon user that not everyone can access alt-texts. She, for example, can't. Thus, explanations in the alt-text are lost to her. I've learned from her that explanations go into the post text. I've put all my explanations into the post text ever since.
I've learned from Mastodon that Mastodon tends to love long, detailed image descriptions. Considering how obscure the contents of my original images are and how nobody knows what anything in them looks like if they don't see it, I came to the conclusion that someone somewhere out there might need full, detailed descriptions. I've given my original images full, detailed descriptions ever since.
I've learned from various sources that alt-text must only describe what's important within the context of a post. But judging from my observations of Mastodon, its culture and its love for long alt-texts override this rule. If someone wants to know about all the small details in your images, the context doesn't matter. Thus, how detailed my image descriptions are depends on whether or not I have to expect someone being curious about the details.
I've learned by experimentation that Mastodon truncates long external alt-texts from outside at the 1,500-character mark. Also, Hubzilla (where I am) can only display so many characters of alt-text, and alt-text cannot be scrolled. Since the audience of my alt-texts is pretty much exclusively on Mastodon, I've put the full, long, detailed image descriptions into the post text.
I've learned from a blog post that alt-texts must never contain line breaks. Line breaks in alt-texts have a nasty side-effect for screen reader users: After each line break, screen readers assume that they're reading a new alt-text for a new image. And they start whatever they consider an individual image alt-text with something like, "Graphic." Thus, I write all my alt-texts as one single paragraph.
I've learned from another blog post, as well as personal experience with various Fediverse server applications, that alt-texts must never contain the double quotes commonly found on keyboards. Different frontends may misbehave in different ways, some fail very ungracefully. Thus, I no longer use these quotes in my alt-texts.
I've learned from Mastodon that even if there is an image description in the post text, there must always be an accurate and sufficiently detailed image description in the alt-text regardless. Otherwise you risk being sanctioned. I have described all my original images twice ever since: with a long and fully detailed description in the post text and a shorter description in the alt-text.
I've learned from blog posts and websites about alt-texts that text in images must be transcribed verbatim. However, nowhere that I've seen this rule written down, I've seen it mention text that's unreadable in the image while the author knows what's written there. My conclusion is that there is no exception for these texts. I tend to have many such texts. Thus, I transcribe all bits and pieces of text within the borders of my images if I have a way to read them. And I usually have.
I've learned from other blog posts about alt-texts that colours must not only be mentioned in image descriptions, but they must also be described. After all, blind people cannot be expected to know what e.g. Burgundy red is. Also, dimensions must be given not simply in absolute measures, but relatively to what else is in the image or to something that everyone is familiar with, namely the human body. Unfortunately, I've learned that so recently that I only have one original image post in which I make use of these techniques; hence, all my older original image posts count as obsolete.
I've learned from yet elsewhere that races must not be mentioned, and genders must not be assumed. I abide by both when describing meme images. My original images, on the other hand, never contain actual human beings. Whenever I show an avatar, it's always one of my avatars whose gender I have personally defined, and these avatars can't really emulate real-life human phenotypes.
Most of the above has never been taken into consideration by anyone on Mastodon. I'm literally the only one in the Fediverse who takes describing images to such levels.
But I go beyond alt-texts and image descriptions.
I've learned from Mastodon that if there's something, anything in a post of yours that might disturb anyone in some way, the post requires a Mastodon-style content warning that mentions in which way the post is disturbing. Here on Hubzilla, that's a summary. It's the same thing, and Hubzilla had summaries before Mastodon had CWs.
From observing both Mastodon and the Web outside the Fediverse, I've compiled a list of potentially triggering topics. Even excluding national/state/provincial/regional politics, I've gathered 111 of these so far. I do my best to include each one whenever necessary. On top of that, I add CWs for many things I post about because I guess I go onto people's nerves when I post about them (the Fediverse, alt-text, image descriptions, hashtags, character limits, quote-posts, actual quote-posting etc.).
However, Hubzilla is not a Twitter wannabe. It's more like Facebook or blogging software. It only offers a summary (Mastodon: CW) field for posts and DMs, but not for comments (it has two different editors for when you reply and when you don't). I could try to add a summary (Mastodon: CW) using a pair of BBcode tags, and I've done so here, but I know from personal experience that the summary tags do not translate to a Mastodon CW in comments. I'd add an individual CW to each one of my comments, but Mastodon users will neither get an actual CW nor understand that I've tried.
So I double almost all my CW'd topics up with an appropriate set of hashtags. This is in line with the culture where I am: Here on Hubzilla and in its whole software family, we don't force poster-side CWs upon each other. Instead, we have them automatically generated for ourselves, reader-side, tailored to our individual needs. But this requires keywords to trigger the automated hiding of content behind CWs.
Also, I know just what may disturb people. The best example is eye contact. You think that eye contact can only be triggering in full-face portraits of a person looking directly at the viewer? Wrong! It's triggering if there's at least one eye in the image. I've been told that some people in the autistic spectrum can detect an eye in an image if it's only a tiny fraction of a pixel. I have to expect this to extend to other potentially triggering things as well.
Thus, if it's potentially triggering and somewhere within the borders of one of my images, even if it's hardly discernible or completely invisible to the neurotypical, I still consider the whole image potentially triggering, and I treat the image and the whole post as such.
In fact, I've stopped posting potentially triggering images here on Hubzilla altogether. That's because Hubzilla has no way of making Mastodon blank an image out. And not long ago, Mastodon's CWs only hid the post text, but not the images belonging to a post. I can't rule out that certain Mastodon apps still behave this way. So I can't even use CWs to hide a triggering image. This is why I only ever post images on (streams) now: (streams) makes Mastodon blank images out when a post contains one or two certain hashtags.
Again, nobody on Mastodon goes even only nearly that far.
Please tell me in which ways exactly this is still insufficient.
#Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #AltText #AltTextMeta #CWAltTextMeta #ImageDescription #ImageDescriptions #ImageDescriptionMeta #CWImageDescriptionMeta #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #Hashtag #Hashtags #HashtagMeta #CWHashtagMeta -
Hey literally every dev, did you know you can make #OpenGraph #OG images accessible with ? <meta property="og:image:alt" content="A short descriptive phrase" /> standards.scangov.org/ogimagealt/ #A11y #Accessibility #ATproto
Open Graph image alt -
@OpenComputeDesign I have a screenshot where when I resized an OpenGL window, graphical content from a browser tab *that was no longer open* showed up.
Given, the video side of my computer is messed up by #Nvidia , 😐 but... yikes, that shouldn't be possible at all. So applications can just read video memory from other processes?? That's a use-after-free #vuln .
See the Alt Text for more.... -
MINISFORUM MS-A1 mini PC is now available with a Ryzen 9 9950X processor
The MINISFORUM MS-A1 is a compact desktop computer that measures 189.5 x 186 x 48mm (7.46″ x 7.32″ x 1.89″), features a robust set of ports that includes USB4, OCuLink, and dual 2.5 Gb Ethernet connectors.
Unlike most smaller mini PCs, the MS-A1 also has an AMD A5 socket that allows you to bring your own processor or upgrade to a more powerful CPU in the future. But if that feels like too much trouble, you can also buy a system that comes with a CPU pre-installed. When the MS-A1 first launched earlier this year it was available either as a barebones computer or with an AMD Ryzen 7 8700G chip. Now the company is selling a version with a higher-performance Ryzen 9 9950X processor.
Both chips are desktop processors that are compatible with motherboards that support AMD’s AM5 chipset. But the Ryzen 7 8700G is a lower-power processor with decent integrated graphics, while the Ryzen 9 9950HX is a higher-performance chip with far more processing power, but less impressive graphics since it’s often paired with a discrete GPU.
Ryzen 7 8700GRyzen 9 9950HXCPU8-cores / 16 threads
Zen 4
4.2 GHz base / 5.1 GHz max freq
24MB total cache
65W TDP (default)16-cores / 32-threads
Zen 5
4.3 GHz base / 5.7 GHz max freq
81MB total cache
170W TDP (default)
100W TDP (as configured in MS-A1)GPUAMD Radeon 780M
12 x RDNA 3 cores
Up to 2.9 GHzAMD Radeon Graphics
2 RDNA 2 cores
2.2 GHzThe MS-A1 is available as a barebones computer (without any memory, storage, or processor) for $259, or you can pay $919 or more for a model with a Ryzen 9 9950X processor. Theoretically it might be cheaper to purchase a barebones model and then buy that processor separately – it currently sells for around $599 or less. But there’s something to be said for the convenience of not having to install the processor yourself.
As for graphics, the integrated GPU is good enough to handle video playback and some hardware-accelerated graphics for web browsing and other apps. But if you want to do any gaming or graphics work, you’ll probably want a discrete GPU.
hile there’s no room inside the MS-A1 chassis for a discrete GPU, you can connect an external graphics dock thanks to the computer’s 64 Gbps OcuLink connector. Theoretically you could also use the USB4 port… but not with an AMD Ryzen 7000 or Ryzen 9000 series processor.
That’s because while this port functions as a 40 Gbps USB4 port when used with a Ryzen 8000 series processor, it tops out at USB 3.0 speeds when the system is configured with Ryzen 7000 or Ryzen 9000 series processors. The USB Type-C port does support DisplayPort Alt Mode no matter what processor you’re using though, so it can always be used as a video output.
Inside the computer there are four M.2 slots with support for PCIe 4.0 NVMe SSDs and two SODIMM slots for up to 96GB of total DDR5-5200 memory.
Ports include:
- x OCuLink (64 Gbps)
- 1 x DisplayPort 2.0
- 1 x HDMI 2.1
- 1 x USB4 Type-C (40 Gbps w/DisplayPort Alt Mode, 10 Gbps with Ryzen 7000/9000)
- 1 x USB 3.2 Gen 2 Type-A (10 Gbps)
- 2 x USB 3.2 Gen 1 Type-A (5 Gbps)
- 2 x USB 2.0 Type-A (480 Mbps)
- 1 x 3.5mm audio
- 2 x 2.5 GbE Ethernet(RTL8125BG)
- 1 x DC power input (19V/12.63A 240W)
via VideoCardz
-
OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]
OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.
Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.
We’ve configured the virtual machine as follows:
We’ve configured a virtual machine to run with:
- Machine type: [1998] Super Socket 7
- Machine: [SiS 5591] Gigabyte GA-5SG100
- CPU: Intel Pentium @ 166 MHz
- Memory: 128 MB
- Video: [ISA16] Cirrus Logic GD5434
- Keyboard: AT Keyboard
- Mouse: PS/2 Mouse
- Sound card: [ISA16] Sound Blaster 16 PnP
- Floppy disk controller: Internal device
- Hard disk controller 1: Internal device
- New hard disk: os2warp452.vhd
- C/H/S: 1054/16/63
- Size: 518 MB
- Bus: IDE
- Channel: 0:0
- CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)
Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called
mcp2-refresh-boot-en.isoto the CD-ROM reader, then configure BIOS as necessary.To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.
After that, we save the changes and restart the virtual machine.
The installer starts by telling you to insert the installation CD-ROM to the drive.
In this case, right-click on the CD-ROM icon, select “Insert…”, select
mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.After that, you should be able to see this welcome screen:
Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.
Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.
Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.
After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:
Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.
Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.
After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.
After that, this partition should be created.
We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.
You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.
Press ENTER again, then select “Use existing partition”.
Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.
Press ENTER, and you should see the menu box below:
Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.
Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.
At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.
Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:
Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.
Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.
After that, the installation of the base system begins.
After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.
After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.
First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.
Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”
Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.
We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.
Once we’ve selected OK, we’re then presented with a set of packages to install.
As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.
Once we clicked Next, we’re presented with a prompt to identify ourselves.
After that, we’re given another set of software packages to install. They represent the client services for OS/2.
Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.
We went to create a new ID and a password for the sharing service
Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”
Once we pressed OK, we’ve seen this result:
Now, we’ve pressed Install, and a confirmation dialog box appeared.
Now, the installation of the remaining system files started here.
Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.
We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.
After that, the remaining portions of the installation started. This is part one of the long waiting journey!
After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.
After that, the long waiting journey continues…
The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.
We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.
Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.
We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…
After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.
Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.
Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!
Nostalgic, isn’t it?
#86Box #Linux #news #OS2 #OS2Warp #OS2Warp4 #OS2Warp452 #Retrocomputing #Tech #Technology #update -
OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]
OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.
Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.
We’ve configured the virtual machine as follows:
We’ve configured a virtual machine to run with:
- Machine type: [1998] Super Socket 7
- Machine: [SiS 5591] Gigabyte GA-5SG100
- CPU: Intel Pentium @ 166 MHz
- Memory: 128 MB
- Video: [ISA16] Cirrus Logic GD5434
- Keyboard: AT Keyboard
- Mouse: PS/2 Mouse
- Sound card: [ISA16] Sound Blaster 16 PnP
- Floppy disk controller: Internal device
- Hard disk controller 1: Internal device
- New hard disk: os2warp452.vhd
- C/H/S: 1054/16/63
- Size: 518 MB
- Bus: IDE
- Channel: 0:0
- CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)
Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called
mcp2-refresh-boot-en.isoto the CD-ROM reader, then configure BIOS as necessary.To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.
After that, we save the changes and restart the virtual machine.
The installer starts by telling you to insert the installation CD-ROM to the drive.
In this case, right-click on the CD-ROM icon, select “Insert…”, select
mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.After that, you should be able to see this welcome screen:
Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.
Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.
Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.
After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:
Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.
Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.
After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.
After that, this partition should be created.
We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.
You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.
Press ENTER again, then select “Use existing partition”.
Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.
Press ENTER, and you should see the menu box below:
Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.
Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.
At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.
Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:
Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.
Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.
After that, the installation of the base system begins.
After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.
After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.
First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.
Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”
Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.
We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.
Once we’ve selected OK, we’re then presented with a set of packages to install.
As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.
Once we clicked Next, we’re presented with a prompt to identify ourselves.
After that, we’re given another set of software packages to install. They represent the client services for OS/2.
Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.
We went to create a new ID and a password for the sharing service
Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”
Once we pressed OK, we’ve seen this result:
Now, we’ve pressed Install, and a confirmation dialog box appeared.
Now, the installation of the remaining system files started here.
Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.
We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.
After that, the remaining portions of the installation started. This is part one of the long waiting journey!
After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.
After that, the long waiting journey continues…
The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.
We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.
Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.
We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…
After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.
Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.
Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!
Nostalgic, isn’t it?
#86Box #Linux #news #OS2 #OS2Warp #OS2Warp4 #OS2Warp452 #Retrocomputing #Tech #Technology #update -
OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]
OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.
Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.
We’ve configured the virtual machine as follows:
We’ve configured a virtual machine to run with:
- Machine type: [1998] Super Socket 7
- Machine: [SiS 5591] Gigabyte GA-5SG100
- CPU: Intel Pentium @ 166 MHz
- Memory: 128 MB
- Video: [ISA16] Cirrus Logic GD5434
- Keyboard: AT Keyboard
- Mouse: PS/2 Mouse
- Sound card: [ISA16] Sound Blaster 16 PnP
- Floppy disk controller: Internal device
- Hard disk controller 1: Internal device
- New hard disk: os2warp452.vhd
- C/H/S: 1054/16/63
- Size: 518 MB
- Bus: IDE
- Channel: 0:0
- CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)
Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called
mcp2-refresh-boot-en.isoto the CD-ROM reader, then configure BIOS as necessary.To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.
After that, we save the changes and restart the virtual machine.
The installer starts by telling you to insert the installation CD-ROM to the drive.
In this case, right-click on the CD-ROM icon, select “Insert…”, select
mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.After that, you should be able to see this welcome screen:
Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.
Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.
Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.
After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:
Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.
Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.
After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.
After that, this partition should be created.
We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.
You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.
Press ENTER again, then select “Use existing partition”.
Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.
Press ENTER, and you should see the menu box below:
Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.
Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.
At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.
Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:
Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.
Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.
After that, the installation of the base system begins.
After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.
After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.
First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.
Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”
Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.
We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.
Once we’ve selected OK, we’re then presented with a set of packages to install.
As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.
Once we clicked Next, we’re presented with a prompt to identify ourselves.
After that, we’re given another set of software packages to install. They represent the client services for OS/2.
Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.
We went to create a new ID and a password for the sharing service
Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”
Once we pressed OK, we’ve seen this result:
Now, we’ve pressed Install, and a confirmation dialog box appeared.
Now, the installation of the remaining system files started here.
Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.
We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.
After that, the remaining portions of the installation started. This is part one of the long waiting journey!
After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.
After that, the long waiting journey continues…
The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.
We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.
Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.
We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…
After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.
Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.
Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!
Nostalgic, isn’t it?
#86Box #Linux #news #OS2 #OS2Warp #OS2Warp4 #OS2Warp452 #Retrocomputing #Tech #Technology #update -
OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]
OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.
Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.
We’ve configured the virtual machine as follows:
We’ve configured a virtual machine to run with:
- Machine type: [1998] Super Socket 7
- Machine: [SiS 5591] Gigabyte GA-5SG100
- CPU: Intel Pentium @ 166 MHz
- Memory: 128 MB
- Video: [ISA16] Cirrus Logic GD5434
- Keyboard: AT Keyboard
- Mouse: PS/2 Mouse
- Sound card: [ISA16] Sound Blaster 16 PnP
- Floppy disk controller: Internal device
- Hard disk controller 1: Internal device
- New hard disk: os2warp452.vhd
- C/H/S: 1054/16/63
- Size: 518 MB
- Bus: IDE
- Channel: 0:0
- CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)
Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called
mcp2-refresh-boot-en.isoto the CD-ROM reader, then configure BIOS as necessary.To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.
After that, we save the changes and restart the virtual machine.
The installer starts by telling you to insert the installation CD-ROM to the drive.
In this case, right-click on the CD-ROM icon, select “Insert…”, select
mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.After that, you should be able to see this welcome screen:
Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.
Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.
Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.
After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:
Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.
Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.
After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.
After that, this partition should be created.
We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.
You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.
Press ENTER again, then select “Use existing partition”.
Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.
Press ENTER, and you should see the menu box below:
Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.
Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.
At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.
Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:
Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.
Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.
After that, the installation of the base system begins.
After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.
After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.
First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.
Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”
Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.
We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.
Once we’ve selected OK, we’re then presented with a set of packages to install.
As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.
Once we clicked Next, we’re presented with a prompt to identify ourselves.
After that, we’re given another set of software packages to install. They represent the client services for OS/2.
Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.
We went to create a new ID and a password for the sharing service
Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”
Once we pressed OK, we’ve seen this result:
Now, we’ve pressed Install, and a confirmation dialog box appeared.
Now, the installation of the remaining system files started here.
Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.
We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.
After that, the remaining portions of the installation started. This is part one of the long waiting journey!
After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.
After that, the long waiting journey continues…
The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.
We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.
Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.
We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…
After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.
Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.
Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!
Nostalgic, isn’t it?
#86Box #Linux #news #OS2 #OS2Warp #OS2Warp4 #OS2Warp452 #Retrocomputing #Tech #Technology #update -
OS/2 Warp 4.52 on 86Box with Super Socket 7 [1998]
OS/2 was a proprietary operating system that was initially developed by IBM in partnership with Microsoft as a replacement of DOS before it became entirely developed by IBM. OS/2 Warp 4 was officially released in 1996, and development slowed down to a halt because it failed to compete Microsoft Windows. OS/2 Warp 4.52 was officially released in December 2001, and this year, it will celebrate its 25th year anniversary.
Our focus in this article is testing OS/2 Warp 4.52 on an 86Box emulated machine with a Super Socket 7 [1998] motherboard. You can download it from here.
We’ve configured the virtual machine as follows:
We’ve configured a virtual machine to run with:
- Machine type: [1998] Super Socket 7
- Machine: [SiS 5591] Gigabyte GA-5SG100
- CPU: Intel Pentium @ 166 MHz
- Memory: 128 MB
- Video: [ISA16] Cirrus Logic GD5434
- Keyboard: AT Keyboard
- Mouse: PS/2 Mouse
- Sound card: [ISA16] Sound Blaster 16 PnP
- Floppy disk controller: Internal device
- Hard disk controller 1: Internal device
- New hard disk: os2warp452.vhd
- C/H/S: 1054/16/63
- Size: 518 MB
- Bus: IDE
- Channel: 0:0
- CD-ROM drive 1: ATAPI (0:1) KENWOOD CD-ROM UCR-421 208E (72x)
Once everything is configured as above, we can now start the virtual machine. Insert the boot disc called
mcp2-refresh-boot-en.isoto the CD-ROM reader, then configure BIOS as necessary.To be more specific, we need to go to the BIOS setup using DEL and change the boot order so that CD-ROM goes first with PGUP/PGDN.
After that, we save the changes and restart the virtual machine.
The installer starts by telling you to insert the installation CD-ROM to the drive.
In this case, right-click on the CD-ROM icon, select “Insert…”, select
mcp2-refresh-install-en.iso, and double-click it. Then, press ENTER.After that, you should be able to see this welcome screen:
Press ENTER, and you’ll be taken to another screen that welcomes you to the operating system installer.
Press ENTER. At this point, since it’s a fresh installation, and the hard drive is already empty, you’ll get the “Volumes Too Small” message. This means that you’ll need to create a single partition that will be used to install OS/2 Warp 4.52 to.
Press ENTER, and you’ll get a warning message telling you that all data on modified volumes will be deleted, and that backups should be made. Since there is no data on the hard drive, you can safely ignore this warning. Just press ENTER.
After that, you’ll be taken to the partitioning screen where you’ll be presented with the logical volume manager, with the logical view being the default. Press F5, and you’ll be taken to a screen where you can see your hard disk, such as the below screenshot:
Here, you can create a physical partition. Press TAB, then ENTER, and you’ll be presented with those options.
Press ENTER to create a new partition. You’ll be asked whether this partition is going to be logical or primary. Select “Primary partition”.
After you select it, you’ll be presented with various dialog boxes telling you to specify the size and the name of the partition, as well as the position of the partition. Select “Create at the start of the free space”, then enter the partition name, then the size.
After that, this partition should be created.
We are not done yet when it comes to partitioning, so we need to go back to the logical view. Press ENTER, then press ENTER on “Create a new volume”. Then, select “Create a volume that can be made bootable”, then C:.
You’ll be brought back to the physical view that will tell you to choose a physical disk. Below the physical disk, the logical partition should be shown at the bottom of the screen. Press ENTER when this dialog box appears.
Press ENTER again, then select “Use existing partition”.
Now, a new logical volume will appear with the partition name that you’ve chosen. However, it’s still not ready yet for installation, since there are extra steps that are needed. We need to make it installable.
Press ENTER, and you should see the menu box below:
Select “Set the volume installable”. The status of your logical volume should change from “Startable” to “Installable”. Afterwards, press F3, and press ENTER when “Save the changes and exit” is highlighted.
Afterwards, you should be able to see the below dialog box telling you to insert the boot CD-ROM to the drive and restart the virtual machine using CTRL + ALT + DEL.
At this point, we need to change the BIOS boot order to avoid the black screen issue. Press DEL, go to BIOS Features Setup, and change the boot order so that CD-ROM goes first.
Then, exit the BIOS setup while saving changes, and follow the instructions all the way until the following screen shows up:
Verify that “Volume C” shows up. If not, you’ll have to configure the partitions again until the volume shows up in this screen. Since we’ve already configured everything, and that Volume C corresponds to our hard disk, press ENTER when “Accept the volume” is highlighted.
Then, the installer asked us whether we’d like to format it slowly or quickly. This is a clean installation, so we’ve chosen a quick format. Then, the installer asked us whether we’d like to use FAT or HPFS. We’ve chosen the HPFS file system.
After that, the installation of the base system begins.
After that, the virtual machine will automatically restart. Go back to the BIOS setup and make sure that the C drive comes first before the CD-ROM.
After that, OS/2 Warp should boot up to the GUI portion of the installer. The first thing you’ll be presented with is the configuration of the system, including the country, the graphics adapter, and the sound adapter.
First of all, we went to “Multimedia Device Support”, and added the SoundBlaster 16 PnP device to the list of installed devices.
Afterwards, we’re presented with another set of configuration, once we’ve selected “Next”. SInce there’s no need to configure anything on that screen, we’ve just clicked Next. Then, it presented us with options to choose the country/region, with the default selected country being “United States.”
Then, the printer configuraion window has shown up. SInce there’s no printer installed, we’ll leave it as it is.
We’re then presented with the graphics adapter configuration. It automatically selected the Cirrus Logic graphics adapter as we’ve chosen earlier for the virtual machine configuration.
Once we’ve selected OK, we’re then presented with a set of packages to install.
As soon as we clicked “Next”, we’re presented with another wizard that lets us configure some more services.
Once we clicked Next, we’re presented with a prompt to identify ourselves.
After that, we’re given another set of software packages to install. They represent the client services for OS/2.
Once we clicked Next, we’re presented with another configuration screen where we needed to configure the user ID and password for the file and print sharing services, and the network adapter and protocol services.
We went to create a new ID and a password for the sharing service
Then, we went to “Network Adapters and Protocol Services”, and a dialog box that told us to add a network adapter appeared. Since we don’t intend to have internet connectivity in this installation of OS/2 Warp 4.52, we’ve selected “No network adapter.”
Once we pressed OK, we’ve seen this result:
Now, we’ve pressed Install, and a confirmation dialog box appeared.
Now, the installation of the remaining system files started here.
Once it was done copying files, we’re asked whether to use the defaults for the monitor type or to use the display adapter utility program.
We’ve chosen the defaults, and an informational box appeared stating that the screen might flicker while the testing was underway.
After that, the remaining portions of the installation started. This is part one of the long waiting journey!
After the restart, depending on the region selected, OS/2 Warp 4.52 might tell you that there’s something wrong in the CONFIG.SYS file related to the codepage, just like below.
After that, the long waiting journey continues…
The system then restarted, and the desktop finally appeared, but with another dialog box asking us whether we needed to install sets of extra tools or not.
We’ve chosen the biggest option, which was “OS/2 Toolkit (English only)”. Then, we’ve clicked on Install once we’ve inserted the boot disk back to the CD-ROM drive.
Then, a configuration window where it tells us to configure the installation of the OS/2 Toolkit, just like below.
We’ve chosen to install everything, so we just chose Install. Yet another long wait journey starts…
After the installation of the toolkit reached 100%, a dialog box that told us that the installation was successful showed up. Once done, we’ve clicked on Quit in the toolkit installer.
Since the dialog box told us that the CONFIG.SYS file was modified and that we needed to restart the virtual machine. Therefore, we’ve clicked on Exit, then right-clicked on an empty area around the desktop and chose “Shut down”.
Once the shut down was done, we had to press CTRL + ALT + DEL in the virtual machine side. After that, the system booted up to the desktop, and the sound works!
Nostalgic, isn’t it?
#86Box #Linux #news #OS2 #OS2Warp #OS2Warp4 #OS2Warp452 #Retrocomputing #Tech #Technology #update