tc2usb supporting PortableApps

[ghisler(Author)]

My card reader creates 4 drive letters (h:, i:, j:, k: ), but only one drive (j: ) is actual accessible (SD-card 2GB).
Tc2usb provides all 4 drives as possible installation destinations.

I decided against that for those people who insert the card after starting the tool. What do other people think?

[sqa_wizard]

There are two workable solutions:

1. Check all drives in advance and show usable drives only (with PortableApps folder)
=> this will result in a restart of tc2usb in case of card is not inserted yet
It is very comfortable to have a selection of 1 drive only , but it takes time to scan on startup and is confusing if no drive is displayed.

2. Show all drives and check on selection for an existing PortableApps folder
=> in case of selecting an unusable drive (without PortableApps folder or not accessible) an according message has to be displayed
Fast at startup, but having a lot of drives you may have to repeatable guess the right one

... on the other hand you should know what you are doing before starting the tool !

For the sake of minimum effort and short startup time I prefer no. 2 with an expressive message in case of unusable drive.

[Laurent]

Just gave it a try and it's working great on first try

Great job Christian, and (i'll never say it enough) thank you for this great app and continuous support!

[HolgerK]

I'd just made a test again, this time only with the card reader.

1. tc2usb selects the first usable drive j: as default.
(Thats fine , I didn't noticed this in my first test, because of an additional usb stick x: with a PortableApp installation)

2. I decided against this preselection and select drive k:

3. proceeded [next>] with the wizard steps

4. got the error message "error copying file"

5. [<back] to 1. wizard page and select drive j: (the one with the SD-Card)

6. confirm [next>] the following wizard pages

7. the last page still shows the error message: "Installation failed!".
- No copy progress( 0%).
- Only the [Cancel] button is available.
- Restart of tc2usb is necessary.

Looks like the [<back] button in step 5 doesn't clear an error state!


Maybe it's a compromise to show a more informative error message (in case of an unavailable destination drive), directly when the user press the [next>] button at the first wizard page?

Regards,
Holger

[ghisler(Author)]

Thanks for your tests. I haven't tested the tool with a mix of PortableApps and "normal" USB sticks yet, maybe that's the problem.

[Peter]

Hello

is this tool still in "Beta"-Status? or are there any news? The EXE on the website is older, it is from March 2008.

Peter

[ghisler(Author)]

Yes, the PortableApps state is still in beta. I didn't have much time to work on it lately because TC 7.5 beta takes all my time...

[Peter]

So a report for further development:

The paths, used in BAR-files, should be modified too. Now they stay at their current state.

Peter

[m^2]

Use %COMMANDER_PATH%, %COMMANDER_DRIVE% etc.
I see no reason to modify bar files.

[Peter]

Use %COMMANDER_PATH%, %COMMANDER_DRIVE% etc.
I see no reason to modify bar files.

The reason is that in my bar-files (I use three of them) are absolute-paths (I don't know why - system error or user error?), and transfering the whole TC to USB stoped working the bars ...

Peter

[m^2]

My last statement said more precisely:

I see no reason for TC to modify bar files.

If you have absolute paths, it's because of how you added buttons. Everytime you add a new one, ensure that path is relative.
You can edit the current bars to fix them. You can do it in TC, but text editor is most likely more comfortable for this task, .bar files are very readable.

[Peter]

...Everytime you add a new one, ensure that path is relative....

Yes, Of course - I should / would / could ..
But if somebody forget to ensure the configuration, the software could / should help him to avoid an error while transfering to USB.

Peter

[m^2]

Sorry, I looked at it too technically, you wanted some idea, not particular implementation.

You asked in wrong thread - TC should update paths, not tc2usb, which made me suspicious and it's actually a big thing: how is TC supposed to search for .bar files that need to be changed?

But inserting %COMMANDER_PATH% automatically would be good.
IIRC it was requested before, but not for .bars.

[karlchen]

Update note:

Please be aware that the current TC2USB version is 1.13 by now and no longer 1.12 beta.

I still have to test it against T.C. 7.50a and T.C. 7.55 pb1 (cf. this bug report, please), but certainly not tonight. <yawn><sorry><01:12 MET>

<Added 10:00 MET>
Value=Done
</Added>

Kind regards,
Karl