this post was submitted on 27 Apr 2024
232 points (93.3% liked)
Technology
57435 readers
3682 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
My job in the a non technical field relies on a laptop to run a label printer, the laptop is ancient and I already had to install revOS on it so that printing labels isn't horribly bogged down waiting on the laptop to load the simple printer program. Is there anyway that proton would be able to run that program? Probably not because of all lack of driver support, if anyone has any ideas I'm all ear, even just pointing me in a direction would be appreciated!
This sounds interesting. What the hell is RevOS? What kind of label maker is that? Does it have a name? Do you know what kind of cable it's using to communicate with the pc?
Yeah it's brand name is kiaro it just uses a usb to connect to the laptop, and revOS is basically just a custom windows install that has as much of the bloatware removed as possible as well as some UI mods to make it feel more like old school windows a little bit. The laptop is from like pre 2010 so Microsoft is slowly killing it's performance with all the bloatware crap. Kinda ridiculous that they don't take older hardware performance very seriously on windows the thing is just trying to run simple GUI printer software and it was struggling hard before revOS.
This is what I think one need to do to test if that would work
If the device is a COM device in windows then I think it should just work out of the box. If not, then the entire device needs to be forwarded using udev rules to wine. Let me know if you want to attempt this :)