O/S Deployment Thread, PXE .sys files for nVidia nForce Networking Controller in Technical; Evening all,
Any idea where i can source or create a .sys/pxe file which will be recognised when booting into ...
-
11th December 2009, 07:36 PM #1 PXE .sys files for nVidia nForce Networking Controller
Evening all,
Any idea where i can source or create a .sys/pxe file which will be recognised when booting into PXE to ghost to/from a PC with a network controller which shows up in device manger as 'nVidia nForce Networking Controller'? I normally use a universal driver for ghosting, however none of the drivers on my existing pxe server are any use for this NIC.
Thanks, ac
-
-
IDG Tech News
-
11th December 2009, 07:42 PM #2 Ever thought about using netbootdisk to accomplish this?
-
-
11th December 2009, 07:45 PM #3 netbootdisk? I havn't. I have always used a pre-configured custom USB boot stick which I built and up until very recently, PXE.
Whats the situation with netbootdisk then?
-
-
11th December 2009, 07:47 PM #4 Netbootdisk is a msdos boot disk that includes network drivers.
You can then launch Ghost via PXE =)
Check my setup guide here - [ame="http://www.youtube.com/watch?v=Yb3YcLDpa8U"]YouTube- TCP IP Network Bootdisk[/ame]
Build the netbootdisk and test it out, make sure it's working correctly on the corrisponding machine.
Create an .img of it and stick it on your PXE server and boot to it.
Below is an example
[ame="http://www.youtube.com/watch?v=jjDtJtuwIps"]YouTube- Fog Project: Modified PXE Boot Menu[/ame]
Last edited by ssx4life; 11th December 2009 at 07:49 PM.
-
-
11th December 2009, 07:54 PM #5 Cheers for that. I'll give it a try. I have just gone over to Windows 7 recently so will give that a try on the test machine.
Would that enable me to get the required .sys/mba files required for PXE too?
-
-
11th December 2009, 07:57 PM #6 A big no on that =)
PXE boot to an .img file
-
-
11th December 2009, 08:00 PM #7 If you need help let me know
-
-
11th December 2009, 08:03 PM #8 Will do, cheers. I'm trying to move away from USB boot sticks and all things bootable to be honest and move across to PXE. enabling me and my team to boot to PXE and image whereever we are on the LAN and limit the amount of machines we need to return to the office and store whilst their in etc.
Looks like I have me mission for this weekend!
-
-
11th December 2009, 08:35 PM #9 I will be around this weekend, so feel free to PM me. (saturday I'm busy but sunday yes)
-
-
11th December 2009, 09:13 PM #10 Thought I'd leave you with 1 more tidbit of info.
#1. You can have a bootable USB version of netbootdisk
Have a good weekend
-
-
11th December 2009, 09:20 PM #11 I've used Gpxe to boot my systems that dont automatically work with the bios lan boot options...
Use the above page and create your own bootcd or boot floppy
-
-
11th December 2009, 10:18 PM #12 It really, truely is that painless =)
Directions are straight forward.
If you have your networking permissions and folder shares set up already it's pretty much plug and play.
Either map to the network folder via the menu, or edit login.bat in the sub folder (I think that's the one). Check the netbootdisk site for more verification and documentation. I just wanted an actual video out there for people to see it in action.
PXE is also straight foward, but have your ducks in a row first. Make sure the disk is working the way you want it to, and then make an .img of it using winimage or other 3rd party application.
Modify your pxe boot menu to include the floppy image. Boot to it... and voila! 
You will need to force a ramdisk change if you boot via PXE. See the main site for more info.....again google is your friend
-
-
15th October 2010, 11:42 AM #13
- Rep Power
- 0
hey im having trouble with pxe booting,i am receive the error PXE-E79 NBP is to big to fit in free base memory and i have been researching every way to find a solution please i need help, im sorry for jumping on this thread
-
-
18th October 2010, 08:06 PM #14
- Rep Power
- 0
Are you trying to use a Ghost PXE? Maybe this will help.
Without more details, it's hard to say what is causing this to occur. Something that has worked in a few past cases is to add two switches to the command line. If you're booting to PC-DOS, it would look like this:
ghost.exe -noide -pfile=c:\
If you're booting to WinPE, this is what the command line would look like:
ghost32.exe -noide -pfile=c:\
You could also try updating your bios.
-
-
19th October 2010, 07:19 AM #15
- Rep Power
- 0
thanks Ill give it a try and let you know if it was successful
-
SHARE: 
Similar Threads
-
By madcyryl in forum Windows Server 2008
Replies: 0
Last Post: 5th May 2009, 03:04 PM
-
By JokHarle in forum Wireless Networks
Replies: 5
Last Post: 15th November 2008, 05:23 PM
-
By contink in forum Hardware
Replies: 13
Last Post: 31st May 2008, 09:00 PM
-
Replies: 14
Last Post: 26th April 2007, 05:48 PM
-
By edie209 in forum Windows
Replies: 7
Last Post: 16th November 2006, 12:55 PM
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules