runtime error 713 Class not registered

I ran inno script version 7.2, to create the iss file. So, in inno script version 7.2 after these,
1) vb runtime files folder
2) visual basic project file (.vbp)
3) inno setup script output file (.iss)
there is a label "OS Updater:" and a combo box next to it with the selections:
None
Win 9x/ME/NT/2K/XP
Win 95/98
Win ME
Win NT
Win 2000
Win XP

and four option buttons Beta, Trial, Release, None. The selected is Release.
I have selected Win XP in the combo box, as my operating system is windows xp. But what happens if for example if i want to install my application in a machine with Windows 98? I think that i must use again inno script in OS Updater combo box i must select Win 95/98 and then push the button "create setup script", so i have to recompile the new iss file. And other peoples with other machine aren't obliged to have installed on their computers inno script and inno setup. Also, if i select none in the combo box next to OS Updater label MDAC's aren't add to iss file.

You olny need the OS Updater for ALL WINDOWS. It will handle every windows OS (as he repeats himself).

"You olny need the OS Updater for ALL WINDOWS. It will handle every windows OS (as he repeats himself)."
I have download the OS Updater for ALL WINDOWS and ran it.

If you saw my iss file, you would have seen

Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_XP.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater

Because i have selected, as i mentioned before, Win XP in the combo box nexto to label "OS Updater" in inno cript 7.2 because my operating system is Windows XP. This, doesn't means that another computer's operating system will be Windows XP, maybe will be Win 95/98, or Win NT whatever.
That means that the VB_DCOM_MDAC_JET_AutoSetup_XP.exe to iss file, must be changed to VB_DCOM_MDAC_JET_AutoSetup_9x.exe if the operating system of a machine is Win95/98. So, at least this i have to do, if i want to install my application in a machine with operating system Windows 95 or 98 is to modify the iss file to the point:
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_9x.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater
So, i have to recomplire the iss file and then run my setup application.
As you can understand, this user, that has a machine that his operating system is Win95/98, isn't obliged to install on his pc the inno setup for me, to change the
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_XP.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater
to
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_9x.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater
and wait to recompile the setup file to run it.
And that's happen because in inno script 7.2 the user must select for OS Updater one of these selection.
None
Win 9x/ME/NT/2K/XP
Win 95/98
Win ME
Win NT
Win 2000
Win XP

If a user selects Win Xp the filename in iss file is:
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_XP.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater

If a user selects Win 95/98 the filename in iss file is:
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_9x.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater

If a user selects Win NT the filename in iss file is:
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_NT.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater

etc.. for other selections

Would it be good idea to change the filename in the iss file:
from
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup_XP.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater
to
Filename: {src}\Support\VB_DCOM_MDAC_JET_AutoSetup.exe; Parameters: /NORESTART /VERYSILENT; WorkingDir: {tmp}; Flags: skipifdoesntexist; Tasks: AutoOSUpdater

The VB_DCOM_MDAC_JET_AutoSetup is the name of the automatic OS Updater setup file downloaded for all version.

Thank you,
much again.

[Comments]
; In the folder where your installation was created is a folder named Support. In this folder you will place the AutoOSUpdater, .Net Framework and the Scripting Runtime installations
; that you want to deploy with your installation. Both you installation exe and this folder need to be deployed fo your installation to work properly

What that exactly means in the iss file? Is there a difference if i run the autoOSUpdater from another file before run my application setup from another folder? And what about "Scripting Runtime installations", does this means the project in vb 6? And what does i t mean "Both you installation exe and this folder need to be deployed fo your installation to work properly"? How can you deploy both installation exe and this folder? Have i to create another iss file to include the support folder? And how?

Thank you
very much.

You basically need to read some of the documentation about that. It is explained very clearly. Look for Internal Installs and External Installs. You can deploy your installation packages two ways but you need to understand the differences if you are going to change things and settings. Inno Script defaults to external installations in which you will need to deploy the Support folder as well. If you chose Internal Installs then you would not need to deploy the support folder.