long install checked build

Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

Well, if you are developer, you really would have known the purpose and requirments of running. As many have said, if you are developer you will run it. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Norman Diamond" wrote in message

Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

Exactly, I know the purpose and I read the requirements. Exactly, since I am a developer I will try to run it. I even explained the purpose; was there some part of it (which you quoted) that wasn't sufficiently clear?
The question is how long it will take to install. Do you know?
"Andre Da Costa [Extended64]" wrote in message

Well, if you are developer, you really would have known the purpose and requirments of running. As many have said, if you are developer you will run it. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

It should depend on the system - so going off an average system...
1.8Ghz AMD processor, 512MB RAM, 80GB hard drive - I'd say just under an hour.
I could stretch it to say 50 mins - 80 mins, but it totally depends on whether you're computer's good or not!
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) $B"d(B ZackNET Enterprises: www.zacknet.co.uk $B"d(B MSBlog on ResDev: http://msblog.resdev.net $B"d(B ZackNET Forum: www.zacknet.co.uk/forum $B"d(B VistaBase: www.zacknet.co.uk/vistabase $B"d(B This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

You have installed the Checked Build? -- -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Zack Whittaker (R2 Mentor)" wrote in message It should depend on the system - so going off an average system...
1.8Ghz AMD processor, 512MB RAM, 80GB hard drive - I'd say just under an hour.
I could stretch it to say 50 mins - 80 mins, but it totally depends on whether you're computer's good or not!
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) $B"d(B ZackNET Enterprises: www.zacknet.co.uk $B"d(B MSBlog on ResDev: http://msblog.resdev.net $B"d(B ZackNET Forum: www.zacknet.co.uk/forum $B"d(B VistaBase: www.zacknet.co.uk/vistabase $B"d(B This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message

Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

Varies according to the amount of RAM and processor speed, the more, the better I guess, check out this post about Installing Windows Vista build 5270 in Virtual PC 2004: http://www.computerperformance.co.uk/vista/virtualpc2004.htm
If it can take up to 1 hour to install on most systems, it could probably be double that. Some persons have experienced 3 hour installation time, for Vista (not VPC). This should change a lot though by BETA 2 when Staged builds is implemented which has been reported to bring the install time down to 15 to 30 mins. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Junxiu Li" wrote in message

How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

It's recommended you don't install Vista into a Virtual Machine though - the Ultimate Edition will have V-PC installed by default so you can put XP back onto it :op
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

Ah, no, Virtual PC Express has not been determined as part of the Ultimate SKU, but it will be a part of the Enterprise Edition: Microsoft Windows Vista Enterprise, Virtual PC Express Available Fall 2006! http://www.microsoft.com/licensing/programs/sa/benefits/vista.mspx
Please also note, this will only be available to Volume License Customers. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Zack Whittaker (R2 Mentor)" wrote in message

It's recommended you don't install Vista into a Virtual Machine though - the Ultimate Edition will have V-PC installed by default so you can put XP back onto it :op
-- Zack Whittaker Microsoft Beta (Windows Server R2 Beta Mentor) » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: http://msblog.resdev.net » ZackNET Forum: www.zacknet.co.uk/forum » VistaBase: www.zacknet.co.uk/vistabase » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, mother or cat. Let's be clear on that one!

You have a checked build of 5270? I could only find the retail build of that one.
When I tried to install a checked build of beta 1 into VPC, the installer crashed very early. That's why I had to buy a separate computer to try to install the checked build of beta 1. (Though there's another reason too. A real computer can access USB devices that VPC can't, so a driver for those devices can only be tested on a real computer.)
"Junxiu Li" wrote in message

How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

Windows Vista/Longhorn Server currently does not support Virtual PC. -- -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Norman Diamond" wrote in message

You have a checked build of 5270? I could only find the retail build of that one.
When I tried to install a checked build of beta 1 into VPC, the installer crashed very early. That's why I had to buy a separate computer to try to install the checked build of beta 1. (Though there's another reason too. A real computer can access USB devices that VPC can't, so a driver for those devices can only be tested on a real computer.)
"Junxiu Li" wrote in message How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

"Norman Diamond" wrote in message

Exactly, I know the purpose and I read the requirements. Exactly, since I am a developer I will try to run it. I even explained the purpose; was there some part of it (which you quoted) that wasn't sufficiently clear?
The question is how long it will take to install. Do you know?
"Andre Da Costa [Extended64]" wrote in message Well, if you are developer, you really would have known the purpose and requirments of running. As many have said, if you are developer you will run it. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

I'd say forever, since your system isn't adequate to run Vista, although I've heard of others putting the regular Vista on similar machines. I really don't see how you will be able to develope anything with such a slow machine.
-- Nancy Ward MVP MSN Messenger

After reading the link before,I have come to know why I am having a terriblly slow installation experience.It is because of my poor physical memory.aha...
Thanks all the same.
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Andre Da Costa [Extended64]" wrote in message

Varies according to the amount of RAM and processor speed, the more, the better I guess, check out this post about Installing Windows Vista build 5270 in Virtual PC 2004: http://www.computerperformance.co.uk/vista/virtualpc2004.htm
If it can take up to 1 hour to install on most systems, it could probably be double that. Some persons have experienced 3 hour installation time, for Vista (not VPC). This should change a lot though by BETA 2 when Staged builds is implemented which has been reported to bring the install time down to 15 to 30 mins. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Junxiu Li" wrote in message How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

You can try again when the official beta 2 comes out with optimization. :) -- -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm "Junxiu Li" wrote in message

After reading the link before,I have come to know why I am having a terriblly slow installation experience.It is because of my poor physical memory.aha...
Thanks all the same.
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Andre Da Costa [Extended64]" wrote in message Varies according to the amount of RAM and processor speed, the more, the better I guess, check out this post about Installing Windows Vista build 5270 in Virtual PC 2004: http://www.computerperformance.co.uk/vista/virtualpc2004.htm
If it can take up to 1 hour to install on most systems, it could probably be double that. Some persons have experienced 3 hour installation time, for Vista (not VPC). This should change a lot though by BETA 2 when Staged builds is implemented which has been reported to bring the install time down to 15 to 30 mins. -- Andre Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta FAQ for MS AntiSpy http://www.geocities.com/marfer_mvp/FAQ_MSantispy.htm
"Junxiu Li" wrote in message How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

On Wed, 1 Feb 2006 07:39:37 -0800, Andre Da Costa [Extended64] wrote:

Varies according to the amount of RAM and processor speed, the more, the better I guess, check out this post about Installing Windows Vista build 5270 in Virtual PC 2004: http://www.computerperformance.co.uk/vista/virtualpc2004.htm

Thanks Andre, might get me out of my install problem I had under the app. -- Tekguru (Daron Brewood) MS-MVP/Mobile Devices
Webmaster: UKs largest Pocket PC Site http://www.4WinMobile.com

if i were you i would put the second hdd into your system and disable the first in your bios, this will allow you to use your good computer for both purposes, but whatever you do, disable the original hdd first as when you install vista, it can mess with the other instasll even though its not on the same hdd. i dont know the reason why but ive run into problems doing vista instaslls withought disabling my other hdds, so., thats my advice to you
after the install, you will have the option of switching hdds in the bios, but i dont recommend having them both enabled at the same time, this way you can boot into one or the other. unless of course, you require having that computer running at all times for whatever reason., point is, dont run vista on that piece of crap pc, you wasted your money on such a low end system considering you bought it to run vista. you could put xp on that one though, no problem, and trasfer the settings from the better pc to use the good pc for vista, this is probably the better of my recommendAtions

anyways, good luck
and by the way, im interested, what are you developing at the moment? maybe we can help test it out if its of any interest.

benny b





"Norman Diamond" wrote in message

You have a checked build of 5270? I could only find the retail build of that one.
When I tried to install a checked build of beta 1 into VPC, the installer crashed very early. That's why I had to buy a separate computer to try to install the checked build of beta 1. (Though there's another reason too. A real computer can access USB devices that VPC can't, so a driver for those devices can only be tested on a real computer.)
"Junxiu Li" wrote in message How long will it take to install 5270 into a VPC?
-- Best Regards, Junxiu Lee http://blogs.itecn.net/blogs/junxiulee
Diyinside presents - written by four MS MVPs http://win2k600tips.msitpro.com Diyinside,the pleasure of technology...
"Norman Diamond" wrote in message Checked builds of Windows operating systems are useful when developing and testing device drivers and some kinds of applications. They are included in MSDN subscriptions for this purpose.
Checked builds run a bit slower than ordinary builds (usually called "free" or "retail"). That's because of all the extra checking they perform in order to help catch bugs. Running a bit slower has sometimes been said to mean running 20 times slower.
Well, that was before Vista.
I'm installing the checked build of Vista beta 1 onto a computer that was purchased for this purpose, as a crash box, intending to help check if a driver or certain applications that I have sometimes been writing might be capable of running under Vista. This has a Pentium III 600 MHz, 320 MB of RAM, and a 17 GB disk partition which started out empty now has around 12.9 GB of free space remaining.
One nice thing about the Vista install method is that during the last stage, when the screen says "Do not restart your computer during this time", you can press Shift+F10 to get a command prompt. This allows things like starting taskmgr to see that MSCORSVW.EXE is taking 99% of the CPU time, or typing a dir command to see the amount of free disk space.
For the first three months, MSCORSVW.EXE was indeed taking 99% of the CPU time. Although 320 MB of RAM isn't luxurious in the Vista era, it was enough, and paging wasn't a problem. However, after the first three months, MSCORSVW.EXE has dropped to an average of around 50% of the CPU time because it has become necessary to wait for some paging operations. The pagefile is now up to 1 GB.
Well, this installer started on Sept. 24, 2005. If checked builds are 20 times slower than ordinary builds, and the checked build's installer has been running for nearly 20 weeks so far, then the ordinary build's installer would be running for nearly 1 week so far with no clue about how much longer it's going to take.
How long does it really take to install a checked build?

wrote in message

if i were you i would put the second hdd into your system and disable the first in your bios,

Although a few notebooks do have room for two internal hdds, this isn't one. Even if it were, I can't imagine what difference it would make to disable one hdd. The installer is running, the installer has nearly the entire machine to itself, except that I did do a Shift+F10 to start taskmgr.exe and the event viewer, and to do a "dir" command nearly every day to see if the installer seems to have added any files that day.

unless of course, you require having that computer running at all times for whatever reason.,

I think it's the only computer that I've kept running at all times for more than 4 months. Of course back in the dark ages when we ran operating systems like VMS or Unix it was possible to keep a computer running for more than 4 months (or more than 4 years), but still there were occasional power failures or OS upgrades which would require reboots. Anyway in this one only the installer is running (plus cmd.exe, taskmgr.exe, and the event viewer which I think is mmc.exe).

point is, dont run vista on that piece of crap pc, you wasted your money on such a low end system considering you bought it to run vista.

I bought it to test some kinds of software under Vista. That's why I'm installing the checked build.
I DID read the release notes for Vista beta 1 before buying the machine. The release notes even contradict themselves, saying that the minimum memory is 256MB and also saying what to do if your memory is less than 256MB, but it doesn't matter, I have more than that.

you could put xp on that one though,

Yes, I have the checked build of Windows XP on another partition. Now it's well past the deadline for activation of that one, so I wonder what will happen if I boot it again after Vista either finishes installing or crashes.

and trasfer the settings from the better pc to use the good pc for vista,

Parse I that can't.

and by the way, im interested, what are you developing at the moment?

At that time of starting the install, I was experimenting with a driver, but I no longer have time for that because paying customers have priority. Now part of a current application includes a service under Windows XP. Things like this do benefit from being tested under betas of future operating systems.

maybe we can help test it out if its of any interest.

I'm not the one who could let you do it. (Except maybe the driver I was experimenting on, since it only came from published sources plus my own efforts.)

well, i guesse i was of no help to you at all then, good luck finding a solution







"Norman Diamond" wrote in message

bbaker@ilrcsudbury.ca> wrote in message if i were you i would put the second hdd into your system and disable the first in your bios,
Although a few notebooks do have room for two internal hdds, this isn't one. Even if it were, I can't imagine what difference it would make to disable one hdd. The installer is running, the installer has nearly the entire machine to itself, except that I did do a Shift+F10 to start taskmgr.exe and the event viewer, and to do a "dir" command nearly every day to see if the installer seems to have added any files that day.
unless of course, you require having that computer running at all times for whatever reason.,
I think it's the only computer that I've kept running at all times for more than 4 months. Of course back in the dark ages when we ran operating systems like VMS or Unix it was possible to keep a computer running for more than 4 months (or more than 4 years), but still there were occasional power failures or OS upgrades which would require reboots. Anyway in this one only the installer is running (plus cmd.exe, taskmgr.exe, and the event viewer which I think is mmc.exe).
point is, dont run vista on that piece of crap pc, you wasted your money on such a low end system considering you bought it to run vista.
I bought it to test some kinds of software under Vista. That's why I'm installing the checked build.
I DID read the release notes for Vista beta 1 before buying the machine. The release notes even contradict themselves, saying that the minimum memory is 256MB and also saying what to do if your memory is less than 256MB, but it doesn't matter, I have more than that.
you could put xp on that one though,
Yes, I have the checked build of Windows XP on another partition. Now it's well past the deadline for activation of that one, so I wonder what will happen if I boot it again after Vista either finishes installing or crashes.
and trasfer the settings from the better pc to use the good pc for vista,
Parse I that can't.
and by the way, im interested, what are you developing at the moment?
At that time of starting the install, I was experimenting with a driver, but I no longer have time for that because paying customers have priority. Now part of a current application includes a service under Windows XP. Things like this do benefit from being tested under betas of future operating systems.
maybe we can help test it out if its of any interest.
I'm not the one who could let you do it. (Except maybe the driver I was experimenting on, since it only came from published sources plus my own efforts.)

the reason i told you to disable the second hdd (thinking you had a box not a book) was when i installed vista the first time, my other drives were enabled and for some reason even though i was not installing vista to the other drives, it changed things on my xp installs and made them extreamly buggy. im not sure why it did this especially considering i did not give it a partition but its own seperate drive, this is why i warned you to disable other installed hdds, then again, i figured you would have a tower.
but this info is still good for anyone to know, as it may help save them from making the same error i did .






"Norman Diamond" wrote in message

bbaker@ilrcsudbury.ca> wrote in message if i were you i would put the second hdd into your system and disable the first in your bios,
Although a few notebooks do have room for two internal hdds, this isn't one. Even if it were, I can't imagine what difference it would make to disable one hdd. The installer is running, the installer has nearly the entire machine to itself, except that I did do a Shift+F10 to start taskmgr.exe and the event viewer, and to do a "dir" command nearly every day to see if the installer seems to have added any files that day.
unless of course, you require having that computer running at all times for whatever reason.,
I think it's the only computer that I've kept running at all times for more than 4 months. Of course back in the dark ages when we ran operating systems like VMS or Unix it was possible to keep a computer running for more than 4 months (or more than 4 years), but still there were occasional power failures or OS upgrades which would require reboots. Anyway in this one only the installer is running (plus cmd.exe, taskmgr.exe, and the event viewer which I think is mmc.exe).
point is, dont run vista on that piece of crap pc, you wasted your money on such a low end system considering you bought it to run vista.
I bought it to test some kinds of software under Vista. That's why I'm installing the checked build.
I DID read the release notes for Vista beta 1 before buying the machine. The release notes even contradict themselves, saying that the minimum memory is 256MB and also saying what to do if your memory is less than 256MB, but it doesn't matter, I have more than that.
you could put xp on that one though,
Yes, I have the checked build of Windows XP on another partition. Now it's well past the deadline for activation of that one, so I wonder what will happen if I boot it again after Vista either finishes installing or crashes.
and trasfer the settings from the better pc to use the good pc for vista,
Parse I that can't.
and by the way, im interested, what are you developing at the moment?
At that time of starting the install, I was experimenting with a driver, but I no longer have time for that because paying customers have priority. Now part of a current application includes a service under Windows XP. Things like this do benefit from being tested under betas of future operating systems.
maybe we can help test it out if its of any interest.
I'm not the one who could let you do it. (Except maybe the driver I was experimenting on, since it only came from published sources plus my own efforts.)