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

Kick starter - Dart is a charger about a quarter of the size of other laptop chargers.


Making room for G4D MBR in a GPT setup?

0
0

I'm currently trying to use a hybrid MBR setup and GRUB4DOS in a computer whose BIOS isn't GPT aware. The problem is that GPT want to put its first partition table in LBA 1, whereas G4D's MBR stage is 8 kiB big. So far I've tried converting a MBR type partition table to a hybrid partition table setup using gdisk. This produces a missing MBR helper upon boot, as expected since LBA 1+ is overwritten by the GPT partition table. Likewise, running bootlace on the drive complains about too few sectors being free.

 

Is there any way to coerce gdisk (or a different tool) into moving the GPT partition table forward, alternatively moving the G4D bootstrap somehow. The solution should in the end work reliably (ie partition table or bootstrap not destructively overwritten in normal use, and OS is able to detect the partitions) under OSX (Hackintosh), Windows 7 32-bit and Linux (Debian).

 

The general task of booting these operating systems (beyond initially getting into G4D) is not a problem and not part of the question.

Action Movie Kid - cool video effects

0
0

This was the first time seeing the video. I was thinking it was real untill you see the end.

 

I went "Holy cr@p". Yeah it got me.

Going to School

 

Action Movie Kid

 

 

 

 

Spring Break Sluts 2 - had laughing

0
0

i like it when he goes. Are we good. then starts the skit.

Hilarious reactions.

 

Drive Manager for Win8PE, LiveXP and Win7PE (Winbuilder 82)

Wimfltr service running

0
0

searched, found nothing related to win8pe se, so I shall ask.

 

In reference to the help files, I am sorry, but they don't really help with the issue.

 

Trying to build and getting to Build - 0 - preconfig when it errors with:

 

Winfltr Service running   (where?? locally??  i don't see this service) 

 

Wimgapi.dll v6.2 not compatible with Wimfltr Running

to fix read "waik Troubles" 

 

Exiting....

 

I have read Waik Troubles and I am still lost....

 

 

it refers to imagex 6.0.6001

I have 6.2.9200 in my project\tools\win8pese folders

 

also Waik troubles appears to be written for wi7pe se though i assume the process is the same. 

 

Also, it has been a while since I have built a win8 and have since upgrade to server 2012, do I need a newer copy of winbuilder?  

 

looks like i have v.49

 

I can build win7pe se's just fine. 

Book Review: Windows Forensic Analysis Toolkit, 4th Edition

0
0

wfa.jpg?w=150&h=150I’ve been waiting until I received the hard copy of this book to write the review. I had the fortune of being the tech editor for this book and enjoyed every minute of it. Although I do not have an ongoing financial interest in this book, I do have a vested personal interest based on the reasons Harlan Carvey lays out in many chapters. I’ll get to my personal interest later in this review.  Also, Harlan has a post on updated book contents here: http://regripper.wordpress.com/2014/04/14/regripper-download-2/

Without reading any reviews, those analysts who buy Harlan’s books will keep buying his books with the full expectation of having a well-written (as in easy-to-read) book on Windows OS forensics. There is no need to read any further in this review if you fit in this category. This is Harlan’s new book. That is all you really need to know. But if you just want my opinion, read on…

The topics in the 4th Edition of WFA are all eye-catching. Volume shadow copies, file analysis, registry, malware, timelines, tracking user activity, and more.   Every topic detailed in all the chapters, is relevant to everyone that touches a Windows system to examine. The difference between Harlan’s books and others is the guidance given. For example, rather than reading a discourse on some technology, Harlan gives practical advice, suggestions, and real-life stories that relate to the points in the book. Since we have all made mistake (or will make mistakes, or have made mistakes but just don’t know it yet), having guidance that reduces mistakes in the way of stories and plain talk is well worthwhile to read.

The book has too much information to be covered in a review. There is more information on accessing volume shadow copies using several different methods than I want to review. The same can be said for file analysis, registry analysis, timelines, and every other topic. Harlan gives several options to accomplish the same task, using different software.   Although I wrote a book on one software (X-Ways Practitioners Guide), I obviously use more than just one software. Any forensic book, other than a manual or software guide, that does not give options with various types of software does not give the reader options to solve problems.

Another facet of Harlan’s book is his never-ending harping of asking everyone to ‘share information’. That sentence may sound negative, but truthfully, I don’t know how Harlan has the energy to push the sharing of information for so long. The book is sprinkled with this tone and I echo the importance of sharing information. I did my best to keep up with Harlan’s book as I tech edited it, working his suggestions. Some of the methods he wrote were new to me, which I would not have found on my own without happening upon the method in a blog..maybe.

Those examiners who conduct investigations, not just an analysis of a machine, will enjoy the guidance on tracking user activity, writing reports, drawing conclusions, correlating data, and making inferences.  Those topics are my personal favorites.

Harlan writes in this book that sharing helps us to know what is possible. That makes sense, because how can you know what you don’t know.

I can say unequivocally that writing a digital forensics book is primarily, if not solely, to share information. Few (no one?) gets rich writing a computer technical book in the niche of digital forensics. The market for a digital forensic book is probably a fraction of a fraction of a fraction when compared to a Tom Clancy or JK Rowling book. With that, consider that when Harlan says he writes to share, he really means that he writes to share, just like all other forensic book writers.

The personal risk to sharing, which everyone knows, is that you could be totally wrong, slightly inaccurate, poorly written, disproved later, or maybe you “discovered” something that everyone else already knew. This risk of sharing keeps the majority of examiners quiet and makes it seem that there are only a few examiners that share information. That is why we see the same names popping up online and conferences through the years. But in the audiences listening to these same names, there are smarter people, better examiners, and great investigators. They just don’t speak up or share information.  (nudge..nudge…feel free to share…no one will bite you).

That is one of Harlan’s premises to keep going and he reiterates it in the book and his blog and when he speaks. We all get ‘smarter’ when we share. None of us move forward when we don’t share.   To share is to take a risk of being wrong and embarrassed. Worse still is the fear to be wrong and get attacked online. However, for all those that share, either by asking questions, giving suggestions, or describing methods you have created or use, my hat goes off to you. It takes guts to put yourself out there, knowing that the sharks are circling and sniffing for blood.

Back to my personal interest in this book. When I have found a method or tool that I like, I want everyone to use it. I don’t hold it close to my chest or hide it. I share it. I become an evangelist to that tool or method to get the word out. The reason? The more examiners in the field that use it, the more chance the method/tool becomes an industry standard. Then it gets improved upon, further developed, “court accepted” in that the results obtained by that tool/method are accepted into a court, and I get to use the tool/method more.

The best personal example I can give to prove this point is with WinFE (https://winfe.wordpress.com). From a two-page Word document typed by Troy Larson of Microsoft, I marketed that little ingenious tool as if I was making a million bucks off it. It’s now in use by every country that does forensics and in just about every agency or company in those countries. It’s even taught in forensic training programs in both the public and private sector. So now, anyone can create and use WinFE without worry of using a non-industry accepted tool. This happened only because those that used WinFE, shared the knowledge of how to use and when to use it. Imagine if we did that with every “new” effective method or tool.

The key point in the prior two paragraphs is that Harlan’s book has lots of those types of ideas that he has shared. He gives credit to ideas created by others along with sharing his own ideas.

My only negative words on WFA/4 is…maybe X-Ways Forensics could have been put in it…but that’s what we have the XWF Guide for..

My suggestion on WFA/4…buy the book. You will not regret it.  My other favorite books are here https://winfe.wordpress.com/books/.

 

 


1153 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

Book Review: Windows Forensic Analysis Toolkit, 4th Edition

0
0

wfa.jpg?w=150&h=150I’ve been waiting until I received the hard copy of this book to write the review. I had the fortune of being the tech editor for this book and enjoyed every minute of it. Although I do not have an ongoing financial interest in this book, I do have a vested personal interest based on the reasons Harlan Carvey lays out in many chapters. I’ll get to my personal interest later in this review.  Also, Harlan has a post on updated book contents here: http://regripper.wordpress.com/2014/04/14/regripper-download-2/

Without reading any reviews, those analysts who buy Harlan’s books will keep buying his books with the full expectation of having a well-written (as in easy-to-read) book on Windows OS forensics. There is no need to read any further in this review if you fit in this category. This is Harlan’s new book. That is all you really need to know. But if you just want my opinion, read on…

The topics in the 4th Edition of WFA are all eye-catching. Volume shadow copies, file analysis, registry, malware, timelines, tracking user activity, and more.   Every topic detailed in all the chapters, is relevant to everyone that touches a Windows system to examine. The difference between Harlan’s books and others is the guidance given. For example, rather than reading a discourse on some technology, Harlan gives practical advice, suggestions, and real-life stories that relate to the points in the book. Since we have all made mistake (or will make mistakes, or have made mistakes but just don’t know it yet), having guidance that reduces mistakes in the way of stories and plain talk is well worthwhile to read.

The book has too much information to be covered in a review. There is more information on accessing volume shadow copies using several different methods than I want to review. The same can be said for file analysis, registry analysis, timelines, and every other topic. Harlan gives several options to accomplish the same task, using different software.   Although I wrote a book on one software (X-Ways Practitioners Guide), I obviously use more than just one software. Any forensic book, other than a manual or software guide, that does not give options with various types of software does not give the reader options to solve problems.

Another facet of Harlan’s book is his never-ending harping of asking everyone to ‘share information’. That sentence may sound negative, but truthfully, I don’t know how Harlan has the energy to push the sharing of information for so long. The book is sprinkled with this tone and I echo the importance of sharing information. I did my best to keep up with Harlan’s book as I tech edited it, working his suggestions. Some of the methods he wrote were new to me, which I would not have found on my own without happening upon the method in a blog..maybe.

Those examiners who conduct investigations, not just an analysis of a machine, will enjoy the guidance on tracking user activity, writing reports, drawing conclusions, correlating data, and making inferences.  Those topics are my personal favorites.

Harlan writes in this book that sharing helps us to know what is possible. That makes sense, because how can you know what you don’t know.

I can say unequivocally that writing a digital forensics book is primarily, if not solely, to share information. Few (no one?) gets rich writing a computer technical book in the niche of digital forensics. The market for a digital forensic book is probably a fraction of a fraction of a fraction when compared to a Tom Clancy or JK Rowling book. With that, consider that when Harlan says he writes to share, he really means that he writes to share, just like all other forensic book writers.

The personal risk to sharing, which everyone knows, is that you could be totally wrong, slightly inaccurate, poorly written, disproved later, or maybe you “discovered” something that everyone else already knew. This risk of sharing keeps the majority of examiners quiet and makes it seem that there are only a few examiners that share information. That is why we see the same names popping up online and conferences through the years. But in the audiences listening to these same names, there are smarter people, better examiners, and great investigators. They just don’t speak up or share information.  (nudge..nudge…feel free to share…no one will bite you).

That is one of Harlan’s premises to keep going and he reiterates it in the book and his blog and when he speaks. We all get ‘smarter’ when we share. None of us move forward when we don’t share.   To share is to take a risk of being wrong and embarrassed. Worse still is the fear to be wrong and get attacked online. However, for all those that share, either by asking questions, giving suggestions, or describing methods you have created or use, my hat goes off to you. It takes guts to put yourself out there, knowing that the sharks are circling and sniffing for blood.

Back to my personal interest in this book. When I have found a method or tool that I like, I want everyone to use it. I don’t hold it close to my chest or hide it. I share it. I become an evangelist to that tool or method to get the word out. The reason? The more examiners in the field that use it, the more chance the method/tool becomes an industry standard. Then it gets improved upon, further developed, “court accepted” in that the results obtained by that tool/method are accepted into a court, and I get to use the tool/method more.

The best personal example I can give to prove this point is with WinFE (http://winfe.wordpress.com). From a two-page Word document typed by Troy Larson of Microsoft, I marketed that little ingenious tool as if I was making a million bucks off it. It’s now in use by every country that does forensics and in just about every agency or company in those countries. It’s even taught in forensic training programs in both the public and private sector. So now, anyone can create and use WinFE without worry of using a non-industry accepted tool. This happened only because those that used WinFE, shared the knowledge of how to use and when to use it. Imagine if we did that with every “new” effective method or tool.

The key point in the prior two paragraphs is that Harlan’s book has lots of those types of ideas that he has shared. He gives credit to ideas created by others along with sharing his own ideas.

My only negative words on WFA/4 is…maybe X-Ways Forensics could have been put in it…but that’s what we have the XWF Guide for..

My suggestion on WFA/4…buy the book. You will not regret it.  My other favorite books are here http://winfe.wordpress.com/books/.

 

 


1153 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

WinFE Success Story

0
0

I get a few stories of how WinFE saved the day and a few of these heroes let me retell their story. This is one of them. The ‘detective’ wishes to be unnamed, but for sake of argument, I know who he is…

————————————————————————————————————————

 A detective from a California law enforcement agency that had attended the SEARCH “Network Investigation and Digital Triage” course contacted the instructors with assistance in building a WinFE based on Windows 8.1. The detective was given guidance and links to the various resources needed to create the WinFE8.1SE. The detective was further given assistance in adding in the utilities he would need and finally validating the build to insure that it was forensically sound.

 In a follow up call, the detective indicated that the he had obtained the duplicate images he needed, with one minor modification. He found that one of the target drives was mounted through an add-in card and was not initially recognized by WinFE8.1SE. Noting that Colin Ramsden’s write protect utility allowed for adding drivers to the system, the detective located the add-in card drivers and added them to the system. WinFE8.1SE and Colin’s WP utility then recognized the additional drive and allowed mounting it read only. The detective then successfully obtained duplicate images of both target drives.

————————————————————————————————————————

winfe-success.jpg?w=578

As a side note, consider that WinFE started with Troy Larson typing out a 2-page Microsoft Word document on changing registry values in a winPe to get a winFe. That little idea is now taught at local, state, and federal agencies as well as public/private education and training courses. Basically, it’s is use by many.   This success story is neat because it shows how easy it is to add a driver on-the-fly. You don’t need much technical experience to use Colin’s app to add drivers or toggle hard drives. We beat it up pretty good to get it right; Colin is one of those extremely competent software writers and I am glad he helped out the WinFE project.

Got a success story? Send it to me and I’ll share the word.


1165 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

Please clarify "wimgapi.dll not compatible" resolution steps

0
0

I am able to build WIN7PE with no problems.

 

WIN8PE and WIN8.1PE  both fail with the same error, this tells me the problem is general to Winbuilder and not to the projects.

 

"Wimfltr service running

wingapi.dll not compatible with wimfltr running.

to fix read 'Waik Troubles'."

 

I have read this 'Waik troubles' multiple times, I have stumbled through trying to pull the required files out of the ADK install and place them in the corresponding folders. It still does not work.  I am sure It is something I am not doing right, but I can't seem to figure out what I am missing. 

 

Again, 7 works like a dream.  I would really like to use 8 or 8.1.

 

Can i get some more detailed instructions?  specific file locations?  one would think there was a Batch or a powershell script that could resolve this.........

 

Installing Windows 7/8 from .iso without unpacking

0
0

Hello!

 

Hardware

I've recently got my hands on one of those SanDisk Extreme 64GB sticks and started tinkering with it. During this story, please keep in mind that this is a model where removable bit is set to 0 (which means Windows sees all its partitions by default - each is shown as a single disk in explorer).

 

Objective

To have multiple functioning Windows installers on a single partition. This either means getting the installer to function from .iso image without unpacking (this is the way which is being pursued in this thread) or editing BCD in such a way to allow installers co-exist on a single partition (alternative way, secondary to the first one).

 

Investigation

Now originally this all started as a question [1] on SuperUser. This was also discussed on RootAccess [2] chat room. This is where the link [3] was discovered. After digging it for 4 straight hours, I was able to successfully get to the screen of Windows installer (this was all attempted on Windows 7 installer but it seems Windows 8 installer is no different - correct me if I'm wrong) where you need to select (create, delete, modify) disk partitions. 

 

Current setup

Simple Windows .iso was used as a starting point for customization. It's boot.wim (\sources\boot.wim) was modified to have ImDisk driver available for installation at the time of running setup.exe. The following commands are used to make our .iso available after switching to protected mode (during setup.exe):

rundll32.exe setupapi.dll,InstallHinfSection DefaultInstall 132 .\imdisk.inf
imdisk -a -f "%%G:\multiboot\ISOS\Win7.iso" -m #:

First line installs the ImDisk driver.

Second line makes our .iso available in form of UDF drive (essentially a CD-ROM).

This script is tested and working (since we are able to select Windows version for installation). It can either be run manually (to be sure what exactly is happening and when) or automatically by using Winpeshl.ini. The modified boot.wim is written back to the .iso file by using WinISO. After that, YUMI [6] is used to boot this iso from the second partition of SanDisk Extreme (using GRUB .iso boot).

 

Current issue

When selecting a partition for Windows installation - a message is displayed saying that 'installer was unable to create or locate the existing system partition'. Accessing the setupact.log during this time reveals that disk0 (the fully empty laptop internal hard drive) was skipped due to not being 'the computer's boot disk'. This same error is described in article [4] (last one):

[BLOCKING reason for disk 0: CanBeSystemVolume] The selected disk is not the computer's boot disk.

Already tried

1. Making the second partition on SanDisk non-bootable. SYSLINUX's altmbr.bin was used to boot second partition by number - not by boot flag. Same issue.

2. Writing Windows installer to another boot stick with unpacking - the usual easy case. When having both sticks plugged in and trying to install from disk with unpacked installer does NOT result in error (although SanDisk is obviously still detected as non-removable hard disk).

 

Questions

1. Not sure why this error is even displayed. How in the hell is it able to determine if it is the boot disk or not. Why in the hell would it even care :(.

2. How can I make it forget this nonsense?

3. Maybe there is altogether different way? Like custom installer described here [5].

 

Related Links:

Question @ SuperUser [1]

RootAccess chat room [2]

ISO install with ImDisk [3]

Article by Tom Richards [4]

Custom installer [5]

YUMI [6]

 

Note to site admins:

As of 11:56 Tuesday, April 22, 2014 (UTC) the registration without Twitter is impossible. Following error is displayed. Also, it's kinda racist to block emails based on domain :)

GFX-Bootmenu issues

0
0

I dug around and did not see any topics on this.  If there is an existing topic on this please point me there.

 

This app works pretty easily, a little cumbersome in rendering, but not hard to figure out.  However, I can't get it to pass all my settings through to the build.  Maybe I am doing something wrong.

 

I want to use menu 3, a white back ground, and our company logo in the upper left corner.  It all looks perfect in the preview, I apply the settings, and run my build.  When I test, the background is black and the logo does not show.

 

I am using a white .PNG for the background and a 256-color bitmap for the logo.  all seems pretty simple to me, but maybe there is a better way?? 

 

Thanks for the help all. 

WinFE Success Story

0
0

I get a few stories of how WinFE saved the day and a few of these heroes let me retell their story. This is one of them. The ‘detective’ wishes to be unnamed, but for sake of argument, I know who he is…

————————————————————————————————————————

 A detective from a California law enforcement agency that had attended the SEARCH “Network Investigation and Digital Triage” course contacted the instructors with assistance in building a WinFE based on Windows 8.1. The detective was given guidance and links to the various resources needed to create the WinFE8.1SE. The detective was further given assistance in adding in the utilities he would need and finally validating the build to insure that it was forensically sound.

 In a follow up call, the detective indicated that the he had obtained the duplicate images he needed, with one minor modification. He found that one of the target drives was mounted through an add-in card and was not initially recognized by WinFE8.1SE. Noting that Colin Ramsden’s write protect utility allowed for adding drivers to the system, the detective located the add-in card drivers and added them to the system. WinFE8.1SE and Colin’s WP utility then recognized the additional drive and allowed mounting it read only. The detective then successfully obtained duplicate images of both target drives.

————————————————————————————————————————

winfe-success.jpg?w=578

As a side note, consider that WinFE started with Troy Larson typing out a 2-page Microsoft Word document on changing registry values in a winPe to get a winFe. That little idea is now taught at local, state, and federal agencies as well as public/private education and training courses. Basically, it’s is use by many.   This success story is neat because it shows how easy it is to add a driver on-the-fly. You don’t need much technical experience to use Colin’s app to add drivers or toggle hard drives. We beat it up pretty good to get it right; Colin is one of those extremely competent software writers and I am glad he helped out the WinFE project.

Got a success story? Send it to me and I’ll share the word.


1165 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

USB3 issues

0
0
Hi

Have been using win7pe_se for a while now (and before that win7rescue_pe)

It is used in my work as an imaging tool, to boot from usb and deploy an image to new computers ready for them to be given to users

All this time I have had no problems at all, but the latest batch of Dell computers have come with just USB 3 ports - so when PE boots it gets halfway and then loses connection to the USB port - hangs for a while and eventually shows a desktop, but I have no access to any programs or the USB device itself


Help!! - I have a huge number of computers to roll out and not sure what I need to do to get win7pe_se working with USB 3?

Has anyone come across this problem or got a solution for it?

Many thanks

Unreal Commander for Win8PE, LiveXP and Win7PE (Winbuilder 82)


Free Course Materials – Placing the Suspect Behind the Keyboard

0
0

Do you teach cybercrime/forensics and use “Placing the Suspect Behind the Keyboard“?  Maybe you are considering using this book in your course?  How would you like to have ready-made PowerPoints for the chapters with additional student materials to go along with the book in your course?  psbk-e1395710807820.jpg?w=700

I have had a few people tell me that this book is being used in their classes, but can’t recall all of the colleges.  If you have used this book in a class, send me the instructor’s name or have the instructor contact me so I can pass along information on materials for the class.

I will be starting on the materials now and will give access to any instructors that want to lend a hand and get early drafts for use right away.  The materials will be freely available for instructors to use and modify in their coursework.  As someone that has taught forensics for a few years, it is very very helpful to have class materials available rather than reinventing the wheel every class…


1172 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

Free Course Materials – Placing the Suspect Behind the Keyboard

0
0

Do you teach cybercrime/forensics and use “Placing the Suspect Behind the Keyboard“?  Maybe you are considering using this book in your course?  How would you like to have ready-made PowerPoints for the chapters with additional student materials to go along with the book in your course?  psbk-e1395710807820.jpg?w=700

I have had a few people tell me that this book is being used in their classes, but can’t recall all of the colleges.  If you have used this book in a class, send me the instructor’s name or have the instructor contact me so I can pass along information on materials for the class.

I will be starting on the materials now and will give access to any instructors that want to lend a hand and get early drafts for use right away.  The materials will be freely available for instructors to use and modify in their coursework.  As someone that has taught forensics for a few years, it is very very helpful to have class materials available rather than reinventing the wheel every class…


1172 b.gif?host=winfe.wordpress.com&blog=1427

View the full article

Kaspersky Rescue Disk Updated

0
0

I try to boot Kaspersky updated from HD.

title Kaspersky LiveCD 10
map (hd0,0)/Iso/Kaspersky/rescue/rescueusb.iso (hd32) || map --mem (hd0,0)/Iso/Kaspersky/rescue/rescueusb.iso (hd32)
map --hook
root (hd32)
chainloader (hd32)

but it not work, see screenshot:

20130421170436.jpg

Do it have a solution?

my win7pese boots straight into Hiren's.

0
0

On a VM it works like a dream, once on the USB, it don't.

 

i can go through the Hiren's  menu and get back to teh bootloader, but I can't figure out why on the flashdrive it jumps right Hiren's 

UEFI MULTI - Make Multi-Boot USB-Drive -

0
0

Posted Image

File Name: UEFI MULTI - Make Multi-Boot USB-Drive -
File Submitter: wimb
File Submitted: 18 Feb 2013
File Updated: 20 Feb 2014
File Category: Boot tools

*** UEFI MULTI - Make Multi-Boot USB-Drive ***

Booting with Boot Manager Menu and using Boot Image files - VHD IMG ISO and WIM


UEFI_MULTI.exe is program to make Multi-Boot USB-Drive to boot computers having BIOS or UEFI firmware

Run UEFI_MULTI and Extract to simple path
In Win 7/8 OS Set User Account Control Off and Reboot

More Info here http://reboot.pro/topic/18182-uefi-multi/?p=168077
and here http://www.911cd.net/forums//index.php?showtopic=25269
and http://reboot.pro/topic/17877-uefi-windows-8-bios-grub4dos-multiboot-usb-harddisk/

Download - http://reboot.pro/files/file/279-uefi-multi-make-multi-boot-usb-drive/

UEFI_MULTI - Make Multi-Boot USB-Drive


=
UFD_FORMAT.exe - Tool to format USB-stick for Booting with Boot Manager Menu on BIOS or UEFI computer and
Tool to make USB-Stick having two partitions - FAT32 Boot partition for WIM or ISO and NTFS System partition for VHD.
Option to Install Grub4dos in MBR BootCode, which allows BIOS computer to boot directly from USB with Grub4dos Menu.
Option to make Boot Manager and Grub4dos Menu on UFD to boot UEFI + BIOS directly from USB with Boot Manager Menu.
Windows 7/8 or 7PE is needed to make Boot Manager Menu.
More Info - http://reboot.pro/topic/19140-ufd-format/
-
Before using UEFI_MULTI.exe you might consider the next 4 Sections as preparation
0. Use UFD_FORMAT to format USB-Stick
1. Prepare USB-Harddisk to have MBR and 3 Primary partitions (always needed)
2. Install Windows 8 on USB-harddisk (option)
3. Create Windows 8 Recovery USB-stick - comparable to WinPE 4.0 (highly recommended)
4. UEFI Multiboot USB - Windows 8 and Linux Parted Magic (option)

Click here to download this file

Attached Thumbnails

  • UEFI_MULTI.png
Viewing all 6812 articles
Browse latest View live




Latest Images