Jump to content
Sign in to follow this  
ctl3d32

Bug in v2.4.2.0 Regarding FAT32 and NTFS Detection.

Recommended Posts

Hi,

 

I've made ImgBurn v2.4.2.0 portable using ThinApp from VMWare.

 

There is this little bug in version 2.4.2.0 that when i run it (the portable one) from my pendrive, it detects c:\ as FAT32. [it seems that it detects the pendrive's file system format and associate it with the HD)

 

When i run the portable imgburn from my c:\, it detects the file system format correctly, as you can see in the logs below.

 

Cheers,

ctl3d32

 

Running from the pendrive:

I 09:45:38 ImgBurn Version 2.4.2.0 started!
I 09:45:38 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 09:45:38 Total Physical Memory: 1.031.392 KB  -  Available: 652.868 KB
W 09:45:38 Drive C:\ (FAT32) does not support single files > 4 GB in size.
I 09:45:38 Initialising SPTI...
I 09:45:38 Searching for SCSI / ATAPI devices...
I 09:45:38 Found 1 CD-ROM and 1 Unknown!

 

Running from the HD:

I 09:40:14 ImgBurn Version 2.4.2.0 started!
I 09:40:14 Microsoft Windows XP Professional (5.1, Build 2600 : Service Pack 2)
I 09:40:14 Total Physical Memory: 1.031.392 KB  -  Available: 677.484 KB
I 09:40:14 Initialising SPTI...
I 09:40:14 Searching for SCSI / ATAPI devices...
I 09:40:14 Found 1 CD-ROM and 1 Unknown!

Share this post


Link to post
Share on other sites

It's only querying the drive with said drive letter (C: in this case) and getting its file system via a single API call, so if anything is confused then it'll be the OS.

Share this post


Link to post
Share on other sites

Hi,

 

Thanks for the fast reply. I'm at work now. I'll try to see it it happens at home too, with XP SP3 installed.

 

Thanks,

ctl3d32

Share this post


Link to post
Share on other sites

Any particular reason for using ThinApp? I mean, ImgBurn is already portable if you use the right command line parameters (have a look at ImgBurn Read Me).

Share this post


Link to post
Share on other sites

Hi,

 

No, no particular reason. It's just because it's too easy to turn normal applications into portable ones using ThinApp. I'm addicted to it. Furthermore, it creates one single and compressed executable file and the fact that the app will live no traces (garbage) in my HD and windows registry.

 

I've made MatLab v2007b portable once, and it's size droped from almost 3GB (normal installation) to almost 1GB (portable). ThinApp saves me space an time (no install needed).

 

Cheers,

ctl3d32

Share this post


Link to post
Share on other sites

When running ImgBurn in portable mode I don't experience this bug you're seeing so it's probably a side-effect of using ThinApp.

 

BTW, I don't think you'll save much space over the 1.89 MB ImgBurn occupies (on my flash drive) by using that app since the ImgBurn executables are already UPX compressed anyway.

Share this post


Link to post
Share on other sites
Sign in to follow this  

×

Important Information

By using this site, you agree to our Terms of Use.