myITforum.com Community Forum myITforum.com Community Forum

Home  Forums  Blogs  Live Support chat  Search Articles  Wiki  FAQ  Email Lists  Register  Login  My Profile  Inbox  Address Book  My Subscription  My Forums 

Photo Gallery  Member List  Search  Calendars  FAQ  Ticket List  Log Out

All Forums RSS Feed Subscription:


  


OSD on new Dell E-series laptops...

 
View related threads: (in this forum | in all forums)

Logged in as: Guest
  Printable Version
All Forums >> [Management Products] >> System Center Products >> System Center Configuration Manager >> OSD on new Dell E-series laptops... Page: [1]
Login
Message << Older Topic   Newer Topic >>
OSD on new Dell E-series laptops... - 9/5/2008 11:03:41 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		I am a new SCCM admin.  We are running Config. Manager 2007, SP1 on Windows server 2008.  We have OSD successfuly working for XP-SP3 and Vista-SP1 on many Dell models.
I've just imported all the drivers for the new Dell E-6500, 6400, 5500 laptops and was testing OSD for XP-SP3.  However, after the PXE boot, PE seems to start to load, I get the SCCM splash screen and an hour glass for a few minutes then the system reboots.  Any ideas where to look to see what might be going on?

Thanks!
Post #: 1
RE: OSD on new Dell E-series laptops... - 9/6/2008 2:45:57 AM   
jkragh

 

Posts: 2
Score: 0
Joined: 3/9/2007
From: Denmark
Status: offline 		Hi,

Maybu anetwork driver  for your DELL is not in your boot image and therefore needs to be added?

/Jens Ole

_____________________________

Jens Ole Kragh
http://jensolekragh.spaces.live.com

(in reply to jboehlke926)
Post #: 2
RE: OSD on new Dell E-series laptops... - 9/6/2008 10:21:55 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		I will need to check that.

Thanks!

(in reply to jkragh)
Post #: 3
RE: OSD on new Dell E-series laptops... - 9/6/2008 3:17:28 PM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Note that ConfigMgr OSD uses Windows PE 2.x (2.0 for RTM, 2.1 for SP1).  Windows PE 2.x is based on Windows Vista, thus you must import and add Windows Vista NIC drivers to the boot images in addition to the suitable XP drivers.

The quick way to troubleshoot lack of NIC drivers is to enable command-line support in your boot image.  You can then press F8 to get a command window and do an ipconfig.  If the command doesn't return anything, you need to add the drivers.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 4
RE: OSD on new Dell E-series laptops... - 9/8/2008 10:11:45 AM   
egiroux

 

Posts: 169
Score: 4
Joined: 4/4/2006
From: Portland, Maine
Status: offline 		if the TS media just sits there for a couple minutes then reboots it seems to always be lack of the necessary NIC driver.

(in reply to jsandys)
Post #: 5
RE: OSD on new Dell E-series laptops... - 9/8/2008 4:42:18 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Thanks Jason.
I do have SP1 installed, so should be PE 2.1.  I did have the F8 option enabled and did ipconfig /all and get no IP address.  I have been able to add the new Intel 82567LM Gigabit Network Connection driver (same download from Dell for XP or Vista) and verified my Applicability in the Drivers properties that XP and Vista are checked.  However, I am still not able to get an IP address.  If I boot from a Linux recovery CD it is able to successfully load an Intel Pro1000 NIC driver and use that, so maybe I will see if I can get that to work for the boot image.  I was thinking that the Pro1000 might already be in WinPE, perhpaps not.

Jeff

(in reply to jsandys)
Post #: 6
RE: OSD on new Dell E-series laptops... - 9/8/2008 5:09:08 PM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Did you add the drivers to the boot image also and not just the driver repository?

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 7
RE: OSD on new Dell E-series laptops... - 9/8/2008 5:19:49 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		egiroux - thanks for your reply as well....
I went ahead and imported the Intel Pro 1000 driver as well, and still no love...  I am not getting any errors when adding the drivers in the PE tab of the Boot Image properties page.  I also see that my version number and date on the boot image is updating, so I am pretty sure the changes are being made.  I do get information on the ipconfig /all, but no IP address.
Should I be looking elsewhere??

Jeff

(in reply to jboehlke926)
Post #: 8
RE: OSD on new Dell E-series laptops... - 9/8/2008 5:22:37 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Jason,
Sorry, missed you last post.  Just to clarify, yes - I am adding to the boot image as well.

Thanks,
Jeff

(in reply to jboehlke926)
Post #: 9
RE: OSD on new Dell E-series laptops... - 9/8/2008 5:22:41 PM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Did you also install/distribute the updated image to your DP(s)?

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 10
RE: OSD on new Dell E-series laptops... - 9/8/2008 5:25:25 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		I believe I did.  In the GUI, after adding the driver on the PE tab, I get a pop-up that asks if I want to go ahead and apply the updates I am making to the DP - click yes to update, no to NOT update.  I clicked on YES.

Jeff

(in reply to jsandys)
Post #: 11
RE: OSD on new Dell E-series laptops... - 9/9/2008 9:40:54 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Here is a thought: the system is 64bit - I have been updating the x86 boot image (I'm installing 32 bit OS, and thus was in that line of thinking).  I am now going to update the x64 boot image with those drivers to see where that gets me.


(in reply to jboehlke926)
Post #: 12
RE: OSD on new Dell E-series laptops... - 9/9/2008 9:58:52 AM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		The 64-bit Boot image will only deploy a 64-bit OS and the 32-bit Boot image will only deploy a 32-bit OS. Note that you still need to make both available to enable PXE boot in WDS to each platform though.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 13
RE: OSD on new Dell E-series laptops... - 9/9/2008 10:08:29 AM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		When you imported the Pro1000 driver, did you import the Vista driver? Double check your PXE DP also to make sure that it has the latest boot image.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jsandys)
Post #: 14
RE: OSD on new Dell E-series laptops... - 9/9/2008 10:30:37 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Adding both the 64bit and 32bit (someone on Technet forums mentioned that worked for them) to the x64 boot image did not help.  Same result

Jason, yes, the version of the Pro1000 that was in my driver collection was for XP and Vista- one for x86, one for x64.  Both boot images are showing the drivers present and are up to date.
Here is the actual error I am seeing in the smsts.log from C:\ of the system we are trying to image:

Failed to download pxe variable file. Code(0x00000001)    TSPxe    9/9/2008 8:39:21 AM    1292 (0x050C)
PxeGetPxeData failed with 0x80004005    TSPxe    9/9/2008 8:39:21 AM    1292 (0x050C)
HRESULT_FROM_WIN32(dwError), HRESULT=80004005 (e:\nts_sms_fre\sms\client\tasksequence\tsmbootstrap\tsmbootstraputil.cpp,1420)    TSPxe    9/9/2008 8:39:21 AM    1292 (0x050C)

Jeff

(in reply to jsandys)
Post #: 15
RE: OSD on new Dell E-series laptops... - 9/9/2008 10:35:12 AM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Hmmm. Are you sure that you are not getting an IP Address. The above error indicates something different. Do you have a Netwrok Access Account set up? OSD uses this account for most of its network authentication.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 16
RE: OSD on new Dell E-series laptops... - 9/9/2008 11:06:07 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		No IP address - and the Access Accounts are present and setup - OSD Task Sequence is working great for other models.
I am only having this problem with these new models.

Jeff

(in reply to jsandys)
Post #: 17
RE: OSD on new Dell E-series laptops... - 9/9/2008 11:37:11 AM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Try the driver straight from Broadcom or Intel or whoever makes the card. Its not unheard of for the OEM drivers to not work properly.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 18
RE: OSD on new Dell E-series laptops... - 9/9/2008 12:56:04 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		We just noticed another twist.  I decided to remove the drivers from the driver collection and re-import them - updated the DP after removal as well.
When attempting to re-import the drivers from Dell (R190974) the package shows 4 drivers will be imported x86 for XP and Vista as well as x64 for XP and Vista.
However, during the import only the XP drivers come in and I get the following error for the Vista drivers:
Error: Failed to import the following drivers:
   \\net\hartfiles\Install\SCCMDSL\drivers\R190974-NIC Wired-V\VISTA32\E1y6032.inf - The selected driver is not applicable to any supported platforms.
   \\net\hartfiles\Install\SCCMDSL\drivers\R190974-NIC Wired-V\VISTAX64\E1y60x64.inf - The selected driver is not applicable to any supported platforms.

So that may have been the problem all along, we can't boot because the Vista drivers were never there.  Now the question is why it won't import these?
I guess we could go ahead and try the ones straight from Intel.  I was over in the Technet forums and seems like others have been having issues with these
built in Intel NICs as well - on HP and Dell models.

If you have any other ideas on why the Vista drivers won't import, I would love to hear it!

Jeff

(in reply to jsandys)
Post #: 19
RE: OSD on new Dell E-series laptops... - 9/9/2008 3:13:22 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Installing the Vista drivers from Intel worked!

Thanks for all the help and ideas.  I learned a lot in the process.

Jeff

(in reply to jboehlke926)
Post #: 20
RE: OSD on new Dell E-series laptops... - 9/9/2008 3:27:25 PM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Chalk another one up to OEM "monkeying" with what works.

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to jboehlke926)
Post #: 21
RE: OSD on new Dell E-series laptops... - 9/11/2008 3:44:11 PM   
lnewingham325

 

Posts: 1
Score: 0
Joined: 5/15/2006
Status: offline 		Im having the same problems with the e6400 laptop and using the intel drivers doesnt work, ive gone so far as to wipe all network drivers out of sccm and then re-add the vista drivers to no luck. any other ideas?


(in reply to jsandys)
Post #: 22
RE: OSD on new Dell E-series laptops... - 9/11/2008 5:31:45 PM   
jsandys


Posts: 531
Score: 17
Joined: 3/24/2005
From: San Antonio, TX
Status: offline 		Same stuff, make sure you add the drivers to the approriate boot image(s), make sure the boot image gets updated and installed on the PXE DP, check the driver in the console to make sure it is for Vista.  Did you launch the command console and do an ip config after the Win PE boot?  Have you tried a working device on the same physcial network connection to verify DHCP?  Did you check smsts.log to see if there are any other errors?

_____________________________

Jason
________________________________________
http://myitforum.com/cs2/blogs/jsandys/default.aspx

(in reply to lnewingham325)
Post #: 23
RE: OSD on new Dell E-series laptops... - 9/12/2008 12:29:38 PM   
wbracken


Posts: 1036
Score: 22
Joined: 4/12/2002
From: St. Louis
Status: offline 		I had issues with using SCCM to apply drivers to the boot image.  I used the manual method for injecting the drivers using the WAIK and this article:
http://apcmag.com/how_to_inject_drivers_into_microsofts_free_os_windows_pe_20.htm

So I update the WinPE.wim (not the WinPE.XXX0003d.wim) and then replaced the one in the boot image source directory.  Then update the DP's which will create the new WinPE.XXX0003d.wim file. and place it on the DP.

Works great!  :)

_____________________________

William Bracken

Visit my new Blog
http://wbracken.wordpress.com/

(in reply to jsandys)
Post #: 24
RE: OSD on new Dell E-series laptops... - 9/18/2008 11:34:54 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		UPDATE:

Well, while this worked for our XP installs we have run into a problem with Vista OSD TS.  Earlier I said I could not get the Dell driver to import and had to get the Intel driver which did import.  This got our Boot image to work.  But now, even though the driver is there, it is not working in the TS for Vista.  After OSD TS is complete we can manually install either the Intel driver (same one that is in my Drivers package) and it installs and works fine.  I can also download the Dell driver (same one we attempted to import, but could not) and that one will install and work fine as well.
I have seen one other post online about others having the same issue, but they are at the same stage I am, got the Intel driver working for Boot image, but not in OSD.

Any ideas on where to go from here?

Thanks,
Jeff

(in reply to wbracken)
Post #: 25
RE: OSD on new Dell E-series laptops... - 9/18/2008 11:40:10 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		I was able to link the other post in text above, but it is not showing up well - text did not change color, so here it is again;
http://episteme.arstechnica.com/eve/forums/a/tpc/f/12009443/m/556005634931

(in reply to jboehlke926)
Post #: 26
RE: OSD on new Dell E-series laptops... - 9/19/2008 11:22:41 AM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		This is strange.  In the setupapi.dev.log I see the NIC listed like this:
PCI\VEN_8086&DEV_10F5&SUBSYS_02331028&REV_03\3&2acf1e9&0&C8
This device ID is not present in either of the .inf files so would explain why it is not installing, but if that is the case, I do not understand how these same drivers install just fine once Vista is installed.

Also, a subset of this device ID (PCI\VEN_8086&DEV_10F5&SUBSYS_02331028) does show up in the Dell driver .inf file, but not in the Intel.  But the Dell driver is the one that I cannot import.  And the Intel driver did import and works for the WinPE Vista32 boot image... it is dizzying.

Any ideas?  Here is the snipet from the log:

>>>  [Setup online Device Install (Hardware initiated) - PCI\VEN_8086&DEV_10F5&SUBSYS_02331028&REV_03\3&2acf1e9&0&C8]
>>>  Section start 2008/09/12 11:31:27.962
    ump: Creating Install Process: DrvInst.exe 11:31:27.962
    ndv: Retrieving device info...
    ndv: Setting device parameters...
    ndv: Building driver list...
    dvi: {Build Driver List} 11:31:27.993
    dvi:      Searching for hardware ID(s):
    dvi:           pci\ven_8086&dev_10f5&subsys_02331028&rev_03
    dvi:           pci\ven_8086&dev_10f5&subsys_02331028
    dvi:           pci\ven_8086&dev_10f5&cc_020000
    dvi:           pci\ven_8086&dev_10f5&cc_0200
    dvi:      Searching for compatible ID(s):
    dvi:           pci\ven_8086&dev_10f5&rev_03
    dvi:           pci\ven_8086&dev_10f5
    dvi:           pci\ven_8086&cc_020000
    dvi:           pci\ven_8086&cc_0200
    dvi:           pci\ven_8086
    dvi:           pci\cc_020000
    dvi:           pci\cc_0200
    dvi:      Enumerating INFs from path list 'C:\Windows\INF'
    inf:      Searched 0 potential matches in published INF directory
    inf:      Searched 29 INFs in directory: 'C:\Windows\INF'
    dvi: {Build Driver List - exit(0x00000000)} 11:31:28.118
    ndv: Selecting best match...
    dvi: {DIF_SELECTBESTCOMPATDRV} 11:31:28.118
    dvi:      No class installer for 'Ethernet Controller'
    dvi:      No CoInstallers found
    dvi:      Default installer: Enter 11:31:28.133
    dvi:           {Select Best Driver}
!    dvi:                Selecting driver failed(0xe0000228)
    dvi:           {Select Best Driver - exit(0xe0000228)}
!    dvi:      Default installer: failed!
!    dvi:      Error 0xe0000228: There are no compatible drivers for this device.
    dvi: {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:31:28.149
    ndv: {Core Device Install}
!    ndv:      Installing NULL driver!
    dvi:      Set selected driver complete.
    dvi:      {DIF_ALLOW_INSTALL} 11:31:28.305
    dvi:           No class installer for 'Ethernet Controller'
    dvi:           Default installer: Enter 11:31:28.305
    dvi:           Default installer: Exit
    dvi:      {DIF_ALLOW_INSTALL - exit(0xe000020e)} 11:31:28.321
    dvi:      {DIF_INSTALLDEVICE} 11:31:28.321
    dvi:           No class installer for 'Ethernet Controller'
    dvi:           Default installer: Enter 11:31:28.321
!    dvi:                Installing NULL driver!
    dvi:                Writing common driver property settings.
    dvi:                {Restarting Devices} 11:31:28.336
    dvi:                     Restart: PCI\VEN_8086&DEV_10F5&SUBSYS_02331028&REV_03\3&2ACF1E9&0&C8
    dvi:                     Restart complete.
    dvi:                {Restarting Devices exit} 11:31:28.336
    dvi:           Default installer: Exit
    dvi:      {DIF_INSTALLDEVICE - exit(0x00000000)} 11:31:28.352
    dvi:      {Build Driver List} 11:31:28.352
!    dvi:           Driver list already built
    dvi:      {Build Driver List - exit(0x00000000)} 11:31:28.352
    dvi:      {DIF_SELECTBESTCOMPATDRV} 11:31:28.352
    dvi:           No class installer for 'Ethernet Controller'
    dvi:           Default installer: Enter 11:31:28.352
    dvi:                {Select Best Driver}
!    dvi:                     Selecting driver failed(0xe0000228)
    dvi:                {Select Best Driver - exit(0xe0000228)}
!    dvi:           Default installer: failed!
!    dvi:           Error 0xe0000228: There are no compatible drivers for this device.
    dvi:      {DIF_SELECTBESTCOMPATDRV - exit(0xe0000228)} 11:31:28.367
    ndv:      Device install status=0x00000000
    ndv:      Performing device install final cleanup...
    ndv: {Core Device Install - exit(0x00000000)}
    ump: Server install process exited with code 0x00000000 11:31:28.367
<<<  Section end 2008/09/12 11:31:28.367
<<<  [Exit status: SUCCESS]

(in reply to jboehlke926)
Post #: 27
RE: OSD on new Dell E-series laptops... - 9/19/2008 12:09:44 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		In looking at the log further - I noticed this:

Enumerating INFs from path list 'C:\Windows\INF'
Searched 0 potential matches in published INF directory
Searched 29 INFs in directory: 'C:\Windows\INF'

So, perhaps the INF is not getting copied down?

(in reply to jboehlke926)
Post #: 28
RE: OSD on new Dell E-series laptops... - 9/19/2008 4:59:46 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Well, based on some info from the following threads:
http://www.911cd.net/forums//index.php?showtopic=22012&st=0&p=149709&#entry149709
http://www.msfn.org/board/Fix-all-Intel-RIS-Driver-problem-t102574.html

I decided to edit the .inf file in the Dell driver.  Here is the way the file looks now, what I did (bold) was to remark some lines and change one other line so that the only section was [Intel] as mentioned in the threads above.

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[Manufacturer]
;%Intel%     = Intel, NTx86.6.0, NTx86.6.0.1
%Intel%     = Intel

[ControlFlags]


[Intel]

;[Intel.NTx86.6.0.1]
; DisplayName                   Section         DeviceID
; -----------                   -------         --------

%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_10F58086

;Dell
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02331028
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02341028
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024D1028
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_024F1028
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02501028
%E10F5NC.DeviceDesc%            = E10F5,       PCI\VEN_8086&DEV_10F5&SUBSYS_02771028

%E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF
%E10BFNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10BF&SUBSYS_10BF8086
%E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB
%E10CBNC.DeviceDesc%            = E10BF,       PCI\VEN_8086&DEV_10CB&SUBSYS_10CB8086

;[Intel.NTx86.6.0]
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

After that, I was able to successfully import the Vista32 driver into my driver package, update the DP, and ran the OSD TS for Vista32 successfully on the E6400.

Hope this is helpful for others.

Jeff

(in reply to jboehlke926)
Post #: 29
RE: OSD on new Dell E-series laptops... - 9/24/2008 12:09:02 AM   
mseely

 

Posts: 40
Score: 1
Joined: 5/4/2008
Status: offline 		Be careful when editing the INF ...

By commenting out NTx86.6.0.1 and NTx86.6.0, the driver which is should be applicable only for Windows Vista is now applicable for ALL systems.  So, it will try to install on  Windows 2000, Windows XP and Windows 2003 even though the driver is not designed for those Operating Systems.




_____________________________

Mark

(in reply to jboehlke926)
Post #: 30
RE: OSD on new Dell E-series laptops... - 9/24/2008 1:28:22 PM   
tmiller


Posts: 665
Score: 18
Joined: 7/29/2003
From: Iowa
Status: offline 		I remember running into a problem like this with an OEM driver a long long time ago.  I think it has something to do with the extra number of dots in "Intel.NTx86.6.0.1"  The problem I ran into was in pre Vista times, but I imagine the problem is the similar.  I think that extra .1 is trouble.  You might have better luck editing out the .1 than making the edit you made.

(in reply to mseely)
Post #: 31
RE: OSD on new Dell E-series laptops... - 9/24/2008 3:59:10 PM   
jboehlke926

 

Posts: 31
Score: 0
Joined: 7/25/2008
Status: offline 		Great input, thanks guys!  I will try just removing the .1 and see how that goes.

Jeff

(in reply to tmiller)
Post #: 32