Bug: "image File Error" As Limited Account On Xp

[gordonf1]

EMC 7.1.1.189 generates this error when trying to save a DVD image file to disk, even with the default save location as %userprofile%\My Documents\My Videos.

 

My guess is DVD Builder really saves a temporary file somwhere that limited users don't have access to, and then moves it to the specified location.

 

I thought this suite was "Designed for Windows XP" certified. Isn't it supposed to run with limited accounts?

[grandpabruce]

EMC 7.1.1.189 generates this error when trying to save a DVD image file to disk, even with the default save location as %userprofile%\My Documents\My Videos.

 

My guess is DVD Builder really saves a temporary file somwhere that limited users don't have access to, and then moves it to the specified location.

 

I thought this suite was "Designed for Windows XP" certified. Isn't it supposed to run with limited accounts?

 

Yes, it is designed for XP. You couldn't use it in ME or 98. Are you on a network? When you installed it, did you choose All Users when prompted for a response?

[gordonf1]

Are you on a network? When you installed it, did you choose All Users when prompted for a response?

 

Standalone machine (Toshiba Satellite, XP Home SP2, NTFS file system). Installed for "All users." Not restricted to Toshiba Satellite notebooks though -- I've had this happen on a Dell Inspiron running XP Pro SP2 and on my own home built machine running Win2K Pro SP4.

 

First I tried it unpatched and got the "Image file error." I applied the 7.1.1.189 patch and received the same message.

 

It seems I can burn a DVD from DVD Builder and from Videowave but I cannot create a disk image file. The only difference is that the error comes up with a limted account but does not with an administrator account. The folder it writes the image to by default (%userprofile%\My Documents\My Videos) lets me create folders, save projects, copy and modify files just like it should.

 

I've tried granting modify access to Users (limited users) for a couple of other folders to see where it's trying to write to, but ultimately I might have to use Filemon or some other utility to figure out where it's trying to write to when it generates the error.

[Guest mlpasley]

It might be trying to write to the TEMP file under Windows Start\ Control Panel\ System Properties\ Advanced\ Environmental Variables (bottom left). You can try to change that location and see if it helps.

[gordonf1]

It might be trying to write to the TEMP file under Windows Start\ Control Panel\ System Properties\ Advanced\ Environmental Variables (bottom left). You can try to change that location and see if it helps.

This was one of the folders I added Modify access to (%systemroot%\temp) but this didn't fix the problem. Not that limited users have any business writing anything in there because %temp% points to %userprofile%\local settings\temp for programs run as a user. Open a command prompt and type "set" to see where it and others point to by default.

 

There was an old bug in XP (and Win2K SP3 and SP4) that had some 16-bit apps use %systemroot%\temp for temporary files, but this was corrected in a patch for NTVDM for Win2K. It was never corrected in XP, but even so that only affects 16-bit apps. Videowave and DVD Builder are 32-bit apps.

 

*sigh* Ok, out comes Filemon. I found it:

 

 

It appears that DVD Builder opens the folder I'm trying to store the image to, but also tries a short test file on the root of the volume I'm asking it to store to.

 

But the root of %systemdrive%, if it's NTFS, is off limits by default for limited accounts on XP Service Pack 2. Users can create folders there, but not files. This was introduced in SP2 to ensure users stored their stuff in their own user profile or the Shared Documents folders. When I set up a Win2K machine these days I try to emulate the XP SP2 behaviour as well, to prevent unwanted software from installing.

 

While I suppose they could work around the bug by creating a test FOLDER first and then creating a test file, isn't this what %temp% is for in the first place? And why not put the test file in the folder I'm selecting?

[Guest mlpasley]

All good questions that I have no answer to because I don't work for Roxio.

[Larry]

This was one of the folders I added Modify access to (%systemroot%\temp) but this didn't fix the problem. Not that limited users have any business writing anything in there because %temp% points to %userprofile%\local settings\temp for programs run as a user. Open a command prompt and type "set" to see where it and others point to by default.

 

There was an old bug in XP (and Win2K SP3 and SP4) that had some 16-bit apps use %systemroot%\temp for temporary files, but this was corrected in a patch for NTVDM for Win2K. It was never corrected in XP, but even so that only affects 16-bit apps. Videowave and DVD Builder are 32-bit apps.

 

*sigh* Ok, out comes Filemon. I found it:

 

 

It appears that DVD Builder opens the folder I'm trying to store the image to, but also tries a short test file on the root of the volume I'm asking it to store to.

 

But the root of %systemdrive%, if it's NTFS, is off limits by default for limited accounts on XP Service Pack 2. Users can create folders there, but not files. This was introduced in SP2 to ensure users stored their stuff in their own user profile or the Shared Documents folders. When I set up a Win2K machine these days I try to emulate the XP SP2 behaviour as well, to prevent unwanted software from installing.

 

While I suppose they could work around the bug by creating a test FOLDER first and then creating a test file, isn't this what %temp% is for in the first place? And why not put the test file in the folder I'm selecting?

I'm afraid I'd have to agree with ML. I don't think any of the regular users here on the user boards are going to be able to help you out. Your best bet probably is to contact Roxio's tech support. On that vein, if this is because you have multiple copies you are using, you may want to start with your volume licensing rep at Roxio first.

[gordonf1]

I don't think any of the regular users here on the user boards are going to be able to help you out. Your best bet probably is to contact Roxio's tech support. On that vein, if this is because you have multiple copies you are using, you may want to start with your volume licensing rep at Roxio first.

I was hoping to find a Roxio / Sonic staffer among the forums. Their new contact system baffles me. Why do companies go out of their way to complicate the support process, set up discussion groups, make frustrated users click through endless menus only to have their support request eaten? Or answered by someone in India who reads their script and tells me to just run it as an admin?

 

OK I'm digressing. That had nothing to do with this bug and it was a cheap shot.

 

This isn't a matter of multiple copies either, as this was just on my home PC. I tried to demo Easy Media Creator on someone's notebook running XP SP2 when I ran into this problem. I happen to run Win2K at home, and I was careful to uninstall it at home first, and then uninstall it off the someone's notebook when I was done there and back on my home PC. I also happen to administer a couple of client networks running Win2K, but don't run Easy Media Creator, and I deal with bad design all the time.

[Larry]

I was hoping to find a Roxio / Sonic staffer among the forums. Their new contact system baffles me. Why do companies go out of their way to complicate the support process, set up discussion groups, make frustrated users click through endless menus only to have their support request eaten? Or answered by someone in India who reads their script and tells me to just run it as an admin?

 

OK I'm digressing. That had nothing to do with this bug and it was a cheap shot.

 

This isn't a matter of multiple copies either, as this was just on my home PC. I tried to demo Easy Media Creator on someone's notebook running XP SP2 when I ran into this problem. I happen to run Win2K at home, and I was careful to uninstall it at home first, and then uninstall it off the someone's notebook when I was done there and back on my home PC. I also happen to administer a couple of client networks running Win2K, but don't run Easy Media Creator, and I deal with bad design all the time.

 

Since you are a single user then (I was only guessing before that you might not be), just go the Tech Support route. It's not likely any Roxio rep is going to see this and be able to help out. Mostly they only make spot checks on here looking for information, ideas, or user abuses. For something as technical as you are looking at, they probably can't help you here either.

Good Luck