Jump to content











Photo
* * * * * 2 votes

nettyPE


  • Please log in to reply
35 replies to this topic

#1 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 30 September 2011 - 01:22 PM

*
POPULAR

nettyPE :D
boot netty Win7PE from CDDVD, HDD, USB, Network(LAN) and start a PXE server

http://youtu.be/Ez0IW11u-rI

Download:

nettyPE.zip v2011_11_07 (129 MB)

nettyPE.zip v2011_11_07 - mediafire (129 MB)

goals:

1st WinPE generating for repair, recovery and setup purposes

2nd WinPE boot from CDDVD, USB, HDD (WinRE) or network (LAN)

3rd RAM usage as low as possible with as much comfort

4th Possibility to start a PXE Server

implementation:

The basis is Win7PE_SE_2011_10_20
Thanks to ChrisR, Lancelot, Homes32, JFX, YahooUK, NightMan and all the others for the excellent work.

The source is Win7 DVD SP0 and SP1, x86 and x64

- µExplorer as Shell

- FBWF cache size: 32 MB

- 1 - Copy Files Copy: Standard

- Boot.wim file ~ 175 MB

- Using the PortableApps.com_EXE script to use portable apps outside the boot.wim

- DiskImages01 - 04 for multiple boot

- Preference of grub4dos menus; the map function provides a better memory usage

- PXE_Netbooting_script for network booting (PXE)

- 1-50_Optimizations.script changed to eliminate static computer name
required for different names in the network

- USBDeviceBCD.script v20 causes that first the BCD boot manager runs from USB.
If F12 key to bring up the boot menu is used, the boot sequence can be first HD and then USB.
In the latter case, the USB drive is not the first drive.
The BCD boot manager sets the USB drive as the first drive, then Win7PE or grub4dos can be started.

I think this compilation is usable. Win7PE in
configuration shown is used extensively by me for a long time:

- Win7PE universally on CDDVD
- USB Win7PE on minimal media size
- Win7PE simply copy to a first NTFS partition.

Changelog:
v2011_11_07: win-pxe.script v9
- Recreate Shortcuts with trying to net use y:
- integrate grub4dos-0.4.5b-2011-11-04.7z by chenall
v2011_11_07: the base is Win7PE_SE_20111120
v2011_09_29: is the first version.

Regards,
NetFanTom :rolleyes:
  • Nuno Brito, TheHive, ludovici and 2 others like this

#2 ludovici

ludovici

    Silver Member

  • .script developer
  • 610 posts
  • Location:France
  •  
    France

Posted 30 September 2011 - 01:26 PM

Thanks NetFanTom :good:
  • Dr.NHTT likes this

#3 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 30 September 2011 - 08:01 PM

Thank you , nice addition and pretty package :clap:


I have on my side some updates and addition coming for the base, a question of time (hard currently).
I'll borrow maybe some of your script updates, You can then make an update of nettyPE, I don't know.

:cheers:
  • Dr.NHTT likes this

#4 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 01 October 2011 - 07:11 AM

to ChrisR (and the others) :D

I've made the netty scripts for all people, so this scripts can be integrated into Win7PE_SE.
I ask even for the fact that this scripts be included in Win7PE_SE.

- possibly 2 - shell & Config_netty
- 1-50_Optimizations_netty.script with possible static computer name elimination
- Apps:TotalCommander7.56a script
- PortableApps.com_EXE script to use portable apps outside the boot.wim
- OtherOS: Diskimages01 - 04 scripts new development for CDDVD, HDD and floppy image files
- PXE_NetBooting: win_pxe.script new development for diskless network booting over PXE server
- USBDeviceBCD.script v20 new is that the BCD menu is not new written but changed.
All previous entries e.g. Multiwim remain. :)

#5 TheHive

TheHive

    Platinum Member

  • .script developer
  • 3,721 posts

Posted 01 October 2011 - 08:54 AM

Tested and boots.
  • Dr.NHTT likes this

#6 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 01 October 2011 - 09:55 AM

I've made the netty scripts for all people, so this scripts can be integrated into Win7PE_SE.
I ask even for the fact that this scripts be included in Win7PE_SE.

Thank you very much NetFan Tom, it is generous :good:.
So I'll watch all that in this direction.

You who study grub4dos-0.4.4-2009-06-20, what it brings in addition (pxe, ...).
What do you think of a change of grub4dos in iso.script by this one.

:cheers:

#7 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 01 October 2011 - 10:45 AM

It looks like that in iso script is GRUB4DOS 0.4.4 2009-05-23.
GRUB4DOS 0.4.4 2009-06-20 has PXE support and may work for all Win7PE_SE purposes. :thumbsup:

#8 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 01 October 2011 - 12:20 PM

Thanks :)

Have a good weekend

#9 Rui Paz

Rui Paz

    Frequent Member

  • Advanced user
  • 188 posts
  •  
    Portugal

Posted 01 October 2011 - 07:00 PM

Hi NetFanTom,

Thanks for sharing your work, just tested and found that the DHCP server isn't working properly. Using your default settings the tftp32 shortcut on the desktop point to Y:\Programs\tftpd32\tftpd32.exe tftp needs to write to the file tftpd32.ini it should point to x:\Programs\tftpd32\tftpd32.exe where it can change the ini file.

I have some how similar setup using LiveXP, in my opinion penetwork should start asking user to choose a network profile, normally the PXE server will have a static IP when its the only one DHCP server available on the network.

By the way the Syslog server part can be left disable...

#10 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 02 October 2011 - 10:10 AM

Hello Rui Paz and all the others! :thumbup:

Thank you for the very interesting question.

Y:\Programs\tftpd32\tftpd32.exe requires only write access to the tftpd32.ini when you have to make changes.
Write permissions have been automatically when you boot from HD, USB with write access or Network with write access.

The nettyPE concept implies that multiple WinPE- computers can communicate on the network.
Therefore, the basic setting is automatic IP receive and DHCP client.
If the PXE server first starts Y:\Programs\tftpd32\tftpd32.exe a DHCP server is started with the IP range starting at 192.168.0.30 with IPv4.

The PXE server assigns itself an IP. From the APIPA IP e.g. 169.254.84.130 will be certainly 192.168.0.30.

If penetwork starts and asks for the selection of a profile, it means additional operating expenses.
This operating expenses is significantly by using multiple computers on the network starts nettyPE.

However asking for penetwork profiles can furnish to everyone.

When a change of tftpd32.ini when booting CDDVD is necessary to,
one can use Start > Programs > Network > tftpd32 CLIENT mode
in place of
start tftpd32 from Desktop (y:\Programs\tftpd32\tftpd32.exe).

tftpd32 CLIENT mode starts tftpd32 without a server
(x:\Program Files\tftpd32\tftpd32.exe).
It has always Write permissions and can start the tftpd32 server manually.

tftpd32 exists twice.
tftpd32 CLIENT mode is intended for network booting,
to transfer a file via tftp without sharing expenses.

#11 blued

blued
  • Members
  • 9 posts

Posted 02 October 2011 - 03:35 PM

For Win7 PE, this is one of the smoothest, trouble free builds I've tried. Just a couple issues I'm having though. When I format and copy to USB, it boots and works OK, but when I start penetwork, the Y drive changes letters. Any shortcuts to apps in Y:\Programs as a result lose their path and of course wont work. Of course I can go to manage in My Computer and fix drive paths, but its a small annoyance. This only begun to happen when I changed penetwork options to start manually instead of automatically (to shorten boot time). Thanks for your work on this.

Edited by blued, 02 October 2011 - 03:41 PM.


#12 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 02 October 2011 - 05:19 PM

USB booting works fine for me.

The requirement is that the WriteMedia USBDeviceBCD script is used for formatting and file copying.

First, the boot.wim file is loaded and an ramdrive with the letter X: set up.

After starting Win7PE the system searches for the file CdUsb.Y.
The drive in which this file is found first, receives the letter Y:.

If the file CdUsb.Y is not found, no Y: drive set up.

One source of error could be that the first CdUsb.Y is not on the (USB) start drive.
Maybe you should rename the first CdUsb.Y e.g. on HD outside of the start drive and boot again. B)

Another source of error could be that the network driver does not work.

#13 Rui Paz

Rui Paz

    Frequent Member

  • Advanced user
  • 188 posts
  •  
    Portugal

Posted 03 October 2011 - 04:44 PM

Hello Rui Paz and all the others! :thumbup:

Thank you for the very interesting question.

Y:\Programs\tftpd32\tftpd32.exe requires only write access to the tftpd32.ini when you have to make changes.
Write permissions have been automatically when you boot from HD, USB with write access or Network with write access.


It also writes the leases information on the ini file.

The nettyPE concept implies that multiple WinPE- computers can communicate on the network.
Therefore, the basic setting is automatic IP receive and DHCP client.
If the PXE server first starts Y:\Programs\tftpd32\tftpd32.exe a DHCP server is started with the IP range starting at 192.168.0.30 with IPv4.

The PXE server assigns itself an IP. From the APIPA IP e.g. 169.254.84.130 will be certainly 192.168.0.30.

This is probably something new on recent versions of TFTPD32 because i remember the program complains if starts with a IP outside the network used on the DHCP pool, didn't know that tftp will assign a IP to the "server itself"

If penetwork starts and asks for the selection of a profile, it means additional operating expenses.
This operating expenses is significantly by using multiple computers on the network starts nettyPE.


That isn't a problem because penetwork will auto continue after 5 sec. using the default profile so it can use DHCP on the client without human input.

#14 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 04 October 2011 - 06:55 AM

Hi!

nettyPE use tftpd32.400.zip version 4.0.

It also writes the lease information on the ini file.

For me, the Y:ProgramsTftpd32tftpd32.ini will not change when I start from CDDVD.
In particular, the leases are not stored in the CDDVD tftpd32.in.

This is probably something new on recent versions of TFTPD32 because i remember
the program complains if starts with a IP outside the network used on the DHCP pool,
didn't know that tftp will assign a IP to the "server itself".

Good news is not it? :thumbsup:
nettyPE does not start with a IP outside the network used on the DHCP pool.
It starts with the APIPA IP and assigns itself an IP from the DHCP pool.

That you could clearly see in the video.

Please go to YouTube and download the video or run it in full screen mode.
From the APIPA IP 169.254.20.230 will be the IP 192.168.0.30.

The only thing you have to do is start tftpd32 and wait a moment
(See video).

In my opinion it is the best to start with no additional input or waiting.
Alternatively, you can configure the Penetwork script the way you want.

Regards,
NetFanTom

#15 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10,122 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 15 October 2011 - 11:45 AM

Hello,

This post gets lost from sight very quickly.

Please post this project at the download portal on http://reboot.pro/fi...ory/4-projects/

I am recommending it to my friends that want to try out PXE without fuss.

:)

#16 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 10,125 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 October 2011 - 12:15 PM

As a side note, debating about grub4dos versions prior than 16-10-2009 is pointless. :ph34r:
Versions earlier than that were buggy (besides missing a few features).
That version is the " base reference" (or "stable") though nowadyas using latest form Chenall :worship: is advised.

:cheers:
Wonko

#17 Nuno Brito

Nuno Brito

    Platinum Member

  • Team Reboot
  • 10,122 posts
  • Location:boot.wim
  • Interests:I'm just a quiet simple person with a very quiet simple life living one day at a time..
  •  
    European Union

Posted 17 October 2011 - 09:44 AM

I've mentioned this project on this week's newsletter.

Congratulations. :)

#18 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 18 October 2011 - 08:49 PM

Thank you for the terrific news. :thumbup:

I have put the project under the downloads available.

http://reboot.pro/fi...ile/68-nettype/


and under
reboot.pro → Groups → WinBuilder → Projects
http://reboot.pro/15656/

I'll test Chenall Grub4Dos version.
I'm sure I'll incorporate this release in the next update.

Regards,
NetFanTom :thumbsup:
  • Nuno Brito likes this

#19 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 783 posts
  •  
    France

Posted 19 October 2011 - 10:06 AM

Hi NetFanTom,

NettyPE with pxe has its own world now, great :thumbsup:.

As you saw, I updated yesterday Win7PE_SE. I have not integrated pxe, by lack of time to test it in detail B).
Perhaps one day, pxe in the base, I need to learn more about pxe.

I wish you a good update of NettyPE with the new base.
If you see things to improve together, do not hesitate. I hope for a good future cooperation. :thumbsup:


ps: I put the latest grub4dos version of chenall :) in Iso and copy to usb script.

Regards,
Chris

:cheers:
  • Nuno Brito likes this

#20 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 19 October 2011 - 11:46 AM

As you know, I'm an accurate tester of my scripts and the Win7PE_SE base. :pressure:

Therefore I can not wait until the implementation of the new basis is completed.

The good future cooperation also on my part is the best foundation. B)

Regards,
NetFanTom
:cheers:

#21 Michele13

Michele13

    Frequent Member

  • Tutorial Writer
  • 164 posts
  •  
    Italy

Posted 19 October 2011 - 04:20 PM

Do I need a Windows 7 DVD to make this project or can I use a WAIK distribution to make it? Can I use an Italian WAIK DVD?

#22 NetFanTom

NetFanTom

    Frequent Member

  • .script developer
  • 117 posts
  •  
    Germany

Posted 20 October 2011 - 09:42 AM

Good question. :suda:

I originally developed the PXE module for minimal sources eg WAIK.
Later I found that WAIK has some disadvantages as the sole source:
  • Standard network driver must be installed explicitly.
  • Network shares do not work, so I often had to use an FTP server and FTP-Drive software.
    This worked only partially.
nettyPE is designed to use an original Windows DVD or ISO as the source,
thus are used standard network driver and the network share. :thumbsup:

I have tested nettyPE successfully with Windows 7 Enterprise 90-Day Trial SP0 and SP1
in English and German. Therefore, I am assuming that the language of the source does not matter.

Windows 7 Enterprise 90-day trial, anyone can download at the following address:
http://technet.micro...r/cc442495.aspx
If you want to have another language version, click on the United States (English) link in the upper right corner.
You can change the language.

Using the tool RT Se7en Lite can integrate SP1.
http://www.rt7lite.com/downloads.html
There the slipstream method is used.
:thumbup:

Regards :)

Edited by NetFanTom, 30 October 2011 - 07:03 AM.
added RT Se7en Lite Info.


#23 Klaus21

Klaus21

    Frequent Member

  • Advanced user
  • 169 posts
  •  
    Germany

Posted 26 October 2011 - 07:06 AM

Hi NetFan Tom,
I also wanted to try your project again my old familiar error - (0-preconfig.script) Error with mounting source! (Install.wim).
The system: Windows 7 x86 SP1 with WAIK installed.

Maybe you have an idea how I can the "Error with mounting source! (Install.wim)" trick?
Here is my log file
http://dl.dropbox.co...9732/logNe.html

regards Klaus

#24 Michele13

Michele13

    Frequent Member

  • Tutorial Writer
  • 164 posts
  •  
    Italy

Posted 26 October 2011 - 10:31 AM

Hi NetFan Tom,
I also wanted to try your project again my old familiar error - (0-preconfig.script) Error with mounting source! (Install.wim).
The system: Windows 7 x86 SP1 with WAIK installed.

Maybe you have an idea how I can the "Error with mounting source! (Install.wim)" trick?
Here is my log file
http://dl.dropbox.co...9732/logNe.html

regards Klaus


maybe the program cannot find the executable that mounts wim files. have you specified where have you installed WAIK before running the project? (look in the source tab: the one where you specified where are the files of Windows 7)

#25 Klaus21

Klaus21

    Frequent Member

  • Advanced user
  • 169 posts
  •  
    Germany

Posted 26 October 2011 - 11:13 AM

Source: C:Win7U - WAIK C:Program FilesWindowsAIK

---> Image Configuration
Wim Tools: Auto
Press "Save / Get Wim Info" everything is OK

If I mark "Use your Exctracted wim folder..."
And press "Save / Get Wim Info" I get the followin error
http://db.tt/13JIxRQz

Have compared the wimgapi.dll:
C: windows system32 wimgapi.dll (6.1.7600.17514 - 397 KB -
with
Tools Win7PE_SE x86 wimgapi.dll (6.1.7600.16385 - 402 KB
I replaced the WIMGAPI but without success




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users