this post was submitted on 09 Nov 2023
1805 points (99.2% liked)

Science Memes

10905 readers
1171 users here now

Welcome to c/science_memes @ Mander.xyz!

A place for majestic STEMLORD peacocking, as well as memes about the realities of working in a lab.



Rules

  1. Don't throw mud. Behave like an intellectual and remember the human.
  2. Keep it rooted (on topic).
  3. No spam.
  4. Infographics welcome, get schooled.

This is a science community. We use the Dawkins definition of meme.



Research Committee

Other Mander Communities

Science and Research

Biology and Life Sciences

Physical Sciences

Humanities and Social Sciences

Practical and Applied Sciences

Memes

Miscellaneous

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 9 points 1 year ago (4 children)

On that Windows 95 anecdote, by the way, beyond gaming that's also one of the advantages of wine. Pretty sure their software would run perfectly on Linux with wine.

[–] [email protected] 29 points 1 year ago* (last edited 1 year ago) (2 children)

Not usually. The main thing for lab equipment is that it is controlling hardware. So you are often using proprietary drivers for custom hardware. Wine can't handle drivers and for security reasons can't get low level hardware access.

[–] [email protected] 8 points 1 year ago* (last edited 1 year ago) (1 children)

On the other hand, something like ReactOS could, in theory, work if it was much more mature and had more developers behind it.

[–] [email protected] 6 points 1 year ago

Not really I'm afraid. ReactOS is focused on implementing the old APIs which allows software that used those APIs to function.

But my experience with old proprietary software from that era is that they were trying to do something which was hard at the time. So they wrote their software with lots of clever tricks and hacks, to make the thing do the thing. This can be as simple as manually invoking interrupts and using undocumented APIs, to setting up non protected memory and communicating with the hardware directly.

I've seen cases where the software would only run with a specific version of Windows 95 and only with specific chipsets. Even changing the cpu from an Intel to a Cyrix for example could cause issues.

I was involved as an intern with a project to fix something like this a long time ago. We chose to simply reverse engineer the hardware interface, put in a custom controller to handle it and write modern software. It took a lot of doing and we lost some features, but the original system was beyond saving.

As time went on more and more hardware abstraction is applied, so I would hope this issue would be fixed in the future. But the whole of the 90s and early 2000s is a big issue.

[–] [email protected] 4 points 1 year ago

Ah yeah, drivers are another thing entirely. Especially for what I imagine is very proprietary undocumented hardware. The only thing that can help there is a reverse engineer / kernel module dev.

load more comments (1 replies)