http://clix.to/YugiPC
Home    |    Downloads    |    Card  Lists    |    Links    |    Game  Pics    |    Codes    |    Character  Info    |    Help

First thouroughly read both the History.txt and Readme.txt files, as these will answer alot of your questions. Second the game has several bugs (Some cards or combos have unexpected results.) And it is not exact in regards to the official rules of the actual card game. It is a work in progress Updates are made, just check back. It is still a very enjoyable game. I will answer any and all E-mail in regards to this game.

Run-time error '53': File not found: 'FILENAME'.

When trying to find help with this error message please be specific. Goto Google and do a search on the exact error, you'll probably find what your looking for. Chances are it's a Visual Basic Run-time file.

Here's an article when and how to install VB files.
Windows XP OCX Error Messages

Run-time error '339'
Component 'COMCTL32.OCX' or one of its dependencies not correctly registered: a file is missing or invalid.

Comctl32.ocx is installed by Microsoft Office 2000. Microsoft Office XP removes this control when upgrading from Office 2000, because the control is no longer used by Office programs.
If you don't have COMCTL32.OCX. Download it from www.imagedig.com/page6.html Or EDO's Site (files yugirun1 & 2.zip) Then register COMCTL32.OCX so it functions properly. (Goto: Start, Run, and type in regsvr32 COMCTL32.OCX) If you need to unregister a non compatable version type:
"regsvr32 COMCTL32.OCX /u"
You'll either get: "DllRegisterServer... succeeded," or "DllRegisterServer... failed. Return code was: 0x8002801c"

Cause:

The error value ‘0x8002801c’ means ‘Error accessing the OLE registry’.

Remedy:

It is likely that permissions on part of the registry have been changed to deny you access. You will need to be a local administrator to register the COM object.

If you are a local administrator (i.e. a member of the ‘Administrators’ group on the workstation) then most likely someone or some application has modified (intentionally or unintentionally) the permissions on one or more registry keys and that this is preventing access. To identify which registry key is causing the problem use Regmon (a freeware tool published by System Internals). Use Regmon to capture all registry access when regsvr32 is run. If an ‘OpenKey’ request fails with ‘Access Denied’ (which is listed by Regmon as ‘ACCDENIED’) then run regedt32 and check the permissions on that registry key. If necessary cange the permissions on the key to grant local Administrators ‘Full Control’. They try registering the COM object again. The only times I have encountered this problem it affected more than one key, so be prepared to repeat this process.

--------------------------------------------------------------------------------

These notes have been tested with Windows NT4, XP and 2000

If you are still having a hard time with the COMCTL32.OCX file, you can also download an Executable file to install it directly from the Microsoft site. Goto: More Information Section


'Unexpected runtime error 50003'

Error message boxes saying "Unexpected error" or "Error 50003" may be symptoms of an incorrect version of the common controls being registered. Microsoft have issued at least 4 versions of comctl32.ocx and 2 of comdlg32.ocx, comct232.ocx and comct332.ocx. All the versions of each component have the same GUID but they are not compatible. This breaks the rules of COM but Microsoft allow themselves to break their own rules however much havoc it causes amongst their customers.

A compiled VB program will work with the set of controls it was compiled with or later versions. However, programs complied with a newer issue of one of these OCXs will not run if an older one is registered. If a VB5 authored program on this web site has this problem it needs the VB6 versions of the controls.

Download the required version and unzip the files into a separate location. For safety do not directly overwrite the Windows\System directory. Unregister the old controls and move them to a temporary location. Then copy the new controls to the System folder and register them. You can register the new controls wherever they are, but some depend on DLLs in the System folder and may not work in another location. To switch back to the original files, reverse the process.

More points to note:

  • Any installation program may install and register a newer version of an OCX without the user noticing, because all existing programs still run. If you install a program written using VB6 it is very likely to install the VB6 versions of the controls to the System folder, overwriting older versions.
  • OCX files may be placed anywhere on the disk, it is only convention to put them in the Windows System folder. If there are different versions of the same file in different places, only the most recently registered one is accessible. As already noted, they may not work in other places due to regular (non-COM) DLL dependencies.
  • Under Windows NT, if you move a registered OCX the Windows registry is updated to point at the new location. If the file is deleted to the recycle bin, the registry points there.
  • VB6 introduced a completely new common control file called MSCOMCTL.OCX. This does not cause any problems because the GUID was changed along with the file name. We are concerned here with the modified versions of the VB5 controls which VB6 also installs.
See this Entire Article