well I don't program myself but if I can get away with it I usually get it. So you will see me upgrading all the freebees I can, and if I can I may just stuff something that shouldn't stuff into a computer in that, and if it crashes, then obviously I can't, but if not I can. I have stuffed 98 into a 95 rated system and xp into a 98 rated system. And sometimes it worked better than the old os. Its a pitty vista is the way it is otherwise I may just stuff vista into my xp system. I wish microsoft kept dcm because if they did guess what I'd be stuffing. Dcm is not the only issue but its the main reason I have not upgraded nor will upgrade until such point I can no longer get an xp licence or my system totally craps out on me. Correction, I know within 3 months I can not get an xp licence which is why I may get a new system and put this old one on backup. I actually wouldn't be supprised if I manage to miss vista out all together and instead get the system after. Windows me was a real dud and the new vista tech is a bit on that side to. Bugs that were all ok in xp exist in vista, not sure with the latest service pack, but still. At 07:34 a.m. 11/04/2008, you wrote: >Hi Jim, > >Quote >Isn't Visual Basic 2008 the whole object oriented thing and not at all >like the Basic >languages that one might be used to and love to use? >End quote > >If you are asking if Visual Basic 2008 is object oriented rather than >procedural programming that is correct. It is very rare now days to find >a programming language that does not in some way use object oriented >design and techniques. It is the foundation of modern programming >design, and there is several very good reasons why programmers have >migrated to an object oriented design mottle. >That said Visual Basic 2008 is not totally different from what you know >and love. For example, a simple print message sub would look like this. > >' VB 2008 print message sub. >Public Sub PrintMessage(message As String) >TextBox1,.Text = message >End Sub > >So with your current knowledge of Visual Basic 6 you already know most >of the basic things like creating subs, if statements, loops, bla. All >you would have to learn is how to use the .Net Framework which is the >foundation of Visual Basic 2008, and to design your programs with a >object oriented mottle in mind. Since you have been totally a procedural >programmer you might have a bit of a tougher time adapting to the new >concepts than someone coming at this totally fresh. However, you do have >the advantage of knowing how to design an if statement so that would >certainly aid someone like you in getting up to speed. > >Quote > Didn't you also once say that >one can not compile and distribute the executable file with it? >End quote > >No, I did not. With Visual Basic Express 2008, which is free, you can >certainly build and redistribute fully working executable and *library >files. The only major diference between Visual Basic Express and Visual >Basic Pro that would concern us is that the Pro versions of Visual Basic >2008 come with Microsoft Setup Installer, Dotfuscator, Microsoft Source >Safe, Microsoft SQL Pro, etc. Most of that you wouldn't probably even >miss though the tools are pretty handy to work with if you have them. > >Quote >Who cares if VB6 is 98 era if it still works and really no one playing >the game would >ever know the difference. >End quote > >Well, to be honest this has been an issue you and I have never agreed >upon, and perhaps never will. The problem lies in the fact that there >are personal reasons as well as technical ones behind our opinions here. >This dramatically influences how we think and feel about a topic like this. >Your general opinion of technology changes has been a view of "who cares >if the old still works." The problem I personally find with the "who >cares" opinion is you are really talking about your own personal opinion >and not an opinion of the blind gaming community as a whole. I am sure >there are plenty of blind gamers on this list that share your opinion >and are quite satisfied using Jaws 4.02, Visual Basic 6, Windows XP, >etc. However, there is also others on the list, such as myself, who want >to move on and take advantage of the new technologies out there for us. >Weather you agree or not Visual Basic 6 is at the end of its life cycle >and mainstream companies are migrating away from its use, and new >technologies such as Visual Basic 2008 is replacing it which are more >compatible for Windows Vista and beyond. >Many blind gamers are moving on, such as myself, and I find myself >frustrated by your general opinions of the newer technologies. For >example, Windows Vista comes with much tighter security policies in >place over Windows XP, and one of these features is user account >control. It so happens that there are several accessible games that >conflict with user account control. I know many blind gamers that simply >disable user account control management so their games will run >correctly as under XP. As a developer myself I feel forcing a user to >disable his or her security to play a game is definitly the wrong way to >go about solving the problem. It makes the end users system less secure, >and it doesn't really solve the problem. It would be better if the >programmer takes it upon him or herself and bring his/her programs up to >technical specifications rather than simply ignoring the problem. >In my personal case I decided I wanted user account control to remain >enabled because I want that extra layer of security Vista provides. In >addition I increased my security setting to run as standard user, rather >than admin, and my Vista machine is very security conscious. More so >than I suspect than your own setup is. SO I had to find a work around >for games like yours that weren't really up to tech specs for Vista. I >discovered after trile and error that by installing them to my user\home >directory that they worked just fine with user account control though I >would have prefered you had addressed and corrected the reasons they >were crashing on my system. >Now, as a developer myself I understand what you are thinking here. I >chose to increase the system security, I chose to use user account >control, I chose to upgrade, bla. In short you are likely thinking it is >all my fault that your games aren't working correctly, because you wrote >them the way you did for your needs. Looking at it from that angle it is >all completely true. >However, there is the other side of the coin where I am coming from that >says I should have the freedom to have maximum security and safety on my >computer, be running whatever version of Windows I like, and be able to >run your games without having to come up with work arounds just because >they don't meet industry technical standards. There isn't a right or >wrong answer to this one, but in my opinion it is always better to meet >technical standards so you are ready for these kinds of issues when they >come up. >Cheers. > > > >--- >Gamers mailing list __ Gamers@audyssey.org >If you want to leave the list, send E-mail to [EMAIL PROTECTED] >You can make changes or update your subscription via the web, at >http://audyssey.org/mailman/listinfo/gamers_audyssey.org. >All messages are archived and can be searched and read at >http://www.mail-archive.com/[EMAIL PROTECTED] >If you have any questions or concerns regarding the management of the list, >please send E-mail to [EMAIL PROTECTED]
--- Gamers mailing list __ Gamers@audyssey.org If you want to leave the list, send E-mail to [EMAIL PROTECTED] You can make changes or update your subscription via the web, at http://audyssey.org/mailman/listinfo/gamers_audyssey.org. All messages are archived and can be searched and read at http://www.mail-archive.com/[EMAIL PROTECTED] If you have any questions or concerns regarding the management of the list, please send E-mail to [EMAIL PROTECTED]
