Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1599
  • Last Modified:

nForce onboard LAN question

Hi,

I am trying to setup network bootdisks for PowerQuest's DeployCenter (Drive Image Pro5).  In the wizard for creating the bootdisk, I have to locate the driver file and the NDIS driver file.

The problem with the nForce is that it's all integrated and there doesn't seem to be any NDIS files.  

Anybody ever done this?
Any ideas?
comments only please.
0
1cell
Asked:
1cell
  • 9
  • 3
  • 3
  • +1
1 Solution
 
jhanceCommented:
Integrated or not, it's still a network adapter and won't work in Windows without an NDIS file.  

Open the DEVICE MANAGER, choose your network adapter, and find out what DRIVER it is using.  For example my 3COM 3C920 uses a driver named:

EL90XBC5.SYS

This is the NDIS driver for the 3C920.  Your mileage may vary depending on which network card is integrated.
0
 
1cellAuthor Commented:
what Deploycenter is looking for is the DOS or COM file.  The only driver I could find to download was the all inclusive system driver.  There doesn't seem to be anything related to NDIS on it.  Most drivers have an NDIS or NDIS2 directory where it's located.
0
 
1cellAuthor Commented:
ok, the drivers being used are:

c:\winnt\system32\drivers\

jedih2rx.bin
jedireg.pat
nvenet.sys
ramsed.bin

however, in the wizard, it is looking for the INF file for the driver, which I have found and referenced.  Then, in the NDIS section, it is asking for me to locate a DOS or EXE file for DOS NDIS.

Their specific words:
The Microsoft TCP/IP NDIS2 DOS driver file will be a file with a ".OS"or ".EXE" extension.  It will usually be located in the "NDIS" or "NDIS2" directory on the driver installation disk.
0
Reclaim your office - Try the MB 660 headset now!

High level of background noise often makes it difficult for employees to concentrate fully on their jobs – or to communicate clearly on calls. The MB 660 headset helps you create a disruption free workspace.  

 
1cellAuthor Commented:
sorry, will be a file with a ".OS"or ".EXE" extension should be a file with a ".DOS" or ".EXE" extension
0
 
1cellAuthor Commented:
well, nvidia and msi are both trying to tell me it doesn't use an msi file.  i don't know what to do.  they say because it is integrated on the chip not just the board, that the NDIS information is not required.  God forbid anybody follow a standard.
0
 
jhanceCommented:
msi is the Microsoft Installer file.  This is NOT a driver but an installer.  A driver MAY be distributed in an msi but the type of driver you need will not be.  You need a DOS mode NDIS driver.

The problem appears to be that NVIDIA has NOT produced a "legacy" DOS mode driver for this chipset.

Their drivers for this product are here:

http://www.nvidia.com/view.asp?PAGE=nforce_drivers

but there are no DOS drivers of any kind.

I think you may be out of luck here....

0
 
1cellAuthor Commented:
MSI = microstar, manufacturer of the motherboard.  I called and talked to Nvidia tech support (believe it or not;-) and from what they tell me they have the driver in an alpha form but they might not ever release it.  The guy is supposed to be emailing me today to tell me if he can let me "test" it.  and once again, I'd like to say, God forbid anyone stick to a standard.
0
 
jhanceCommented:
NDIS _IS_ a standard.  You're problems are:

1) You're using a product from a vendor (NVIDIA) who doesn't support their products well.

2) You're using a software package (PowerQuest) that relies on OBSOLETE drivers.  DOS is dead!  They should break their dependence on DOS and its drivers and move into the present.  It is entirely possible to make a DriveImage that ran in protected mode and used protected mode drivers.  But they are just too lazy to do so IMHO!!

In the future you should check for proper interesection of available drivers and what is required by your software.  I think you're going to see FEWER and FEWER cases of vendors making DOS mode drivers for their products now that DOS, Win3.1, and finally Win9x/ME are at end-of-life.  Windows 2000 and XP DO NOT EVER use real-mode drivers and DOS simply does not exist in those environments.
0
 
1cellAuthor Commented:
I know NDIS is a standard, that was my point.  it would be nice if Nvidia stuck to it.  

As for the DOS reliance, DeployCenter not only uses DOS while imaging the system drive but also when booting a OS'less system to pull an image from the network.  Norton Ghost is the same way.  
0
 
1cellAuthor Commented:
I guess I'll be buying some $10 nics.
0
 
Kyle SchroederEndpoint EngineerCommented:
They do however have Linux drivers for nForce...looks like cheapo NICs are the way you'll have to go.  Or put the harddrives in a different machine to dump the build onto, then after the driveimage finishes swap them back into the nForce mobo machines...

-dog*
0
 
1cellAuthor Commented:
well, just to let you guys know.  i finally received an email from nvidia support.  i thought they had blown me off.  they actually sent me a zip file with the NDIS/PXE "suite" of drivers.

if you guys would like it, drop an email to unocell@hotmail.com.  I'd be happy to share;-)
0
 
Kyle SchroederEndpoint EngineerCommented:
1cell:

Might want to do the world a favor and post it to www.driverguide.com.  They have an option to Upload drivers to their server.  Username is "drivers", password "all" to help other poor unfortunates who may run into this issue.  Was there any warnings about re-distibuting the driver, because in that case you probably would want to avoid it...

-dog*
0
 
Kyle SchroederEndpoint EngineerCommented:
Also, since we couldn't help you and you eventually resolved the problem yourself through nvidia, post a request in Community Support to have the points refunded to you and the question moved to the PAQ for future reference of others with this issue.

-dog*
0
 
MindphaserCommented:
Points refunded and moved to PAQ

** Mindphaser - Community Support Moderator **
0
 
1cellAuthor Commented:
in response to the recent flood of emails, please find the necessary driver at:

http://www.digi-spy.com/Ethernet.zip

thankyou.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 9
  • 3
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now