beta 6.1 still has bugs

[mikesw]

Running on Win 2k Pro Sp4.

 

a). IOBIT V6.1 doesn't see FAT partitions.

b). IOBIT v6.1 gets constant "no disk" exceptions when zip

disk is NOT inserted.

c). IOBIT v6.1 seems to run alot slower during analyze vs. v5.0.1.

d). Version number in files is 0.0.6.1 and not 6.1.0.0.

 

 

I'm kind of curious as to when IOBIT will fix these serious bugs.

Although its free at the moment, it makes me wonder what the

other software is like that one pays for from iobit.com. Hopefully

it's better quality than the free stuff.:-x

[solbjerg]

Hi Mikesw

a) do you mean that the previous version did? FAT32 or FAT16?

b)Is your computer set to start from a floppy disk or a zip disk in BIOS?

c) how many times have you run it?

d)Yes the .exe file has a version number 0.0.6.1 the program is called Beta version 6.1, - on the other hand the install/uninstall version is 51.49.0.0 - and that sure looks as if they have worked very hard on that to generate that many versions :-)

Cheers

solbjerg

 

 

Running on Win 2k Pro Sp4.

 

a). IOBIT V6.1 doesn't see FAT partitions.

b). IOBIT v6.1 gets constant "no disk" exceptions when zip

disk is NOT inserted.

c). IOBIT v6.1 seems to run alot slower during analyze vs. v5.0.1.

d). Version number in files is 0.0.6.1 and not 6.1.0.0.

 

 

I'm kind of curious as to when IOBIT will fix these serious bugs.

Although its free at the moment, it makes me wonder what the

other software is like that one pays for from iobit.com. Hopefully

it's better quality than the free stuff.:-x

[mikesw]

Hi Mikesw

a) do you mean that the previous version did? FAT32 or FAT16?

b)Is your computer set to start from a floppy disk or a zip disk in BIOS?

c) how many times have you run it?

d)Yes the .exe file has a version number 0.0.6.1 the program is called Beta version 6.1, - on the other hand the install/uninstall version is 51.49.0.0 - and that sure looks as if they have worked very hard on that to generate that many versions :-)

Cheers

solbjerg

 

a). It is MSDOS FAT16. My system is multi-boot. V5.0.1 was able to

see and defrag this partition. However, V6.0, v6.1 can't see it since

it will not show the drive letter or info for this partition.

 

b). your comment about the BIOS is irelevant. Regardless of the boot device,

it will start booting from the HDD and load the OS. Iobit is in the startup list

and during login, iobit is started and put in systray It is at this point that it

constantly complains with the exception ,since I don't have a zip disk

inserted. When it is inserted, iobit is happy. If no zip disk inserted,

and iobit exited and restarted using the desktop icon, the problem still

occurs. Note: MSofts defrag software doesn't generate these exceptions.

So IOBIT isn't detecting removable disks properly.

 

 

c). It's not a matter of running it. During startup, iobit starts scanning

the drives to build a list of their filesystem formats. It's during this

step, that it sees the zip drive not containing a disk and starts complaining.

 

d). Various inventory programs I use scan for my software versions. Iobit is

supposed to be v6.1; however, it shows up in my inventory list as v0.0.6.1

So iobit doesn't even conform to a standard software versioning convention.

No its not my inventory software program that has a problem.

 

e). The only thing I see that's different between v5.0.1 and v6.x is that the

GUI interface got changed around a little bit.

 

f). IOBIT is supposed to generate a "softwarebugreport.txt" file in the

install directory. However, I've never seen this file generated, not even

creating some sort of listing when it is initializing properly to tell one how

far along it got before problems start occuring. So I can't even send

in this txt file to have them look at the debug info.

 

The bottom line is, I've sent countless emails to their support email with

no response, and posted here these various bugs. If free software bugs

arent being responded to, then this makes one think that purchased software

will have the same support response.

 

A free software package that works is JKDEFRAG; however, the developer

doesn't plan on running it in systray, but only under the scheduler. This

isn't ideal either.

[solbjerg]

Hi Mike

I agree with you that these problems ought to be looked into.

They promise to read every report they recieve, and yours are fairly descriptive, so maybe they are working on it. But they also write that they can't answer everybody, and I find that understandable too, if they recieve a million reports a year.

They like to recieve pictures that shows the problem and they like to recieve the bug report, but as none is generated by you, then it's hard to accommodate that wish. :-)

About the Bios - I just thought that ISD might have a bug that reacted to the setting if floppy disk was the first startup location that was checked.

 

Cheers

solbjerg

 

 

a). It is MSDOS FAT16. My system is multi-boot. V5.0.1 was able to

see and defrag this partition. However, V6.0, v6.1 can't see it since

it will not show the drive letter or info for this partition.

 

b). your comment about the BIOS is irelevant. Regardless of the boot device,

it will start booting from the HDD and load the OS. Iobit is in the startup list

and during login, iobit is started and put in systray It is at this point that it

constantly complains with the exception ,since I don't have a zip disk

inserted. When it is inserted, iobit is happy. If no zip disk inserted,

and iobit exited and restarted using the desktop icon, the problem still

occurs. Note: MSofts defrag software doesn't generate these exceptions.

So IOBIT isn't detecting removable disks properly.

 

 

c). It's not a matter of running it. During startup, iobit starts scanning

the drives to build a list of their filesystem formats. It's during this

step, that it sees the zip drive not containing a disk and starts complaining.

 

d). Various inventory programs I use scan for my software versions. Iobit is

supposed to be v6.1; however, it shows up in my inventory list as v0.0.6.1

So iobit doesn't even conform to a standard software versioning convention.

No its not my inventory software program that has a problem.

 

e). The only thing I see that's different between v5.0.1 and v6.x is that the

GUI interface got changed around a little bit.

 

f). IOBIT is supposed to generate a "softwarebugreport.txt" file in the

install directory. However, I've never seen this file generated, not even

creating some sort of listing when it is initializing properly to tell one how

far along it got before problems start occuring. So I can't even send

in this txt file to have them look at the debug info.

 

The bottom line is, I've sent countless emails to their support email with

no response, and posted here these various bugs. If free software bugs

arent being responded to, then this makes one think that purchased software

will have the same support response.

 

A free software package that works is JKDEFRAG; however, the developer

doesn't plan on running it in systray, but only under the scheduler. This

isn't ideal either.

[JimPetersen]

It also hangs during Analysis

 

I have 2 drives. On one it hangs at 96% during Analysis and the other at 18%. And when I try to STOP them, it says "stopping" forever.

 

XP SP3

[solbjerg]

Hello Jim

How fragmented are your drives?

Have you tried defragmenting them with the Windows defragmenter?

What does that say?

Cheers

solbjerg

 

I have 2 drives. On one it hangs at 96% during Analysis and the other at 18%. And when I try to STOP them, it says "stopping" forever.

 

XP SP3

[JimPetersen]

Hello Jim

How fragmented are your drives?

Have you tried defragmenting them with the Windows defragmenter?

What does that say?

Cheers

solbjerg

Windows defrag worked just fine. As for how fragmented? I was hoping SmartDefrag would tell me.

[solbjerg]

OK Jim

But what did Windows say in it's report?

Is this ISD 6.1 your first defragmenter from IObit?

How did you install it?

solbjerg

 

Windows defrag worked just fine. As for how fragmented? I was hoping SmartDefrag would tell me.

[JimPetersen]

6.1 is not the 1st release of SmartDefrag. All of the previous releases, I have never had a problem with. This is the 1st installation of SmartDefrag on this computer however. Installation was download from website and straight install.

 

Windows Defrag says that the disk should be defragmented. Average fragments is 1.45 2500 files are fragmented.

[solbjerg]

Hi Jim

Do you have a bug report in the ISD folder?

If you do, - send it to IObit and explain your trouble.

Sounds as if it is not too badly fragmented, -and it also sounds like there is room enough for defragmentation, since it hasn't complained about that.

At the moment I have no ideas, sorry!

Solbjerg

 

6.1 is not the 1st release of SmartDefrag. All of the previous releases, I have never had a problem with. This is the 1st installation of SmartDefrag on this computer however. Installation was download from website and straight install.

 

Windows Defrag says that the disk should be defragmented. Average fragments is 1.45 2500 files are fragmented.

[mikesw]

Hi Jim

Do you have a bug report in the ISD folder?

If you do, - send it to IObit and explain your trouble.

Sounds as if it is not too badly fragmented, -and it also sounds like there is room enough for defragmentation, since it hasn't complained about that.

At the moment I have no ideas, sorry!

Solbjerg

 

 

You mention a bug report. What triggers this bug report to be written

to the ISD install folder? I've never seen one written! :shock:

[solbjerg]

Hi mikesw

I don't rightly know, - I have one bugreport.txt with 3 reports in it, but two are from December 2007 and one from January 2008. Since then nothing!

So I am not sure that it functions OK.

solbjerg

 

 

You mention a bug report. What triggers this bug report to be written

to the ISD install folder? I've never seen one written! :shock:

[Luc J. Patenaude]

When was the last time you clicked on 'Windows Update'?

Sounds like you have not updated your drivers for a very long time. Or, worse, the Bios of your mainboard might be failing you onto understanding the full content of the data contained onto your current HD. You do need to check every component of your machine via the Device Driver Manager through the system properties of the features module of 'My Computer'. Simply double click on one of these components, Driver, then onto the 'Update driver' button(it will automatically go online of the internet for finding the latest driver that is best suited for the current configuration of your current-in-use machine).

You might end up with more than you thought out of this machine, yet. Microsoft tends to all of our machines like it is entirely theirs. If MS finds the necessity to make you install a special program that accentuates the stability of operation of your machine, they will gladly do so.

[mikesw]

Running on Win 2k Pro Sp4.

 

a). IOBIT V6.1 doesn't see FAT partitions.

b). IOBIT v6.1 gets constant "no disk" exceptions when zip

disk is NOT inserted.

c). IOBIT v6.1 seems to run alot slower during analyze vs. v5.0.1.

d). Version number in files is 0.0.6.1 and not 6.1.0.0.

 

 

I'm kind of curious as to when IOBIT will fix these serious bugs.

Although its free at the moment, it makes me wonder what the

other software is like that one pays for from iobit.com. Hopefully

it's better quality than the free stuff.:-x

 

 

Just to let everyone know that piriforms defraggler at

http://www.defraggler.com has no problem with zip, floppy, usb

drives. I've defragged them all. So IObit has a problem and it

is not a driver problem. The only problem with defraggler is

that it is slow and doesn' work out of systray like iobit does.

Moreover, it can only defrag one drive at a time.