Hello dear guest!

Boot Land is a community driven pc software site established since 2006 and focused on recovery/backup boot disks, research of Microsoft Windows 2000/XP/2003/Vista/7 install/deployment/lease/antivirus/antispam tools, customizing Microsoft Windows PE administration systems and even learning how to recover computer data from disaster situations!

How about joining our boot disk community? So do it. Life's short!

  - You get free access to our newsletter with all the interesting buzz about boot disks
  - We share publicity revenue with everyone who wishes to participate at the forums
  - Publicity is never, never, never displayed to members (along with many other cool things)
http://boot-land.net/register


diddy

Tutorial Writer

**

Joined: 3-July 08
Profile Views: 23*
Last Seen: 11th June 2010 - 02:06 PM
Local Time: Jun 16 2010, 08:27 PM 78 posts (0.11 per day)

diddy doesn't have a personal statement currently.

Profile
Personal Photo
Personal Info
Contact Information

 

diddy
Member
Age Unknown
Gender Not Set
Location Unknown
Birthday Unknown
AIM No Information
Yahoo No Information
ICQ No Information
MSN No Information
Contact Send Message
Contact Private

Topics
Posts
About Me
Files E2T
Comments
Friends
My Content
5 Jun 2010
Read Topic
Windows 7 Network Share Missing In Explorer
I've just noticed some very strange behaviour when using the command line to mount network shares in Windows 7.

Used an elevated command prompt and entered the following command -
net use * //IP_ADDRESS/SHARENAME \user:USER_NAME PASSWORD

The command completed successfully and mounted the share as drive Z:

All files/folders are present when using the command line (e.g. using the dir command lists the contents correctly), however the drive is not mounted in Windows Explorer.

The Z: drive is present in a43.

Using the same command with a non elevated command prompt worked correctly and also mounted the share in explorer.



Another observation -

Used an elevated command prompt with command net use * //IP_ADDRESS/SHARENAME \user:USER_NAME PASSWORD - drive mounted as Z:

Then used a non elevated command prompt to mount a different share - this failed to detect that the Z: drive was already in use and also mapped as Z:

Weird stuff

diddy
25 May 2010
Read Topic
BCDEdit Version 6.1.7600 Notes/Guide
See http://diddy.boot-land.net/bcdedit/index.htm for my notes on BCDEdit usage. These notes also apply to previous versions of BCDEdit - with the exception of Windows 7 features (VHD support).

Feedback welcome.

diddy
25 May 2010
Read Topic
gPXE notes for net booting from a remote http server
After reading the boot over http/ftp thread (here) and following the subsequent link to joakim's posts in the Booting diskless Windows over HTTP thread (here) my interest in gPXE has been piqued.

Here's my initial notes.

Booting via http on the LAN - method 1 and Booting via http (files obtained from externel web server) - method 1 both require a tftp server (tftpd32 used).

Booting via http on the LAN - method 2 and Booting via http (files obtained from externel web server) - method 2 use manually assigned network settings and do not require a tftp server. It should be possible to adapt Booting via http (files obtained from externel web server) - method 2 to boot from most routers with internet access. Remember that DNS will probably need disabling on the router.




Test system setup

Used Rom-o-Matic to generate a gPXE .lkrn file for my network adapter.

PC1 - gPXE client. Netbook with gPXE lkrn file loaded via grub4dos.

PC2 - DHCP/TFTP/HTTP Server on LAN. IP address 192.168.2.2. Tftpd32 running as DHCP and TFTP server. HTTP root directory contains grub.exe, DOS.iso, pxelinux.0, menu.c32 and pxelinux.cfg\default. pxelinux configuration file (pxelinux.cfg\default) contains the following entries -
CODE
default menu.c32

LABEL gpxe
MENU LABEL gPXE test
INITRD DOS.iso
KERNEL grub.exe
APPEND --config-file="map --mem (rd)+1 (0xff); map --hook; root (0xff); chainloader (0xff)"


Router - belkin router. IP address 192.168.2.1. DNS disabled. All PC's use static IP addresses.




Booting via http on the LAN - method 1

Booted PC1 (the netbook) and loaded gPXE.lkrn (via grub4dos - menu.lst entry kernel (hd0,0)/gPXE.lkrn).

Pressed [ctrl] + [B] keys to enter gPXE command-line.

Entered the following at the command prompt (connects to tftpd32 which assigns an IP address, etc) -
CODE
dhcp net0


Entered the following at the command prompt (this will set the configuration file as pxelinux.cfg\default (it will not search for a config file based on mac address etc) and will ensure that all entries in pxelinux.cfg\default will be prefixed with http://192.168.2.2/) -
CODE
set 209:string pxelinux.cfg/default
set 210:string http://192.168.2.2/


Enterered the following at the command prompt (to chainload pxelinux.0 on the http server)
CODE
chain http://192.168.2.2/pxelinux.0


Due to the commands entered above the pxelinux configuration file will be interpreted as -
CODE
default http://192.168.2.2/menu.c32

LABEL gpxe
MENU LABEL gPXE test
INITRD http://192.168.2.2/DOS.iso
KERNEL http://192.168.2.2/grub.exe
APPEND --config-file="map --mem (rd)+1 (0xff); map --hook; root (0xff); chainloader (0xff)"





Booting via http on the LAN - method 2

Booted PC1 (the netbook) and loaded gPXE.lkrn (via grub4dos - menu.lst entry kernel (hd0,0)/gPXE.lkrn).

Pressed [ctrl] + [B] keys to enter gPXE command-line.

Entered the following at the command prompt to configure network settings -
CODE
ifopen net0
set net0/ip 192.168.2.3
set net0/netmask 255.255.255.0
set net0/gateway 192.168.2.1
set net0/dns 192.168.2.1


Entered the following to download DOS.iso from the http server -
CODE
initrd http://192.168.2.2/DOS.iso


Entered the following to download grub.exe from the http server (note the text that was previously added to the APPEND line in pxelinux.cfg\default has been added to the kernel line) -
CODE
kernel http://192.168.2.2/grub.exe --config-file="map --mem (rd)+1 (0xff); map --hook; root (0xff); chainloader (0xff)"


Booted DOS.iso by entering the following at the command prompt -
CODE
boot grub.exe





Booting via http (files obtained from externel web server) - method 1

The steps are very similar to those in Booting via http on the LAN - method 1, however http://192.168.2.2 must be replaced with the url of the remote web server. E.g. -
CODE
dhcp net0
set 209:string pxelinux.cfg/default
set 210:string http://SERVER_IP/
chain http://SERVER_IP/pxelinux.0





Booting via http (files obtained from externel web server) - method 2

The steps are very similar to those in Booting via http on the LAN - method 2, however http://192.168.2.2 must be replaced with the url of the remote web server. E.g. -
CODE
ifopen net0
set net0/ip 192.168.2.3
set net0/netmask 255.255.255.0
set net0/gateway 192.168.2.1
set net0/dns 192.168.2.1
initrd http://SERVER_IP/DOS.iso
kernel http://SERVER_IP/grub.exe --config-file="map --mem (rd)+1 (0xff); map --hook; root (0xff); chainloader (0xff)"
boot grub.exe


Following also works (chainloads pxelinux.0 on the web server)
CODE
ifopen net0
set net0/ip 192.168.2.3
set net0/netmask 255.255.255.0
set net0/gateway 192.168.2.1
set net0/dns 192.168.2.1
set 209:string pxelinux.cfg/default
set 210:string http://SERVER_IP/
chain http://SERVER_IP/pxelinux.0





Embedded Scripts

Now that these commands are working it's possible to embed them into gPXE (using Rom-o-Matic) using an embedded script. E.g. -
CODE
#!gpxe
dhcp net0
initrd http://SERVER_IP/DOS.iso
kernel http://SERVER_IP/grub.exe --config-file="map --mem (rd)+1 (0xff); map --hook; root (0xff); chainloader (0xff)"
boot grub.exe





http://boot.kernel.org

http://boot.kernel.org is worth checking out and has been configured as a http boot server. To connect to it boot gPXE and start a command prompt, then enter either of the following set of commands (remember to ammend the IP addresses to reflect your own setup -
CODE
ifopen net0
set net0/ip 192.168.2.3
set net0/netmask 255.255.255.0
set net0/gateway 192.168.2.1
set net0/dns 192.168.2.1
set 209:string pxelinux.cfg/default
set 210:string http://boot.kernel.org/bko/
chain http://boot.kernel.org/bko/pxelinux.0


CODE
dhcp net0
set 209:string pxelinux.cfg/default
set 210:string http://boot.kernel.org/bko/
chain http://boot.kernel.org/bko/pxelinux.0


net0 is the first network card. If multiple network cards are installed this may also need editing.

A sample script for a static IP address setup (note that the config net0 command will halt the boot process and allow for the settings in the script to be amended -
CODE
#!gpxe
ifopen net0
set net0/ip 192.168.2.3
set net0/netmask 255.255.255.0
set net0/gateway 192.168.2.1
set net0/dns 192.168.2.1
config net0
set 209:string pxelinux.cfg/default
set 210:string http://boot.kernel.org/bko/
chain http://boot.kernel.org/bko/pxelinux.0


Have fun!

diddy
2 May 2010
Read Topic
WinPE 3.0 - annoying point 2, Browse for Folder error
Adding the folder "Windows\System32\config\systemprofile\Desktop" enables a number of programs to correcly display a folder tree.

Unfortunately this workaround does not work for a number of other programs including Recuva.

When trying to recover lost files (after running recuva) a blank "Browse for Folders" dialog box appears - the directlry tree is missing and the program will not work as a result.

Any ideas or suggestions?

BTW - I'm not interested in adding Explorer as shell to get this functioning as it's far too bloated for my requirements.

diddy
2 May 2010
Read Topic
WinPE 3.0 - annoying point 1
A number of file managers including a43 do not display system files when run in WinPE 3.0.

To display hidden and system files the following registry keys/values need adding -

HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Advanced
"ShowSuperHidden"=dword:00000001
"SuperHidden"=dword:00000000

They can be added when running or included during the build by mounting the DEFAULT registry hive.

diddy

Extras
Options
Options
Interests
No Information
Other Information
Country:: No Information
Last Visitors


28 May 2010 - 22:54
Todd


17 Jan 2010 - 4:07
bigshotuk


28 Dec 2009 - 19:45


9 Nov 2009 - 13:35
Twilight Crui...


9 Nov 2009 - 0:12
Comments
Nuno Brito
Welcome back... ;)
20 Apr 2009 - 22:33
Friends
There are no friends to display.
* Profile views updated each hour