-Brading Software Message Board
+--Forum: Mp3/Tag Studio Support and Bug Reports
+---Topic: Windows 7 64 bit started by hfth_audio
Posted by: Guest on June 22 2011,02:24
After reading previous, posts on Win 7, I downloaded the latest version from the site to be sure I had the correct version. Cleaned up registry from previous install attempts, then installed mps3ts 3.5 beta 21.
Installation appeared to go OK. But when launching the app, it crashes with the message below.
Any ideas?
-David.
Problem signature:
Problem Event Name: APPCRASH
Application Name: mp3tag_s.exe
Application Version: 0.0.0.0
Application Timestamp: 2a425e19
Fault Module Name: mp3tag_s.exe
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 2a425e19
Exception Code: c000001d
Exception Offset: 000a19fd
OS Version: 6.1.7600.2.0.0.256.48
Locale ID: 1033
Additional Information 1: dcc4
Additional Information 2: dcc4422e68844330a1fd2a44908e7623
Additional Information 3: b83e
Additional Information 4: b83ee91744733f101e726c6110a81c5c
Posted by: Magnus Brading on June 22 2011,04:37
No, I have no idea what might be problem, since it seems to work crash free for all other users here on Windows 7 64 bit?
Posted by: Guest on Nov. 09 2011,19:22
i'm having the same problem. i really don't like it when software purveyors blame the user.
what arrogance.
Posted by: Magnus Brading on Nov. 15 2011,03:14
I don't "blame" anyone, but a crash that happens on 0.01% of all users' systems, without any further clues, is quite hard to debug (and yes, the probability of it being some other software on these systems interfering is actually quite high).
Posted by: Guest on Dec. 15 2011,21:48
Well, it seems that this issue may be more widespread than suggested. I have just upgraded to Windows/7 64bit and also have the same crash issue. I have downloaded the latest version from this website ad re-installed but same issue. At first I thought it was due to my choosing a different folder/file name for the product inside of "Program files (X86)" but I tried it again letting it use the default but same issue. Crashes each time I try to launch it.
I would like to see the developer take a bit more interest in this problem as it seems to be affecting more than just one person.
Posted by: Magnus Brading on Dec. 16 2011,14:49
Please post the version of Mp3/Tag Studio you are running, exactly as listed in your start menu.
Posted by: Guest on Dec. 16 2011,14:53
I've been a long time user of mp3tag and I still find it to be the best tagger for my purposes.
I've just put together a brand new computer using Windows7 Pro 64bit. I'm still at the point where I'm not sure if I like this new OS from M$ but I'll get used to it.
Installed and registered the latest version of mp3tag and it works just fine for me with one exception. The context (right-click) menus don't appear at all. Any ideas ?
I'm using the program as an Administrator in W7 Pro 64.
Mvh,
TomThumb
Posted by: Magnus Brading on Dec. 16 2011,15:00
Tom, please see the following thread:
< http://www.magnusbrading.com/cgi-bin....;t=3667 >
Posted by: Guest on Dec. 16 2011,18:21
Hi
Thanks for responding. Here is are the statistics....
Start Menu Listing: Mp3-Tag Studio 3
Properties of above:
Target Type = Applicaiton
Target Location = Mp3-Tag Studio 3.05
Target = Mangus Brading\Mp3-Tag Studio 3.05\Mp3tag_s.exe
Start in = C:\Program Files (x86)\Magnus Brading\Mp3-Tag Studio 3.05\
Shortcut Key = None
Run = Normal Window
Advanced = Run as admin is UN-checked. Run in separate memory sapce is gray but CHECKED
Compatibility tab: nothing checked
PLease let me know what other info will help you look into this issue.
Posted by: Guest on Dec. 16 2011,18:25
Hi Again,
Here is some more info that may be useful. This is the text from the pop up that comes up when I try to execute the program. The title of this pop up box is "mp3tag_s.exe has stopped working". Below is the content of the "details" drop down...
Problem signature:
Problem Event Name: APPCRASH
Application Name: mp3tag_s.exe
Application Version: 0.0.0.0
Application Timestamp: 2a425e19
Fault Module Name: StackHash_37f4
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 00000000
Exception Code: c0000005
Exception Offset: 7efde000
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 37f4
Additional Information 2: 37f432d17f3c3ae51e5eafd85842ea37
Additional Information 3: fd5e
Additional Information 4: fd5ed954a7fd7d93eb7bb3789d4e52ab
Posted by: Magnus Brading on Dec. 16 2011,23:20
That's what I suspected, you are not using the latest beta after all, but rather the older 3.05 version.
Please use version 3.5 beta 22, and it will work.
So, yes, it is only one single person that claims to have had problems with the 3.5 version.
Posted by: gharris999 on Dec. 16 2011,23:49
I'm having trouble with MP3TagStudio 3.5b22 and Windows 7 ultimate 64bit too.
Whenever I launch the program, I'm getting several (7, in fact) "Warning: Inconsistency in registry entries detected" message boxes, one after the other.
If I run the program with administrator credentials, I don't get the warning message boxes.
Sounds like a registry permissions problem.
This was a clean install from mp3ts35b22.zip on a system that hadn't had MP3TagStudio installed on it before. I did manage to enter my registration info when running it with administrative credentials.
Posted by: gharris999 on Dec. 16 2011,23:58
Actually, this has to be registry permissions problems. If I run regedit.exe with administrative credentials, I see the expected "Magnus Brading Software" key under HKCU\Software. However, if I run regedit.exe under my regular user account, the key is missing under HKCU.
Running regedit.exe again as an administrator, if I export the "Magnus Brading Software" key to a reg file and then merge that regfile under the regular user account, MP3TagStudio then starts up fine without the annoying message boxes.
Verdict: running as a regular user, MP3TS3.5b22 fails to create its registry keys under HKCU.
Posted by: Guest on Dec. 17 2011,00:33
Thanks, re-installing with beta 22 seems to have done the trick. It's so nice when it's a simple thing (operator error in this case :-) )
Posted by: Magnus Brading on Dec. 18 2011,01:13
Gharris999, the registry key issue you are describing doesn't have anything to do with permissions.
The HKCU key is by default unique per user in Windows, and this is because each user account should be able to have individual configuration settings.
Posted by: gharris999 on Jan. 13 2012,17:13
None the less, while the software gets installed by an administrative account, when it is subsequently run by a regular user, it fails to create the required keys under HKCU. I think I've shown that I've verified that this is the case.
Posted by: gavind on Jan. 27 2013,15:01
Another work around here is to have this software run as admin. Even with the user profile.
end