Total Commander

Sorry, porting >300'000 lines of code to C++ is not an option.

2ghisler(Author)
I just wanted to hear the sentence porting ">x lines of code to C++ is not an option" where x was unknown

Dordhs wrote:Actually GPT and 32/64 bit have nothing to do with each other technically. Perhaps Windows has this linked, but older versions of windows dont know GPT any way. I recently had to partition a 4 GB array using GPT and Parted Magic worked fine on it using debian. Just make sure everything is done right. I believe you even need to make a small partition to store the extra partition information I cant remember exactly, just search for GPT

What the hell are you talking about?

lr123,
It was spam it seems. A very nice one, I must admit.

Roman

+1 for 64 bit Total Commander version.

I just migrated to Windows 7 64 bit and I must say that working with Total Commander is not as fun as it used to be.

I have encountered a case in which Total Commander could not find a file (oemlogo.bmp) under c:\windows\system32 or c:\windows\syswow64, but Windows Explorer did.

I don't know when Delphi 64 bit would be released, but the port to 64bit will be required.

Also I don't know how many differences will be from Lazarus 64 bit and Delphi 64 bit, but I guess the core concepts will be the same.

Any progress on a Total Commander port to Lazarus?

Hello, drac.

I have encountered a case in which Total Commander could not find a file (oemlogo.bmp) under c:\windows\system32 or c:\windows\syswow64, but Windows Explorer did.

The 32-bit Explorer???

Please, have a closer look at Explorer + Total Commander: Content of system32 different and in particular find out about Sysnative.

There is no file on a Windows system that Total Commander cannot locate unless it is hidden from the Windows APIs.

Kind regards,
Karl

I have encountered a case in which Total Commander could not find a file (oemlogo.bmp) under c:\windows\system32 or c:\windows\syswow64, but Windows Explorer did.

Did you try to search it in C:\windows\sysnative? When you're in 64-bit Windows within 32-bit program Windows substs syswow64 folder when you open system32 folder (yes it's dumb but it is so) so your system32 and syswow64 folders have equal contents (except some virtual folders that TC displays in system32 folder like drivers\etc).

If you don't using 64-bit shell extensions a lot, it shouldn't be a great problem to use 32-bit TC under 64-bit Windows - I don't know any problems at all (I've installed 32-bit TortoiseSVN and it works in TC perfectly, 32-bit 7-Zip's shell extensions are working from context menu within TC but not in Explorer - 64-bit Explorer doesn't support 32-bit shell extensions at all ).

@MVV, @karlchen I didn't know about Sysnative, thanks for pointing this out.

I have Tortoise SVN installed as 32bit, because it is faster to reach by context menu

7zip I've installed as 64bit, because it should be faster and it should have access to more memory. Pismo File Mount installs only a 64 bit extension.

A 64 bit version of Total Commander would be more consistent, fewer choices to make

I've been using TC in x64 for years and have not had any problems, unlike other 32-bit apps that do not play well.

fwiw, treating 64bit as a standard, a finished product, whatever.. uhmm, no. win7 64 with it's myriad improvements is still as wonky as server/x64. I'm pretty sure this is why Delphi has had to move their dates, it is a moving target when you need to talk to the guts that the consumer thankfully never sees. x64 drivers were a long time coming and they still have problems, like a lack of all but basic functionality in too many cases. Most didn't -need- 64bit, but had to dev for that environment to be allowed to talk to their hardware, and the scramble for the tools and people to accomplish it looked a bit like a 1920's slapstick movie.

It's better now (after only five to eight years), and we all Need storage and RAM addressing, but elsewise, it is a damned strange brew. syswow exists because 64bit is simply not necessary beyond the fundamental addressing needs, in the lion's share of consumer app. Most folks will be a Lot more pissed that their favorite Old programs cannot run in the wundervironment a la' applespeak.. they'll never benefit from 64bit other than addressing.

Like so many things, 64bit is Not the wave of the near future, but that the consumer makes it so, i.e., "is this 64 bit?" because that is one of the questions that they've been taught to ask, Not because they understand why they are asking it.

8bit was Required. 32bit was Required. 256bit Will be required.

all else is just another intel 286 CPU (doncha' hate hardware jokes?).
Unless I'm wrong, and 64bit cyborgs can be taught to dev in 256bit and speed things along. hm..
end rant.
/jk

Like many before me already have posted; an x64 TC would be quite welcomed. And while I understand that one limiting factor is Delphi I can't really wrap my head around Ghisler's response:

ghisler(Author) wrote:Sorry, porting >300'000 lines of code to C++ is not an option.

Yes, it would suck to do that port, but I would think that if proposed by Ghisler himself quite a few people would be willing to help out. Unless, of course, he is afraid that the source will end up in places where it shouldn't be. Which of course is a legitimate concern.

In which language is TC written?

ghisler(Author) on Thu Aug 05, 2010 12:39 pm wrote:Yes, I've been using Delphi 2 with handmade Unicode support, but I'm currently porting to Lazarus/Free Pascal which has Unicode controls based on UTF-8. I have already ported all my Unicode controls to Lazarus, it was quite easy. Now I'm changing OLE2 code to Lazarus (Delphi 2 works quite differently here).

ghisler(Author) on Mon Aug 09, 2010 11:44 am wrote:2Lefteous
I'm of course searching the forum for information, but so far I didn't have to ask a question. The only thing I wonder right now is how to recompile the system unit. Due to a small parameter problem (WC_NO_BEST_FIT_CHARS doesn't exit in 95), Lazarus programs will not run properly on Windows 95.

I'm curious why you are putting effort into a Lazarus TC.

The only reason why I'm doing this is 64-bit. Lazarus can create 64-bit programs, Delphi can't. It has been announced for many years, but nothing has happened, so I could no longer wait. Already 46% of all new computers are sold with 64-bit Windows, according to Heise.de (German link).

Is there any progress on this?

How is the porting going?

I don't use any plugins, so I don't care about those, but I'd be willing to test a version of TC-64

Most of it works, but there are some things which I couldn't solve yet - for example, when you minimize the main program, Lazarus minimizes all the other windows (e.g. Lister, compare tool etc) too. Although I use Windows 7 x64 myself, I'm still using TC 32-bit for every day work, because the 64-bit version just isn't ready yet.

2ghisler(Author)

Hello,

what are your plans for the Delphi-based version? Do you plan to abandon the Delphi version when the Lazarus-based version has been finished?

Probably not, currently I'm updating both in parallel.