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


4 Pages V   1 2 3 > » 

booting with pxe using tftpd32
diddy
Posted on: Jun 7 2010, 09:17 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@bergoto
Sorry for this late response. In answer to your questions -

QUOTE (bergoto @ May 21 2010, 10:12 AM) *
...in ur guide ("Install Windows XP" section) u wrote that XP cant be installed with its startup files and should be used files from Win2003...

This only applies when using grub4dos (not sure about newer versions) and some older versions of pxelinux (including 3.81/3.82). First test with the XP files and if they are not working try using server 2003 SP1/R2 files instead.

You only need to hexedit the files if they have been renamed - there is no need to rename the files if you are only installing XP (other than renaming setupldr.exe as ntldr). Keep the process as simple as possible until you get one OS working.

Just for the record, it is possible to install Windows XP from a Windows 7 RIS server if Shao's instructions are followed. Basically set up the share and security permissions to allow Anonymous Login and everyone and tweak the settings in the Network and Sharing Centre (Start > Control Panel > Network and Internet > Network and Sharing Center and select Change advanced sharing settings).

QUOTE (bergoto @ May 21 2010, 10:12 AM) *
...i get BSoD when the image is loaded on the laptop...

If the BSOD you are referring to occurs when XP is installed it might be due to the partition you are installing on having been created using Windows 7/Vista. If the BSOD occurs when booting a PE disc (.iso) then make sure that you are using a ram loading method (see here).

diddy

  Forum: Tftpd32 · Post Preview: #101873 · Replies: 24 · Views: 3,366

FiraDisk (0.0.1.22)
diddy
Posted on: Jun 7 2010, 12:16 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


QUOTE (supaJ @ Jun 7 2010, 10:33 AM) *
Great work! How do I create the disk image? Is it VHD or VMDK? Please advise.


Simply follow the instructions in Karyonix post and ammend the boot.ini entry - adding/amending /firadisk=disk,vmem=C:\win.img,size=2147483648.

Reboot Windows and choose the new option in the XP boot menu

The disk image (in this case c:\win.img) will be created and mounted - it will still require initializing in diskmgmt.msc (or by using diskpart).

Note - the size is in bytes.

diddy
  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #101825 · Replies: 300 · Views: 70,034

FiraDisk (0.0.1.22)
diddy
Posted on: Jun 6 2010, 09:20 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@karyonix
Great work. Just tested this morning - XP is now booting fine from a disk image not mapped to RAM.

First test failed as I forgot to edit the arcpaths in boot.ini - oops!

Was in the process of updating my firadisk guide however in view of the speed of your updates and forthcoming feature implementations I think it best to wait.

diddy

  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #101715 · Replies: 300 · Views: 70,034

Windows 7 Network Share Missing In Explorer
diddy
Posted on: Jun 5 2010, 11:06 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@Wonko
Hope you (and the cats) are well smile.gif

QUOTE (Wonko the Sane @ Jun 5 2010, 09:31 AM) *
What happens if you run another instance of Explorer with elevated credentials? unsure.gif

cheers.gif
Wonko


Nothing!

Running Windows 7 with UAC disabled the shares are however displayed correctly.

diddy

  Forum: Windows 7 · Post Preview: #101653 · Replies: 2 · Views: 218

Windows 7 Network Share Missing In Explorer
diddy
Posted on: Jun 5 2010, 09:12 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


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
  Forum: Windows 7 · Post Preview: #101643 · Replies: 2 · Views: 218

BCDEdit Version 6.1.7600 Notes/Guide
diddy
Posted on: May 25 2010, 06:41 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


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
  Forum: Windows 7 · Post Preview: #100919 · Replies: 1 · Views: 364

gPXE notes for net booting from a remote http server
diddy
Posted on: May 25 2010, 06:08 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


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
  Forum: LAN and any other methods · Post Preview: #100917 · Replies: 1 · Views: 412

PXE Boot Guide using Windows XP server
diddy
Posted on: May 19 2010, 05:27 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@cdob

In response to your post here - removing the /d switch works as you described to display the correct descriptions for WinPE entries. Sorry for the late response I only recently got around to testing it due to other commitments. The use of different {ramdiskoptions} may well be a lifesaver in future.

cheers.gif

diddy
  Forum: Boot from USB / Boot anywhere · Post Preview: #100566 · Replies: 14 · Views: 10,703

Multi-boot BCD entries -some guides are WRONG
diddy
Posted on: May 19 2010, 05:22 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


Also refer to cdob's post here.

In addition to covering removing the /d switch in {ramdiskoptions} it also gives instructions for using two (or more) ramdisks.

diddy

p.s. I only recently got aroud to testing this but it's definitely working. Cheers cdob.
  Forum: Tftpd32 · Post Preview: #100564 · Replies: 6 · Views: 622

booting with pxe using tftpd32
diddy
Posted on: May 19 2010, 05:14 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


QUOTE (Sha0 @ May 18 2010, 08:56 PM) *
diddy: Please try the following permissions changes in "classic file sharing" mode:
  • Share permissions
    • Everyone: Full Control
    • ANONYMOUS LOGON: Full Control
  • NTFS permissions
    • Everyone: Full Control
    • ANONYMOUS LOGON: Full Control

And see if that makes a difference. I don't use Simple File Sharing, but am able to boot BartPE or install Windows via SMB. See also the permissions details given at the XP/2003 Recovery Console via PXE, TFTP, SMB tutorial.


@Sha0

Thanks for the tip - I look forward to testing this soon.

I'll feedback and update my guide if it works.

cheers.gif

diddy


  Forum: Tftpd32 · Post Preview: #100561 · Replies: 24 · Views: 3,366

WinPE 3.0 - annoying point 2, Browse for Folder error
diddy
Posted on: May 19 2010, 05:07 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@tsetya

Many, many thanks - you are a genius!!!

This did the trick and will now allow me to use a number of essential programs under WinPE (3.0).

It's great to see a simple solution to the problem.

cheers.gif

diddy

  Forum: Windows PE · Post Preview: #100560 · Replies: 8 · Views: 1,250

booting with pxe using tftpd32
diddy
Posted on: May 18 2010, 07:19 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@bergoto

This is a shameless bit of self promotion however see my guide here (and here) - it's based upon Gianluigi Tiesi's "OpenSource Implementation of MS RIS Server" guide.

Although it users Windows XP on the server much of it will still apply.

The main problem you will have if using Windows 7 on the server is with share permissions - see here. This is an issue I was not able to solve unfortunately.

Good luck!

diddy
  Forum: Tftpd32 · Post Preview: #100455 · Replies: 24 · Views: 3,366

WinPE 3.0 - annoying point 2, Browse for Folder error
diddy
Posted on: May 15 2010, 09:16 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


My frustration continues. Some observations.

Tested recuva and getdataback. The "browse for folder" dialog box is empty - the dialog box includes a "Make New Folder" button.

When using getdataback I noticed that a secondary "browse for folder" dialog box correctly displays the folder tree and works - this dialog box does not include a "Make New Folder" button.

Context menu "Open with" - no drive tree.

Regedit > Load Hive... - no drive tree.

I would appreciate any help in getting this functioning in a basic build of WinPE 3.0 - no Explorer and minimal registry changes (e.g. not importing a full classes key from a Windows 7 registry hive).

diddy
  Forum: Windows PE · Post Preview: #100204 · Replies: 8 · Views: 1,250

Need help mounting .wim in WinPE 3.0
diddy
Posted on: May 6 2010, 11:32 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


Just for the record -

DISM and ImageX (version 6.1.7600) are dependant upon the wimmount service and require wpeinit to be executed when using in WinPE 3.0. I suspect that WimCaptEx behaves in the same way but have not tested yet.

ImageX (versions 6.0.6000 and 6.0.6001) is dependant upon the wimfltr service. Thanks to paraglider I've now played around with these versions on WinPE 3.0 - installing at run time and starting the wimfltr service manually. As paraglider stated these versions of ImageX are considerably faster than DISM (and ImageX version 6.1.7600) when mounting and unmounting images.

Based on initial tests once the WinFltr service has been installed and started then DISM (and probably ImageX version 6.1.7600 and maybe WimCaptEx) stops functioning correctly. With the WimFltr service started DISM was able to mount and unmount .wim files however I was not able to mount the registry hives correctly. I have no idea whether injecting drivers works as I have not had time to test.

Will test (more) fully after the weekend and report back.

@Wonko
Will check out your batch files after the weekend - I'm going on a short break from tomorrow and have been banned from taking the netbook with me.

diddy


  Forum: Windows PE · Post Preview: #99494 · Replies: 6 · Views: 571

WinPE 3.0 - annoying point 2, Browse for Folder error
diddy
Posted on: May 4 2010, 10:52 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@wimb
Do you have any idea which classes need adding. Merging the registry file included in Make_PE3 is overkill for my needs - it's about 20MB and includes entries for a lot of stuff not in my custom build.

Make_PE3 looks like a great project - I'm sticking with my custom build scripts though, due to the time I've invested in them.


@JFX
It might come as a surprise but I don't really use winbuilder. I've managed a few LiveXP builds in the past however I'm migrating to WinPE 3.0 built with batch files. Is µExplorer available as a standalone project and will it add browse for folders.


@nuno
If you're reading this then just for the record I have nothing against winbuilder - I just don't have the time to learn how to build scripts with it at the moment.

diddy
  Forum: Windows PE · Post Preview: #99393 · Replies: 8 · Views: 1,250

Need help mounting .wim in WinPE 3.0
diddy
Posted on: May 4 2010, 10:33 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@dera

Many thanks for the information. My WinPE is built from custom batch files and doesn't have many changes from a basic build (built following MS instructions - nothing added).

I built and tested a basic build and found that DISM worked as you stated. After much consideration and a quick test I realised that the only major difference between a basic build and my custom build is that I use a custom shell and do not run startnet.cmd - which runs wpeinit.exe

I managed to get DISM working in my build by running wpeinit.exe from a batch file.

Thanks for putting me on the right track.

diddy
  Forum: Windows PE · Post Preview: #99392 · Replies: 6 · Views: 571

WinPE 3.0 - annoying point 2, Browse for Folder error
diddy
Posted on: May 2 2010, 03:14 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


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
  Forum: Windows PE · Post Preview: #99274 · Replies: 8 · Views: 1,250

WinPE 3.0 - annoying point 1
diddy
Posted on: May 2 2010, 03:07 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


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
  Forum: Windows PE · Post Preview: #99272 · Replies: 0 · Views: 364

Need help mounting .wim in WinPE 3.0
diddy
Posted on: May 2 2010, 03:00 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


I've been playing around with WinPE 3.0 recently and noticed that DISM.exe, wimmount.sys and wimgapi.dll are included in the base image.

After booting into WinPE 3.0 I've started the wimmount service and attempted to mount an image using DISM (and ImageX and WimCaptEx) however it always results in errors.

The relevant registry settings and tools all seem to be included - has anyone had any success.

If yes please post instructions.

I'm not sure if wimfsf is causing the problem - this service appears to be running in WinPE but does not appear to be included in a running Windows 7.

diddy
  Forum: Windows PE · Post Preview: #99269 · Replies: 6 · Views: 571

PXE Boot Guide using Windows XP server
diddy
Posted on: Mar 24 2010, 10:46 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


Sorry for the mix up with the scripts.

I've re-uploaded the guide - scripts are included this time.

diddy

p.s. Child commitments continue to keep me busy so appologies for lack of responses over the past few months.
  Forum: Boot from USB / Boot anywhere · Post Preview: #95751 · Replies: 14 · Views: 10,703

FiraDisk (0.0.1.22)
diddy
Posted on: Oct 21 2009, 05:48 AM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


QUOTE (karyonix @ Oct 21 2009, 12:32 AM) *
Test-signed firadisk 0.0.1.12...

Thank you for the fast response. 10 out of 10 for service. cheers.gif

BTW, don't know what you mean about development having slowed down. Version 0.0.1.12 is rock solid stable on my system. I look forward to testing whatever you add with the next build.

diddy
  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #82254 · Replies: 300 · Views: 70,034

Problems with Firadisk
diddy
Posted on: Oct 20 2009, 08:37 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


QUOTE (Marietto2009 @ Oct 20 2009, 09:15 PM) *
1) I found a very good version of Windows 7 lite from the torrent websites.

No offence - I wouldn't trust a torrent download for testing purposes as you have no idea what might have been added or removed.

QUOTE (Marietto2009 @ Oct 20 2009, 09:15 PM) *
3) I copied manually \Users,\Documents and Settings and \ProgramData from...

Fair enough - this shouldn't be the case however strange things can happen in windows

QUOTE (Marietto2009 @ Oct 20 2009, 09:15 PM) *
4) When I ran this command...

The firadisk driver must be installed on the operating system you plan to copy to the disk image (in your case the Windows 7 lite install)- it's no use running this command on a windows installation you are not copying to the RAM disk.

QUOTE (Marietto2009 @ Oct 20 2009, 09:15 PM) *
5) I think that the grub4dos entry has been added automatically to boot.ini when I wrote these commands...

It shouldn't have been.

No offence but if I was you I'd test booting a full XP or 2003 first as these systems are known to work. Once you have spent the time learning the steps involved then try imaging your Windows 7 install. I'm not even sure that you have managed to boot Grub4dos yet and this step must be completed first.

diddy
  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #82241 · Replies: 14 · Views: 2,387

FiraDisk (0.0.1.22)
diddy
Posted on: Oct 20 2009, 08:20 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


@karyonix
It will come as no great surprise that firadisk also works with Vista 32-bit and 64-bit - virtual floppy and virtual hard disks are mounted, virtual CD is not. Disable Driver Signature Enforcement is required when using Vista 64-bit.

I have also tested the driver with a non ram loading build of WinPE 3.0 (the image was applied to a hard disk and does not boot from a .wim image). This functioned similarly to Windows 7 and Vista with virtual floppy and virtual hard disks being detected correctly - virtual CD's are not. With some messing around I was able to boot non ram loading versions of WinPE 3.0 (x86 and amd64) from a disk image. The steps taken were as follows -

1) Mounted a disk image as drive R:

2) Applied the contents of a .wim image to drive R: using command syntax imagex.exe /apply my.wim 1 R:

3) Copied boot folder and bootmgr to R:

4) Deleted R:\boot\BCD

5) Created new BCD store by running the following batch -
CODE

@echo off

BCDEDIT.EXE /createstore R:\boot\BCD
BCDEDIT.EXE /store R:\boot\BCD /create {bootmgr} /d "Boot Manager"
BCDEDIT.EXE /store R:\boot\BCD /set {bootmgr} device boot

for /f "tokens=3" %%A in ('BCDEDIT.EXE /store R:\boot\BCD /create /d "WINPE" /application osloader') do set guid=%%A
echo guid=%guid%
echo.
BCDEDIT.EXE /store R:\boot\BCD /set %guid% osdevice boot
BCDEDIT.EXE /store R:\boot\BCD /set %guid% device boot
BCDEDIT.EXE /store R:\boot\BCD /set %guid% path \Windows\system32\boot\winload.exe
BCDEDIT.EXE /store R:\boot\BCD /set %guid% systemroot \Windows
BCDEDIT.EXE /store R:\boot\BCD /set %guid% winpe yes
BCDEDIT.EXE /store R:\boot\BCD /set %guid% detecthal yes
BCDEDIT.EXE /store R:\boot\BCD /displayorder %guid% /addlast
pause


6) Mounted R:\windows\system32\config\system as HKLM\_WinPE_SYSTEM

7) Merged one of the following .reg files -

x86 registry file
CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0001]
"InfPath"="firadisk.inf"
"InfSection"="FiraDiskDevice"
"InfSectionExt"=".NTx86"
"ProviderName"="Karyonix"
"DriverDateData"=hex(3):00,40,19,FA,84,2E,CA,01
"DriverDate"="9-6-2009"
"DriverVersion"="0.0.1.12"
"MatchingDeviceId"="root\\firadisk"
"DriverDesc"="FiraDisk Virtual Disk Enumerator"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT\0000\Control]
"ActiveService"="Fastfat"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000]
"Capabilities"=dword:00000000
"Class"="SCSIAdapter"
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"ConfigFlags"=dword:00000004
"DeviceDesc"="FiraDisk Virtual Disk Enumerator"
"Driver"="{4D36E97B-E325-11CE-BFC1-08002BE10318}\\0001"
"HardwareID"=hex(07):72,00,6f,00,6f,00,74,00,5c,00,66,00,69,00,72,00,61,00,\
64,00,69,00,73,00,6b,00,00,00,00,00
"Mfg"="Karyonix"
"Service"="firadisk"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\Control]
"ActiveService"="firadisk"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf]


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk\Enum]
"0"="ROOT\\SCSIADAPTER\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\root#firadisk]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="firadisk"
"DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\GroupOrderList]
"SCSI Miniport"=hex:3f,00,00,00,00,01,00,00,01,01,00,00,19,00,00,00,01,00,00,\
00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00,06,00,00,00,07,00,00,00,\
08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,00,00,0c,00,00,00,0d,00,00,00,0e,\
00,00,00,0f,00,00,00,10,00,00,00,11,00,00,00,12,00,00,00,13,00,00,00,14,00,\
00,00,15,00,00,00,16,00,00,00,17,00,00,00,1a,00,00,00,18,00,00,00,1b,00,00,\
00,1c,00,00,00,1d,00,00,00,1e,00,00,00,1f,00,00,00,20,00,00,00,23,00,00,00,\
24,00,00,00,25,00,00,00,26,00,00,00,27,00,00,00,28,00,00,00,29,00,00,00,2a,\
00,00,00,2b,00,00,00,2c,00,00,00,2d,00,00,00,2e,00,00,00,2f,00,00,00,30,00,\
00,00,31,00,00,00,32,00,00,00,33,00,00,00,34,00,00,00,35,00,00,00,36,00,00,\
00,37,00,00,00,38,00,00,00,39,00,00,00,3a,00,00,00,3b,00,00,00,3c,00,00,00,\
3d,00,00,00,3e,00,00,00,3f,00,00,00


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\services\firadisk]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,66,00,69,00,72,00,61,00,64,00,69,\
00,73,00,6b,00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="FiraDisk Virtual Disk Driver"
"Group"="SCSI miniport"
"DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"


[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\detected#firadisk]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="firadisk"
"DriverPackageId"="firadisk.inf_x86_neutral_094ec26a72ff2a56"



amd64 registry file
CODE

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\Class\{4D36E97B-E325-11CE-BFC1-08002BE10318}\0001]
"InfPath"="firadisk.inf"
"InfSection"="FiraDiskDevice"
"InfSectionExt"=".NTAMD64"
"ProviderName"="Karyonix"
"DriverDateData"=hex:00,40,19,fa,84,2e,ca,01
"DriverDate"="9-6-2009"
"DriverVersion"="0.0.1.12"
"MatchingDeviceId"="root\\firadisk"
"DriverDesc"="FiraDisk Virtual Disk Enumerator"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\LEGACY_FASTFAT\0000\Control]
"ActiveService"="Fastfat"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000]
"ClassGUID"="{4d36e97b-e325-11ce-bfc1-08002be10318}"
"Class"="SCSIAdapter"
"Driver"="{4d36e97b-e325-11ce-bfc1-08002be10318}\\0001"
"Mfg"="@firadisk.inf,%mfakaryonix%;Karyonix"
"HardwareID"=hex(7):72,00,6f,00,6f,00,74,00,5c,00,66,00,69,00,72,00,61,00,64,\
00,69,00,73,00,6b,00,00,00,00,00
"CompatibleIDs"=hex(7):64,00,65,00,74,00,65,00,63,00,74,00,65,00,64,00,5c,00,\
66,00,69,00,72,00,61,00,64,00,69,00,73,00,6b,00,00,00,00,00
"Service"="firadisk"
"DeviceDesc"="@firadisk.inf,%firadiskdevice%;FiraDisk Virtual Disk Enumerator"
"ConfigFlags"=dword:00000000
"Capabilities"=dword:00000000
"ContainerID"="{00000000-0000-0000-FFFF-FFFFFFFFFFFF}"
"ParentIdPrefix"="1&2afd7d61&0"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\Control]
"ActiveService"="firadisk"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Enum\Root\SCSIADAPTER\0000\LogConf]

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk\Enum]
"0"="ROOT\\SCSIADAPTER\\0000"
"Count"=dword:00000001
"NextInstance"=dword:00000001

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\root#firadisk]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="firadisk"
"DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\GroupOrderList]
"SCSI Miniport"=hex:3f,00,00,00,00,01,00,00,01,01,00,00,19,00,00,00,01,00,00,\
00,02,00,00,00,03,00,00,00,04,00,00,00,05,00,00,00,06,00,00,00,07,00,00,00,\
08,00,00,00,09,00,00,00,0a,00,00,00,0b,00,00,00,0c,00,00,00,0d,00,00,00,0e,\
00,00,00,0f,00,00,00,10,00,00,00,11,00,00,00,12,00,00,00,13,00,00,00,14,00,\
00,00,15,00,00,00,16,00,00,00,17,00,00,00,1a,00,00,00,18,00,00,00,1b,00,00,\
00,1c,00,00,00,1d,00,00,00,1e,00,00,00,1f,00,00,00,20,00,00,00,23,00,00,00,\
24,00,00,00,25,00,00,00,26,00,00,00,27,00,00,00,28,00,00,00,29,00,00,00,2a,\
00,00,00,2b,00,00,00,2c,00,00,00,2d,00,00,00,2e,00,00,00,2f,00,00,00,30,00,\
00,00,31,00,00,00,32,00,00,00,33,00,00,00,34,00,00,00,35,00,00,00,36,00,00,\
00,37,00,00,00,38,00,00,00,39,00,00,00,3a,00,00,00,3b,00,00,00,3c,00,00,00,\
3d,00,00,00,3e,00,00,00,3f,00,00,00

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Services\firadisk]
"Start"=dword:00000000
"Type"=dword:00000001
"ErrorControl"=dword:00000001
"ImagePath"=hex(2):73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,\
52,00,49,00,56,00,45,00,52,00,53,00,5c,00,66,00,69,00,72,00,61,00,64,00,69,\
00,73,00,6b,00,2e,00,73,00,79,00,73,00,00,00
"DisplayName"="FiraDisk Virtual Disk Driver"
"Group"="SCSI miniport"
"DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"

[HKEY_LOCAL_MACHINE\_WinPE_SYSTEM\ControlSet001\Control\CriticalDeviceDatabase\detected#firadisk]
"ClassGUID"="{4D36E97B-E325-11CE-BFC1-08002BE10318}"
"Service"="firadisk"
"DriverPackageId"="firadisk.inf_amd64_neutral_094ec26a72ff2a56"


8) Copied firadisk.sys/firadisk64.sys as R:\Windows\System32\Drivers\firadisk.sys

9) Copied firadisk.inf to R:\Windows\inf

The fact that the Windows 7 based PE booted successfully makes me optimistic that a full Windows 7 (and probably Vista) can be booted from a disk image IF the source can be reduced to fit in a small enough disk image.

@Everyone.
Having to use Disable Driver Signature Enforcement for 64-bit operating systems is a pain in the a$$ - can anyone create a test certificate.


  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #82239 · Replies: 300 · Views: 70,034

Problems with Firadisk
diddy
Posted on: Oct 20 2009, 07:46 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


QUOTE (karyonix @ Oct 20 2009, 03:39 PM) *
@Marietto2009
How do you reduce Windows 7 size to just 3GB ?
Good question - I've not found any way of getting close to this.

@Marietto2009
I'm confused by your system setup. Why manually copy the files (in step 6) when you can edit exclude.txt and use the following entries instead.
CODE
:\RECYCLER
:\$Recycle.Bin
:\bootstat.dat
:\hiberfil.sys
:\pagefile.sys
:\PerfLogs
:\System Volume Information
\Temp\
\Temporary Internet Files\


You mention that the RAM disk files are copied from Windows 7 lite USB - what is this.

In step 9 devcon is used to install firadisk - firadisk should have been installed in the operating system you copied - before copying it to the disk image. BTW - does devcon work in Windows 7?

You appear to have added a grub4dos entry to boot.ini and a BCD store - which one are you booting.

You mentioned having copied grldr.mbr to drive C: - did you also copy grldr to any of your drives.

If grub4dos has been installed correctly then you should be able to use the command line by pressing C. Try entering your commands from the command line (check link to grub4dos guide in my signature if you are unsure how to use the command line).

If you want to test this I'd suggest temporarily removing some of your hard disks as your setup is confusing even by my standards.

diddy




  Forum: FileDisks/RamDisks: Firadisk, etc. · Post Preview: #82233 · Replies: 14 · Views: 2,387

No Destination Folder Tree
diddy
Posted on: Oct 14 2009, 01:13 PM


Member
**

Group: Tutorial Writer
Posts: 78
Joined: 3-July 08
Member No.: 16,331


I have no experience with Win7PE and do not know if this will work, however I remember a similar problem when using some programs in WinPE 2.0.

I workaround was posted on the 911cd forum (sorry I can't remember who by)- creating the following folder (in the wim image prior to booting) enabled browse for files -

Windows\System32\config\systemprofile\Desktop

Hope this helps,

diddy

  Forum: Win7PE · Post Preview: #81780 · Replies: 4 · Views: 712

4 Pages V   1 2 3 > » 

New Posts  New Replies
No New Posts  No New Replies
Hot topic  Hot Topic (New)
No new  Hot Topic (No New)
Poll  Poll (New)
No new votes  Poll (No New)
Closed  Locked Topic
Moved  Moved Topic