Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

"cannot save to dat file"

1 view
Skip to first unread message

d_c...@adobeforums.com

unread,
Nov 8, 2008, 11:42:51 AM11/8/08
to
When I click to implement action by a third party plugin (buZZ Pro 3) I get an error message -

"buzz error - cannot save to dat file".

If I click the only option - "OK" - the action proceeds correctly. I'd be grateful if anyone can tell me what the error message means. What is likely to be the problem if the buzz action is not being saved to a dat file? I am not clear what a dat file is.

This happened first when I was using CS3 and weirdly when I installed another plugin (Nik Sharpener) this corrected the buZZ problem and I stopped getting the buZZ error message. However, in CS4, installing Nik Sharpener did not sort out the buZZ problem. I have no idea why.

It's not the end of the world because I can still use the buZZ plugin but it's a nuisance - compounded by the fact that buZZ settings are not staying from one buZZ use to another. Perhaps this inability to keep the last settings used is related to a failure to save to a dat file.

Sorry this is so vague. I'd be very happy to get any ideas on what's happening and a solution.

Thanks.

Myle...@adobeforums.com

unread,
Nov 9, 2008, 7:30:33 AM11/9/08
to
Well, *.dat is probably a generic data dump created by the plugins themselves to store settings. As very clearly these files cannot be written for some reason, I guess it is once more a matter of file permissions and user priviliges. Therefore you will have to check the respective directories if under your user account the "User" and "System" have full access. The folders in question should be C:\Program Files\Adobe\Photoshop CS4\Plug-Ins and C:\Documents and Settings\dcole\Application Data\Adobe. The latter is by default an invisible system directory, so make sure to set Explorer's view options accordingly first.

Mylenium

d_c...@adobeforums.com

unread,
Nov 9, 2008, 12:57:16 PM11/9/08
to
Thank you very much for this advice. Sorry not to have responded sooner. I'll follow your suggestions and let you know how I get on..

David

d_c...@adobeforums.com

unread,
Nov 9, 2008, 1:35:25 PM11/9/08
to
Brilliant! Utterly Brilliant! I went to Files/Adobe/Adobe Photoshop CS4/Plugins/buZZ Pro 3/Data folder (which is determinedly Read Only) and finally to the BuzzPro.dat file inside this folder. This file is not Read Only, but I opened its Properties, selected "Security" and gave "Full Control" and "Modify" permissions to "Users" (in addition to the existing "System" permission). Bingo! That was all it took.

I have repeated all the steps above so that anyone suffering from the same problem with the buZZ plugin will know what to do.

Thanks again Mylenium for sorting out this irritating problem.

David

Myle...@adobeforums.com

unread,
Nov 10, 2008, 1:33:32 AM11/10/08
to
Glad it worked out for you. ;-)

Mylenium

Isabel...@adobeforums.com

unread,
Nov 21, 2008, 12:16:31 PM11/21/08
to
I tried the above method and can't seem to access System settings to grant permission. Any secrets for doing this.

This whole permission thing with Vista is driving me nuts!

And what's more somehow in working with files I must have inadvertently dragged my system file in Explorer so now I have TWO system files. That can't be too good.

What do I do to get rid of one SAFELY?

TIA.

Isabel

Isabel...@adobeforums.com

unread,
Nov 21, 2008, 12:16:44 PM11/21/08
to
Oops! Forgot to subscribe to get email notification.
Isabel

d_c...@adobeforums.com

unread,
Nov 21, 2008, 12:49:34 PM11/21/08
to
I am not sure what System file you mean. In my process the only "System" entity is a class of permission in the Security tab area of the BuzzPro.dat file which is in the Plugins/buZZ Pro 3/Data folder. Under the Security tab I just selected "Edit" (the permission) and then gave Full Control permission to Users. I do not understand where you are in Vista - where is the system file you have duplicated? Hopefully, someone here can give you some Vista specific advice.

David

Isabel...@adobeforums.com

unread,
Nov 21, 2008, 1:32:12 PM11/21/08
to
Thank you for your quick response, David. Being new to Vista and all the permissions I have to give, I'm a bit confused.
I have uploaded a screen grab to show you what I am experiencing in Vista. I can't seem to access the grayed out areas to allow permission:
<http://www.isabelcutler.com/Cantgivefullcontrol.jpg>

Isabel

d_c...@adobeforums.com

unread,
Nov 21, 2008, 7:34:01 PM11/21/08
to
OK. Try highlighting the "Users/Isabel\420\Users" line in the "Security" page and you should be able to change the permission to "Full Control" for Users.

David

Isabel...@adobeforums.com

unread,
Nov 21, 2008, 8:23:10 PM11/21/08
to
David! I appreciate your sticking with me on this. I cannot believe how much trouble I got myself into this afternoon mucking around with my computer. I am not a novice!

BuZZ Pro has been deleted from my machine because I started having a problem with one of my three hard drives running incessantly.

This machine is only one week old and was quiet as a sleeping lamb and all of a sudden this afternoon not long after I installed a new program, it just started running and running and running. Sounded like a machine gun.

I had that problem with Windows XP and indexing, which I turned off and that ended the problem, but I have no idea what's causing it this time.

I did a system restore to way before I was trying to get the license key into buZZ pro.

I am feeling as bad as when I saw "Fatal Error" on a computer screen many years ago!

Isabel

d_c...@adobeforums.com

unread,
Nov 21, 2008, 8:28:19 PM11/21/08
to
Bad luck. I've posted the solution to your other buZZ problem (reluctant serial code) in DPR/Retouching where you posted it. I am having no problems with buZZ Pro 3 in Vista and CS4.

Topaz Simplify looks very interesting.

Isabel...@adobeforums.com

unread,
Nov 21, 2008, 8:36:13 PM11/21/08
to
Thank you, David. I will have to take a look at Topaz Simplify!
I have disable indexing (for search) and windows fetch and the darned thing is still running.
Isabel
0 new messages