![]() |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
| Welcome to Windows Vista Forums. Our forum is dedicated to helping you find solutions with any problems, errors or issues you are experiencing with Windows Vista. The Vista forum also covers news and updates and has an extensive Windows Vista tutorial section that covers a wide range of tips and tricks. |
| |||||||
![]() |
| |
| | #1 (permalink) |
| | how to test a script for compatibility with different Windows Versions Hi, is there a way to test a VBS script (that uses lots of WMI functions) for compatibility with Win2000,XP,Vista,Win2003,Win2007 ...? The only way that I can think of is to install each of this Versions (for example on a virtual PC...) However, I still have to buy a licence for each version.... Is there something like a "emulator" that I could use for compatibility checks...? Or maybe a website that offers such a service...? thank you |
My System Specs![]() |
| | #2 (permalink) |
| | Re: how to test a script for compatibility with different Windows Versions "Heinz" <no@xxxxxx> wrote in message news:e1QTRC63JHA.4412@xxxxxx Quote: > Hi, > > is there a way to test a VBS script (that uses lots of WMI functions) for > compatibility with Win2000,XP,Vista,Win2003,Win2007 ...? > > The only way that I can think of is to install each of this Versions (for > example on a virtual PC...) > However, I still have to buy a licence for each version.... > > Is there something like a "emulator" that I could use for compatibility > checks...? > Or maybe a website that offers such a service...? > > thank you post (which I answered in detail), the thought crossed my mind that a little "thank you" would have gone down well instead of just asking for yet another free piece of advice. IMHO the "thank you" closure in your initial post, while common, is too perfunctory. Maybe I'm old-fashioned. |
My System Specs![]() |
| | #3 (permalink) |
| | Re: how to test a script for compatibility with different Windows Versions Heinz wrote: Quote: > > is there a way to test a VBS script (that uses lots of WMI functions) for > compatibility with Win2000,XP,Vista,Win2003,Win2007 ...? > > The only way that I can think of is to install each of this Versions (for > example on a virtual PC...) > However, I still have to buy a licence for each version.... > > Is there something like a "emulator" that I could use for compatibility > checks...? > Or maybe a website that offers such a service...? > classes, indicates which OS does or does not support the class or function, but not always (especially for OS's no longer supported). Yes, you would need a license for each OS installed. You might look into an MSDN subscription, which would allow you to install each OS you mention (and other software) for testing, as long as it's not in production. For hardware you can either get cast off or used machines for cheap with miniumum requirements (you can upgrade RAM easily), or spend the money on a few powerful computers and install virtual PC's. I try to maintain a lab with as many OS's as possible for testing, but it is not easy. I get cast off computers from clients I consult for. I don't care about performance, but I don't have Windows 7, for example, because I have no hardware that would support it. I had to spend money for hardware that would support Windows Server 2008. Actually, if your code works on Windows 2000, it will work on all of the others, except for the security and UAC issues introduced with Vista. You really only need to test on Windows 2000 and Vista to ensure it works on all. -- Richard Mueller MVP Directory Services Hilltop Lab - http://www.rlmueller.net -- |
My System Specs![]() |
| | #4 (permalink) |
| | Re: how to test a script for compatibility with different Windows Versions you are right - but I have sent my second question before reading your answer to my first question... so I hope it is not too late to say "Thank you" "Pegasus [MVP]" <news@xxxxxx> schrieb im Newsbeitrag news:uoc0iM63JHA.1716@xxxxxx Quote: > > "Heinz" <no@xxxxxx> wrote in message > news:e1QTRC63JHA.4412@xxxxxx Quote: >> Hi, >> >> is there a way to test a VBS script (that uses lots of WMI functions) for >> compatibility with Win2000,XP,Vista,Win2003,Win2007 ...? >> >> The only way that I can think of is to install each of this Versions (for >> example on a virtual PC...) >> However, I still have to buy a licence for each version.... >> >> Is there something like a "emulator" that I could use for compatibility >> checks...? >> Or maybe a website that offers such a service...? >> >> thank you > I don't know the answer to this question but in referring to your previous > post (which I answered in detail), the thought crossed my mind that a > little "thank you" would have gone down well instead of just asking for > yet another free piece of advice. IMHO the "thank you" closure in your > initial post, while common, is too perfunctory. Maybe I'm old-fashioned. > |
My System Specs![]() |
| | #5 (permalink) |
| | Re: how to test a script for compatibility with different Windows Versions ok, thanks... I guess I have buy the licences and install some virtual machines ... "Richard Mueller [MVP]" <rlmueller-nospam@xxxxxx> schrieb im Newsbeitrag news:O8DfHd63JHA.5816@xxxxxx Quote: > Heinz wrote: > Quote: >> >> is there a way to test a VBS script (that uses lots of WMI functions) for >> compatibility with Win2000,XP,Vista,Win2003,Win2007 ...? >> >> The only way that I can think of is to install each of this Versions (for >> example on a virtual PC...) >> However, I still have to buy a licence for each version.... >> >> Is there something like a "emulator" that I could use for compatibility >> checks...? >> Or maybe a website that offers such a service...? >> > I know of no emulator application. Sometimes documentation, such as for > WMI classes, indicates which OS does or does not support the class or > function, but not always (especially for OS's no longer supported). Yes, > you would need a license for each OS installed. You might look into an > MSDN subscription, which would allow you to install each OS you mention > (and other software) for testing, as long as it's not in production. For > hardware you can either get cast off or used machines for cheap with > miniumum requirements (you can upgrade RAM easily), or spend the money on > a few powerful computers and install virtual PC's. > > I try to maintain a lab with as many OS's as possible for testing, but it > is not easy. I get cast off computers from clients I consult for. I don't > care about performance, but I don't have Windows 7, for example, because I > have no hardware that would support it. I had to spend money for hardware > that would support Windows Server 2008. > > Actually, if your code works on Windows 2000, it will work on all of the > others, except for the security and UAC issues introduced with Vista. You > really only need to test on Windows 2000 and Vista to ensure it works on > all. > > -- > Richard Mueller > MVP Directory Services > Hilltop Lab - http://www.rlmueller.net > -- > > |
My System Specs![]() |
![]() |
| Thread Tools | |
| |
Similar Threads | ||||
| Thread | Forum | |||
| Windows 7 ISV Compatibility Test | Vista General | |||
| Script to test authentication on Windows local accounts? | PowerShell | |||
| Script to retrieve file versions | VB Script | |||
| Domestic license and key compatibility with foreign versions | Vista installation & setup | |||
| Test your router/IGD for Vista compatibility | Vista networking & sharing | |||