Hi Andy,
Visual Basic 6 is very old and out of date technology. Next year 
Microsoft will be completely dropping support for it on Windows 2000, 
XP, and Vista so it isn't even worth bothering with any more. However, 
there are alternatives for writing accessible games.
There is Visual Basic .Net 2005 which is a fully modern object oriented 
language which has allot in common with Visual Basic 6, but also is 
quite diferent in many ways.
Another language used allot by blind gamers is C# .Net 2005, called 
C-Sharp, which is also easy to learn, and is a great beginners language.
You can download free compilers for C# .Net and Visual Basic .Net from 
the Microsoft web site, and you can purchase accessible books from
http://safari.oreilly.com.
As far as registration goes the reg info can be stored in a dll and can 
be easily attached to your application. All you need to do is follow the 
SDK or API guidelines for having the application use the dll to decode 
the product keys.
I'm right now working on my reg program, and if you know what you are 
doing they aren't super difficult to make.
Basically you need three things. A dll to generate and decode product 
keys, a reg program which takes the product key checks to see it is 
valid and write out a license file, and a product key generator that the 
developer uses to creat the keys.
That's all I am going to say on reg program development as that is a 
sensative subject amung developers.
How the keys are generated, where they are stored, etc is a matter of 
privacy.

Andy Smith wrote:
> How bout vb6? Where can I get a good book on vb6? And the reg
> programs, that must be real hard to compose with vb6. Maybe a dll
> attatched to an .exe, example: .exe program runs, then dll runs ontop.
> Dont know if it works though.


_______________________________________________
Gamers mailing list .. Gamers@audyssey.org
To unsubscribe send E-mail to [EMAIL PROTECTED] You can visit
http://audyssey.org/mailman/listinfo/gamers_audyssey.org to make
any subscription changes via the web.

Reply via email to