Quantcast
Channel: Reboot.pro
Viewing all 6812 articles
Browse latest View live

help needed: booting wee -> grldr config (easy2boot)

$
0
0

dear community,

 

i have to admit that i'm a beginner when it comes to bootloaders but i've managed to create several usb-bootsticks with the help of grub4dos, rmprepusb and easytoboot.

 

what i am currently looking into is to have easy2boot booting of an ext2-formatted usb-stick (ext-filesystem preferrable in my case for reasons not related to booting itself).

 

i got this idea when i learned that wee is able to boot grldr from an ext-partiton (an weesetup.exe is not included in RMPrepUSB) but somehow i seem stuck at a certain point and after trying several configurations for hours am unsure would be the right thing to do.

 

i got as far as getting easy2boot's /menu.lst on the boot partition executed but instead of executing the files last command 'configfile /%grub%/menu.lst' i end up on the grub-shell.

there i can see that the variable %grub% has been set correctly and the easy2boot-scripts will launch successfully if i enter the last command manually 'configfile /%grub%/MENU.lst'.

so i wonder how i may automate this so that i don't have to manually type this last command every time i boot.

 

what seems a bit weird to me is how weesetup.exe makes use of script files provided by the '-s mymenu.txt' parameter as there seems to be some sort of hard-coded values/options that may remain if using a shorter script (visible when looking at the corresponding sectors with a hex-editor).

 

i already tried to add the command 'configfile /%grub%/menu.lst' to mymenu.txt in different ways but i don't seem to get it right.

is there a way to specify a menu.lst including a path as a parameter to grldr such as '--config-file=/my/path/to/menu.lst' or do i need an entirely different approach?

 

thanks for any hints,

anti


Create a bootable WinPE 5.0 x64 USB drive

$
0
0

This tutorial will show you how to manually create a bootable WinPE 5.0 x64 USB drive. WinPE 5.0 is based on Windows 8.1.
It is very similar to my previous tutorial, but there are a few small changes to the packages.
 
I assume you are computer savvy and have at least basic knowledge regarding running commands and batch scripts.
 
By the way, there's also a much faster way to create a WinPE 5.0 USB drive, for those who have Windows 8.1 installed, using the command RecoveryDrive.exe.
We're not going to use this command in this tutorial, rather get our hands a little dirty and do it all manually.
 
*All screenshots in this tutorial are from Windows 7 SP1 x64 eng.
 
Let's begin.
 
1. First you need a PC with Windows 7 (or higher) installed on it. You obviously need a flash drive, 4GB should be enough.
 
2. You'll also need to download the ADK for Windows 8.1 from Microsoft, and install it (the actual download is pretty large - 2.85GB).
   When installing the ADK, you'll only need to select the 2 options I marked in this screenshot:
 

screenshot_11.png

 
3. Now we're going to make your flash drive bootable. Make sure it doesn't contain important files. Open CMD with admin rights, and type:
 [ATTENTION: Replace ‘#’ with the DISK number of your flash drive as it appears after typing LIST DISK]
 

diskpart
list disk
select disk #
clean
create par primary
select par 1
active
format quick fs=fat32
assign
exit

Here's an example screenshot:

screenshot_12.png

 

 
4. Go to: [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\Media
 
5. Copy the entire "Media" folder to C:\Temp\PE5 (so now you should have C:\Temp\PE5\Media).
 
6. Copy [ADK Install DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\en-us\winpe.wim into: C:\Temp\PE5\Media\Sources (create this new "Sources" folder).
 
7. Rename the file you copied, from “winpe.wim” to “boot.wim“.
 
8. From the Start Menu -> All Programs -> Windows Kits -> Windows ADK, open the Deployment and Imaging Tools Environment, and type:
 

screenshot_13.png  

cd C:\Temp\PE5
C:

 
9. We now need to create a new folder which will act as a mount point for the WIM file, so type:

md C:\MOUNT

10. To mount the WIM file, type:

DISM /Mount-Wim /WimFile:C:\Temp\PE5\Media\Sources\boot.wim /Index:1 /MountDir:C:\MOUNT

screenshot_14.png

 

11. We’re now going to modify the boot.wim file by inserting some optional components, which can be found here:
      [ADK INSTALL DIR]\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs
 
      Copy the "WinPE_OCs" folder to C:\Temp\PE5 (so now you should have C:\Temp\PE5\WinPE_OCs).
 
12. ATTENTION: After adding each component, we must also add its corresponding language file, otherwise the component you add won’t work!!
      I recommend adding the following components, in the order they appear:
 

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-WMI.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-WMI_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-Scripting.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-Scripting_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-NetFx.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-NetFx_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-SecureStartup.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-SecureStartup_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-PowerShell.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-PowerShell_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-Dot3Svc.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-Dot3Svc_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-StorageWMI.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-StorageWMI_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-EnhancedStorage.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-EnhancedStorage_en-us.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-SecureBootCmdlets.cab"

dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\WinPE-DismCmdlets.cab"
dism /image:C:\MOUNT /add-package /PackagePath:"C:\Temp\PE5\WinPE_OCs\en-us\WinPE-DismCmdlets_en-us.cab"

* The SecureBootCmdlets package doesn't have a language file associated with it.

* You can put this code in a .bat file and run it to add all these packages in one go.

 
13. Now let's see how to add some drivers to your WinPE5.0.
First, you'll need to extract the driver so that its CAT, SYS and INF files are accessible, i.e. not in ZIP file.
 
To add a (single) driver, type for example:

dism /image:C:\MOUNT /add-driver /driver:"C:\PathToDriver\drivername.inf"

     Preferably, if you have a folder containing several drivers (each in its own folder), you can add them all in one go by typing:

dism /image:C:\MOUNT /add-driver /driver:[PATH TO DRIVERS FOLDER] /Recurse /ForceUnsigned

      This will take a while depending on the quantity and size of the drivers.

 
14. At this point, prior to committing your changes and unmounting the WIM file, you can copy certain portable standalone applications (such as Process Explorer, Ghost64, etc) into C:\MOUNT so that they will reside inside the WIM file.
However, I discourage you from doing so, as there's a better way, so bare with me.
 
15. Go into C:\MOUNT\Windows\System32 and open the file StartNet.cmd with Notepad (right-click on it and select "Edit").
 
16. By default, it only contains a single line (wpeinit). Replace its contents with the following, then save the file:

wpeinit
@echo off
for %%p in (a b c d e f g h i j k l m n o p q r s t u v w x y z) do if exist %%p:Qdir set w=%%p
call %w%:Qdir\Q-dir.exe

      The code below is based on Microsoft's own documentation; it does pretty much the same as above.
      I've tried it, and it works just as well, so use one or the other:

wpeinit
@echo off
@color 1F
:: sets bg color to blue, and text to white

wpeutil.exe WaitForRemovableStorage
wpeutil.exe UpdateBootInfo

set PEBootRamdiskSourceDrive=
for /f "tokens=1-3 delims== " %%a in ('reg.exe query "HKLM\SYSTEM\CurrentControlSet\Control" /v "PEBootRamdiskSourceDrive" 2^>nul') do (
if %%a.==PEBootRamdiskSourceDrive. @set PEBootRamdiskSourceDrive=%%~dc
)
if Defined PEBootRamdiskSourceDrive (
echo PEBootRamdiskSourceDrive is %PEBootRamdiskSourceDrive%
)

@call %PEBootRamdiskSourceDrive%\QDir\Q-Dir.exe

17. ATTENTION: We’re now going to commit our changes and unmount the WIM file. Close ALL file explorers, or the unmount process will give you an error!!
      Then type the following command:

DISM /Unmount-Wim /MountDir:C:\MOUNT /Commit

When this process is finished, the C:\MOUNT folder will be empty.

 

18. It is advised to optimize the WIM file, so run the command:

DISM.exe /export-image /sourceimagefile:C:\Temp\PE5\Media\Sources\boot.wim /sourceindex:1 /destinationimagefile:C:\Temp\PE5\Media\Sources\boot_optimized.wim

   The optimized file should be a little smaller. It is safe to delete the boot.wim file, and then rename the boot_optimized.wim to boot.wim.

 
19. Now copy the contents of the folder C:\Temp\PE5\Media to your flash drive (To clarify: Copy what's inside the folder, not including the folder itself).
      The WinPE5.0 flash drive is now bootable.  :clap: 

20. Grab Q-Dir portable x64 from here, and extract the files to your bootable flash drive. Make sure the folder is named "QDir" and resides on the root of the drive.
 
21. Eject the flash drive, and boot from it by selecting it from the BIOS Boot Menu.

      The exact key  to get to the Boot menu depends on which motherboard you have.

      On Dell computers it's usually F12. On Gigabyte motherboards it's also F12.

      Other manufacturers use a different key to get to the boot menu. Please check yours.

      Once you are in the boot menu, you'll probably see something like this (I'm using a Gigabyte motherboard, and SanDisk flash drive):

 

Boot_Menu.jpg

 

      You can choose to boot in legacy mode, or in UEFI mode. Both should work just fine.

 

22. Once it's done loading, QDir should appear and you can pretty much do anything from here on.


Win_PE5.png

USB Stick Fat32 Empty on 1 XP, Ok on another

$
0
0

As in title.

 

What does it?

Good thing is, I haven't lost the files.

Bad thing is... Crap!

 

16 GB Sandisk Cruiser. Most files in root folder.

 

Thanks,

 

r.

anticpation window setting doesn't appear to work

$
0
0

HI,

 

I'm using version 4.00 and changing the # of bytes in the anticipation window appears to have no affect on the transmitted data rate.  I have the block size set to 1024 bytes.  When I view the traffic, I never see consecutive transmitted blocks, only a transmitted block followed by an acknowledge.  How do I reduce the wait time and increase the bandwidth?

willing to pay for help with winbuilder

$
0
0

Hello Group,

 

I an having such hard time making a bootdisk that has all the programs I want, I am using  Win7PE.

I tried many diffrent ways of making it but with no luck

 

So I am willing to pay somone to do a teamviewer along with a phone call so we can talk wile teamviewer is up

 

I thingk I need about 20 to 30 minutes of someones time just to get me started..

 

So give me a price and a payment method for say 30 minutes.

 

I am in New York

 

Tonyrizman@hotmail.com

 

Thanks

 

Tony

 

What I have done: I have created a boot disk that boots but I cant get the programs I want to work. 

I don't fully understand where to put the scripts and if the program is needed to be put somware.

I made one with recuver that works but I need other programs as well

a Hoverboard. Anyone!

$
0
0

Hendo Hoverboard:

 

So where does the HENDO hoverboard stand today? Well, about 1 inch off the ground. As you can see from the video above, the prototype is real and it works! But to see it hover in person, and better yet, to defy gravity by riding it, is something you need to experience as well.
Riding the Hendo hoverboard

Flying car to debut this month - Production-ready Aeromobil

Booting Windows 7 on software raid

$
0
0

Hi.

Hopefully I'm posting in the right forum now ;)

 

I'm trying to boot Windows 7 on a striped Windows software raid. All my googling so far has only told me it can not be done, but after seeing some of the cool stuff that has been done here (WinRAM and so) I think that maybe someone can give some input :D.

 

So, I have an Intel 910 Series SSD (basically 4 SSD'n on a PCI-E card) it is not visible from BIOS/UEFI and it has no hardware RAID (at least not enabled). So I want to run a striped RAID on it and install windows on top of it...

 

I totally accept that the boot partition and such needs to be on another drive and that's fine.

 

If this would have been Linux then the kernel and initrd would be on the boot disk and then it would load start the RAID and then continue booting, shouldn't that be possible with Windows as well?

 

Thank's guys and hope I was some clear ;)


40,000 HD Movies On A Single DVD

Need help for rename a file in syslinux

$
0
0

Hi,

I create an USB bootable with syslinux 4.06. (USB format NTFS).

I create 2 syslinux.cfg file. Their name are: syslinux.cfg and syslinux_custom.cfg

I add a menu in syslinux.cfg which allow choose default configure file. My screano is: when we choose this menu, we will boot to DOS then in DOS mode, my batch file will find syslinux.cfg on USB then rename it to syslinux_org.cfg and rename syslinux_custom.cfg to syslinux.cfg.

But I get some error when do it.

In AUTOEXEC.cmd, I add this line

for %%x in (A C D E F G H I J K L M N O P Q R S T U V W X Y Z) do if exist %%x:\syslinux.cfg set USB=%%x:

then from it my batch will rename syslinux.cfg file from %USB% drive. But it now work.

Can someone help me?

Thanks :)

P/s: I'm so sorry for my poor English.

Negative offset in a proxy request?

$
0
0

Is there a possibility that the driver sends a request to a proxy with a negative offset?

After a quick look in the source, I found no test about that. As I prefer to leave this kind of check to the proxy, it's not a problem for me, but I would like to be sure. So, Olof, if you can confirm... :)

LockVolume

$
0
0
This is a specilaized application that will lock and unlock a volume for you. Since Vista, new security mechanisms was added to Windows that prevented raw disk access as was before nt6.x; http://msdn.microsof...y/ff551353.aspx . I posted an ugly workaround for it about 2 years ago; http://communities.v.../docs/DOC-10455

Later user TheK made the first good solution using the win api in his LockDismount tool; http://reboot.pro/12413/

LockVolume is more or less the same as his, except it is written AutoIt and source is attached. However, some differences are present;

1. My tool is per volume, whereas his is per disk.
2. Mine can optionally dismount if necessary, whereas his will dismount (not 100 % sure though)

Anyways, the only purpose was to provide some source for AutoIt coders to reuse. If there's bugs, the source is provided for you to fix.. :whistling: There will likely never be an updated version as this was just a side-effect of something else I'm doing.

Posted Image

Some explanation of the GUI:
Usually clicking on just "Lock It" and "Unlock It" should be enough. But sometimes you may want to dismount the volume as well. If so, then click on "Safe Dismount", after volume is locked. But if something is preventing the volume from being locked, then you must force dismount it by clicking on "Force Dismount" (no need to lock it afterwords then). Remounting the volume after a forcefully dismount, is done by clicking on "Force Remount". The activated buttons should be activated when it makes sense to use them, and if not show an error message. Either way, if anything goes wrong, just close the application, and all locks will be unocked. Just beware that a forced dismount may cause issues if something serious was going on on the file system for that volume.

Download; http://www.mediafire.../LockVolume.zip

How to load Kaspersky (kav_rescue_10.iso) from Syslinux Menu?

$
0
0

I follow this base guide to make Syslinux bootable ISO:

http://www.syslinux.org/wiki/index.php/ISOLINUX

 

My isolinux.cfg

UI vesamenu.c32
PROMPT 0
TIMEOUT 300
MENU TITLE Kaspersky Rescue Disc
MENU BACKGROUND krd_eula.jpg
MENU TABMSG  http://www.kaspersky.com
MENU WIDTH 72
MENU MARGIN 10
MENU VSHIFT 3
MENU HSHIFT 6
MENU ROWS 15
MENU TABMSGROW 20
MENU TIMEOUTROW 22
menu color title 1;36;44 #66A0FF #00000000 none
menu color hotsel 30;47 #C00000 #DDDDDDDD
menu color sel 30;47 #000000 #FFFFFFFF
menu color border 30;44	#D00000 #00000000 std
menu color scrollbar 30;44 #DDDDDDDD #00000000 none

label Memtest
  kernel /kernel/memdisk
  append iso raw initrd=/images/memtest.iso

label Kaspersky Rescue Disc
  kernel /kernel/memdisk
  append iso raw initrd=/images/kav_rescue_10.iso

And I add more this files:

 

vesamenu.c32
libutil.c32
libcom32.c32

 

Here the result:

8MaZZT1.png

 

I'm making one menu with many tools, this image is only begining, the problem is when I got load 'kav_rescue_10.iso' from this menu, the iso doesn't load, but the other iso 'memtest.iso' load normally...

 

What the problem? I can load kaspersky from iso on this menu?

Have any parameter should I use so that it can load?

 

sorry for my bad english :)

VHD Proxy for ImDisk

$
0
0

Hi,

 

Another proxy for ImDisk, this time to support VHD files (fixed, dynamic, differencing).

ImDisk already had support for fixed type, but not for dynamic or differencing (unless one used DiscUtils).

This is based on libvhdi Joachim Metz work.

 

Find here attached the proxy.dll (and the source code) for ImDisk (and other software using sharedmemory proxy such as ImgMount / Arsenal driver).

 

To launch the proxy : devio --dll=proxy.dll;dllopen shm:test_proxy c:\test.vhd.

To use the proxy from ImDisk : imdisk -a -t proxy -o shm -o ro -f test_proxy -m Z: .

 

Note the RO flag as the libvhdi does not support writing for now.

 

 

Regards,

Erwan

Attached Files

NT 6.x fast installer: install win7 directly to usb external drive

$
0
0
I reopen the removed post request by the admin

As you know, stupid setup.exe for nt 6.x (vista/win7/2008/2008 r2) has many limitations:

1. You can't start install vista/win7 under xp based pe (winpe 1.x) and can't install win7 under win2000
2. You can't install win7 directly to USB hard disk
3. The stupid setup.exe may put the boot files to a wrong drive when you boot winpe with USB device and there is even no way to choose the boot partition Posted Image
4. When you install win7 from winpe, the drive letter of the OS partition will always be C:, no matter which partition you choose.

On the other hand, the fastest way to install nt 6.x is imagex+bcdboot, e.g

imagex f:\sources\install.wim 5 c:

bcdboot c:\windows /s c:

bootsect /nt60 c:

And no setup.exe is needed.

Based on this, I wrote an "nt 6.x fast installer" which has the following advatages compare to the original M$ setup.exe:
1. You can install nt 6.x directly from iso file mounted by any kind of virtual drive.
And you needn't extract or burn the iso.
2. You can directly install nt 6.x from any version winpe and win2000 above windows
3. You can install the OS directly onto a USB external hard drive.
And no virtual machine, copy tool or complicated "tutorial" is needed.
4. You can manually choose which partition is the boot partition.
5. You can decide which letter the OS partition will occupy in Win7/2008 R2.
6. The install speed is very fast. With this installer, you can install win7 in 11-12 min for 5400rpm notebook hdd, and in less than 10min for desktop 7200 hdd (vista needs about 2 min more because of the score evaluation)

Attached Thumbnails

  • 1.png
  • 2.png
  • 3.png

PartitionGuru 4.01 Create Partitions by specify starting sector

$
0
0

http://www.eassos.com/partitionguru-free.php

PartitionGuru401 is the best partition manager I have found. I have tried Acronis Disk Director, EaseUs, GParted, Paragon. No other partition manager lets you so easily and specifically tell it the exact "starting sector" and "ending sector" when creating your partition - so you can design your hard drive with exactly your own perfect preferred partition alignment. Plus it is only 2 MB whereas the other competing solutions are often 100MB+.

 

http://sites.google.com/site/webuploads7373/PartitionGuru401FreeDOS.img

2.88MB Download - Here I have used the application's feature to create a bootable USB stick and then I have copied the payload into a blank 2.88 IMG file provided by steve6375. This will save you from having to install the application if you only want to try it in Boot Mode.

 

For menu.lst

title PartitionGuru401FreeDOS.img
map /PartitionGuru401FreeDOS.img (fd0)
map --hook
root (fd0)
chainloader /kernel.sys

 

When creating a Partition - it allows you to enter directly StartingSector and EndingSector which very few other utilities do without confusing interfaces. I always create my partitions with StartingSector divisible by 4096. You should also have (EndingSector + 1) be divisible by 4096. This results in TotalSectors being divisible by 4096 since TotalSectors = (Lastsector + 1 - Firstsector).

Installing Windows 7 on USB hard disk wont let me

$
0
0

when I try to load win7 on external hd using aik and win installer I get windows 7\WAIK files\imagex.exe is not a valid win32 application , I am running win xp pro sp3

Rufus v1.3.0 has been released

$
0
0
(Starting a new topic with this new release, since the old one has gotten pretty long)
 
It is my great pleasure to announce the release of Rufus v1.3.0.
 
What this new release brings is as follows:
  • FAT32 format support for >32GB drives, based on fat32format, from Ridgecrop Consultants Ltd:
  • Automated update check
  • Relax ISO9660 compliance for Arch Linux images
  • Add support for VMWare ESXi 5.1 ISO images
  • Update Syslinux to v4.0.6 and libcdio to v0.90
  • Miscellaneous UI improvements and fixes
The feature that actually required the most development time was the check for updates, which I foolishly thought would be a matter of a couple of days to implement, but I hope it'll be worth it. I also hope that, time permitting, you won't have to wait another 6 months to get the benefits of having automated check for updates in Rufus... ;)
 
On that subject, since someone expressed doubts about prompting every new user about the update checks, be aware that you can avoid the prompt altogether, and get the default check for update options, if you either download the version called rufus.exe or rename your download to rufus.exe.
Personally, I believe that any feature that sends data to a remote server, no matter how minimal, should be opt-in, rather than opt-out, which is why I'll continue linking to a prompting rufus_v1.3.0.exe, rather than the promptless rufus.exe (which is what I did for the downloads section) but of course you're free to spread rufus using whichever option you prefer.
 
Also note that since github abruptly decided to remove their file upload feature, I am now hosting all downloads on http://rufus.akeo.ie/downloads (and yeah, there are ads here too, which I don't like either, but it helps funding my new code signing cert).
 
Finally, along with the automated check for updates, that creates some keys in the registry (under HKCU/Software/Akeo Consulting), I also added a new Alt-R "cheatmode", that will delete all the registry keys created by Rufus, in case you want to reset the check for updates settings. I'll try to create a wiki page with Rufus tips and tricks, where I list all theses cheatmodes, when I get a chance.
 
As usual, feel free to comment or report issues either in this thread, or using the github issues page.
 
PS: Most likely, the feature I'll be adding next will be NTFS support for Syslinux, and I'll also try to investigate the large FAT32/4K sector situation. I may also add a feature to try to detect DOS based ISOs, to copy their content to a FreeDOS formatted USB, but as usual, the time I am able to spare for Rufus will be the determining factor of what features make it into a upcoming version, especially as there are plenty to choose from...

Linux - Load your root partition to RAM and boot it

$
0
0
This tutorial will guide you through the steps to modify your initramfs to load all files from / to a tmpfs. This will only work with Debian 5 or newer and Ubuntu 9 ? or any unix thats supports booting from a initramfs. Since this is a virtual filesystem in RAM, not a virtual harddisk, this has many advantages.

What you need:
* lots of RAM
* Debian based distribution or any that supports booting from initramfs
* mkinitramfs or a tool to build a new initramfs
* some linux knowledge
* no need to create an image
* no need for Grub4Dos
* no need for a "special driver"

Step 1:
Choose a distribution thats supports booting from initramfs. (like ubuntu)

Step 2:
Install to harddisk. Make sure you split it into multiple partitions (/, /boot, /home, swap, ...).

Step 3:
Boot your new system, install updates, drivers if neccessary (this will improve performance), strip it down to the minimum. Every file will be loaded to RAM ! A fresh install uses about 2 GB auf harddisk-space.

Step 4:
modify /etc/fstab :
* make a backup
cp /etc/fstab /etc/fstab.bak
* find the line specifing the root partition and change it in:
none / tmpfs defaults 0 0
* save

Step 5:
edit the local script in your initramfs:
cd /usr/share/initramfs-tools/scripts/
* make a backup of /usr/share/initramfs-tools/scripts/local
cp local local.bak
* modify local, find this line:
# FIXME This has no error checking

# Mount root

mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} ${rootmnt}
* change it to:
# FIXME This has no error checking

# Mount root

#mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} ${rootmnt}

mkdir /ramboottmp

mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} /ramboottmp

mount -t tmpfs -o size=100% none ${rootmnt}

cd ${rootmnt}

cp -rfa /ramboottmp/* ${rootmnt}

umount /ramboottmp

* save
* execute, or rebuild initramfs
mkinitramfs -o /boot/initrd.img-ramboot
* replace modified local with original file
cp -f local.bak local
Step 6:
* modify this file (needs a better solution)
/boot/grub/grub.cfg
* copy the first boot entry and replace the /initrd line with this:
/initrd /initrd.img-ramdisk
* label the new entrie as RAMBOOT
This will boot our generated initramfs instead the original one.
Step 7:
* reboot
* choose standart boot (no ramdisk)
* choose RAMBOOT and all your files on the root partition will be loaded to a tmpfs

Results:
Test setup:
*Kernel : Linux 2.6.38-8-generic (i686)
*Compiled : #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011
*Distribution : Ubuntu 11.04
*no graphics driver
*Desktop HP 8100E
*Core i7 860
*4GB Memory 2 Modules (DDR3)
*WDVeliciraptor 10k rpm 160GB

Tiotest results for 4 concurrent io threads:

,----------------------------------------------------------------------.

| Item                  | Time     | Rate         | Usr CPU  | Sys CPU |

+-----------------------+----------+--------------+----------+---------+

| Write         800 MBs | 0.1489 s | 5372.806 MB/s |  2.80 %  | 32.40 % |

| Random Write   16 MBs | 0.0025 s | 6320.793 MB/s |   0.0 %  |   0.0 % |

| Read          800 MBs | 0.0928 s | 8616.790 MB/s |  11.7 %  |  11.7 % |

| Random Read    16 MBs | 0.0021 s | 7454.676 MB/s |   0.0 %  |   0.0 % |

`----------------------------------------------------------------------'

Tiotest latency results:

,-------------------------------------------------------------------------.

| Item         | Average latency | Maximum latency | % >2 sec | % >10 sec |

+--------------+-----------------+-----------------+----------+-----------+

| Write        |        0.003 ms |        0.048 ms |  0.00000 |   0.00000 |

| Random Write |        0.002 ms |        0.011 ms |  0.00000 |   0.00000 |

| Read         |        0.002 ms |        0.025 ms |  0.00000 |   0.00000 |

| Random Read  |        0.002 ms |        0.023 ms |  0.00000 |   0.00000 |

|--------------+-----------------+-----------------+----------+-----------|

| Total        |        0.002 ms |        0.048 ms |  0.00000 |   0.00000 |

`--------------+-----------------+-----------------+----------+-----------'

I hope this helps a bit :)
siro

PXE chain SCCM 2012 R2 WDS

$
0
0

Followed this:

http://sysmagazine.com/posts/175669/

but with a difference, that I am still using my existing PXE menu from a different PXE server, but just added to existing default this entry:

label sccm
menu label Boot to SCCM 2012 R2
COM32 pxechn.c32
APPEND 10.0.0.86::smsboot\x86\wdsnbp.com -W

which starts booting from SCCS PXE, but crashes as it can not find its BCD store:

\\ssccm-server\REMINST\SMSTemp\2014.10.30.11.15.17.01.{10CEDB89-9093-44D6-BF1B-0FA357C08F58}.boot.bcd

I hate how SCCM is not configurable in any way, but have to live with it.

So does anybody know how to make it work?

I do not want to use SCCS PXE as default, as it means that my iso images are transferred by TFTP (currently I boot ipxe undionly.0 which does the transfer by http - which is way faster!)

sebus

Viewing all 6812 articles
Browse latest View live




Latest Images