Shrink Can't Open ISO's split to 3.99 GB on FAT32

[calweycn]

I don't know if this is a problem with ImgBurn, Shrink, or my PC. When I create ISOs split to

3.99 GB on FAT32 drive, Shrink can't open or analyze the MDS file. "DVD Shrink encountered

an error and cannot continue. Failed to open file XXXXX.I00."

 

The image can be mounted with Daemon-Tools and played. I can analyze the mounted image

with Shrink. It burns and plays fine. But the image can't be loaded in Shrink. Has anyone else

had this problem? Any solutions?

 

I found that using 2 GB splitting or smaller on FAT32 will fix it, but I prefer to I use 3.99 GB.

I asked LUK about this a while ago and he said it should work. I used to have this problem

with DVDD as well. I had to use 2 GB file splitting on FAT32 drives.

[LIGHTNING UK!]

If everything else can use the images ok I would think it's DVD Shrinks problem.

 

I guess its image loading code just can't cope or has a bug in it.

 

You'll have to stick with 2 GB as obviously that program isn't being updated now.

[calweycn]

If everything else can use the images ok I would think it's DVD Shrinks problem.

 

I guess its image loading code just can't cope or has a bug in it.

 

You'll have to stick with 2 GB as obviously that program isn't being updated now.

 

Thanks, LUK. I'm still curious if others have seen this problem. There's no

technical reason that Shrink shouldn't be able to read the files. FAT32 will

allow file sizes up to 3.99 GB. Every other program can handle the image

files. But it might be a configuration problem with my computer or Shrink.

That's why I'm interested if others have this problem.

 

If anyone has a link to something addressing this as a bug in Shrink. I'd

like to see it. This scared me the first time, because I thought the HD was

going bad. It's probably a limitation in Shrink's code. Afterall, Shrink uses

1 GB file splitting when writing an ISO to FAT32 drives.

[polopony]

you dont say what OS you're using but if its xp you might consider converting to NTFS and it wont be an issue.You can also remove and re install Shrink and see if that helps

[calweycn]

you dont say what OS you're using but if its xp you might consider converting to NTFS and it wont be an issue.You can also remove and re install Shrink and see if that helps

I'm using Windows XP Pro SP2. I've always had this problem with Shrink not being able

to recognize 3.99 GB files on FAT32. I have found NTFS to be unreliable, in that several

drives have had lost data or corrupted files. This has occurred often enough to be noted

as a definite pattern. The FAT32 drives have never lost data.

 

I use NTFS for my system partition and another drive, but I have found FAT32 to be a

more reliable bet. Files on NTFS become corrupted at random, in my experience. Many

people don't notice this, but I suggest quickly running through all of your MP3 files or

viewing all of your photos. You may find that 1% are garbage.

 

Microsoft can't do much of anything right, as I'm sure many of you know. Their new NT

file system just introduces a lot of new problems, IMO. I use an UPS, antivirus, firewall,

and other safeguards. Still, I have lost NTFS data repeatedly.

[LIGHTNING UK!]

If NTFS was bad, don't you think all the businesses around the world would have let Microsoft know?!

 

Every one of them would be using NTFS for it's security/permissions stuff and they'd sure as hell notice if vital business documents kept getting screwed up.

[dontasciime]

What IO are you using also is the file splitting set to Auto

 

edit i have just formatted one drive to fat32 again and read iso that was 5 gig + and shrink read in mds file in no trouble, your are using open disc image in shrink and not open disc ?

 

 

or is the disc you read in a VR one ie one from a home dvd recorder

Edited August 9, 2006 by dontasciime

[lfcrule1972]

I have never heard of these problems with NTFS !

[Shamus_McFartfinger]

Me neither. I'd be fooked if I had to go back to using FAT32. Ugh.

[calweycn]

If NTFS was bad, don't you think all the businesses around the world would have let Microsoft know?!

 

Every one of them would be using NTFS for it's security/permissions stuff and they'd sure as hell notice if vital business documents kept getting screwed up.

I didn't imagine losing 1% of my songs and photos, due to random file corruption

on hard drives and partitions. Most of them were irreplaceable. FAT32 drives have

never lost data. That's enough to make me wary of using NTFS.

 

They might not notice if 1% of their files were randomly turned into garbage. I do

not want to take that chance. 60 files out of 6,000 - lost. Not exactly what inspires

confidence in users. No bad sectors on the drives. I've had battery back-up since

day one, so there were no sudden power outages, either.

 

EDIT: Many businesses use Apple, Linux, or Unix. They avoid Microsoft.

Edited August 9, 2006 by calweycn

[lfcrule1972]

Really ? None of the businesses I have worked for use them.....

[volvofl10]

i would suggest your loss of 1% was due to your actual drive being at fault as opposed to it being a NTFS file system .

i cant honestly say i have ever heard of people losing stuff from an NTFS drive ,but not losing stuff on a FAT32 drive.

I'm not saying you didn't lose the 1% you mentioned, but you cant put that down purely to the NTFS system , some other factor must have been involved .maybe lack of defrag , bad sectors on that drive ect ect.

i don't know of any business that uses FAT32, they all use NTFS, that makes me think there must be a reason for it, usually as xp pro works well with it.

 

your going to have to take the gamble if you want shrink to work with your ISO's by changing to NTFS , OR get an external drive and format that as NTFS instead. then you can have the best of both worlds

[calweycn]

What IO are you using also is the file splitting set to Auto

 

edit i have just formatted one drive to fat32 again and read iso that was 5 gig + and shrink read in mds file in no trouble, your are using open disc image in shrink and not open disc ?

 

or is the disc you read in a VR one ie one from a home dvd recorder

I'm using SPTI. File splitting was at Auto, but it didn't work for me.

Shrink can't open the MDS, unless I use 2 GB splitting. Auto uses

3.99 GB splitting on FAT32. If it works for you, then there must be

something wrong with my configuration - either in DVD Shrink or

ImgBurn. I don't know what it could be.

[calweycn]

i would suggest your loss of 1% was due to your actual drive being at fault as opposed to it being a NTFS file system .

 

We're getting off-topic, but I've tested the disks thoroughly with chkdsk,

Partition Magic, and other software. There were never any bad sectors

found. I seriously doubt that it was a hardware problem. All the files with

corruption were on NTFS drives. Most people wouldn't even notice if 1%

of their files were lost, because they don't check them.

 

I'm not saying you didn't lose the 1% you mentioned, but you cant put that down purely to the NTFS system , some other factor must have been involved .maybe lack of defrag , bad sectors on that drive ect ect.

I run defrag regularly (PD7). There have never been any bad sectors

found on the drives. There have never been any power failures, as I

have used battery back-ups for years.

 

i don't know of any business that uses FAT32, they all use NTFS, that makes me think there must be a reason for it, usually as xp pro works well with it.

Businesses also make errors from time to time. Probably at a rate of

at least 1%. Also, the files that are corrupted might never be checked

again. Many files in Windows are never used.

 

your going to have to take the gamble if you want shrink to work with your ISO's by changing to NTFS , OR get an external drive and format that as NTFS instead. then you can have the best of both worlds

Shrink DOES work with 2 GB file splitting on FAT32, but not Auto (which

uses 3.99 GB splitting). It will work with any size file splitting for NTFS.

It's not a big deal for me to use 2 GB splitting in ImgBurn Build Mode. I

just wondered if this was a universal problem. Since at least one person

has said they don't have this problem, it may be something caused by

how my computer or software is configured.

[calweycn]

Really ? None of the businesses I have worked for use them.....

 

Apple/Linux/Unix may not be dominant in the front office, but they are

dominant in servers and the back office. I can never trust NTFS. I have

continued to lose files at a rate of ~1%, long after initially noticing the

pattern. They are files I have just set in a folder and not accessed with

any program (except defrag). When I go back later, some of them are

garbage. This happens across partitions and drives, but only with NTFS.

Never had it happen with data on FAT32.

 

I go to play a video or song and find it's corrupt. Not just a few errors,

but the whole file is garbage data. I've checked for viruses routinely,

and even did a clean install of the whole OS. Nothing has stoppd these

problems from occurring. Perhaps most people don't notice a 1% loss

of their data, but to me it's unacceptable.

 

Whether the problem is caused by NTFS is a moot point. The problem

has only been observed by me with NTFS.

[polopony]

it may be a stupid question but are you sure that those files were not corrupt to start with ?I've been using NTFS for as long as XP pro is out and cant say I've lost anything, but files I have downloaded have been corrupt especially where music was concerned

[blutach]

dupe

[blutach]

Perhaps these vids/songs had DRM which ran out.

 

Only happen on vids/songs then?

 

Regards

[dontasciime]

or if your using maxtor

[spinningwheel]

Or if you simply want to keep beating a dead horse...