DTM and Vista x64 (v.6000)
in [Device Drivers]
|
Prev: severe HID problem
Next: Renaming USB drivers
From: David J. Craig on 20 Jan 2007 00:32 Are you running the server with a dozen or two clients and providing the OS images for each of them? One driver at a time, with the client OS being loaded directly on the client can work with a lot less memory. The CPU does get a little busy when several jobs are running at the same time. I suspect the databases will grow with time and may need a bigger drive over time. "Colin H" <colinh(a)noemail.noemail> wrote in message news:E8AC4B25-DAF0-4969-93AC-FBE7DE17879E(a)microsoft.com... > We've recently started giving DTM a whirl. It was a surprise to us that we > were going to need a Server 2003 machine, but ok. We nearly fell off our > chairs, however, when we read the ram/disk requirements! > We decided to try anyway, with the old hardware we had lying around spare: > 2GHz Athlon, 256MB RAM, 40GB hard disk. > All seems fine so far - though I'm still struggling to get to grips with > the > wonder of programming that is the DTM Studio (seriously - it seems very > impressive!). > Glad now we didn't simply believe the figures and go waste a load of money > on a new machine. Why are such huge minimum requirements given, or are we > going to hit problems somewhere down the line? > > > "Don Burn" wrote: > >> When you install the WDK, the initial installation dialog allows a choice >> of the development environment, DTM or both. You need to install the DTM >> controller on a seperate computer running Windows Server 2003 SP1, this >> machine needs a couple processors, 1MB or more of memory, and 200MB free >> of >> disk. You, also need one or more test computers for the DTM controller >> to >> drive, these require additional installations of parts of DTM (this is >> discussed in the release notes). So basically you need three or more >> computers: >> >> 1. Your development systems >> 2. A DTM controller computer >> 3. One or more test systems. >> >> >> -- >> Don Burn (MVP, Windows DDK) >> Windows 2k/XP/2k3 Filesystem and Driver Consulting >> http://www.windrvr.com >> Remove StopSpam from the email to reply >> >> >> "Eddie" <egrogan(a)apcc.com> wrote in message >> news:1167920137.695337.203510(a)51g2000cwl.googlegroups.com... >> > >> > >> > Hi there, >> > >> > I've just been asked to prepare our driver for WHQL submission. From >> > reading the documentation on the Mircosoft web-site, it seems that I >> > need to install a set of DTM components. My problem is that I can't >> > find where there components are located on the on the latest WDK >> > relaese from MS Connent site (6000.16386.a). I would appreciate if you >> > could tell me where I might find these components. Also, does anyone >> > know of any document that might detail how DTM should be used to test >> > 64-bit (or 32-bit) drivers on Vista. >> > >> > Any help would be greatly appreciated. >> > >> > Thanks >> > Eddie >> > >> > >> > DoronM wrote: >> >> Hi, >> >> >> >> Did you install the client using the network share? you need to >> >> install >> >> it >> >> using the network and not via WDK DVD >> >> if you did, it looks like you don't have connection problem >> >> >> >> Doron >> >> >> >> >> >> "Elad Raz" wrote: >> >> >> >> > Hi. >> >> > >> >> > I'm trying to build a test for vista submission. Unfortunately, the >> >> > client and the server are not speaking with each other. >> >> > >> >> > The problem is that the Studio can see only itself (WHQL) and the >> >> > 'Vista-PC' machine wasn't added to the machine pool. >> >> > >> >> > The network connection is OK, TCP port 1778 can be accessed by the >> >> > client. There is no firewall between these two computers. >> >> > >> >> > >> >> > Please help me! >> >> > >> >> > Regards, >> >> > Elad. >> >> > >> >> > >> >> > >> >> > Here is my hardware & software configuration: >> >> > WDK/DTM Build 6000 >> >> > Client OS: Vista 6000 (Business) on a x64 machine >> >> > >> >> > For the controller >> >> > ============ >> >> > >> >> > A x64 machine installed with a clean copy of Windows 2003 Service >> >> > Pack >> >> > 1 and the DTM controller (express install). This machine also >> >> > contains >> >> > a DTM Studio installed. >> >> > >> >> > The machine is not connected into a domain and don't have a >> >> > domain.(WORKGROUP) >> >> > >> >> > (The machine name is WHQL) >> >> > >> >> > >> >> > >> >> > For the client >> >> > ========== >> >> > >> >> > A clean Vista installation (Work location) with the client >> >> > controller >> >> > installed. The machine is connected to WORKGROUP. >> >> > >> >> > (The machine name is Vista-PC) >> >> > >> >> > >> >> > >> >> > ERROR MESSAGES >> >> > ================ >> >> > >> >> > Inside the WTTSrv.txt of the client, I see: >> >> > >> >> > ============================= >> >> > >> >> > .... >> >> > >> >> > .... >> >> > >> >> > WTTProtocolTCPIP::ClientOpen : Trying Identifier >> >> > >> >> > 10.6.1.15 VISTA-PC->WHQL: >> >> > >> >> > 2016 2088 2006:12:3 17:14:50:921 Entering COMM receive >> >> > VISTA-PC->WHQL: >> >> > >> >> > 2016 2088 2006:12:3 17:14:50:937 CMG: Heartbeat message successful. >> >> > >> >> > 2016 2088 2006:12:3 17:14:50:937 CMG: Heartbeat reply is empty. >> >> > >> >> > 2016 2044 2006:12:3 17:14:50:952 CMG: Plugin Loaded. >> >> > >> >> > .... >> >> > >> >> > .... >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC main thread. >> >> > >> >> > waking up to check health WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "CMG" is in >> >> > >> >> > state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "DIAG" is in >> >> > >> >> > state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "EaManager" >> >> > >> >> > is in state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "HOST" is in >> >> > >> >> > state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "MACMAN" is >> >> > >> >> > in state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "MESSAGING" >> >> > >> >> > is in state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Service "POLICY" is >> >> > >> >> > in state "RUNNING" WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > registered : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > Stopped : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services Stop >> >> > >> >> > Pending : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > Reset : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > Reset Pending : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > Paused : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services >> >> > >> >> > Pause Pending : 0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services Running >> >> > : >> >> > 7 >> >> > WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 WTTSVC: Services Start Pending : >> >> > 0 >> >> > WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:398 Request came for Service POLICY >> >> > WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:51:414 CheckForUpdate: AUTO-UPDATE KEY not >> >> > found assuming it is enabled WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:53:695 CheckForUpdate: The release share >> >> > version is 1.0.6000.0 WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:53:695 CheckForUpdate: Not updating the >> >> > installation. WTTsvcMainThread >> >> > >> >> > 2016 2032 2006:12:3 17:24:53:695 going back to sleep.... >> >> > >> >> > >> >> > >> >> > >> >> > >> >> > Inside the WTTSvc.txt server log I see >> >> > >> >> > =========================== >> >> > >> >> > 1652 856 2006:12:3 6:57:30:218 Entering >> >> > >> >> > CMGMachineIDMessageHandler Vista-PC->WHQL: >> >> > >> >> > 1652 856 2006:12:3 6:57:30:218 ParseCMGMessage XML >> >> > >> >> > String is <MachineId >> >> > >> >> > MachineGuid="534A5350-E387-4805-8497-D2D87FCB4CD0"><Key >> >> > >> >> > Name="Name"><Value>Vista-PC</Value></Key><Key >> >> > >> >> > Name="QualifiedName"><Value>Vista-PC</Value></Key><Key >> >> > >> >> > Name="MacAddress0"><Value>00-16-76-c8-fb-eb-00-00</Value></Key><Key >> >> > >> >> > Name="MacAddress1"><Value></Value></Key><Key >> >> > >> >> > Name="MacAddress2"><Value></Value></Key><Key >> >> > >> >> > Name="MacAddress3"><Value></Value></Key><Key >> >> > >> >> > Name="SmbiosUuid"><Value>64FE66D8-8550-DB11-B738-000C6E0802BC</Value></Key><Key >> >> > >> >> > Name="SmbiosAssetTag"><Value> >> >> > >> >> > </Value></Key><Key >> >> > >> >> > Name="SmbiosSerialNumber"><Value> >> >> > >> >> > </Value></Key><Key >> >> > >> >> > Name="SmbiosManufacturer"><Value> >> >> > >> >> > </Value></Key><Key >> >> > >> >> > Name="SmbiosModel"><Value> >> >> > >> >> > </Value></Key><Key >> >> > >> >> > Name="Drive0Vendor"><Value></Value></Key><Key >> >> > >> >> > Name="Drive0Product"><Value>WDC >> >> > >> >> > WD1600JS-00NCB1</Value></Key><Key >> >> > >> >> > Name="Drive0SerialNumber"><Value>2020202057202d4443574e41364d373234393538</Value></Key><Key >> >> > >> >> > Name="SqmMachineId"><Value>{8D9BCAC5-8E03-4A62-A803-75280E96ECE7}</Value></Key><Key >> >> > >> >> > Name="RamSize"><Value>1045741568</Value></Key><Key >> >> > >> >> > Name="Hash1"><Value>DA3AFDEDC429A7BF1FE7B54C583C47D7</Value></Key><Key >> >> > >> >> > Name="Hash2"><Value>BE6A06A406D960977CE89BADB0746ABD</Value></Key><Key >> >> > >> >> > Name="PublicKey"><Value>0602000000A400005253413100040000010001002F9B3C1244F4FC2A16B530507D9403D4925E6CE76D569124F2EA2E3E8C33F60551969C853367C64EC840BB246BD81448CF14BFE2824B3018E89021A35F46FEE3D95A4B4F6F278D8B2CA3B8F3FB9B6F997A9708BD74F07EB22C4F9F0D3064A6FB7FE8EE212E02D256C28C98D01B82D8C6161AD20888FD080645DA903D2550CA8AG06020000002400005253413100040000010001006D24657525874E1FCE2AE4E3EF92BE5098B1AF7813CE0F031F5F8E553529D2F4971EE8950FDACEFFDE7267E5497D136E3691CBC7215BBF70D6360C40D0F5FAC91E315A4D430FE8A16DEEB50A215FDAD6650ACC1E2037A90D12618569D6B4CBCD8552FF6A6FEA6D381C7DEA15D7C7C05A238A9015D09F350052C0BA02FD08B0EC</Value></Key><Key >> >> > >> >> > Name="RuntimeVersion"><Value>1.0.6000.0</Value></Key></MachineId> >> >> > >> >> > Vista-PC->WHQL: >> >> > >> >> > 1652 856 2006:12:3 6:57:30:406 Exiting >> >> > >> >> > CMGMachineIDMessageHandler Vista-PC->WHQL: >> >> > >> >> > 1652 856 2006:12:3 6:57:30:406 Entering Handler thread >> >> > >> >> > proc >> >> > >> >> > 1652 856 2006:12:3 6:57:30:406 Entering >> >> > >> >> > CMGHeartbeatMessageHandler Vista-PC->WHQL: >> >> > >> >> > 1652 856 2006:12:3 6:57:30:421 ParseCMGMessage XML >> >> > >> >> > String is <Heartbeat >> >> > >> >> > MachineGuid="534A5350-E387-4805-8497-D2D87FCB4CD0"><Module >> >> > >> >> > Name="CMG"><Details Value="0" /></Module></Heartbeat>
From: Colin H on 20 Jan 2007 08:46
Nope - just testing a couple of USB/BDA drivers! Didn't realise you could download os images. But then there's a lot I don't know about DTM yet - like getting the simplest of tests to run without a load of less-than-helpful "can't copy file" kind of errors..... Hopefully I'll soon figure out what I'm doing wrong! (I suppose my gripe was that the DTM docs give the impression that you *have* to have that spec of server - no attempt to scale requirements to levels of testing.) "David J. Craig" wrote: > Are you running the server with a dozen or two clients and providing the OS > images for each of them? One driver at a time, with the client OS being > loaded directly on the client can work with a lot less memory. The CPU does > get a little busy when several jobs are running at the same time. I suspect > the databases will grow with time and may need a bigger drive over time. > |