Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why does the Commander not work in GNU/Linux, OS/2 and Windows?

Commander GNU linux OS Windows
0
10 Posted

Why does the Commander not work in GNU/Linux, OS/2 and Windows?

0
10

Please, read the “Usage” section in the documentation. It contains information on the extra requirements under multi-tasking operating systems. In all cases, get prepared for timeouts and lockups because Commodore drives expect a tighter synchronization than the Commander can keep under a multi-tasking system. You get the best results by running the Commander under plain DOS. Also, if there exists a native transfer software for your favorite operating system then use that one instead for transferring and use the Commander for conversion only. • Q: Will you do a GNU/Linux, OS/2, or Windows version of the Commander? A: No, I won’t. Although the routines of the Borland Pascal run-time library rely on being run under DOS, I did take my time with extending them with the capability of handling Windows-style long file names. Unfortunately, there are some more aspects keyboard, file and screen handling and some quirks that are related to DOS too much. I’m not willing to create a native version

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123