WINE Compatible version of TCC

#1
While I can run 4NT8 on WINE (http://www.winehq.org/), I cannot run any later version of TCC.

For those who are moving away from Microsoft Windows, and moving towards (Ubuntu) Linux, being able to take the latest version of TCC with them would allow them to use the command processor they are used to, instead of having to learn BASH or another <insert Unix shell>.

Presently, TCC has a rating of Garbage at http://appdb.winehq.org/objectManager.php?sClass=version&iId=27696

If TCC were made WINE Compatible, I'm sure it would get a rating of Gold, as it deserves.

You can vote for this suggestion at http://jpsoft.uservoice.com/forums/...stions/4207806-wine-compatible-version-of-tcc

Joe
 
#3
IMHO a very important reason for a POSIX-compatible version of TCC is for system administrators who have to deal with both MS and POSIX type systems. A single language with more power than any other command processor for all systems would be worth lots of gold. With MAC now using Intel compatible chips and POSIX-like OS, the product wold have nearly 100% compatibility with all microcomputers (embedded systems not included).
 
#6
That "Garbage" rating seems a bit on the unfair side. But then, Un*x/Linux people always were kinda harsh... :-/
Not harsh, just narrow-minded: TCC is NIH.

In the style of that report the software in your mobile phone, the software for your hospital's MRI and CAT scan are all garbage - cannot be run under WINE... Under the same rule its author is also garbage - (s)he does not live in my home.
 
Last edited:
#7
The title of that report is Take Command/32, describd as a GUI interface to 4NT, but provides the 2013-01-20 version and build information. It even warns that the test results are very old.

The report does not state that the above referenced description itself is wrong. Take Command/32 is a full-fledged command processor with a GUI, sharing most of its code and syntax with the text-mode command processor 4NT.
 
#8
TCC only uses vanilla documented Windows APIs. This has to be a Wine bug -- I doubt it's worthwhile to try to cripple TCC to match Wine bugs, in order to appeal to a (very, very) small group of users.
????????????????????????????????????????????????

You do NOT change anything in TCC in order to make it run under WINE on Linux/Mac/Android.

Instead, WINE works to modify THEIR code, so that your program runs under WINE on Linux/Mac/Android.

http://www.codeweavers.com/services/engagements/

Microsoft never asked that their software run on WINE. It was the users of Microsoft Software that persisted in getting Microsoft (insert product here) Software to run on WINE.

Other software companies, who want more than just the Microsoft Windows Market, work with Crossover/WINE so that their product can run on WINE.

BTW, Linux/Mac/Android are not a (very, very) small group of users, and yes, I did purchase a license for Crossover, so that I can run my Microsoft Windows apps on Ubuntu (Linux).

Joe

Ref: http://en.wikipedia.org/wiki/CodeWeavers
http://en.wikipedia.org/wiki/Wine_(software)
https://twitter.com/CodeWeavers
http://www.codeweavers.com/services/
 

rconn

Administrator
Staff member
May 14, 2008
10,755
97
#10

Charles Dye

Super Moderator
Staff member
May 20, 2008
3,724
47
Albuquerque, NM
prospero.unm.edu
#11
So -- they want me to pay them to fix WINE so it will run a vanilla Windows app?!?
In fairness, it's a stretch to call Take Command a 'vanilla Windows app'. I suspect that if you were to document all the APIs it calls, it would be a long list and include some pretty obscure functions. Subtract all the ones supported by WINE, and it might still be a long list....
 
#12
In fairness, it's a stretch to call Take Command a 'vanilla Windows app'. I suspect that if you were to document all the APIs it calls, it would be a long list and include some pretty obscure functions. Subtract all the ones supported by WINE, and it might still be a long list....
Isn't that simply Wine's shortcoming?
 

rconn

Administrator
Staff member
May 14, 2008
10,755
97
#13
In fairness, it's a stretch to call Take Command a 'vanilla Windows app'. I suspect that if you were to document all the APIs it calls, it would be a long list and include some pretty obscure functions. Subtract all the ones supported by WINE, and it might still be a long list....
True, if we were talking about Take Command. But Joe was asking about running TCC, which is much simpler.