|
|
Me too a little, copying a file around the harddrive has nothing to do with support for video codec's, it is just a file.
The codec's only come into play once into some form of media player.
|
|
The author of the above post is a thinkbroadband staff member. It may not constitute an official statement on behalf of thinkbroadband.
|
|
|
XRaySpex,
Booting into safe mode did the trick: had to check "Full Control" from Security. Those settings seem to have stuck after booting normally and I can now do what I like with those mp4 files in the XP Shared Documents folder whilst physically operating the XP machine.
regsvr32 is a technique for deleting any corrupted file when other methods fail with XP.
Will I have to download ftp://ftp.dataforce.net/pub/support/WinNT4/Secure/sc...
or do you think those settings done whilst in safe mode will last indefinitely, guess only time will tell?
Cheers,
4M2.
|
|
|
|
MrSaffron,
"...codec's only come into play once into some form of media player."
Sorry not quite true: if one uses, for example, a AviSynth script with the VirtualDub app and one tries to export unknowingly using a codec that is not licensed for a particular function then a corrupt file can result, e.g. working on 1920x1080 video file that needs resizing larger than that size for stabilization, cropping and resizing back to 1920x1080 a small file will be created with the correct extension but may be corrupt and can not be deleted by normal means. Its not always a decoding issue with media players.
|
|
Register (or login) on our website and you will not see this ad.
|
|
|
I knew what regsvr32 is but didn't understand your reasons for using it; still I'll pass on that codec stuff. Will I have to download ftp://ftp.dataforce.net/pub/support/WinNT4/Secure/sc...
or do you think those settings done whilst in safe mode will last indefinitely, guess only time will tell? Those particular settings will stick, but you could have the same issues on other files transferred across the network in future, unless you can find out the root cause of why some such files end up with Full Control and some with Read Only. So I'd highly recommend installing that download to save having to boot into Safe Mode when this happens as well as giving you greater control of your own files in general.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 17 Meg Untweaked 19 Meg Tweaked WBC
|
|
|
|
XRaySpeX,
Thanks a million - now my networking between Win7 and XP has gone from 99% to 99.9% effective. As you say finding out why some files end up with full control and others don't should make it 100% effective.
I'll hold back on the download for a while until I'm sure that my Kaspersky false positive trojan issues with the codec are fully stable for a few days.
Many thanks for your excellent advice and patience,
4M2.
|
|
|
YVW! As you say finding out why some files end up with full control and others don't should make it 100% effective. Idea: Did you login as different Win7 users to transfer files to XP? You talk about transferring from diff. Win7 drives. Do some these users share their names with XP users and some not?
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 17 Meg Untweaked 19 Meg Tweaked WBC
|
|
|
XRaySpex,
Same user log-ins on both computers and all drives - only one user/adminstrator using the machines.
Will have to do a thorough check, but I feel that it is the files copied from the Win7 OS drive rather than those copied from the Win7 E:\ storage drive that didn't have full control by XP.
BTW. much prefer XP for general computing although Win7 32bit is great for editing videos with Sony Vegas
|
|
|
XRaySpeX,
Just done a quick test and I copied a 6 months old video file (contemporary with some of the ones that were troublesome) across the network from the Win7 OS drive to XP Shared Documents folder and it is under full control by XP (that file had not been previously copied via the network nor by any other means between machines) - the whole thing seems to be a mystery...definitely seems like the XP safe boot etc did the trick
|
|
|
Logging in on Win7, You could compare the Permissions of the original source of files, 1 that ended up as Full Control on XP and 1 that gave issues on XP by resulting as Read Only, and see if that gives you any clue; without doing any network transfers.
1999: Freeserve 48K Dial-Up => 2005: Wanadoo 1 Meg BB => 2007: Orange 2 Meg BB => 2008: Orange 8 Meg LLU => 2010: Orange 16 Meg LLU => 2011: Orange 17 Meg Untweaked 19 Meg Tweaked WBC
Edited by XRaySpeX (Fri 12-Aug-11 21:40:33)
|
|
|
|
XRaySpeX,
Permissions are the same on both original source files when viewed on the Win7 machine, i.e. Properties > Security > Permissions for System: Full control, Modify, Read & execute, Read, Write, are all allowed and Special permissions is neither Allow nor Deny. Advanced Security Settings > Permission entries are also the same with both files.
Don't you just love all the settings available for each file with Win7!!!
|