OK so maybe this one isnt nVidias fault but its always nice to point the finger at them after all that BSOD in Vista due to crappy drivers.....thats another story....
Having had the joy of booting into the BDD image and getting the NIC to see my distribution share we moved on to getting the image installed, no problem until after the first boot and I get a 'disk read error has occurred' which appears to come straight after the BIOS.
First up, its not likely your drive if you are in the middle of an install so dont panic. Secondly there are some fixes (http://support.microsoft.com/kb/931760):
In short:
1) Change the BIOS settings from your drive to LARGE from AUTO, it will still be full size.
2) Get hotfix 931760, this can be downloaded from the nice chaps at http://thehotfixshare.net/
The problem has something to do with the XP kernel hence a hotfix for XP, fixed in SP3 apparently but who wants to jump the gun early on that one eh?
Thursday, 29 May 2008
BDD 2007 and nForce
I just started experimenting with BDD 2007 with MDT 2008, great product and the right price - FREE!
Got the whole thing setup, smacked in some drivers, XP with SP2, few apps for testing, under an older test computer with an nForce2 mobo it worked a treat except for a few app tweaks but under the newer Shuttle SN68SG2 systems we use in house there is another issue.
The Win PE 2 that is used is based on Vista so Vista drivers are required for it to build the PE image that boots from the network, fine no probs, however the driver used a two-tier model as discussed here: http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/29/language/en-US/Default.aspx
Now this is all well and good however it doesnt work! Looking at other drivers I have added for the nForce2 mobo the two-tier driver did as it was told and a 'Network Bus Enumerator' driver is added as well automatically. With the Vista on the 630a drivers this doesn't happen so when I boot my image it simply doesnt work, although it boots off the network image entering the user details for the share simply says 'Network Not Found', running IPConfig shows only the internal network adapter :(
Lets hope nVidia can sort out there drivers once and for all, since the days of playing with BartPE nForce drivers have never been easy.
UPDATE: It would seem that the Vista driver for this type of board works differently, I removed all the nVidia drivers from BDD and updated the install point and readded the WIM image, booting now works.....on to the SATA driver now :(
Got the whole thing setup, smacked in some drivers, XP with SP2, few apps for testing, under an older test computer with an nForce2 mobo it worked a treat except for a few app tweaks but under the newer Shuttle SN68SG2 systems we use in house there is another issue.
The Win PE 2 that is used is based on Vista so Vista drivers are required for it to build the PE image that boots from the network, fine no probs, however the driver used a two-tier model as discussed here: http://www.deployvista.com/Blog/JohanArwidmark/tabid/78/EntryID/29/language/en-US/Default.aspx
Now this is all well and good however it doesnt work! Looking at other drivers I have added for the nForce2 mobo the two-tier driver did as it was told and a 'Network Bus Enumerator' driver is added as well automatically. With the Vista on the 630a drivers this doesn't happen so when I boot my image it simply doesnt work, although it boots off the network image entering the user details for the share simply says 'Network Not Found', running IPConfig shows only the internal network adapter :(
Lets hope nVidia can sort out there drivers once and for all, since the days of playing with BartPE nForce drivers have never been easy.
UPDATE: It would seem that the Vista driver for this type of board works differently, I removed all the nVidia drivers from BDD and updated the install point and readded the WIM image, booting now works.....on to the SATA driver now :(
Wednesday, 28 May 2008
FlexLM and ESX
We were a little worried about migrating a server running FlexLM as the licensing was tied to the MAC address of the network card and we had never tried this before.
We took the plunge however with a couple of potential fixes in the pipeline. Well first fix and a winner! All we had to do on the guest was enter the MAC address of the old server into the advanced settings of the network card configuration. Windows did the rest and as it is in the VM itself this means VMotion will work too.
The second fix involved editing config files on the VM to hardcode the MAC onto the ESX servers virtual cards, this of course would mean the server would have to reside on that virtual card at all times which could be a problem when using HA and VMotion.
We took the plunge however with a couple of potential fixes in the pipeline. Well first fix and a winner! All we had to do on the guest was enter the MAC address of the old server into the advanced settings of the network card configuration. Windows did the rest and as it is in the VM itself this means VMotion will work too.
The second fix involved editing config files on the VM to hardcode the MAC onto the ESX servers virtual cards, this of course would mean the server would have to reside on that virtual card at all times which could be a problem when using HA and VMotion.
Subscribe to:
Posts (Atom)