Doesn’t every printer work with CUPS?
Claude writing a macOS driver for my obscure HP printer built only for Windows
121–130 of 241 posts
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#122Reminded me of when I had a Teletype ASR33 on AirPrint (https://github.com/hughpyle/ASR33/tree/master/cups). With LLMs that would have taken a half hour. It would have maybe been less fun? but there's a lot of time faffing around on PPD that I'll never get back.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#123[dead]
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#124I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
Are we either in a dangerous time where we'll run out of people that have weeks to months, and the resolution/boredom/ability to figure this sort of thing out?
Or are we in a really cool time where we've solved everything so much so many times we can focus on other things?
Tertiary question: If answer two, what the fuck is that?
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#125I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
Ditto (except not being an AI detractor): I used Claude and Codex to reverse engineer the proprietary protocol for controlling Devialet amplifiers and then build an iOS controller app to replace the manufacturer's abandoned official app.
The whole thing took about a day, spread out over a week or so. Without AI, I wouldn't have even started the project, because I couldn't spare the time it would have taken.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#126Earlier quoted context omitted.
For the amount of electricity wasted by the LLM in the data center it would have been more efficient to buy a new printer that works out of the box.
Redditors actually believe this
Also, they seem to care about wasting electricity but doesn’t bat an eye of discarding a perfectly fine printer.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#127I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
I wonder how hard it would be to create various firmware updaters for drives or other devices.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#128Very cool. I want to do something similar to ressurect old Orb disks from over 25 years ago.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#129I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
I wonder how hard it would be to create various firmware updaters for drives or other devices.
Firmware is a lot harder for a whole host of reasons but it is possible / I've done it.
The odds of success go up a LOT when the stock firmware is easy to extract and reverse engineer.
Re: Claude writing a macOS driver for my obscure HP printer built only for Windows
#130I was able to (through heavy Claude use) successfully reverse engineer a golf cart motor controller that is programmable over USB, but only was supported by a Windows application. Claude walked me through using ILSpy on the .NET assembly, using Wireshark to capture the protocol over USB, and to completely map out all of the functionality in the Windows application. The output was a portable C library and CLI program…
Ditto (except not being an AI detractor): I used Claude and Codex to reverse engineer the proprietary protocol for controlling Devialet amplifiers and then build an iOS controller app to replace the manufacturer's abandoned official app. The whole thing took about a day, spread out over a week or so. Without AI, I wouldn't have even started the project, because I couldn't spare the time it would have taken.
i looked those up, that's pricey gear. is that a similar app abandonment like with Sonos deprecating and moving to newer protocols?