• Registered: 2008-04-23
  • Posts: 6

Topic: W2k Dell Latitude D531

Hi list,

I´m currently having problems installing W2k on a Dell Latitude D531 notebook. We´re using unattended install (unattended.sf.net) and driver packs (Method 2), which works perfectly on any other system. With the D531, install works smoothly, devices are being recognized and the installation of w2k finishes. But at the first boot of the os, the progress bar (white on black, "Starting Windows") freezes at 100%.

If I put only the original Dell drivers for chipset, nic audio and video into the i386\$oem$\$1 of my installation source (no driverpacks included), the installation runs as desired and Windows boots up correctly.

What am I doing wrong? I´d be glad, if you had any hints on this.
If you need any further information, please let me know.

Thanks and best regards,
Chris

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: W2k Dell Latitude D531

Welcome to DriverPacks.

Does it start in safe mode in win2000?
Can you post the winnt.sif (without the key) please? (use code tags)
A HWID txt in code tags in a second post would be nice too.

Question, does it also happen when you do XP on the dell latitude 531?
(Do you use DriverPacks 7052? Then please clear QSC when you plan to slipstream another type of OS)
Question, what versions do you use? (a slipstream log can be useful.)
Question, in which order do you prepare the source?

The answer was 42?
Kind regards, Jaak.
  • Registered: 2008-04-23
  • Posts: 6

Re: W2k Dell Latitude D531

Hello and thanks for the quick reply.

w2k doesn´t start in safe mode either. I also tried starting in vga-mode, but no success.
I didn´t try xp yet, since the dells have to have w2k installed on them.

Usually, I do the following steps to prepare the source:
- copy W2k-cdrom to harddisc
- slipstream service pack 4 into source
- slipstream update rollup 1 for service pack 4 into source
- slipstream driverpacks into source
- copy source to installation server

How do I get the desired HWID txt?

My winnt.sif looks like this:

;
; Generated by DriverPacks BASE 7.05.2
; http://www.driverpacks.net/
;


[Data]
	MsDosInitiated=No
[GUIRunOnce]
	command9="%SystemDrive%\DPsFnshr.exe"

Here you can find the slipstream.log

2008-04-08 11:05:51 : <INIT> DriverPacks BASE 7.05.2 initialized.
2008-04-08 11:05:51 : <INIT> Host environment: WIN_2000 Service Pack 4 on X86 CPU.
2008-04-08 11:05:51 : <INIT> Created temporary working directory.
2008-04-08 11:05:51 : <INIT> Imported proxy settings from Internet Explorer.
2008-04-08 11:05:51 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Chipset 8.03!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack CPU 7.04.1!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Graphics A 8.02!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Graphics B 7.12.1!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Graphics C 7.12!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack LAN 8.02.1!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack MassStorage 8.02.1!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Sound A 8.02.1!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack Sound B 7.12!
2008-04-08 11:05:51 : <INIT> 	Detected DriverPack WLAN 8.03!
2008-04-08 11:05:51 : <INIT> 	Could not detect any 3rd party DriverPacks.
2008-04-08 11:05:51 : <INIT> 	Finished scanning.
2008-04-08 11:05:51 : <INIT> Detected settings file "C:\una\DPs_BASE.ini".
2008-04-08 11:05:51 : <INIT> No OS could be detected.
2008-04-08 11:05:51 : <INIT> Imported settings from settings file.
2008-04-08 11:05:51 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2008-04-08 11:05:51 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2008-04-08 11:05:51 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2008-04-08 11:05:51 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2008-04-08 11:05:51 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (CCC) was set.
2008-04-08 11:05:51 : <INIT> [OptionalSettings]\KTD default (false) was set.
2008-04-08 11:05:51 : <INIT> [OptionalSettings]\QSC default (no)    was set.
2008-04-08 11:05:51 : <GUI>  Initialized GUI.
2008-04-08 11:05:51 : <GUI>  Created a list of all available language files.
2008-04-08 11:05:51 : <GUI>  Set the last used language, English, as the GUI language.
2008-04-08 11:06:05 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to C:\una\w2k4urdp.
2008-04-08 11:06:06 : <GUI>  Windows 2000 Professional-CD -  SP4 detected.
2008-04-08 11:06:06 : <GUI>  The platform wnt5_x86-32_disc will be used (which is the 'disc' installation platform for the OS family 'wnt5_x86-32').
2008-04-08 11:07:21 : <GUI>  Saved settings!
2008-04-08 11:07:21 : <GUI>  Closed GUI.
2008-04-08 11:07:21 : <SEL>  Selected module: mod_slip_w2k_x86-32_disc_m2.
2008-04-08 11:07:26 : <PREP> Extracted DriverPack MassStorage to a temporary working directory.
2008-04-08 11:07:29 : <PREP> Removed all attributes from \I386.
2008-04-08 11:07:29 : <PREP> Deleted old DriverPack MassStorage text mode drivers.
2008-04-08 11:07:29 : <PREP> Generated \I386\winnt.sif file.
2008-04-08 11:07:29 : <PREP> Created a backup of \I386\txtsetup.sif.
2008-04-08 11:07:29 : <PREP> Created a backup of \I386\dosnet.inf.
2008-04-08 11:07:29 : <SLIP> Created necessary directory structure for method 2.
2008-04-08 11:07:30 : <SLIP> Copied files necessary for method 2.
2008-04-08 11:07:30 : <SLIP> Extracted files necessary for method 2.
2008-04-08 11:07:30 : <SLIP> Created \I386\presetup.cmd file.
2008-04-08 11:07:30 : <SLIP> Updated \I386\txtsetup.sif to support method 2.
2008-04-08 11:07:30 : <SLIP> Updated \I386\dosnet.inf to support method 2.
2008-04-08 11:07:50 : <SLIP> Copied DriverPacks to \OEM.
2008-04-08 11:07:50 : <SLIP> Updated \I386\svcpack.inf file to support KB888111.
2008-04-08 11:07:50 : <SLIP> Updated \I386\txtsetup.sif file to support KB888111.
2008-04-08 11:07:51 : <SLIP> Updated \I386\dosnet.inf file to support KB888111.
2008-04-08 11:08:09 : <SLIP> Slipstreamed DriverPack MassStorage text mode driver files.
2008-04-08 11:08:10 : <SLIP> Removed entries from \I386\txtsetup.sif that will be updated.
2008-04-08 11:08:10 : <SLIP> Removed entries from \I386\dosnet.inf that will be updated.
2008-04-08 11:08:31 : <SLIP> Updated \I386\dosnet.inf and \I386\txtsetup.sif to support DP MassStorage text mode drivers.
2008-04-08 11:08:31 : <SLIP> Updated \I386\winnt.sif to support method 2.
2008-04-08 11:08:31 : <SLIP> Updated DPsFnshr.ini to enable KTD for all DriverPacks.
2008-04-08 11:08:31 : <SLIP> Updated \I386\winnt.sif's GUIRunOnce section.
2008-04-08 11:08:31 : <SLIP> Slipstream finished in 1 minutes and 9 seconds.
2008-04-08 11:08:46 : <CLNP> Temporary working directory successfully deleted.
2008-04-08 11:08:46 : Program terminated.

Thank you very much for helping.
Best regards,
Chris

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: W2k Dell Latitude D531

Hi

you said you use unattended, but DriverPacks BASE did not find winnt.sif when you streamed so you use another answertxt.
I wanted to see that answertxt.

This is either not processed when you run setup, or you forced yours so yours get used and then the drivers won't be properly processed.
In my signature you see links to tutorial (it is a good read), and to a HWIDS reading tool which will create a txt you can post.

I suggest you start from a source you have never ran DriverPacks on, put your answertxt in there and rename it to winnt.sif, after which you run DriverPacks BASE.
(I don't know why you need KTD.. the last lines say it set dpsfinisher to enable KYD.. this is a waste of time on laptops.)

have you added Dot_net to windows 2000?
CCC uses .net, so that choice looks wrong.
-------

(I want to see the answertxt file you use for a particular reason. remove the key)
- - -
I just read your posts again and see it runs setup from a file from server?

DriverPacks enhanced sources can be made to run from RIS, and siginets autoimage should be a good tool for that.
I have no experience with that sad
(right now I don't even have networked computers at home. I've been too busy and found no time to set up new machines for that.)

Last edited by Jaak (2008-04-23 21:55:00)

The answer was 42?
Kind regards, Jaak.
  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: W2k Dell Latitude D531

OH, Wlan 803 would break KTD.
now, there is good reason to update all downloads. smile
most are 804 now.. smile

The answer was 42?
Kind regards, Jaak.
  • Registered: 2008-04-23
  • Posts: 6

Re: W2k Dell Latitude D531

Hi,

Yes I run networked install. The answer file is called unattend.txt
You can find it here:

; General user information
[UserData]

[GuiUnattended]
    ; See <http://unattended.sourceforge.net/timezones.html>
    TimeZone=35
    OEMSkipRegional=1
    OemSkipWelcome=1

[Unattended]
    DriverSigningPolicy=Ignore
    UnattendMode=DefaultHide
    FileSystem=ConvertNTFS
    ExtendOemPartition=1
    OemSkipEula=Yes
    OemPreinstall=Yes
    ; Needed for XP - see <http://support.microsoft.com/?kbid=294801>.
    UnattendSwitch=Yes

[Components]
    ; Install IIS by default
    iis_common=Off
    iis_inetmgr=Off
    iis_www=Off
    ; Docs suggest iis_pwmgr only works on Win2k, but include it
    ; anyway
    iis_pwmgr=Off
    ; Include docs
    iis_doc=Off

[Data]
    AutoPartition=1
    MsDosInitiated="0"
    UnattendedInstall=Yes

[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=75

[LicenseFilePrintData]
    AutoMode=PerServer
    AutoUsers=5

[Networking]
    InstallDefaultComponents=Yes

[NetOptionalComponents]
    ; Install Print Services for UNIX
    LPDSVC=1

Some more properties are being held in a csv-file:

Lookup,Property,Value
Default,FullName,******
Default,OrgName,"******"
Default,AdminPassword,******
Default,"Windows 2000 Professional- ProductID","00000-00000-00000-00000-00000"
Default,"Windows 2000 Professional- ProductKey","11111-00000-00000-00000-00000"
Default,JoinWorkgroup,INSTALL
Default,format_cmd,"format /y /z:seriously /q /u /a /v: c:"
Default,replace_mbr,1
Default,ntp_servers,10.3.3.1
Default,TimeZone,110

The hardware ID txt reads as follows:

=========== 
PCI Devices 
=========== 
PCI\VEN_1002&DEV_4380&SUBSYS_02061028&REV_00\3&61AAA01&0&90 : Standard-Zweikanal-PCI-IDE-Controller
PCI\VEN_1002&DEV_4383&SUBSYS_02061028&REV_00\3&61AAA01&0&A2 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_1002&DEV_4384&SUBSYS_00000000&REV_00\3&61AAA01&0&A4 : PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_1002&DEV_4385&SUBSYS_02061028&REV_14\3&61AAA01&0&A0 : PCI Device
PCI\VEN_1002&DEV_4386&SUBSYS_02061028&REV_00\3&61AAA01&0&9D : Standard PCI-zu-USB erweiterter Hostcontroller
PCI\VEN_1002&DEV_4387&SUBSYS_02061028&REV_00\3&61AAA01&0&98 : Standard-OpenHCD-PCI-zu-USB-Hostcontroller
PCI\VEN_1002&DEV_4388&SUBSYS_02061028&REV_00\3&61AAA01&0&99 : Standard-OpenHCD-PCI-zu-USB-Hostcontroller
PCI\VEN_1002&DEV_4389&SUBSYS_02061028&REV_00\3&61AAA01&0&9A : Standard-OpenHCD-PCI-zu-USB-Hostcontroller
PCI\VEN_1002&DEV_438A&SUBSYS_02061028&REV_00\3&61AAA01&0&9B : Standard-OpenHCD-PCI-zu-USB-Hostcontroller
PCI\VEN_1002&DEV_438B&SUBSYS_02061028&REV_00\3&61AAA01&0&9C : Standard-OpenHCD-PCI-zu-USB-Hostcontroller
PCI\VEN_1002&DEV_438C&SUBSYS_02061028&REV_00\3&61AAA01&0&A1 : Standard-Zweikanal-PCI-IDE-Controller
PCI\VEN_1002&DEV_438D&SUBSYS_00000000&REV_00\3&61AAA01&0&A3 : PCI Standard-ISA-Brücke
PCI\VEN_1002&DEV_7910&SUBSYS_00000000&REV_00\3&61AAA01&0&00 : PCI Standard-Host-CPU-Brücke
PCI\VEN_1002&DEV_7912&SUBSYS_00000000&REV_00\3&61AAA01&0&08 : PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_1002&DEV_7916&SUBSYS_00000000&REV_00\3&61AAA01&0&30 : PCI Standard-PCI-zu-PCI-Brücke
PCI\VEN_1002&DEV_791F&SUBSYS_02061028&REV_00\4&3496ADA2&0&2808: ATI Radeon X1270   
PCI\VEN_1022&DEV_1100&SUBSYS_00000000&REV_00\3&61AAA01&0&C0 : PCI Standard-Host-CPU-Brücke
PCI\VEN_1022&DEV_1101&SUBSYS_00000000&REV_00\3&61AAA01&0&C1 : PCI Standard-Host-CPU-Brücke
PCI\VEN_1022&DEV_1102&SUBSYS_00000000&REV_00\3&61AAA01&0&C2 : PCI Standard-Host-CPU-Brücke
PCI\VEN_1022&DEV_1103&SUBSYS_00000000&REV_00\3&61AAA01&0&C3 : PCI Standard-Host-CPU-Brücke
PCI\VEN_1217&DEV_00F7&SUBSYS_00F71217&REV_02\4&CC5B14E&0&0CA4: OHCI-konformer IEEE-1394-Hostcontroller
PCI\VEN_1217&DEV_7135&SUBSYS_02061028&REV_21\4&CC5B14E&0&08A4: Standard-CardBus-Controller
PCI\VEN_14E4&DEV_1673&SUBSYS_02061028&REV_02\4&1FD2E0F5&0&0030: Broadcom NetXtreme 57xx Gigabit Controller
ROOT\DISPLAY\0000                                           : PCI GDIHOOK5
24 matching device(s) found.
 
=========== 
USB Devices 
=========== 
USB\ROOT_HUB\4&13D1E180&0                                   : USB-Root-Hub
USB\ROOT_HUB\4&3597E59&0                                    : USB-Root-Hub
USB\ROOT_HUB\4&672AB6C&0                                    : USB-Root-Hub
USB\ROOT_HUB\4&7FE5038&0                                    : USB-Root-Hub
USB\ROOT_HUB\4&B177D4B&0                                    : USB-Root-Hub
USB\ROOT_HUB20\4&CC7A9B8&0                                  : USB 2.0-Root-Hub
6 matching device(s) found.
 
============= 
Input Devices 
============= 
No matching devices found.
 
============ 
ACPI Devices 
============ 
ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft-Netzteil
ACPI\PNP0100\4&2C4C3B2A&0                                   : Systemzeitgeber
ACPI\PNP0200\4&2C4C3B2A&0                                   : DMA-Controller
ACPI\PNP0303\4&2C4C3B2A&0                                   : Standardtastatur (101/102 Tasten) oder Microsoft Natural Keyboard (PS/2)
ACPI\PNP0501\4&2C4C3B2A&0                                   : Kommunikationsanschluss (COM1)
ACPI\PNP0800\4&2C4C3B2A&0                                   : Systemlautsprecher
ACPI\PNP0A03\2&DABA3FF&0                                    : PCI-Bus
ACPI\PNP0B00\4&2C4C3B2A&0                                   : System CMOS/Echtzeituhr
ACPI\PNP0C01\1                                              : Systemplatine
ACPI\PNP0C01\2                                              : Systemplatine
ACPI\PNP0C01\3                                              : Systemplatine
ACPI\PNP0C01\4                                              : Systemplatine
ACPI\PNP0C01\5                                              : Systemplatine
ACPI\PNP0C04\4&2C4C3B2A&0                                   : Numerischer Coprozessor
ACPI\PNP0C0A\1                                              : Microsoft ACPI-konforme Kontrollmethodenbatterie
ACPI\PNP0C0A\2                                              : Microsoft ACPI-konforme Kontrollmethodenbatterie
ACPI\PNP0C0C\2&DABA3FF&0                                    : ACPI-Einschaltknopf
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI-Deckel
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI-Sleepknopf
ACPI\PNP0C14\0                                              : Microsoft Windows-Verwaltungsschnittstelle für ACPI
ACPI\PNP0F13\4&2C4C3B2A&0                                   : PS/2-kompatible Maus
ACPI\THERMALZONE\THM_                                       : ACPI-Thermozone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-konformes System
ROOT\ACPI_HAL\0000                                          : ACPI-Multiprocessor-PC
24 matching device(s) found.

In the meantime, I tried with latest Driverpacks - no change.

dotnet is being installed after the os installation process finishes. But at the moment, I don´t get to that point.

Thanks once again for helping!
Best regards,
Chris

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: W2k Dell Latitude D531

you are useing CCC for ATI so .net needs to be installed before the finisher runs.

Boom... it's probably that simple 
install .net before the finisher or switch to CCP.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: W2k Dell Latitude D531

Doesn't he have to add the finisher line to his unnattend answerfile?
I had a look.

[Unattended]
DriverSigningPolicy=Ignore ; (is present)
NonDriverSigningPolicy=Ignore ; (is NOT present, and is most helpful)

=====
the settings in [display] have to have settings known to work .
(I came across TFT screens that would do Vrefresh 60 and 75 but would blackscreen on 70.. )
I currently use
[Display]
    BitsPerPel=32
    Xresolution=1024
    YResolution=768
    Vrefresh=60
    AutoConfirm=1


-----------
and this is not in answertxt
[GUIRunOnce]
    command9="%SystemDrive%\DPsFnshr.exe"

--
hehe
I mentioned dotnet too.

Last edited by Jaak (2008-04-24 00:05:14)

The answer was 42?
Kind regards, Jaak.
  • Registered: 2008-04-23
  • Posts: 6

Re: W2k Dell Latitude D531

Hi all,

thanks for yuor replies.
I´ll switch to CCP and post the results as soon as possible...

  • Jaak
  • Old Timer Rookie
  • Offline
  • From: Eeklo, in the East Flanders
  • Registered: 2006-07-23
  • Posts: 3,594

Re: W2k Dell Latitude D531

let us know, will you?

The answer was 42?
Kind regards, Jaak.
  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: W2k Dell Latitude D531

I agree that we can't see how he is calling the finisher... perhaps he has a script for that...

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2008-04-23
  • Posts: 6

Re: W2k Dell Latitude D531

Hi list,

to get the finisher running with my network install, I have to take a few more steps first, just to prepare the installation source being network compliant:
As described here http://www.mail-archive.com/unattended- … 06842.html, I create a directory i386\$oem$\$1 and move the DriverPack´s OEM folder in there.
Then, as described here http://www.mail-archive.com/unattended- … 07224.html, I create a directory i386\$oem$\$$\system32 and move the files presetup.cmd and setuporg.exe there.

Last, since I earlier experienced some problems with portcls.sys not being found during w2k installation, I adapt txtsetup.sif and dosnet.inf to fit our needs. For wxp, this doesn´t seem to be necessary.

All this works perfectly:
-> During text-based part of the w2k installation, the DriverPacks are being copied to the local harddisc automatically.
-> After finishing the text-based part and rebooting, DriverPacks are being extracted on the local harddisc automatically (by the finisher).
-> w2k installation continues with recognizing the devices
-> installation finally ends with a logon prompt of my newly installed w2k system

It´s only the dell d531, that doesn´t like DriverPacks.
If I only put the adequate dell drivers into the i386\$oem$\$1 directory, installation runs as smoothly as desired.
If I put the driver packs in there as described above, the d531 freezes after completing the installation right before showing the logon prompt.

Probably, you have some more hints to get this laptop running?
Thanks anyway for helping and thanks for your great work at DriverPacks!
Chris

P.S.: Switching to ATI ccp didn´t help, sorry.

  • OverFlow
  • DriverPacks Administrator & BASE Developer
  • Offline
  • From: Cincinnati
  • Registered: 2006-12-02
  • Posts: 6,730

Re: W2k Dell Latitude D531

I belive you will find your answer in the setupapi.log of the offending system.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!
http://driverpacks.net/userbar/admin-1.png
The DriverPacks, the DP_Base program, and Support Forum are FREE!.

OverFlow's Website

  • Registered: 2008-04-23
  • Posts: 6

Re: W2k Dell Latitude D531

Hi OverFlow,

I looked through the setupapi.log, but didn´t find anything unusual. Is there something special I have to look for?

Thanks in advance, best regards to Cincinnati (great place!),
Chris