Hi Everyone,
I have a bootable CD which can load few different kind of drivers that we need in our environment. Currently when we use this CD then it will come up with menu which is sorted by the motherboard/NIC types and once you make a selection then it will load ghost automatically.
Now that this is working so I want to make these changes if possible:
1. Scan for NICs and report back the results
2. If found only one NIC then automatically load the drivers for that NIC
I know that pciscan.exe can load the drivers but I don't know how to use with properly.Finding the NICs and report back part I am not sure if it is possible with pciscan utility.
Thanks in advance,
Full Version: Need help with Pciscan.exe
hello ,
useful information:
http://netbootdisk.com/
The Universal TCP/IP Network Bootdisk is a DOS bootdisk that provides TCP/IP networking support. It's designed for use in Microsoft networking environments, on either peer-to-peer or domain based LANs. Currently 95 different network card drivers all included, all on the single 1.44MB disk!
Most people use this bootdisk for "Ghosting" PC's over a network connection. This disk will provide the DOS networking and drivers to allow the mapping of a network drive containing your imaging software and files. TCP/IP based image transfers, like GhostCast is also supported.
I am rusty as far as DOS is concerned so I leave that to others to advise .
Regards Ben
useful information:
http://netbootdisk.com/
The Universal TCP/IP Network Bootdisk is a DOS bootdisk that provides TCP/IP networking support. It's designed for use in Microsoft networking environments, on either peer-to-peer or domain based LANs. Currently 95 different network card drivers all included, all on the single 1.44MB disk!
Most people use this bootdisk for "Ghosting" PC's over a network connection. This disk will provide the DOS networking and drivers to allow the mapping of a network drive containing your imaging software and files. TCP/IP based image transfers, like GhostCast is also supported.
I am rusty as far as DOS is concerned so I leave that to others to advise .
Regards Ben
Hi Ben,
Thanks for your help and yes, that site has lots useful stuff but not what I was looking for. Do you use Pciscan.exe in your bootdisk to detect NIC?
Thanks,
Thanks for your help and yes, that site has lots useful stuff but not what I was looking for. Do you use Pciscan.exe in your bootdisk to detect NIC?
Thanks,
The txt file included with Bart's pciscan download gives full details how to use the utility including an example batch file.
I have read thru that file and as modified the file with my NIC information but when I scan still can't find my system NIC. Here is the my system information:
Motherboard: Intel 945GTP
NIC: Intel R Pro/1000 PM (Onboard)
Device ID: 108C (Found using device manager)
Driver file: E1E6032.sys (Found using device manager)
Vender: Intel
OS: Windows Vista Enterprise
Here is what I have added into NIC.map file (as it was stated in the pciscan.text file)
ret="e1e6032.sys"
ven=8086 "Intel"
dev=108C "Intel R PRO/1000 PM Network Connection"
After saving the text file this how I ran at the command prompt:
c:\pciscan.exe -v nic.map
Can anyone please tell me if this is wrong or any other ways for scanning NIC in the system?
Thanks,
Motherboard: Intel 945GTP
NIC: Intel R Pro/1000 PM (Onboard)
Device ID: 108C (Found using device manager)
Driver file: E1E6032.sys (Found using device manager)
Vender: Intel
OS: Windows Vista Enterprise
Here is what I have added into NIC.map file (as it was stated in the pciscan.text file)
ret="e1e6032.sys"
ven=8086 "Intel"
dev=108C "Intel R PRO/1000 PM Network Connection"
After saving the text file this how I ran at the command prompt:
c:\pciscan.exe -v nic.map
Can anyone please tell me if this is wrong or any other ways for scanning NIC in the system?
Thanks,
QUOTE (music5_5 @ May 1 2009, 09:15 PM) 
ret="e1e6032.sys"
That's a Vista driver.
Does your bootable CD boot DOS?
Does your bootable CD boot Vista?
Use a DOS driver for a DOS solution.
PRODOS_v14_0.exe does contain driver e1000.dos.
QUOTE (cdob @ May 2 2009, 02:15 AM)
That's a Vista driver.
Does your bootable CD boot DOS?
Does your bootable CD boot Vista?
Use a DOS driver for a DOS solution.
PRODOS_v14_0.exe does contain driver e1000.dos.
Does your bootable CD boot DOS?
Does your bootable CD boot Vista?
Use a DOS driver for a DOS solution.
PRODOS_v14_0.exe does contain driver e1000.dos.
As of right now, I am using this utility with in Vista and that is why I was using that file. I have tried changing that file name to e1000.dos but still, it won't find my NIC. Here is what I have been doing:
1. I have unzip a copy of pciscan.zip into my D: drive
2. Then I have edit the nic.map file and added the following line:
ret="e1000$.dos"
ven=8086 "Intel"
dev=108C "Intel R PRO/1000 PM Network Connection"
;
3. After this I have tried to run "pciscan.exe -v nic.map" using the comman prompt.
4. But still getting this message:
0 PCI devices found
No PCI devices have been found!
Can someone please tell me if I need to place the dos driver file in very specific folder (system32 or whereever the pciscan.exe sits) so that this tool can find my NIC?
Thanks,
QUOTE (music5_5 @ May 4 2009, 02:10 PM)
I am using this utility with in Vista and that is why I was using that file.
Please clarify:
which utiliy do you use?
which pciscan.exe do you use?
which bootable cd do you use?
do you use a DOS boot cd?
do you use a Vista boot cd?
Do you us pciscan from http://www.nu2.nu/utils/
This is a DOS utility. Results at Vista are not defined. Don't use a DOS utiliy at Vista.
QUOTE (cdob @ May 4 2009, 08:30 AM)
Please clarify:
which utiliy do you use?
which pciscan.exe do you use?
which bootable cd do you use?
do you use a DOS boot cd?
do you use a Vista boot cd?
Do you us pciscan from http://www.nu2.nu/utils/
This is a DOS utility. Results at Vista are not defined. Don't use a DOS utiliy at Vista.
which utiliy do you use?
which pciscan.exe do you use?
which bootable cd do you use?
do you use a DOS boot cd?
do you use a Vista boot cd?
Do you us pciscan from http://www.nu2.nu/utils/
This is a DOS utility. Results at Vista are not defined. Don't use a DOS utiliy at Vista.
which utiliy do you use? pciscan.exe
which pciscan.exe do you use? PCISCAN v1.10
which bootable cd do you use? It is not downloaded from web, it is very simple dos bootable CD.
do you use a DOS boot cd? Yes
do you use a Vista boot cd? No
Sorry for the confusion but what I meant that I was testing this tool (pciscan.exe) and see how it works before i can modify my dos bootable CD.
Since I don't know where and how will I use this tool in my autoexec.bat file so I thougt that I should try to run this in my own desktop and see what kind of result it produces before adding into my bootable cd.
Thanks,
Here is a copy of my autoexec.bat:
And here is a copy of config.sys
and here is a copy of pciscan.bat
Once I create an ISO from winimage and then boot using virtual image, I can find virtual nic (AMD) but when I use the menu option then I got this error:
"Bad command or file name"
Can anyone tell me why am i getting this error?
Thanks,
P.S: sorry for the very long post
QUOTE
@echo off
Path=c:\;c:\dos;c:\files;c:\programs;
prompt $p$g
MOUSE
doskey
goto %config%
:Local
goto next
:INTELPRO
set bind=INTELPRO
:INTEL82567
set bind=INTEL82567
:INTEL
set bind=INTEL
:YUKON
set bind=YUKON
:REALTEK
set bind=REALTEK
:3COM
set bind=3COM
:AMD
set bind=AMD
:PCI
c:\dos\pciscan.bat
:end
c:\dos\netbind.com
c:\files\1.bat
:next
c:\files\0.bat
Path=c:\;c:\dos;c:\files;c:\programs;
prompt $p$g
MOUSE
doskey
goto %config%
:Local
goto next
:INTELPRO
set bind=INTELPRO
:INTEL82567
set bind=INTEL82567
:INTEL
set bind=INTEL
:YUKON
set bind=YUKON
:REALTEK
set bind=REALTEK
:3COM
set bind=3COM
:AMD
set bind=AMD
:PCI
c:\dos\pciscan.bat
:end
c:\dos\netbind.com
c:\files\1.bat
:next
c:\files\0.bat
And here is a copy of config.sys
QUOTE
[menu]
menuitem=Local, Local [ DOS Prompt ]
menuitem=INTEL82567, Intel [ Tecra A10 ]
menuitem=INTELPRO, Intel [ D945GTP, DQ35JO, Tecra A8, A9 ]
menuitem=YUKON, Yukon [ D915GAG, Tecra A3 ]
menuitem=INTEL, Intel [ D865Perl, Tecra A2, Satellite R10 ]
menuitem=REALTEK, Realtek [ Satellite A70, A20 ]
menuitem=3COM, 3COM [ 3COM PCI ]
menuitem=AMD, AMD [ VMWare Nic ]
menuitem=PCI, PCI [ Testing ]
MenuDefault MS-DOS
MenuColor 15,1
[Local]
[INTEL82567]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e1000.DOS
[INTELPRO]
device=c:\dos\dosprotman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e1000b.DOS
[YUKON]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\yuknd.dos
[INTEL]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e100b.dos
[REALTEK]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\rtsnd.dos
[3COM]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\el90x.dos
[AMD]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\pcntnd.dos
[PCI]
Echo Test
menuitem=Local, Local [ DOS Prompt ]
menuitem=INTEL82567, Intel [ Tecra A10 ]
menuitem=INTELPRO, Intel [ D945GTP, DQ35JO, Tecra A8, A9 ]
menuitem=YUKON, Yukon [ D915GAG, Tecra A3 ]
menuitem=INTEL, Intel [ D865Perl, Tecra A2, Satellite R10 ]
menuitem=REALTEK, Realtek [ Satellite A70, A20 ]
menuitem=3COM, 3COM [ 3COM PCI ]
menuitem=AMD, AMD [ VMWare Nic ]
menuitem=PCI, PCI [ Testing ]
MenuDefault MS-DOS
MenuColor 15,1
[Local]
[INTEL82567]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e1000.DOS
[INTELPRO]
device=c:\dos\dosprotman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e1000b.DOS
[YUKON]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\yuknd.dos
[INTEL]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\e100b.dos
[REALTEK]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\rtsnd.dos
[3COM]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\el90x.dos
[AMD]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\pcntnd.dos
[PCI]
Echo Test
and here is a copy of pciscan.bat
QUOTE
@echo off
rem Sample batchfile for loading Dos ASPI device drivers (up to 3)
rem batchfile uses 'device.com' for loading them
set pci0=
set pci1=
set pci2=
pciscan.exe -v c:\dos\nic.map
if errorlevel 1 goto _err1
if "%pci0%" == "pcntnd.dos" goto AMD
echo Loading %pci0%
device.com %pci0%
if errorlevel 1 goto _err2
rem Check for second adapter
if "%pci1%" == "" goto _end
echo Loading %pci1%
device.com %pci1%
if errorlevel 1 goto _err2
rem Check for third adapter
if "%pci2%" == "" goto _end
echo Loading %pci2%
device.com %pci2%
if errorlevel 1 goto _err2
:AMD
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\pcntnd.dos
goto _end
:_none
echo *** PCISCAN did not find any matching PCI device(s)
echo Here's a list of devices in your system, check if your adapter
echo needs to be added to the mapfile.
echo.
pciscan -v
pause
goto _end
:_err1
echo *** PCISCAN returned an error...
pause
goto _end
:_err2
echo *** Error loading device driver...
pause
:_end
rem End of sample batchfile
rem Sample batchfile for loading Dos ASPI device drivers (up to 3)
rem batchfile uses 'device.com' for loading them
set pci0=
set pci1=
set pci2=
pciscan.exe -v c:\dos\nic.map
if errorlevel 1 goto _err1
if "%pci0%" == "pcntnd.dos" goto AMD
echo Loading %pci0%
device.com %pci0%
if errorlevel 1 goto _err2
rem Check for second adapter
if "%pci1%" == "" goto _end
echo Loading %pci1%
device.com %pci1%
if errorlevel 1 goto _err2
rem Check for third adapter
if "%pci2%" == "" goto _end
echo Loading %pci2%
device.com %pci2%
if errorlevel 1 goto _err2
:AMD
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\Drivers\pcntnd.dos
goto _end
:_none
echo *** PCISCAN did not find any matching PCI device(s)
echo Here's a list of devices in your system, check if your adapter
echo needs to be added to the mapfile.
echo.
pciscan -v
pause
goto _end
:_err1
echo *** PCISCAN returned an error...
pause
goto _end
:_err2
echo *** Error loading device driver...
pause
:_end
rem End of sample batchfile
Once I create an ISO from winimage and then boot using virtual image, I can find virtual nic (AMD) but when I use the menu option then I got this error:
"Bad command or file name"
Can anyone tell me why am i getting this error?
Thanks,
P.S: sorry for the very long post
QUOTE (music5_5 @ May 6 2009, 01:51 PM)
I can find virtual nic (AMD) but when I use the menu option then I got this error:
"Bad command or file name"
"Bad command or file name"
QUOTE (pciscan.bat)
device=c:\dos\protman.dos /I:\
This is not a batch command line.Did you add file device.com?
A idea, not tested:
change config.sys, load always
CODE
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\dos\dis_pkt.dos
pciscan.bat
CODE
:AMD
device.com c:\Drivers\pcntnd.dos
Remember, this is for testing only.device.com c:\Drivers\pcntnd.dos
Do you know where can I download device.com file from?
I have modified a line in pciscan.bat to following:
I am little confused about the change in config.sys:
In this config file, I have only added the this line:
Everything else in that file is working fine. Can you please let me know what line needs to be changed?
Thanks,
I have modified a line in pciscan.bat to following:
QUOTE
:AMD
device.com c:\Drivers\pcntnd.dos
device.com c:\Drivers\pcntnd.dos
I am little confused about the change in config.sys:
QUOTE
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
device=c:\dos\dis_pkt.dos
In this config file, I have only added the this line:
QUOTE
[PCI]
Echo Test
Echo Test
Everything else in that file is working fine. Can you please let me know what line needs to be changed?
Thanks,
QUOTE (music5_5 @ May 6 2009, 07:53 PM)
Do you know where can I download device.com file from?
bfd107.zip\utils.cabhttp://www.nu2.nu/bootdisk/cdrom/index.php?p=1
config.sys
CODE
[menu]
menuitem=Local, Local [ DOS Prompt ]
menuitem=Network, load Network
menuitem=PCI, PCI [ Testing ]
MenuDefault MS-DOS
MenuColor 15,1
[Local]
[Network]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
[PCI]
Echo Test
menuitem=Local, Local [ DOS Prompt ]
menuitem=Network, load Network
menuitem=PCI, PCI [ Testing ]
MenuDefault MS-DOS
MenuColor 15,1
[Local]
[Network]
device=c:\dos\protman.dos /I:\
device=c:\dos\dis_pkt.dos
[PCI]
Echo Test
First of all, let me thank you and other members who helped me to get this far.
After I copied the device.com into my disk, now I can scan and load drivers for my NIC (using original config.sys).
After I copied the device.com into my disk, now I can scan and load drivers for my NIC (using original config.sys).
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.