(BeSweetGUI) BeSweet Runtime Error '52'

[Letricheur]

I get this error message running the GUI0.6b 38 or 39 with either BeSweet 1.2 or b1.8 or b1.9. I use Win98 and have placed ansi.com in the GUI directory (same as the besweet.exe). The program stalls as it is opening and gives this error message. I searched the forums and found no solution. I tried deleting all the files and re-installing to no avail. Any ideas on how to solve this?

[DSPguru]

Read before reporting BeSweet bugs! (http://forum.doom9.org/showthread.php?s=&threadid=15738) (line 13).

[Letricheur]

I think there has been some misunderstanding, for which I am sorry. I did read the sticky beforehand and found no reference to runtime error 52. Also, I made no mention of vob inputs, which I have never used but somehow "(vob inputs)" was added to my post subject line. I hadn't even got far enough to state the input, the program just wouldn't open at all. I had intended to convert an ac3 to mp2.

Anyway, I eventually solved the problem by removing the registry software reference. After that the program opened and I was able to do the conversion. I found a reference to removing the registry key while scouring the forum; it was in relationship to another runtime error.

[DSPguru]

1. BeSweet & BeSweetGUI are two different programs. you have reported a "BeSweet Runtime Error '52'" (err52 = no support for vobs), while the problem was with BeSweetGUI (err52=file not found).
2. in 95% of the cases, searching (http://forum.doom9.org/showthread.php?s=&threadid=22978) for old posts will help you solve the problem.

[Letricheur]

Good point and good tip to be more precise.

[DSPguru]

:D

[Gorr]

Hi guys,
This morning haveing exact same problem with besweet gui.
Run-time erro '52'.
Bad file name or number

This thing appeared just this day two machines.
I tried downloading both besweet and gui from doom9 to no avail.
Still the same. However now gui will start and only then the box presenting the message appears. Pressing ok closes the program.

I have noticed the program title bar displayin win2k mode. Could it be that this mode cozes the problem?

Both machines having NT 4 operating system.

I tried searching the forum and
1 the search engin will not accept quires containing 52 as 52's length is less then 3 chars.
2 what has been yield without 52 din't contain any usable information.

Thanks