How to create a bootable usb? with what tool? I find a tool called AOMEI PE builder, which bootable usb is based on Winpe, following is official turorial:
http://www.aomeitech.com/pebuilder/tutorials/make-a-bootable-usb-1004.html
easy,right?
↧
Create A Bootable USB
↧
Make a Windows 7 boot disk
Pure boot disk is good, winpe boot disk is better? I read this article
http://www.aomeitech.com/pebuilder/tutorials/windows-7-boot-disk-1004.html
What do you guys think?
↧
↧
Synchronous dismount
If I attempt to unmount a volume, and then to mount right away with imdisk.exe another volume on the same device unit, I get a translated error that says that the file already exists.
By adding a small delay, the error disappears.
So, it seems that the dismount (or at least a part of it) is asynchronous.
Is there a way to make it synchronous? What is the easiest way to check that a device is completely dismounted?
↧
Prevent Windows Setup From Creating Page/Hibernation Files?
When installing Windows, it always create both a page and hibernation file on my C drive on the SSD, both files appear there when logging into your user account for the first time. This is a problem for me, since my C is on an SSD, and Windows 7 creates a page file of around 16GB, to match the size of my RAM, and a hibernation file as well. I would like to prevent these hits to my SSD at all, even though they can be manually disabled/moved after they're created, this isn't optimal. Are there any commands/tweaks whch can prevent these files from being created at all?
Perhaps creating empty 0/1 byte page/hiber files (with Notepad) might work, then renaming them with a .sys extension? Or will Windows simply overwrite them?
Thanks!
↧
Sad news about Renosite
The good guy that attempted to do something (for free) about CD/DVD emulation has announced that the whole project is going to die 
:
http://renosite.com/forum/viewtopic.php?f=7&t=12746
Those not aware about the nice thingy/ideas may want to read something about it here:
http://reboot.pro/topic/8944-boot-any-iso-image-or-boot-all-iso-images/
http://reboot.pro/topic/8944-boot-any-iso-image-or-boot-all-iso-images/?p=112851
@creno,
if you happen to pass by, consider this post as a friendly hug 
and a farewell 
, hope to "see you " again on some new interesting project. 
Wonko
↧
↧
Rufus (introduction topic)
Hello all,
If you look in the Boot Tools section, you will see a new entry called Rufus. I am the author of this program.
Rufus, is a Windows utility that helps format and create bootable USB drives. It can do so using either DOS (embedded) or an user provided bootable ISO, such as Windows or Linux installation media.
Why would you want to use Rufus?
Rufus takes the approach compensating for a feature that should be enabled in every OS by default, which is the ability to quickly and easily create a bootable USB, either for DOS or from a bootable ISO.
With USB now being ubiquitous, we see little reason why, in 2012, the default Windows formatting dialog offers the option to create an obsolete bootable floppy, but not a more useful bootable USB.
As such we believe that, any Windows user, be them sysadmins or occasional users, should have the ability to quickly and painlessly create a bootable USB, and this is exactly what Rufus aims at providing.
- Need a DOS bootable USB to flash a BIOS or some other firmware? Launch Rufus, click the Start button, copy the ROM and flasher files and you're done.
- Have a bootable ISO that you'd like to convert to USB? Launch Rufus, select the ISO, click the Start button and that's it.
A bootable USB tool really shouldn't be more complicated than that!
Rufus Features
Now, while the above can be achieved with other tools (though we believe not as easily) this is what we think makes Rufus stand above the competition:
- Rufus is fast: It is usually quite a bit faster than the competition, especially because we use an internal ISO library (libcdio) while most other tools reuse 7z, which is actually slower than libcdio on extraction. For some speed comparison results, please see here.
- Rufus is small: Why should a bootable USB creation tool be more than 1 MB? Rufus is currently around 150 KB, and still offers ISO support.
- Rufus is simple to use: Its UI is very similar to the familiar Windows formatting dialog, and it doesn't bother the user with options that are confusing or unneeded.
- Rufus doesn't require an installer: An utility that does a simple task, that most users will only perform occasionally shouldn't require an installer. Just download, run it, and get done with it.
- Rufus keeps true to the original ISO content: Unlike other tools, Rufus does not override any of the config files that were set by the original creators - instead it just reuses them.
- Rufus is generic: A bootable USB creation tool should not have to ask its users about the type of ISO provided. This also ensures that the tool will support ISOs that have yet to be created. For a non exhaustive list of bootable ISOs Rufus is known to work with, please see here.
- Rufus can check devices for bad blocks: Up to 4 passes can be selected to find out if your media is defective. We believe that a formatting utility should always come with the ability to check for defects.
- Rufus will detect and set a non US locale (DOS): If the Windows version you use is set to a specific locale, you probably want DOS to use the same. Why should you be constrained to use DOS with an US keyboard? Rufus will detect and set the locale for you (while still providing the option to fall back to US keyboard during boot, if needed).
- Rufus can set an internationalized/extended label: If you format a disk to FAT, being constrained to 11 uppercase English characters for the label is very limiting. NTFS also has its limitations. Rufus can use the autorun/autoplay feature of Windows to display a label that contains any characters you like.
- There's a version of Rufus that comes with native FreeDOS: While slightly larger than the standard version of Rufus (~410 KB) it offers a more modern and much improved version of DOS. Check it out!
- Rufus is 100% Free Source: Rufus is released under GPLv3. If you're a developer and you really would like a new feature added, you very much can!
For additional info, you are invited to have a look at its entry in the downloads section or its official homepage.
For a more technical overview of how Rufus works, please read on.
![Posted Image]()
The utility originally started as a replacement for the venerable HPUSBFW tool and basically offers all the features HPUSBFW has, apart from the ability to provide external DOS files. The reason behind that is that we provide a version of Rufus with FreeDOS embedded, therefore use for external DOS files would be very limited. Thus, Rufus should detect and formats USB drives in pretty much the same fashion as HPUSBFW, except it uses ms-sys to create the DOS or FreeDOS boot sectors.
For ISO9660 and UDF support, Rufus relies on libcdio (which seems much faster than 7zip for extraction) and syslinux. The way isolinux config files are handled is by creating a /syslinux.cfg on the target (if needed) that references an already existing config file. So far, this method seems work very well, apart from a small issue with distros that use obsolete versions of vesamenu.c32. The application will also attempt to update the existing isolinux/syslinux config file, if a disk label is required by the kernel.
With this, the produced USB is as close as possible to the original ISO, while most recent isolinux based bootable ISOs should be supported in a generic fashion.
With regards to Windows support (Vista or later), we simply format the drive as NTFS (which, btw, is the only filesystem that can properly handle the > 4GB install.wim from the x64 version of the Windows 8 developer preview) and use ms-sys to add the NTFS record, along with the bootmgr we pick from the ISO.
Finally, if requested (and if none exists) Rufus can also add an autorun.inf and icon, to set a customized/internationalized label as well as a drive icon.
If you have comments or ideas for improvement, feel free to do so, knowing that:
- I am not planning to create a commandline version of the utility, since I'd rather see features added to it than have it reused in another application.
- I am not planning to look into multiboot. I think multiboot is way too user specific and I don't see a generic solution for it that I could find acceptable. Also, if people need a tool to create a multiboot USB for them, I don't think they should be using multiboot in the first place. This is even more true if a program like Rufus can manage to make it quick and easy to switch between ISOs instead of having to create a multiboot USB.
Right now, the next thing I'd like to support would be BartPE and XP, though this may be a bit of a challenge. I'm hoping that either the ISO's existing SETUPLDR.BIN can be used (even if it needs to be patched) or that ReactOS's freeldr can help. Basically, I'd like Rufus to support anything WinPE based.
I'm also aware about grub4dos and iPXE, though I'm not currently sure whether anything specific should be done there. It looks to me like simply installing a blank syslinux and letting users do the chainloading would be acceptable, especially as I'd like to keep the utility small.
Again, please don't hesitate to give Rufus a try and let me know what you think.
If you look in the Boot Tools section, you will see a new entry called Rufus. I am the author of this program.
Rufus, is a Windows utility that helps format and create bootable USB drives. It can do so using either DOS (embedded) or an user provided bootable ISO, such as Windows or Linux installation media.
Why would you want to use Rufus?
Rufus takes the approach compensating for a feature that should be enabled in every OS by default, which is the ability to quickly and easily create a bootable USB, either for DOS or from a bootable ISO.
With USB now being ubiquitous, we see little reason why, in 2012, the default Windows formatting dialog offers the option to create an obsolete bootable floppy, but not a more useful bootable USB.
As such we believe that, any Windows user, be them sysadmins or occasional users, should have the ability to quickly and painlessly create a bootable USB, and this is exactly what Rufus aims at providing.
- Need a DOS bootable USB to flash a BIOS or some other firmware? Launch Rufus, click the Start button, copy the ROM and flasher files and you're done.
- Have a bootable ISO that you'd like to convert to USB? Launch Rufus, select the ISO, click the Start button and that's it.
A bootable USB tool really shouldn't be more complicated than that!
Rufus Features
Now, while the above can be achieved with other tools (though we believe not as easily) this is what we think makes Rufus stand above the competition:
- Rufus is fast: It is usually quite a bit faster than the competition, especially because we use an internal ISO library (libcdio) while most other tools reuse 7z, which is actually slower than libcdio on extraction. For some speed comparison results, please see here.
- Rufus is small: Why should a bootable USB creation tool be more than 1 MB? Rufus is currently around 150 KB, and still offers ISO support.
- Rufus is simple to use: Its UI is very similar to the familiar Windows formatting dialog, and it doesn't bother the user with options that are confusing or unneeded.
- Rufus doesn't require an installer: An utility that does a simple task, that most users will only perform occasionally shouldn't require an installer. Just download, run it, and get done with it.
- Rufus keeps true to the original ISO content: Unlike other tools, Rufus does not override any of the config files that were set by the original creators - instead it just reuses them.
- Rufus is generic: A bootable USB creation tool should not have to ask its users about the type of ISO provided. This also ensures that the tool will support ISOs that have yet to be created. For a non exhaustive list of bootable ISOs Rufus is known to work with, please see here.
- Rufus can check devices for bad blocks: Up to 4 passes can be selected to find out if your media is defective. We believe that a formatting utility should always come with the ability to check for defects.
- Rufus will detect and set a non US locale (DOS): If the Windows version you use is set to a specific locale, you probably want DOS to use the same. Why should you be constrained to use DOS with an US keyboard? Rufus will detect and set the locale for you (while still providing the option to fall back to US keyboard during boot, if needed).
- Rufus can set an internationalized/extended label: If you format a disk to FAT, being constrained to 11 uppercase English characters for the label is very limiting. NTFS also has its limitations. Rufus can use the autorun/autoplay feature of Windows to display a label that contains any characters you like.
- There's a version of Rufus that comes with native FreeDOS: While slightly larger than the standard version of Rufus (~410 KB) it offers a more modern and much improved version of DOS. Check it out!
- Rufus is 100% Free Source: Rufus is released under GPLv3. If you're a developer and you really would like a new feature added, you very much can!
For additional info, you are invited to have a look at its entry in the downloads section or its official homepage.
For a more technical overview of how Rufus works, please read on.
The utility originally started as a replacement for the venerable HPUSBFW tool and basically offers all the features HPUSBFW has, apart from the ability to provide external DOS files. The reason behind that is that we provide a version of Rufus with FreeDOS embedded, therefore use for external DOS files would be very limited. Thus, Rufus should detect and formats USB drives in pretty much the same fashion as HPUSBFW, except it uses ms-sys to create the DOS or FreeDOS boot sectors.
For ISO9660 and UDF support, Rufus relies on libcdio (which seems much faster than 7zip for extraction) and syslinux. The way isolinux config files are handled is by creating a /syslinux.cfg on the target (if needed) that references an already existing config file. So far, this method seems work very well, apart from a small issue with distros that use obsolete versions of vesamenu.c32. The application will also attempt to update the existing isolinux/syslinux config file, if a disk label is required by the kernel.
With this, the produced USB is as close as possible to the original ISO, while most recent isolinux based bootable ISOs should be supported in a generic fashion.
With regards to Windows support (Vista or later), we simply format the drive as NTFS (which, btw, is the only filesystem that can properly handle the > 4GB install.wim from the x64 version of the Windows 8 developer preview) and use ms-sys to add the NTFS record, along with the bootmgr we pick from the ISO.
Finally, if requested (and if none exists) Rufus can also add an autorun.inf and icon, to set a customized/internationalized label as well as a drive icon.
If you have comments or ideas for improvement, feel free to do so, knowing that:
- I am not planning to create a commandline version of the utility, since I'd rather see features added to it than have it reused in another application.
- I am not planning to look into multiboot. I think multiboot is way too user specific and I don't see a generic solution for it that I could find acceptable. Also, if people need a tool to create a multiboot USB for them, I don't think they should be using multiboot in the first place. This is even more true if a program like Rufus can manage to make it quick and easy to switch between ISOs instead of having to create a multiboot USB.
Right now, the next thing I'd like to support would be BartPE and XP, though this may be a bit of a challenge. I'm hoping that either the ISO's existing SETUPLDR.BIN can be used (even if it needs to be patched) or that ReactOS's freeldr can help. Basically, I'd like Rufus to support anything WinPE based.
I'm also aware about grub4dos and iPXE, though I'm not currently sure whether anything specific should be done there. It looks to me like simply installing a blank syslinux and letting users do the chainloading would be acceptable, especially as I'd like to keep the utility small.
Again, please don't hesitate to give Rufus a try and let me know what you think.
↧
UEFI MULTI - Make Multi-Boot USB-Drive
File Submitter:
File Submitted: 18 Feb 2013
File Updated: 24 Oct 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/
-
Win8.1SE x64 boot.wim of size 400 MB is Universal WIM Boot Image file for booting BIOS and UEFI computers
Thanks to ChrisR for making Win8.1SE - http://www.msfn.org/board/topic/170546-win81se/
After booting from USB with x64 boot.wim you can use portable App WinNTSetup_x64.exe to mount XP/7/8 Setup ISO in ImDisk Virtual Drive.
WinNTSetup3 will prepare local harddisk for Install of XP/7/8
Thanks to JFX for making WinNTSetup3 - http://www.msfn.org/board/topic/149612-winntsetup-
-
Click here to download this file
Attached Thumbnails
↧
Has anyone used Easy2Boot on a Surface Pro 3?
I can't get it to work. It doesn't recognize that the drive is even there. It sees it inside of Windows just fine, but when I try to boot from the USB drive it jsut skips it and goes into Windows normally. Don't know if it's just me or what.
↧
All-in-one Windows installation USB?
Hey guys, I'm wondering if there's some known way to set up an all-in-one vista, 7, 8 and 8.1 usb flash drive.
The catch is, I need it to be FAT32, support UEFI, and somehow be able to use the extracted files from ISO's rather than copying over the ISO's themselves.
Why? well, because unfortunately, the MSDN Windows 8.1 with Update 64-bit iso is over 4 gigs, and can't be put onto a FAT32 drive. But as far as I know, UEFI can only boot x64 windows 8 from FAT32.
Any insights to this would be greatly appreciated. The closest I've come so far is WinSetupFromUSB(which uses ISOs) and Easy2Boot(which also uses ISOs or PTN files)
↧
↧
Indiegogo - TouchPico Projector: Turn Any Surface Into A Touch Screen
TouchPico Projector: Turn Any Surface Into A Touch Screen
you need the pen it seems to interact with projected screen
A tiny handheld projector that turns any surface into a giant 80" interactive touchscreen.
833% funded - ($458,418USD raised of $55,000 goal)
https://www.indiegogo.com/projects/touchpico-turn-any-surface-into-a-touch-screen
http://techcrunch.com/video/touchpico-android-projector/518343781/
↧
Debugging Grub4dos
I have installed grub4dos on a USB stick.
How would one go about debugging Grub4dos?
There are at least a couple of options that I am trying (have not got them to work yet):
- QEMU + gdb in a linux environment
- Virtualbox + Vboxgdb (in Windows - see http://sysprogs.com/VBoxGDB/tutorial/)
Is there another more 'standard' way to debug the code?
I looked through this forum hoping to find a tutorial or example on this but no success yet.
/Newbie
↧
Does anyone use Symantec Ghost?
Hello,
sorry for my bad English, I'm from Germany.
Does anyone use Symantec Ghost on Windows PE?
Which Version of WinPE?
Which Version of Ghost?
Why do you use Ghost?
Can you send a screenshot?
Thanks for help! 
best regards,
kuemmel
↧
winpe10 et wifi
Bonjour,
Windows10 en beta propose un adk avec winpe10 en beta ( comment appeler ce winpe ?)
J'utilise une iso de Windows10 Entreprise Insider Preview - build 10075 upgrade 10130 )
L'adk contient un winpe10 build 10075.
Ces différences de versions beta compliquent l'intégration dans winpe des drivers de MS qui ne sont pas fournis avec winpe. Il faut ajouter des fichiers build 10130 et les .cat associés. Il peut aussi y avoir des effets de bords avec des dll de versions différentes. Des points d'entrée dans les dll pourraient ne pas exister Mais le risque est faible.
L'idée est d'utiliser uniquement des scripts ( cmd ou ps1 ) mais pas de programme tout prêt : cela permet de comprendre ce que l'on fait. C'est long et parfois fastidieux mais enrichissant de le faire soi même au moins une fois.
L'outil de base : procmon ( 64 pour moi )
J'avais déjà bloqué sur le fameux menu "démarrer" de winpe4/5. Avec winpe10, c'est la même chose. J'ai lu dans le forum mfsn que l'intégration d'une carte wifi restait complexe dans winpe. J'ai donc voulu tenter l'aventure wifi avec winpe10. Et de fil en aiguille, j'ai pu constater qu'il est plus facile avec winpe10 d'obtenir un bureau confortable avec la barre de tâches. Et mettre d'épingler les programmes dans cette barre. Le ruban me donne le même résultat, une bande vide sous la barre de titre des fenêtres.
Je suis loin des méthodes de "pro" comme winbuilder mais quelques scripts sont peut être plus pédagogiques.
Ma méthode ( une parmi d'autres ) :
1 - disposer d'un Windows 10 entreprise ( actuellement build 10074/10130), de l'adk pour Windows 10 (actuellement build10075) et faire attention aux fichiers .cat des composants logiciels ajoutés.
2 - construire son winpe avec les paquets souhaités : un cmd qui monte le boot.wim, fait les ajouts des pilotes wifi( registre et fichiers ) pour le wifi principalement et démonte cette image.
3 - au démarrage de winpe, lancer un script powershell pour la personnalisation de winpe.
note : depuis que les pilotes s'installent sans erreur, je place les fichiers et les scripts sur une clé usb pour faire les modifications plus facilement sans refaire boot.wim.
Chaque carte ayant son pilote, je n'ai fait le test que sur une seule carte ( intel Centrino Wireless-n2200 )
Une image pour se rendre compte :
http://noel.blanc.free.fr/public/winpe10-wifi.bmp
Les scripts sont simples, rudimentaires et à adapter à votre besoin. Mais rien de vraiment compliqué.
Si vous êtes intéressés je peux les mettre en ligne.
Noël Blanc
↧
↧
CloneDisk
Hello Gents,
I made a small freeware app that allows one to clone a drive (physical or logical) to/from another drive or image.
On top of that the tool can :
-save/restore the MBR or BS,
-delete the layout of the drive,
-wipe with 0's,
-create a raw image file,
-make a vmdk/vhd from a raw image file to boot your cloned disk in vmware,
-do various operations on the registry around booting,
-format any device to fat16/fat32/ntfs/exfat/udf (includig usb pen),
-read faulty devices (with bad sectors for instance),
-perform speed tests,
-edit the partition table, view the boot sector ,
-create a disk, create a partition,
-extend / shrink a volume.
Tool can be downloaded here or here
There are plenty of other tools (and possibly better) that can do the same.
What I was looking for was a GUI (no command line tool), merging several functionalities at once and free.
Feedback and requests welcome 
Regards,
Erwan.
Attached Thumbnails
↧
Using Arsenal Image Mounter in C
I am trying to send commands to the AIM driver by using the instructions here.
What I want is to remove a created device which has 000000 as ID.
Unfortunately, the call to DeviceIoControl fails (GetLastError returns 1 but I don't know if it's relevant).
I also would like to know how to determine the N value in \\.\ScsiN:. I tried with 0 or 1 and it fails in both cases.
Of course, the executable has the administrative privileges.
#include <windows.h>
#include <stdio.h>
#include <ntddscsi.h>
#include "common.h"
int wmain(int argc, TCHAR *argv[])
{
HANDLE device;
SRB_IMSCSI_REMOVE_DEVICE srb;
DWORD dw;
BOOL result;
device = CreateFile(L"\\\\.\\Scsi0:", GENERIC_READ | GENERIC_WRITE, FILE_SHARE_READ | FILE_SHARE_WRITE, NULL, OPEN_EXISTING, FILE_ATTRIBUTE_NORMAL, NULL);
if (!device) {
printf("CreateFile() failed.\n");
return 0;
}
srb.SrbIoControl.HeaderLength = sizeof(SRB_IO_CONTROL);
memcpy(srb.SrbIoControl.Signature, FUNCTION_SIGNATURE, 8);
srb.SrbIoControl.Timeout = 10;
srb.SrbIoControl.ControlCode = SMP_IMSCSI_REMOVE_DEVICE;
srb.SrbIoControl.Length = sizeof(SRB_IMSCSI_REMOVE_DEVICE) - sizeof(SRB_IO_CONTROL);
srb.DeviceNumber.LongNumber = 0x000000;
result = DeviceIoControl(device, IOCTL_SCSI_MINIPORT, &srb, sizeof srb, &srb, sizeof srb, &dw, NULL);
if (!result)
printf("DeviceIoControl() failed (error=%u)\n", (UINT)GetLastError());
return 0;
}
↧
Windows 10 Compact OS
Recently I have done a Compact install of Win10 Insider Preview last update to VHD's located on my internal HDD and on USB external HDD's using WinNTSetup 3.80RC3 and doing properly it works flawlessly see my post in that forum: http://www.msfn.org/board/topic/149612-winntsetup-v379-v38-rc3/page-50#entry1101479
This is Microsoft info about Compact mode: https://msdn.microsoft.com/en-us/library/windows/hardware/dn940129%28v=vs.85%29.aspx
This is the Win10 Pro X64 IP (Compact mode installed to VHD) when I open it using 7Zip v9.38Beta, it is a full install but all files and folders are compressed as you can see in the attachment, (NTFS is not compressed, just files and folders in it).
When you make Wimboot installs you need to have the install.wim in same disk (can be in another partition), because the install is only pointer files to the .wim, if you remove the .wim you can't boot this any more.
Well now in compact install you don't need the install.wim any more to boot the system (good for portable environments), my install to VHD in USB HDD is only 5.70 GB (before run it fist time) (31.32% smaller), and standard install to VHD is 8.3 GB
Attached Thumbnails
↧
MistyPE
File Submitter: misty
File Submitted: 20 Sep 2013
File Updated: 06 Jul 2014
File Category: Projects
This is a minimalist 32 or 64-bit WinPE/WinFE with a GUI shell (BBLean - based on BlackBox for Windows) - originally created for system deployment, backup, restore and recovery.
Use this project to create WinPE (version 2.*/3.*/4.0/5.0) in a matter of minutes from Windows installation media - a DVD, local folder, network share or mounted disc image. WAIK/ADK is not required.
There is also an option to collect the necessary files from the host operating system used to run winbuilder - Windows 7/8/8.1 supported. Credit to Erwan.l whose QuickPE project pointed the way to the required commands. This option requires that WinRE be copied from the C: drive - if WinRE was not copied to the C: drive during the Windows install then it won't be possible to use this method.
Project goals -
- A successful build every time!
- Clean and simple user interface
- Good quality instructions
Please see here for more information and to post feedback - http://reboot.pro/topic/18917-mistype/
Regards,
Misty
Documentation is included in the download and is also available online - http://mistype.reboot.pro/mistype.docs/readme.html
For changelog, see here
Click here to download this file
↧
↧
searching for Bay Trail - SD Card bootable driver
Hi,
playing arround with my bay trail netbook.
I like to boot win7 from a sdcard.
Problem is that i need to install a hdd-disk driver for the sd-card.
"SDA compliant SD Host Controller"
I still searching for a Version that works aout of the box with a bay trail chipset.
"refind" still helped me to start the bootsequence from the 2nd drive ... but it stopping during the bootsequence.
the usb-patch (for usb-sd-card boot) seems to be not working with baytrail ?!
Thanx.
André
↧
How to restore deleted folder from wiped SSD?
when I updated my BIOS and booted into Windows, part of SSD#0 is gone. Not just deleted, but turned into unallocated space. It's a Kingston SV300 240gb SSD, split into a 50gb Windows partition (this was unaffected) and the remainder for a partition for a few but nevertheless extremely important data. I got a new HDD today to act as a backup, but as luck would have it, before I could install it and make duplicates of my important files, this happened.
The partition is now unallocated space. I know the folder names, but not specific file names. I need to recover these folders with some urgency. I've tried Recuva but it can't seem to target specific directories, only files of a given name or type. Additionally, Recuva can't scan unallocated space.
What can I do? I haven't done anything to the unallocated space: haven't created a new volume or anything.
Some things I know:
TRIM is enabled
I know the folder names
Partition letter was M:\
rough idea of total size of files deleted (<20gb)
↧
Imdisk whether there is a detection of memory size
Imdisk whether there is a command to detect the size of the memory or the size of the remaining memory.
Because I want to test the memory size in the batch, and then create a different size of memory disk based on this size.
↧