Remix.run Logo
▲ linzhangrun 3 hours ago

Seriously speaking, I feel the market is sorely lacking an Agent for the large number of existing devices running WinXP, Win7, and the like. Not for developing on them, but for all kinds of debugging work it would be very useful; nowadays I'm used to just directing an Agent for everything.

▲xmeadow 36 minutes ago | parent | next [-]

https://github.com/xmeadow/igor runs on react OS but was tested on XP and win7. Works flawlessly.

▲keyle 20 minutes ago | parent [-]

I wonder what kind of sandboxing you'd get on those machines though. Likely nought.

▲egeozcan 2 hours ago | parent | prev | next [-]

Couldn't agents just Remote Desktop or ssh into them?

For seriously older stuff, I'd run the disk image in a VM.

If they interact with legacy systems and/or virtualizing is no option and/or they have no internet access, a simple USB-to-COM adapter can create wonders. I remeber doing that on a win3.1 machine using TERMINAL.EXE many many years ago.

▲ulrikrasmussen 28 minutes ago | parent | next [-]

In general, I've wondered whymost (all?) harnesses perform the API calls to the provider from the same machine that runs the tools. Why not have a client/server architecture? Then one session could talk to as many tool harnesses as it wanted to and you wouldn't have this kind of arbitrary limit of the session being tied to one specific workspace.

▲linzhangrun 39 minutes ago | parent | prev [-]

A typical scenario is that you walk into a small company and find they're still using Windows 7 or an early version of Windows 10. Then you have to help them deal with all sorts of problems.

▲kristopolous an hour ago | parent | prev | next [-]

I've got an agent that just uses legacy perl 5.0001 ... close but there's no perl by default on windows (although it's easy enough to get on there)

https://github.com/kristopolous/old-agent

I've used it on plenty of old things.

I'd probably do a pure .vbs version if it was windows or a static pure win32 exe.

▲linzhangrun 3 hours ago | parent | prev | next [-]

Almost all agents require Windows 10 1809 or later. Debugging issues on older devices often turns out to be a real headache, and the only option is to get SSH working.

▲anthk 6 minutes ago | parent | next [-]

There are Golang ports for WXP and up (check the Reticulum-go GH repo and the users), and there's MIn-C as a port of core OBSD tools for XP (Unix tools, compiler, vi, openssh and a bunch more).

▲shevy-java 2 hours ago | parent | prev [-]

But should not AI be able to solve all these mentioned problems? Why can they not solve that?

It would not make a whole lot of sense to me.

▲linzhangrun 38 minutes ago | parent [-]

For old Windows, "setting up an SSH tunnel" itself takes quite a bit of fiddling. Especially when the device you need to deal with is on a distant external network, and you can't even remote in—you're limited to video calls and the like.

▲shevy-java 2 hours ago | parent | prev [-]

Agreed. Kind of strange how AI promises everything but the old platforms are still ignored and neglected.