> The drawback of running Vista in a Virtual PC is you won't see the UI > problems associated with Areo. A 256MB Video card is sufficient to run > Vista with Areo to see the problems.
heh-heh, no wonder it ran so well <g>... Thanks for the Heads Up. I did, as an aside, also install Vista from MSDN onto the same machine as a dual boot unit. I also ran my app under that envionment, just because (I had not considered the aero impact). That video card has 512Mg RAM, but I do not know if it actually uspport aero anyway (DirectX 9, or something that is required for aero in addition to just > 256Mg RAM?). Thus far not one of my clients is running Vista, other than on a laptop in one case. That client initially loved the Vista interface, then quickly became disenchanted when the OS began to give him some pushback. Finally the HDD gave out within warranty. He got a punchier unit with XP Pro on it as a swap out, and is happy as a clam now. Gil > -----Original Message----- > From: [email protected] > [mailto:[email protected]]on Behalf Of Tracy Pearson > Sent: Monday, December 29, 2008 3:17 PM > To: [email protected] > Subject: RE: Base Windows Vista recommendations; FoxPro porting issues? > > > The drawback of running Vista in a Virtual PC is you won't see the UI > problems associated with Areo. A 256MB Video card is sufficient to run > Vista with Areo to see the problems. > > If Memory serves, Doug Hennig had a blog entry relating to Vista issues. I > don't know if he ever covered them all, or had a synopses post pointing to > the others. > > Tracy > > -----Original Message----- > From: Gil Hale > Sent: Monday, December 29, 2008 3:05 PM > > This would be a great time to look into the M$ Empower ISV program, where > you can get full MSDN for a year for under $400 (used to be about > that much, > I do not know the current fee). I did this for a few years running (in a > lull this year and next, no need for it yet), and set up the VPC > 2007 app in > a 2Gb P4 2.8Ghz machine and set up FistYa Ultimate (from the MSDN > pack). No > need for me to get a separate physical machine to test my VFP apps under > FistYa (it did fine, other than being slower - some of which was > due to the > VPC I am sure.). > > https://partner.microsoft.com/40011351 (you will want to use IE, > of course, > to have their site display correctly. Not FF friendly) > > > Gil > > > > -----Original Message----- > > From: Ted Roche > > Sent: Monday, December 29, 2008 2:33 PM > > > > Well, one of our customers has decided to update some of their > > workstations and wants to run Windows Vista. > > > > We'll need to obtain a machine to test our vertical-niche FoxPro 7 > > application on Vista and make the changes necessary to run on that > > platform. Two questions for our esteemed forum: > > > > 1. Recommendation of a base machine to run Vista on for compatibility > > testing purposes? > > > > I'm thinking that just buying the OS (Vista Biz for $299) and trying > > to install it on a VM under Linux and then running it via RDP might > > introduce too many variables that would make testing and > > troubleshooting difficult, so I'd just buy an acceptable box, throw it > > in the data center and let us work on it as needed. How much > > processor, RAM and video should I spec? What can I expect a pre-built > > box to run me? Any recommendation on vendors? > > > > I can pick up a certified refurb Dell Lattitude D630: 2 Gb RAM, Core > > Duo 2.16, 14.1", 60 Gb SATA HDD for $729 > > > > or an equivalent OptiPlex for $539. Both have video cards w/ 256 mb. > > > > Is that sufficient? Bear in mind we'd just be using the machine for > > installation and support testing, not as a developer's workstation. > > > > 2. How to port a WinXP app to Vista? > > > > Is there a list of the gotchas moving to Vista and a set of > work-arounds? > > > > For example, I know there will be permissions issues; the app is using > > the classic loader trick of starting a small VFP EXE, checking for > > updates on the server, downloading and chaining them. I understand > > Vista's security can be an issue here, and that there's some trick of > > using user-writable directories to cache executables; I'll have to > > visit the leafe.com archives for details. Has anyone collected a list > > of these tricks anywhere? > > > > -- > > Ted Roche > > Ted Roche & Associates, LLC > > http://www.tedroche.com > > > > > > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
