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

Reboot featured on Dilbert :-)


Need help understanding RMPartUSB parameters about super floppies

0
0

Hi people,

 

I've read the documentation of the RMPartUSB tool, but I still cannot understand what some parameters do.

Specifically, I'd like to know what's the difference between CHS, ZIP and USBFDD

 

Do the CHS and ZIP parameters add an MBR to the drive?

 

What partition type does ZIP set when the filesystem is FAT16 ?

 

Thanks!

the song remains the same.

System Profile W2000

0
0

Hi,

I have found a computer (W2000 operating system) with a System Profile under Document and Settings Folder. As far I know this user doesn´t log in the computer. In a new W2000 PC this system profile folder doesn`t appear. In the registry under:

Microsoft\Windows NT\CurrentVersion\ProfileList

there is a key with id S-1-5-18 and Date Modified: 11/09/2013 9:33:13. Analyzing profile's folders in MFT I've found that Std Info Modification date is prior to Std Info Creation date in some folders under System profile, for example:

Filename #1: /Documents and Settings/SYSTEM/SendTo
Std Info Creation date : 2013-05-29 11:33:44.724249
Std Info Modification date: 2005-07-05 12:28:58
Std Info Access date: 2014-02-07 13:48:16.765625 (this date is because the disk was plugged by usb cable to check it)
Std Info Entry date: 2013-05-29 11:33:46.083626
FN Info Creation date: 2013-05-29 11:33:44.724249
FN Info Modification date: 2013-05-29 11:33:44.724249
FN Info Access date: 2013-05-29 11:33:44.724249
FN Info Entry date. 2013-05-29 11:33:44.72424

The system was installed in 2005.

Could anyone help me to understand what happened? Is this the result of an exploit? Why Std Info Modification date is prior to Std Info Creation date?

Best Regards and thanks in advance.   

Confused as Hell...

0
0

I want to make a PE with XP (preferably), or 7. Beside DiskCryptor, and Macrium Reflect Free, I don't really need anything else.
But I don't know what to use - this website has WinBuilder 2013.09.01 as a featured download. The tutorials I've found are for some undisclosed versions (but not that ^ one). Even your own tutorial from here:
http://reboot.pro/topic/4111-newcomers-tutorial-livexp-win7pe-portable-apps/
just adds to my confusion:
 

The projects discussed in this tutorial are customized and frozen versions of their progenitors, LiveXP and Win7PE_SE. They are more or less updated to reflect their counterparts but have different setups and contain additional scripts and features not offered in the official versions found elsewhere in the forum.

My only other PE experience was with BartPE, so I'm a "little" overwhelmed :ermm:
I got other questions too, but let's take it one step at a time :)

WinBuilder

0
0

Posted Image

File Name: WinBuilder
File Submitter: pscEx
File Submitted: 04 Sep 2013
File Updated: 03 Mar 2015
File Category: Winbuilder legacy

This is the easiest Windows PE builder on earth (not kidding)

Quick start:
  • Download WinBuilder from this page
  • Extract the zipped file to a folder, choose a short path like c:\winbuilder
  • Run Winbuilder.exe
  • Type "AUTO" on the main window to create a Win7PE boot disk
The instructions on the screen tell where you find the Win7PE ISO image.


Would you like to see new features added? Click on the "Support topic" button on the right side of this web page.

---------------------

Description

In this page you find the easiest and most advanced Windows PE builder ever created. It is easy and advanced, but it also has an "ugly" look (we will explain why).

---------------------

Supported Operating Systems

The new WinBuilder has been written to be independent from whichever operating system you are using, it is meant to work from Windows, Linux and MacOSX.

For Windows users, we make available "WinBuilder.exe". You just need to double-click for launch and then type "AUTO" to build a boot disk.

For Linux / MacOSX users, you should:
  • Open a console window
  • Change to the directory where you have "WinBuilder.exe"
  • Set once the execute bit to winbuilder.jar and launchEx.jar
  • Type: java -Xsm640m -Xsx1024m -jar winbuilder.jar
  • Type "AUTO" to launch the boot disk build
We haven't tested all possible platforms. If something doesn't work then please get back in contact with us to provide details about the machine where it is not working, so that we can fix it.

Our software is based in the Java platform. We do this in a very secure manner, for Windows users we include our own version of Java that does not require Java to be installed on your machine.

---------------------

Commands available

A short list of commands that are available inside WinBuilder

ART - Creates a banner in ASCII art
AUTO - Fully-automated boot disk creation
BUILD - Creates a new boot disk PE ISO using the actual project
CONFIG - Changes the settings of the specified plugin
CREDITS - Lists the credits and licenses of resources used in this software
CLS - Clears the screen
DOWNLOAD - Allows downloading pre-defined files from the Internet
EXIT - Concludes the execution of this program
INSTALL - Download and install apps from http://reboot.pro/files
LIST - Lists the available commands
SAY - Provides a valuable life lesson from the rebooter community
SET - Change the system settings using the key/value format
SOURCE - Chooses a Windows source from where the boot disk is built
UPGRADE - Upgrades rebuilder to the most recent version
UNINSTALL - Uninstalls a resouce from http://reboot.pro/files
VERSION - Informs about the current version of this program
WEB - Allow users to control this program from a web browser

To know better how each command works, type the command name followed by an "?"

Here is an example for a command that is useful:
install ?
Go ahead and try them all as you wish.

---------------------

Installing new stuff / plugins?

All plugins that you see available here on the reboot download center are available for direct download and install from within winbuilder. To see what is available, just type:
install
To install something, you can for example try:
install irfanwiew
---------------------

License

Copyright © 2013, 2014, 2015, Nuno Brito and Peter Schlang
Permission to use this software for your own personal usage is hereby granted, all other rights are reserved and require explicit permission from the copyright holders.

THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.


If you want to distribute WinBuilder, somehow use WinBuilder as part of your projects or any other licensing related matter then please contact Nuno Brito through mail@nunobrito.eu to explain your context and obtain a permission.

---------------------

Why is the new WinBuilder so ugly?

On this version we did not added a pretty GUI with buttons and nice graphs. This was intentional and recognize that that the "new look" is not pretty. Maybe can explain a bit better why we did it this way.
  • Easier for those who have no sight. We noted that the previous winbuilder was quite difficult for visually impaired users
  • Consistency. We support Windows, MacOSX, Linux and a web interface. If we only had a GUI like before we'd be spending our time trying to make a user interface that would look good on all these platforms
  • Expansion. With our new plugin system it is easy to write new commands by yourself or by other developers. Using only a traditional GUI would be difficult (and messy) to make this kind of thing possible
Reality is that you are using WinBuilder to get a boot disk done, not because it looks pretty. We deliver a solid builder, you just need to type one single command and things get done without drama.

Other builders out there that look prettier will:
  • require one hour (at minimum) to build a boot disk
  • ask full administrative permissions over your machine
  • only run on windows
  • force you to use a compatible source
  • fail four or five times until you get something
We don't have any of these troubles. You unpack, run and get a working boot disk. Simple.

Have fun! :)

Click here to download this file

Accessibility

0
0

can any one help i am trying to get "Accessibility options sticky keys" Win Pe? 

I am using wINBUILD 082

 

 

 

 

 

 

 

Thanks

Josh

Rufus 2.0 has been released

0
0

(Starting a new thread, since the previous one has grown quite big and this is a major release - Yet, I'm not going to shy away from shamelessly copy/pasting the blurb I wrote for the beta :ph34r:).

 

It is my great pleasure to announce the release of Rufus 2.0! :D

 

The Changelog for this version is as follows:

  • Major UI improvements (improved font, new info field, no separate progress dialog, etc.)
  • Add support for Windows To Go (when Rufus is running on Windows 8 or later)
  • Add support for Grub4DOS and GRUB 2 based images (e.g. FreeNAS)
  • Add portable application support, through a 'rufus.ini' file
  • Add native decompression support for DD images (.Z, .gz, .lzma, .bz2 and .xz)
  • Add seamless UEFI boot of NTFS partitions, for Windows ISOs with large files (>4GB)
  • Add support for Windows multipart install.swm
  • Add support for non Microsoft VHD drivers
  • Add Norwegian translation, courtesy of JED
  • Fix a crash on image selection when no device is present
  • Fix broken VHD support for non-English version of Windows
  • Fix write error for DD images that are not a multiple of the sector size
  • Fix broken Unicode support
  • Update Syslinux to 6.0.3
  • Other improvements and fixes

The points of interest that I'd like to stress out, in no particular order, is that Rufus should now look much nicer for eastern Asian languages (as long as you're not using XP... but you really shouldn't), the slightly annoying separate progress dialog is now gone, FreeNAS is now supported (through GRUB 2), seamless support for NTFS under EFI is provided for Windows images (convenient if you have a >4GB install.wim for instance) and the new info field should make the UI a bit more helpful for newcomers.

 

I'll also take a moment to explain how the portable feature works:

  • If you have a rufus.ini in the directory where you are launching Rufus from (even if it's a blank one), Rufus will use that, instead of the registry, to store its settings.
  • Also, if any part of the executable name contains a 'p' (for portable), Rufus will create a rufus.ini if one doesn't already exists, and use that one. This means that if you call the executable rufus_2.0p.exe, Rufus will automagically activate its portable mode.
    Oh, there is now a convenient link to such a portable download on the homepage - isn't that nice? ^_^
  • The format of rufus.ini is documented here.

Note however that portability does not equate unmodified registry, as Rufus will still apply LGP policies to temporarily avoid the annoying "Hey, I detected a new drive - do you want to format it?" messages that Windows would otherwise pop out. If you are that paranoid about registry changes, you can however use portable mode and enable DisableLGP, in which case registry changes originating from Rufus should be removed. You will of course get the annoying popups from Windows then.

 

With regards to Windows To Go, all I want to say is: You need to be running Rufus on Windows 8 or later for the 'Windows To Go' feature to be available to you, provided you use a compatible image (which include some Windows 7 ISOs). If you run Rufus on Windows 7 or earlier, you'll have to look elsewhere for Windows to Go support for the time being. The reason is detailed here. The Rufus usage notes also provide a bit more details with regards to To Go support in Rufus.

 

Also, while some people have reported success with Windows 10 (at least for the x86_32 version), at this stage, you should really expect Windows To Go support NOT to work for Windows 10, as all the tests I have conducted with 10 x64 have ended with an infinite boot, even when using the official Microsoft To Go tool from a Windows 10 Enterprise Preview 2 physical installation.

Thus, as far as I am concerned, ANYTHING that is preview, such as Windows 10, is unsupported which means you're on your own with Windows 10 until the formal release...

 

Finally, if you want to understand why this new version of Rufus is a bit plumper than the last one, have a look here.

 

Enjoy! ^_^


How to install WinAOE Driver on Windows 7 x86 32 bits / 64 bits, Windows 8 and 2008 Servers

0
0
Hello,

WinAOE Server is like iscsi, but i think is better because it broadcast the targets to the network (LAN), and the configuration is more simple to mount , its suporte .img , .iso and .vhd images !

You can use WinAOE Driver to boot many flavors of Windows Operating Systems entirely on Diskless Machines.

The WinAOE Driver from Coraid Systems on readme file of the package said that only work for:


Diskless AoE Driver for:
Windows 2000
Windows XP
Windows XP 64bit
Windows 2003
Windows 2003 64bit
Windows 2003R2 *
Windows 2003R2 64bit *
Windows Vista
Windows Vista 64bit *

But the Driver can be installed on Windows 7 , Windows 8 and 2008 systems !!! :D

With a little procedure you can do it.

Step 1 - To driver be loaded we should disable the Integrity checks for sign certification of drivers.

In Windows open a cmd ( command prompt ) and type


C:bcdedit  -set  TESTSIGNING ON



C:>bcdedit -set loadoptions DDISABLE_INTEGRITY_CHECKS


Step 2 - reboot Windows ( mandatory )

Step 3 - Download the driver here, because this version is self signed : winaoe.zip

Step 4 - Uncompress file into a folder

Step 5 - Go to Start Button -> Run --> type 'hdwwiz.cpl'

Step 6 - Install driver with type Storage Adapter.

Posted Image


Thats all;

other faq for XP: http://www.etherboot.org/wiki/sanboot/winnt_aoe


WinAOE working on Windows 7 x86 32 bits, 64 bits and Windows 2008...

Im preparing a new how to boot Windows Diskless with AOE Targets...

Im compiled the vblade ( aoe target system ) for Windows too.

Comming soon...


To see other Windows diskless boot method -> see my iSCSI FAQ : https://windowsdiskless.wordpress.com/

enjoy.

Win7VBlock

0
0
Four lines of code were enough to get WinVBlock working on Windows 7. Three lines to sign the drivers. One line to allow Windows 7 to use a WinVBlock optical disc.

Here is how I get WinVBlock going from Windows 7 Setup:
  • Boot Windows 7 Setup disc.
  • Press any key to boot from CD or DVD... -> Start hitting F8 repeatedly.
  • Windows is loading files...
  • At the F8 menu, choose to Disable Driver Signature Enforcement
  • At the first Install Windows window, click the Next button.
  • Click the Repair your computer link.
  • At the System Recovery Options window, click the Next > button.
  • At the Re-image Your Computer warning window (if you see it), click the Cancel button.
  • At the Re-image Your Computer window, click the Cancel button.
  • At the System Recovery Options window, click the Command Prompt link.
  • In the "DOS box" (CLI), change the working directory to your WinVBlock F6 floppy drive's root directory:
    
    cd /d a:\
    
    
  • Install the WinVBlock driver:
    
    sc create WinVBlock type= kernel binPath= a:\wvblk32.sys
    
    
  • Load the .INF file so the device is auto-installed:
    
    drvload a:\winvblk.inf
    
    
  • Start the driver:
    
    net start winvblock
    
    
  • Now WinVBlock is installed. You could attach an .ISO with:
    
    winvblk -cmd attach -m c -u c:\some.iso
    
    
    or a floppy disk image with:
    
    winvblk -cmd attach -m f -u c:\some.vfd
    
    
    or an HDD image with:
    
    winvblk -cmd attach -m h -u c:\some.hdd
    
    
  • You may return to Windows 7 Setup with:
    
    x:\setup
    
    
Contents of your WinVBlock F6 floppy:
  • WinVBlk.cat
  • WinVBlk.exe
  • WinVBlk.Inf
  • WVBlk32.sys
  • sc.exe
  • txtsetup.oem
Use the latest development binaries. Enjoy. Report problems. Whatever.

RMPrepUSB - faster FAT32 write access on Flash memory drives

0
0

[Edit]

Note: All versions of RMPrepUSB/RMPartUSB later than 2.1.647 have this new write speed improvement change.

The new versions of RMPrepUSB (click to download) can be found on the Beta Download page of my site.

See this post for the theory of how/why it works.

[/Edit]

 

 

I have modified a version of RMPartUSB (used by RMPrepUSB) so that when formatting as FAT32, the first file cluster will be set to a 1MB boundary location. This may give faster file i/o speeds (may be noticeable on writes??) compared to previous versions.
Here is the output from RMPrepUSB DriveInfo with the new format.

I would guess that some small speed improvement may be noticeable when using small file writes and maybe someone would like to compare this new format to the previous one when doing file i/o operations?

RMPrepUSb DriveInfo for P1 displays:
FAT32
000B Bytes Per Sector = 512 (0200h)
000D Sectors Per Cluster = 8 (08h)
000E Reserved Sectors before first FAT = 1067 (042Bh)
0010 Number of FATs = 2 (02h)
0011 Root Entries = 0 (0000h)
0013 Total Log Sectors (small) = 0 (0000h)
0015 Media Descriptor = 248 (F8h) HDD
0016 Sectors per FAT table = 0 (0000h)
0018 Sectors per Track = 63 (003Fh)
001A Number of Heads per Cylinder = 255 (00FFh)
001C Hidden Sectors preceding Partition = 63 (0000003Fh)
0020 Total Log. Sectors (big) = 16193457 (00F717B1h)
0024 Log. Sectors per FAT = 15815 (00003DC7h)
0028 Mirroring Flags = 0 (0000h)
002A Version No. = 0 (0000h)
002C Cluster No. of Root Dir Start = 2 (00000002h)
0030 Log. Sector No. of FS Info Sector = 1 (0001h)
0032 First logical sector number of a copy of the three FAT32 boot sectors, typically 6 = 6 (0006h)
0040 Physical Drive Number = 128 (80h) First Fixed Disk
0042 Extended Boot Signature = 41 (29h)
0047 Volume Label = NO NAME
0052 FileSystem Type = FAT32

First FAT begins at LBA 1130
Second FAT begins at LBA 16945
Root Directory begins at LBA 32760
First file data (cluster 0) begins at LBA 32768

ListUSBDrives displays:
MountPoint = K:
Volume Label = RMPARTUSB
Volume Size = 8 GB (FAT32, 4 KB clusters, 8 GB free)
Volume Serial = C925-3A9D
Partition Type = FAT32x (0C), boot
Partition Align = 512
1st Cluster Align = 4 K
Volume Name = ?Volume{03f6d2f7-61ed-11e1-a1fe-005056c00008}
Partition Name = DeviceHarddisk3Partition1
Bus Type = USB
Drive Type = removable
Device Types = ---
NoMediaNoLetter = no (configure >= 3)
Volume DevID = STORAGEVOLUME_??_USBSTOR#DISK&VEN_PRETEC&PROD_08GB_REX100&REV_1.00#09021000000000000264762875&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}
Drive DevID = USBSTORDISK&VEN_PRETEC&PROD_08GB_REX100&REV_1.0009021000000000000264762875&0
USB DevID = USBVID_4146&PID_090209021000000000000264762875
Ctrl2 DevID = USBROOT_HUB204&4E48F5B&0
Host Ctrl DevID = PCIVEN_8086&DEV_293A&SUBSYS_020D1028&REV_023&2411E6FE&1&EF
Host Ctrl Name = Intel® ICH9 Family USB2 Enhanced Host Controller - 293A
Volume DosDevName = DeviceHarddiskVolume6
Disk DosDevNames = DeviceHarddisk3DR3, Device00000093
Removal Policy = orderly removal ('Optimize for performance')
WriteCache = no
Hotplug Device = no
Hotplug Media = no
Removable Media = yes
Partition Number = 1 of 1
Friendly Name = PRETEC 08GB REX100
Requested Power = 500 mA (bus powered)
USB Version = 2.1 (High-Speed)
USB Friendly Name = PRETEC 08GB REX100
USB Serial = 09021000000000000264762875 (exceeds the maximum length!)
USB Port Name = 8-4

Need Help Setting Up UEFI DUET On Alienware M14X R1

0
0

So, I recently bought an Alienware M14X R1 on Craigslist. It was manufactured in early 2011. And I just now discovered that it has no support for UEFI whatsoever. I had looked through the BIOS before purchasing and noticed that UEFI options weren't present anywhere, but the laptop was in such good condition and it was a really good deal for the price, that this wasn't a dealbreaker for me. The seller was honest and didn't try to up the price at all. And so far it has exceeded my expectations in terms of playing games, even newer titles seem to run pretty well on it. I haven't had any major issues thusfar. Installing Windows 8.1 Pro was easy enough, the biggest issue I had was finding the right drivers. But now everything is running like a dream.

 

However, I would now like to experience the benefits of booting Windows on GPT partitioning, and I now realize that emulating Windows via DUET will be the only viable option for doing so on my hardware. I recently found milindsmart's post here on reboot.pro (http://reboot.pro/topic/19516-hack-bootmgr-to-boot-windows-in-bios-to-gpt/). But using that method isn't desirable, since it won't allow for repairing Windows via the native options available on the setup USB. And I am uncertain of how to get it working in conjunction with an Arch Linux dualboot scenario, which preferably will boot in UEFI mode on GPT partitioning.

 

I have also noticed a few other things, which are, namely, that DUET supposedly doesn't support AHCI mode. I have read that using IDE mode will be necessary. Now that 2015 is here, is this still the case?

 

If I can get some assistance in getting this set up, and what I will need to do so, then I would be very grateful. I know that I will at least need one USB drive, a Windows setup USB/disc (for dual-boot), and (preferably) some flavor of Linux to initially set up DUET, as well as SysLinux or GRUB2.

 

I also apologize in advance if I posted this in the wrong area of the forum, I'm relatively new here. Feel free to relocate it to the correct area if neccessary.

 

Thanks in advance!

iConsole Micro - HDMI Mini PC on a stick with Android ConsoleOS , around $129 - unlocked, 64-bit UEFI bootloader

0
0

Similar specs to Intel Compute Stick and MeeGoPad T01

 

https://liliputing.com/2015/03/iconsole-micro-tv-stick-with-an-intel-cpu-console-os-android-software.html

 

Console OS is a custom version of Android optimized to run on computers with Intel processors.

 

feature a 64-bit quad-core Atom processor, 32GB of storage, 802.11n WiFi, Bluetooth 4.0, a microSD card slot and an HDMI connector.

available this summer for about $129.

 

device has an unlocked, 64-bit UEFI bootloader which means that if you want to install Windows, Ubuntu, or other operating systems, there’s nothing stopping you from doing that.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

GLP 8-Circuit Biological AI (Artificial Intelligence) WARNING BEWARE

0
0
hi everyone,

I havnt posted in this subforum before. forensics is not an area I am too familiar with but I was reading an interesting thread about mysterious Artificial Intelligence. GLP 8-Circuit Biological AI GodLikeProductions.com here:

WARNING: This could possibly be the most advanced, hostile malware/virus/trojan ever! only the most elite experts in this field should even consider testing it. consider that infection may transfer/spread from system hardware to human body!!!

PROCEED ONLY WITH EXTREME CAUTION!

http://www.godlikeproductions.com/forum1/message2806175/pg1

there is a .rar file available on the second page "usb.rar" to download that I thought some of the experts here might be able to instruct me on how to inspect it safely.

my first thoughts are to put it on a freshly formated USB flashdrive then boot into a ram loaded OS from another USB drive in a system with no HDD installed then remove the USB drive the image was booted from then open the VERY Questionable "usb.rar" file for inspection.

does this seem safe or should I use a system that is disposable alltogether? (which I dont have really)


Thanks

Easy2boot RestoreE2B modified

0
0

Steve, I have a question for yah relating to your tools, namely RMpartUSB and my multi-boot drive using your wonderful E2B (This post seems the most logical of the ones you seem to be watching to post it in, sorry in advance if I got it wrong).

 

So I have gotten a new drive and in the process of copying my stuff over to the new drive I see you updated E2B and I decided to update my toolsets, and making use of your new features and the fact I had driver packs become not accessible due to the new fancy partition mapping you do to support uefi, I have finished working up a work around but have one last snafu that Google isn't helping with and I believe you are the author of the program with the snafu.

 

For better or worse I have edited your 'RestoreE2B (run as admin).cmd' into 'RestoreE2Bscript.cmd' having changed 1 or 2 lines and deleting 4 to 5 lines, code as follows

@ECHO Off
cls
SETLOCAL ENABLEEXTENSIONS
color 1f
echo.



pushd "%~dp0"
if exist "%systemdrive%\Program Files\RMPrepusb\RMPartusb.exe"  pushd "%systemdrive%\Program Files\RMPrepusb"
if exist "%systemdrive%\Program Files (x86)\RMPrepusb\RMPartusb.exe" pushd "%systemdrive%\Program Files (x86)\RMPrepusb"
if not exist RMPARTUSB.exe echo Please install RMPrepUSB to the standard Program Files location & echo OR copy RMPartUSB.exe to %~dp0! & pause & goto :end

echo %~n0 [SSi] v1.00
echo.

echo SELECT A USB DRIVE
echo ==================
echo.
rmpartusb% LIST | find "DRIVE"
echo.
set DD=
set /a DD=1
if "%DD%"=="" goto :end
if "%DD%"=="0" goto :end

set LBA=30
set MBR=
set PTN=
call :getsec
if "%MBR%%PTN%"=="11" goto :gotsec

set LBA=60
set MBR=
set PTN=
call :getsec
if "%MBR%%PTN%"=="11" goto :gotsec

set LBA=1
set MBR=
set PTN=
call :getsec
if "%MBR%%PTN%"=="11" goto :gotsec
echo No backup MBR found! & pause & goto :end


:gotsec
RMPARTUSB drive^=%DD% usbinfo usbstart^=%LBA% LENGTH=1SEC sure
echo Found backup MBR at SECTOR %LBA%
echo.

:: MUST NOT USE USB drive to store .TMP file as RMPartUSB cannot access it after dismounting the volume!

:: Save LBA 0 to E2B0.TMP
RMPARTUSB USBTOFILE drive=%DD% FILE="%TEMP%\E2B0.TMP" USBSTART=0 LENGTH=1SEC FILESTART=0 SURE > nul

RMPARTUSB USBTOFILE drive=%DD% FILE="%TEMP%\E2B%LBA%.TMP" USBSTART=%LBA% LENGTH=1SEC FILESTART=0 SURE > nul
if errorlevel 1 goto :end
RMPARTUSB FILETOUSB drive=%DD% FILE="%TEMP%\E2B%LBA%.TMP" USBSTART=0  LENGTH=1SEC FILESTART=0 > nul
if errorlevel 1 goto :end
echo MBR Restored OK
pause

:end
popd
endlocal
GOTO :EOF


:getsec
FOR /F "tokens=16,17 delims=- " %%A IN ('RMPARTUSB drive^=%DD% usbinfo usbstart^=%LBA% length=1sec sure`^| FIND "01F0"') DO (
if "*%%A*%%B*"=="*55*AA*" echo Found MBR & set MBR=1
)
FOR /F "tokens=4 delims=- " %%A IN ('RMPARTUSB drive^=%DD% usbinfo usbstart^=%LBA% length=1sec sure`^| FIND "01C0"') DO (
if not "*%%A*"=="00" echo Found Partition 1 Entry & set PTN=1
)

goto :eof

:check_Permissions
    >nul 2>&1 "%SYSTEMROOT%\system32\cacls.exe" "%SYSTEMROOT%\system32\config\system"
	REM --> If error flag set, we do not have admin.
	if '%errorlevel%' NEQ '0' (
        echo.
	echo Sorry - you need to run this script as Administrator.
        echo.
	echo Please use right-click - Run as administrator.
	echo.
	echo.
	color cf
	pause
	Set ADMIN=FAIL
    ) else (
	echo Administrative permissions confirmed.
    )


The idea being to use it as part of a startup script on auto pilot. almost all prompts have either been removed or hard coded save one that is a dialogue box courtesy of RMpartusb. is there a way to prevent or auto acknowledge that dialogue box with no user interaction?

 

PS: this is intended for use in modified pe3 where by default you are already administrator, the idea being as before this script is run the main drive where I keep my driver packs is inaccessible and they are scripted into the start up of said pe3. So what I am doing is running this do get drive access back, running imdisk to remount the image elsewhere and then with the drive once again accessible the drivers go ahead and load.


The tftp32 ignore block is different from wireshark.

Easy2Boot

0
0

Hi,

 

I want use easy2boot on my main système (hd0), not on usb (bd) :

 

My Settings of (hd0) are like follow :

 

*Part1 or (hd0,0) : System Windows A

*Part2 or (hd0,1) : System Windows B

*Part3 or (hd0,2) : Datas

*Part4 or (hd0,3) : Easy2Boot

 

* = Partition Principal NTFS

 

I copied all the files and directories of Easy2boot on Part4 (hd0,3) and i installed grub4dos on MBR !

At boot time Grub4Dos check grldr on (hd0,0), (hd0,1), (hd0,2), (hd0,3), find it on (hd0,3) and load [of course] menu.lst

 

Anyway i get this Message Error :

 

Booting Easy2Boot v1.62 (4) - counting files please wait ...

ERROR: PARTITION TABLE 4 (type0x7)  IS ALREADY IN USE ON THIS DRIVE!

Press C and [Enter] to delete it :

 

I tried to check the FAQ, but easy2boot website is little bit like a mess and i can't find solution to my problem !

Maybe here ? : http://www.easy2boot.com/make-an-easy2boot-usb-drive/using-other-partitions-or-drives/

 

Anyway i don't understand so much and do u have idea how to solve this problem ?

Thanks

CFC to CFC

0
0

Hi All

 

I use CFC's to boot industrial CPU boards on various machines, and have done for many years.

All was well using WinImage until the CFC's got over 1 gB, and after that it was problematic.

 

Then the CFC's changed and only the Industrial versions were bootable.(on Windows)

Simply creating a vhd image and then writing it onto another didn't work anymore.

 

Now I am in situation where the 2gB CFC's are no longer available, so I need to read a 2gB CFC and rewrite

it to a 4gB.

So, discovered RMPrepUSB, and downloaded the latest version, but there are some problems.

Reading the source CFC with "Drive -> File" and picking various formats (vhd,img , raw etc) does not transfer the second partition when you use File->Drive and select the .vhd you just created. Strangely the .raw image is

the right size , but it writes nothing to the target CFC with "File->Drive"

 

The detail of the source CFC.

WinXP embedded

HORM protected C: as primary partition.

Second partition as D: used for changable files.

 

I selected / used  the following options in RMPrepUSB

Bootloader WinPE , NTFS, Boot as HDD

 

There has to be a better and simpler way to do this.

 

Can SKS tell me how make a 4gB bootable CFC with two partitions from a source CFC that is less then 4gB.

 

Regards

 

Integrate WoW in 64-Bit PE, but...

0
0

but without Winbuilder!

 

I´m coerced to work here with a highly customized winPE image.

 

The PE is doing everything i want - except running 32-Bit apps.

 

For different reasons i cant use winpe builder and i cant decode the 5-Wow64.script

 

Is there a way to "decode" the script?

 

Is there somewhere a guide integrating Wow in PE_X64? 

The guide doesnt have to be step-by-step guide - its enough that i can get an idea which files an which registry keys i need - I can check the details by myself.

 

thx

netlord

 

DISM-scratchspace

0
0

Posted Image

File Name: DISM-scratchspace
File Submitter: Tony4219
File Submitted: 06 Mar 2015
File Category: App scripts

Increase the scratch space (available, writable space) on X: on your X/Y USBstick, post-build. This script uses DISM.EXE which should be present in your Winbuilder build already, and is preset to use 512MB. No need for additional files. It will modify your WIM file present at Y:\sources\boot.wim and does some error checking.

Why? Well, Winbuilder is set to 128MB scratch space, and some apps are larger, and some stubborn apps and installers want to install themselves to the boot drive (with no option to change). Some trial apps leave registry entries that won't let you reinstall them after the first expiration date. And many fail to install because of insufficient temporary space. If possible, I like to use Winbuilder as a virtual machine on new apps that I don't yet trust on my 'good machines'. Changes, installs, modifications, and additions you make on X: and in the registry ARE NOT saved. Winbuilder is GREAT!

However, changing the scratch space to your BOOT.WIM file is permanently saved. This script will modify the same WIM you booted from (unless you change it). I suggest keeping a copy of your original BOOT.WIM just in case.

I found information to increase the WIM scratch space at MSFT and elsewhere. You can modify WIM files after they are built. Your choices of scratch space are 128/256/512 MB. If the host machine has little RAM, you probably don't want to run this. See notes.

I now have X: 456.34 MB (2.49MB used, 453.85 MB free) and the rest of the 16GB USBstick is for Y:

(Tested on Winbuilder [080] using Win7 Pro x64. I know it is old. It should work on [082] with no modifications, but I learned the hard way that alternating back and forth between [080] and [082] will mess up some internal Winbuilder scripts because Winbuilder modifies itself)

As many have noted, DISM rejects scratchspace settings beyond 512MB. As an aside, I found forum notes at reboot.pro from Joakim from 2009 about using a registry hack to get 1024 MB Winbuilder scratch space, and was not able to get it to work.

Click here to download this file
Viewing all 6812 articles
Browse latest View live




Latest Images