Read the full developer blog entry here.

I downloaded and installed VE 1.2 beta. It won’t take my 1.1 license key, and tells me that the trial period has expired. Do I need to do anything?

BillChapman - 07 February 2008 12:33 PM

I downloaded and installed VE 1.2 beta. It won’t take my 1.1 license key, and tells me that the trial period has expired. Do I need to do anything?

Hi BillChapman and welcome to the forums!
We haven’t changed the registration code in the new release. Please send me a private message with the license key that you are using, I will double check and get back ASAP. Thanks!

Hey Anton,

I just installed Virtual Explorer 1.2 and I must say I am impressed.  NOTE:  I am not a current registrered user of VE.

I did hit one odd occurrence.  I was playing with the Tree Settings.  I selected High Res Icons.  That seemed to work fine...but the icons were then too big for my QVGA device, so i unselected that option.  I then set it to a setting called (I think) Single Expand Mode...or something similar.  At that point I clicked on a folder that had subfolders.  VE kind of “freaked out” and selected folder switched back and forth very quickly...kind of flashing.  VE eventually quit.

Now I cannot use VE when I re-launch it (even after soft reset).  It does come up, but I cannot click on anything, and the bottom bar (Edit, View, etc) does not show.  Something about that setting my device does not like.

I have an AT&T;Tilt (WM6)

Regards.

Hi Anton and other beta testers,
I found the installation of version 1.2 didn’t give me any warning about uninstalling the previous version (x51v). It installed over the previous version and came up as expired on the first run. However, my version 1.x code worked fine.

Update: I was mistaken. Version 1.2 installs as a new application while ignoring the 1.x installation. I found a new Wizcode folder with version 1.2 in it. I still have a Anton Tomov folder with the old 1.x in it. I think that’s why the new installation is expired until you enter a serial number.

Anton,
Can you update the installer to be aware of previous versions and go through the normal warning process (on WM5) that the previous version will be uninstalled before proceeding?

Thanks,
Mark

mkss55442 - 08 February 2008 08:16 PM

Hi Anton and other beta testers,
I found the installation of version 1.2 didn’t give me any warning about uninstalling the previous version (x51v). It installed over the previous version and came up as expired on the first run. However, my version 1.x code worked fine.

Update: I was mistaken. Version 1.2 installs as a new application while ignoring the 1.x installation. I found a new Wizcode folder with version 1.2 in it. I still have a Anton Tomov folder with the old 1.x in it. I think that’s why the new installation is expired until you enter a serial number.

Anton,
Can you update the installer to be aware of previous versions and go through the normal warning process (on WM5) that the previous version will be uninstalled before proceeding?

Thanks,
Mark

Hi Mark,
The new version installs under “Wizcode” while the old one was using “Anton Tomov”. Therefore the installer treats the two versions as different products. I will check if we can add code to detect a previous version and warn the user but as far as I remember this is part of the Windows CE CAB manager. Anyway the easiest thing we can do is to issue a warning message to the user in case an older version is detected.

Thanks very much for the feedback, we will post a new update (v1.21) shortly.

kwickone - 08 February 2008 10:51 AM

Hey Anton,

I just installed Virtual Explorer 1.2 and I must say I am impressed.  NOTE:  I am not a current registrered user of VE.

I did hit one odd occurrence.  I was playing with the Tree Settings.  I selected High Res Icons.  That seemed to work fine...but the icons were then too big for my QVGA device, so i unselected that option.  I then set it to a setting called (I think) Single Expand Mode...or something similar.  At that point I clicked on a folder that had subfolders.  VE kind of “freaked out” and selected folder switched back and forth very quickly...kind of flashing.  VE eventually quit.

Now I cannot use VE when I re-launch it (even after soft reset).  It does come up, but I cannot click on anything, and the bottom bar (Edit, View, etc) does not show.  Something about that setting my device does not like.

I have an AT&T;Tilt (WM6)

Regards.

Hi kwickone,
Thanks for the report - we will try to reproduce the issue and will post back with a status report!

I tried the v1.2 beta. It is the fastest explorer I’ve ever used. However, there are two annoying features.

1. When I do an cut and paste in the same SD card, VE will copy the files 1st and delete old file. This wastes lots of time, and do some unnecessary read write operation. Why is it this way? Seems to me that cut and paste only required to change the location information.

2. There is still no “Open With” option. It just asked me to “run the application 1st”. I think it should allows me to open the files with any program, and allows me to set it as default or not. Since if I used the application to find the files, it would be slow.

Overall, I think VE is very good. But there are some room for improvement.

Thank you.

Hi Ross,

thank you for your comments. The both items are in our todo list. We are planning to have the first one done for the stable release and the second item probably for the next one.

And yes - you are right, there are some room for improvement (there will be always such room)

I think I have found a bug in 1.20
When I tap on the 4 pane icon on the toolbar the program crashes and exits
Dell Axim x51v WM5 ROM A12
Otherwise seems to be a great upgrade

Thank you for the detailed report, we will check what is wrong and the upcoming stable version will include the fix.

Another bug in 1.20?
When I press and hold on a folder or card icon and choose properties the size, size on disk and contains information is not reported.
When I do the same on file, it works properly
Dell Axim x51v WM5

Hi Simon,

thank you for your report. The bug is result of the new (and faster) way to collect the File-System information. It will be fixed in the stable version 1.20 (it is almost ready and should be released in the next few days).

Thanks again for the report!