I will be travelling tomorrow and will only return within a week, still, I would like to wish all rebooters reading this message across the world a great holiday season.
Do a lot a of silly stuff, have fun and be nice to others. 
Merry Xmas everyone!
↧
↧
AOMEI Data Backuper
File Submitter: Aeolis
File Submitted: 25 Dec 2012
File Updated: 25 Dec 2012
File Category: App scripts
CREDITS: My BIG THANK YOU for the Reboot.pro community!
DESCRIPTION: This script is designed to help backup tasks on PE environment using AOMEI Data Backuper as the tool for that. With it you can add shortcuts to Desktop, Start Menu and a Start Menu custom folder.
THE PROGRAM: Free backup and restore software for home and commercial use. AOMEI's software with System Backup, Disk Backup, Partition and Volume Backup, System Recovery, Disk and Partition Recovery and Selective file restore features will ensure the safety of your data. In addition to backup and restore functions, AOMEI Data Backuper supports cloning operations with Disk Clone and Partition and Volume Clone features. Other features are: Incremental and differential backups, Encryption and Compression, Image file checker and explorer, Comment Backups and Splitting Backups and Create Bootable Rescue Media.
FROM AUTHOR: I hope you like using it as much as I liked creating it. I hope you can test and post your comments here. I would like suggestions on how to clean/improve this script.
Best regards,
Aeolis
Click here to download this file
↧
[PortableApps] Portable program Maker Tool
=============================================================================
Portable program Maker Tool
=============================================================================
Hi
Portabilizer is a free software designed to create launcher executables with custom icons
for creating portable programs. Launchers created with Portabilizer, can run specified
program with specified parameters. You can download it from link below:
http://www.softpedia.com/progDownload/Wind...oad-106956.html
And here i am going to tell how to use that in few lines,But befor starting tutor i should mention
that for using this program first you should make ready your portable program Files and folders as
i said in link below, and put them some where in your hard.
http://www.boot-land.net/forums/?showforum=73
In real world the "Portabilizer" does not make a portable program (as it's name says),
it just makes a file by your favorite icon to load your portable program from any place
that you have put your portable files.I mean you do not need to make shortcut for your
portable program to work,and just double click to a file that you make by Portabilizer.
I suppose that :
_ you have downloaded "Portabilizer Portable 1.0" and extracted to a folder some where.
_ you have made portable "Auslogics Disk Defrag 1.4" and placed it in C:\Disk Defrag directory.
-------------------------------------
how to use Portabilizer Portable 1.0
-------------------------------------
1.Select your favorite ICON for use in this tutor and place it some where (for example C:\01.ico).
2.Run Portabilizer Portable 1.0 ,and fill the coming window as figure_1 in attachment.
3.Click on "start" in portablizer window,after a few seconds ,a dialog box will be appeiered and
will say "process completed", click OK.
Now if you go to c:\ (in this example),you will see that C:\Disk Defrag 1_4 Portable.exe is
created ,and if you double click on it,the diskdefrag.exe will run.
-------
Note:
-------
After making as i said above,If you copy C:\Disk Defrag from your system to drive "C" of other
system,and place created file (C:\Disk Defrag 1_4 Portable.exe) any place in that system,by
clicking that the diskdefrag.exe will run.
=================================
thats all
hope will be helpful
shirin zaban
Portable program Maker Tool
=============================================================================
Hi
Portabilizer is a free software designed to create launcher executables with custom icons
for creating portable programs. Launchers created with Portabilizer, can run specified
program with specified parameters. You can download it from link below:
http://www.softpedia.com/progDownload/Wind...oad-106956.html
And here i am going to tell how to use that in few lines,But befor starting tutor i should mention
that for using this program first you should make ready your portable program Files and folders as
i said in link below, and put them some where in your hard.
http://www.boot-land.net/forums/?showforum=73
In real world the "Portabilizer" does not make a portable program (as it's name says),
it just makes a file by your favorite icon to load your portable program from any place
that you have put your portable files.I mean you do not need to make shortcut for your
portable program to work,and just double click to a file that you make by Portabilizer.
I suppose that :
_ you have downloaded "Portabilizer Portable 1.0" and extracted to a folder some where.
_ you have made portable "Auslogics Disk Defrag 1.4" and placed it in C:\Disk Defrag directory.
-------------------------------------
how to use Portabilizer Portable 1.0
-------------------------------------
1.Select your favorite ICON for use in this tutor and place it some where (for example C:\01.ico).
2.Run Portabilizer Portable 1.0 ,and fill the coming window as figure_1 in attachment.
3.Click on "start" in portablizer window,after a few seconds ,a dialog box will be appeiered and
will say "process completed", click OK.
Now if you go to c:\ (in this example),you will see that C:\Disk Defrag 1_4 Portable.exe is
created ,and if you double click on it,the diskdefrag.exe will run.
-------
Note:
-------
After making as i said above,If you copy C:\Disk Defrag from your system to drive "C" of other
system,and place created file (C:\Disk Defrag 1_4 Portable.exe) any place in that system,by
clicking that the diskdefrag.exe will run.
=================================
thats all
hope will be helpful
shirin zaban
Attached Thumbnails
↧
access fdubcd.iso content from grub4dos
I am using UBCD 5.1.1, usually booting it to the isolinux/syslinux menu. There is an alternative grub4dos menu, and both menus can chainload from/to each other.
From the syslinux menu, fdubcd.iso (listed as FDUBCD in the initial boot menu of UBCD) can be booted (using MEMDISK), and all the DOS-based programs can be accessed as expected.
But, when FDUBCD is booted from grub4dos, the content of fdubcd.iso can't be accessed once in DOS, so most of the DOS programs can't be executed.
For those that already know UBCD 5.1.1, the difference is that when booting fdubcd.iso with isolinux -> MEMDISK, then drive "T:" in fdubcd is the content of fdubcd.iso (as expected), but when booting fdubcd.iso with (isolinux ->) grub4dos, then drive "T:" in fdubcd is the content of the full UBCD, so the content of fdubcd.iso can't be accessed.
When booting fdubcd.iso from the syslinux/islonux menu, the entry (which works correctly) is:
When booting fdubcd.iso from the grub4dos menu, the entry (which boots fdubcd.iso correctly but doesn't allow the expected access to its content once in DOS) is:
If I customize UBCD by expanding the content of fdubcd.iso (and the content of fdubcd.img inside it), thus having the images and their expanded contents in UBCD, then grub4dos can use the DOS programs because it finds them (expanded already) in UBCD.
I would like to avoid this "extra" expansion in my customized UBCD, and still have access to the content of fdubcd.iso once in DOS. I am hoping that some improvements to the grub4dos entry could achieve the goal, but if this would be not enough, then any other advice is welcome. If there is a specific grub4dos version that could solve this issue, I'd be happy to know about it.
I don't know much about grub4dos commands / parameters, so the menu posted above is just the one that comes in UBCD 5.1.1.
I would appreciate any advice on the potential modifications to the above grub4dos menu so to achieve the goal.
If I wasn't clear enough, or some additional info is required, I'll be happy to provide it; just ask.
From the syslinux menu, fdubcd.iso (listed as FDUBCD in the initial boot menu of UBCD) can be booted (using MEMDISK), and all the DOS-based programs can be accessed as expected.
But, when FDUBCD is booted from grub4dos, the content of fdubcd.iso can't be accessed once in DOS, so most of the DOS programs can't be executed.
For those that already know UBCD 5.1.1, the difference is that when booting fdubcd.iso with isolinux -> MEMDISK, then drive "T:" in fdubcd is the content of fdubcd.iso (as expected), but when booting fdubcd.iso with (isolinux ->) grub4dos, then drive "T:" in fdubcd is the content of the full UBCD, so the content of fdubcd.iso can't be accessed.
When booting fdubcd.iso from the syslinux/islonux menu, the entry (which works correctly) is:
LABEL FDUBCD LINUX /boot/syslinux/memdisk INITRD /ubcd/images/fdubcd.iso.gz APPEND iso raw
When booting fdubcd.iso from the grub4dos menu, the entry (which boots fdubcd.iso correctly but doesn't allow the expected access to its content once in DOS) is:
title FDUBCD\n map --mem /ubcd/images/fdubcd.iso.gz (hd32) map --hook root (hd32) chainloader (hd32)
If I customize UBCD by expanding the content of fdubcd.iso (and the content of fdubcd.img inside it), thus having the images and their expanded contents in UBCD, then grub4dos can use the DOS programs because it finds them (expanded already) in UBCD.
I would like to avoid this "extra" expansion in my customized UBCD, and still have access to the content of fdubcd.iso once in DOS. I am hoping that some improvements to the grub4dos entry could achieve the goal, but if this would be not enough, then any other advice is welcome. If there is a specific grub4dos version that could solve this issue, I'd be happy to know about it.
I don't know much about grub4dos commands / parameters, so the menu posted above is just the one that comes in UBCD 5.1.1.
I would appreciate any advice on the potential modifications to the above grub4dos menu so to achieve the goal.
If I wasn't clear enough, or some additional info is required, I'll be happy to provide it; just ask.
↧
Copying in different PING automated isolinux.cfg files via Grub4Dos
Hi - I like to run PING (Partition Is Not Ghost) backup/restore in unattended mode via the isolinux.cfg file on the root of the file.
I have 5 different ISOs for PING currently on my flash drive. Each ISO is 33MB but they are all the same except for one file isolinux.cfg being different in each one. The rest of the files except for isolinux.cfg are all the same. Is there some way that I can keep 5 different versions of the file, load 1 common ISO of PING, and then copy the correct isolinux.cfg file into the in-memory loaded ISO image depending on the selection in Grub4DOS?
For example: I have: isolinux.cfg.computer1, isolinux.cfg.computer2, isolinux.cfg.computer3, isolinux.cfg.computer4, isolinux.cfg.computer5
Currently I have:
title PING302-automated-computer3 map --mem (hd0,0)/iso/PING302-automated-computer3.iso (hd32) map --hook chainloader (hd32) boot
I would like to do something like the following (note bolded line in red):
title PING302-automated-computer3
map --mem (hd0,0)/iso/PING302-commonfiles.iso (hd32)
cp /pingautomatedfiles/isolinux.cfg.computer3 (hd0,0)/isolinux.cfg
map --hook
chainloader (hd32)
boot
Is something like this possible so I don't have to keep 5 different versions of the entire ISO - and can just copy in the configuration files? Thanks.
↧
↧
[script]PENetwork
Hi everybody,
I uploaded version 037 of the script for my "PENetwork"-manager - this is primary for LiveXP.
A script version for VistaPE (current beta v04) you will find here: http://reboot.pro/7036/
All included tools in this script (especially "startnet.exe") are selfcreated by myself -> completely licensefree.
The script you can download from 'my' personal WinBuilder-website (http://holger.winbuilder.net).
DirectDL (zipped 493KB): http://holger.orgfre...s/PENetwork.zip
If you have any questions, suggestions (maybe later when I finish the most) or problems just let me know.
Tested by others and me with XP-SP2/SP3/W2K3-SP1-source and VMWare / VirtualBox / QEmu / RealWorld - thank you all very much![:)]()
Greets...
Holger
Current state:
15.07.2009 - v37 (PENM 0.54):
- Changed: Internal handling of .icl-file - now it's possible to use own "PENetwork.icl" (for now it has
to be copied manually to the system32 dir)
- Changed: Default ini values of sharing to off and timer to 5 sec
- Added: Registering of "rsaenh.dll" after WiFi service installing to connect to
WPA-PSK/WPA2-PSK networks (BootSDI-option OR addtional FBWF-plugin/script is still needed - PE root must be writable)
- Added: "PENetwork.icl" to source zip
Note!: network browsing doesn't work in QEMU by default cause of the buildin firewall
History:
Script-screenshot:
![Posted Image]()
Screenshots of PENM at work:
Silver and Dark color scheme:
![Posted Image]()
![Posted Image]()
Some older:
![Posted Image]()
![Posted Image]()
![Posted Image]()
![Posted Image]()
![Posted Image]()
I uploaded version 037 of the script for my "PENetwork"-manager - this is primary for LiveXP.
A script version for VistaPE (current beta v04) you will find here: http://reboot.pro/7036/
All included tools in this script (especially "startnet.exe") are selfcreated by myself -> completely licensefree.
The script you can download from 'my' personal WinBuilder-website (http://holger.winbuilder.net).
DirectDL (zipped 493KB): http://holger.orgfre...s/PENetwork.zip
If you have any questions, suggestions (maybe later when I finish the most) or problems just let me know.
Tested by others and me with XP-SP2/SP3/W2K3-SP1-source and VMWare / VirtualBox / QEmu / RealWorld - thank you all very much
Greets...
Holger
Current state:
15.07.2009 - v37 (PENM 0.54):
- Changed: Internal handling of .icl-file - now it's possible to use own "PENetwork.icl" (for now it has
to be copied manually to the system32 dir)
- Changed: Default ini values of sharing to off and timer to 5 sec
- Added: Registering of "rsaenh.dll" after WiFi service installing to connect to
WPA-PSK/WPA2-PSK networks (BootSDI-option OR addtional FBWF-plugin/script is still needed - PE root must be writable)
- Added: "PENetwork.icl" to source zip
Note!: network browsing doesn't work in QEMU by default cause of the buildin firewall
History:
Spoiler
)Script-screenshot:
Screenshots of PENM at work:
Silver and Dark color scheme:
Some older:
↧
Boot from HDD or Network
Ok, so here it goes. I have a customers system who's bios password is locked and will not reset even when the bios battery, the main battery (laptop) and the memory are pulled. The bios has been programmed to disable booting from the CD and the USB ports, so I have to design a tool to boot from (either a hard drive that I make internal, or a network) that can install a new bios. The bios I have to install is here. I have tried using a newest free dos CD on the HDD installed on a different computer to install Free Dos locally on the drive, and then putting it back into the other computer, but the Bios install program wont run for some reason. I get a bunch strange numbers when I try to the upgrade.
↧
Will You Switch To Windows 8?
Will You Switch To Windows 8?
↧
Top 3 Options to Reset Forgotten Windows 8 Picture Password?
As a Windows 8 user, you can login your pc with multical ways. Picture passwords, standard passwords, and pin code logins are all demonstrated in Windows 8. And the new picture password feature in Windows 8 will let you use gestures like circles, lines and points to login quickly. Moreover, you can create a Windows 8 picture password for user accounts as a supplement of its traditional password. The picture password is said to be more secure and easier to remember. But no one is sure that he or she will never forget this password. What to do if you forgot Window 8 picture password.
Option 1: Sign in Windows 8 with password
If forgot Windows 8 picture password, you can simply use the traditional text password to or other options like PIN code (if you have created in advance) to get back in your computer.
[1]:Click Switch to password button on the picture logon screen.
[2]:Enter the password you used when you created your account, and then press Enter to get in Windows 8.
Option 2: Reset forgotten windows 8 picture password
Once you are logged in, you can reset the forgotten picture password as Windows 8 comes with ability to play the picture password.
[1]:Press Windows +C to open the charms bar, select Settings -> Change PC settings to open PC settings window.
[2]:Select Users on the left pane and then click Change picture password in Sign-in Options section on the right.
[3]:Type the password of the current user account, and then click Ok button.
[4]:Click Replay button to see your forgotten picture password again.
Option 3: Use Third-Party password reset software
What if you forgot Windows 8 password?
If you are using a Microsoft account, you can simply reset the forgotten password by going to the Microsoft account sign-in webpage.
If are using a local account, you can use the password hint as a reminder to help you recall what your Windows 8 password. You can also reset the lost Windows 8 password with a previously created password reset disk or another admin account. Besides, a great number of Windows password recovery programs are out there to help you easily reset Windows 8 password. Here I highly recommend Windows Password Key 8.0.
Windows Password Key 8.0 is an easy-to-use tool designed for resetting Windows local account or domain passwords on any Windows system. Passwords can be reset in 3 minutes, no matter how long and complicated the password is. Besides password recovery function, it even can change any local admin/user/domain admin password, and create a new Administrator account via CD/DVD or USB drive.
Strengths: Easy (3 steps: Download – Burn – Reset); Fast (Only 3 minutes even less); Safe (Read-only and non-destructive design, no any data loss or damage). Indeed, it is the best Windows 8 password recovery.
↧
↧
CD Rom shows up in Disk Manager, but no CD drive shows up
Narrative:
My computer is a Mac (MBP Retina 15") but my team sets up servers and some Windows support so I need it to work on both Mac and Windows.
I received my 2 ISOSticks today. Initially everything was fine on my Mac until I noticed that my card had a guid partition table and therefore the ISOstick would not work on Windows. I saved the config directory and the ISOs to a folder on my desktop and then re-formatted the card w/ MBR,FAT32,4K. I put the files back on the card and now the contents show up on windows and Mac, but the CD-rom drive never shows up. On windows the CD-rom is listed in the Disk Manager, but not in My Computer. Cards are 32GB and 64GB cards listed in compatibility list as working great. I made sure the txt file was names properly ("/config/iso_filename.txt") and opened it in notepad++ to make sure the text was ANSI. the ISO filename is correct and is in the root. The same ISO w/ the same iso_filename.txt worked before the swap to MBR instead of GPT.
TLDR:
On both my Mac and 2 windows machines the card shows up fine inside the device, but no CD-rom.
Not sure what the deal is here.
Side notes (not complaints, just observations):
1. When updating firmware both mine show up as "isostick emergency recovery (/dev/cu.usbmodem40121)" instead of what you said in the tutorial.
2. Figuring out the direction of the card was fairly easy by looking in the hole, but knowing how far to push it in wasn't. I thought that I would be pushing it in too far and either damage the connector or lose the card inside the device.
3. The crypticness/non-straightforward way this device works is fine for a Kickstarter thing, but I kinda expected something being sold on Amazon to be a little more polished. It almost seems easier to just keep carrying around a keyring full of 4GB usb sticks to install things from. :-(
↧
Get a trustworthy domain and website
I don't know about other people, but a website like https://sites.google.com/site/shamurxboot/ doesn't inspire to me any kind of trust.
Anyone can create a Google Site, yet I'm supposed to entrust installing my OS to software without a clear author ("Shamu"? Is that the author's name, or is it the whale, http://en.wikipedia.org/wiki/Shamu, or a joke?). After all, a tool that burns ISOs has the potential to be the ultimate trojan, as it could inject malicious code that executes before the kernel itself.
I'm not saying I don't trust XBOOT, but the current branding doesn't help. Here are some suggestions:
1. Publish the source code on a reputable repository like GitHub.
2. Get a domain name for XBOOT.
2. Get a decent website, with a modern trustworthy look. Twitter Bootstrap is great for open-source projects. http://www.coreboot.org/ is a website for a Linux/booting project that looks trustworthy and is done using Mediawiki (Wikipedia's engine).
Here's a web application that has access to very sensitive data - my Gmail. http://www.streak.com/
Yet it looks very trustworthy, so I trust it, and have been using it for over a year now.
↧
Crash Plan Pro Client
Is there a script for adding Crash Plan Pro Client to a boot disk?
↧
Easy2Boot Development Discussion
This thread is to discuss how the Easy2Boot (as it is currently called) grub4dos multiboot USB drive project can be developed, enhanced and improved.
The idea (from sambul61) is to create a multiboot USB drive to which the novice user can easily and quickly add any boot image he or she wants to their multiboot USB drive.
All that is needed is the correct grub4dos menu mnu file and the 'payload' file (an ISO in most cases). We, at reboot.pro can easily provide the required grub4dos menu file (called xxxxx.mnu for Easy2Boot) and so can provide a bank of these mnu files which can be kept up to date.
This project is similar to the grub4dos grub4dos, .iso images and (hd32) or (0xFF) mapping topic, but Easy2Boot will apply to any type of bootable binary that can be booted via grub4dos (or possible from grub4dos via syslinux) and will provide a .mnu file which the user simply copies to his Easy2Boot USB drive (no editing of their menu.lst required).
The user can delete the 'payload' files and leave the mnu files on the drive - the relevant menu entries will NOT appear on the user menu until the user chooses to add back on the payload file.
There is an embryo tutorial at http://www.rmprepusb...asy-to-maintain
Working and tested .mnu files can be posted at http://reboot.pro/16426/ (note that it is NOT a discussion thread - please use this thread for any any discussion).
Some points for discussion are (amongst others):
1. Is the name Easy2Boot OK? (if not we need to change it quickly)?
2. Do you think the idea will catch on and encourage multiboot newbies to have a go (and will you contribute mnu files with a few instructions for your favourite bootable binary?) - or is cut and paste and editing a menu.lst file not really that hard (even for a newbie)?
3. Is the choice of /_ISO for the main folder OK (again if not we need to change it quickly)?
4. What would make the best, generic, foolproof (multi-national) USER.mnu (the default menu settings) - currently I have this set to a UK kbd and a 'borrowed' background image just for test purposes.
5. Would someone like to donate a royalty free splashimage (maybe with Easy2Boot printed across it and reboot.pro?)
Please try out this tutorial and see how this process works (or doesn't) and report back!
The idea (from sambul61) is to create a multiboot USB drive to which the novice user can easily and quickly add any boot image he or she wants to their multiboot USB drive.
All that is needed is the correct grub4dos menu mnu file and the 'payload' file (an ISO in most cases). We, at reboot.pro can easily provide the required grub4dos menu file (called xxxxx.mnu for Easy2Boot) and so can provide a bank of these mnu files which can be kept up to date.
This project is similar to the grub4dos grub4dos, .iso images and (hd32) or (0xFF) mapping topic, but Easy2Boot will apply to any type of bootable binary that can be booted via grub4dos (or possible from grub4dos via syslinux) and will provide a .mnu file which the user simply copies to his Easy2Boot USB drive (no editing of their menu.lst required).
The user can delete the 'payload' files and leave the mnu files on the drive - the relevant menu entries will NOT appear on the user menu until the user chooses to add back on the payload file.
There is an embryo tutorial at http://www.rmprepusb...asy-to-maintain
Working and tested .mnu files can be posted at http://reboot.pro/16426/ (note that it is NOT a discussion thread - please use this thread for any any discussion).
Some points for discussion are (amongst others):
1. Is the name Easy2Boot OK? (if not we need to change it quickly)?
2. Do you think the idea will catch on and encourage multiboot newbies to have a go (and will you contribute mnu files with a few instructions for your favourite bootable binary?) - or is cut and paste and editing a menu.lst file not really that hard (even for a newbie)?
3. Is the choice of /_ISO for the main folder OK (again if not we need to change it quickly)?
4. What would make the best, generic, foolproof (multi-national) USER.mnu (the default menu settings) - currently I have this set to a UK kbd and a 'borrowed' background image just for test purposes.
5. Would someone like to donate a royalty free splashimage (maybe with Easy2Boot printed across it and reboot.pro?)
Please try out this tutorial and see how this process works (or doesn't) and report back!
↧
↧
Easy2Boot - post link to ANY live ISO or Floppy you want to boot
This topic is dedicated to forum members' Live Image Boot support requests. Ask here to supply a Grub4DOS Menu section for ANY bootable Image file or Distro like ISO, IMA, IMG or such, you want to boot, but don't know how, or if a generic Menu doesn't work for you. The idea is to make it easier for novices to try any Live Distro or PC Repair CD, and help start using Multiboot.We could have a new topic called 'mnu files for sambul's Multiboot disk', and rebooter's could post their mnu donations on it. So a standard expert's post would be a URL to the download for the 'image' file plus the mnu as an attachment. So we could build up a library of mnu files (instead of users having to add a menu entry to their menu.lst).
Instructions for a user would be:
1. Create a multiboot basic drive following instructions (e.g. use RMPrepUSB ...)
2. Download your ISO (or whatever and copy to your drive)
3. Download mnu file and copy it to the same folder
Some images will need special instructions (like extract folder xyz from the iso and copy it to xyz on the USB drive for some 'special' ISOs that won't boot from an ISO file!)
Do you want to try booting a new image from USB or HD on a real PC? You don't have to know anything about bootloaders like Grub4DOS or multiboot. Just post a link to your Image file here, add a few words what do you need this Image for, how it can be of interest to other members, what is your PC setup, and someone will try provide Grub4DOS Menu section for you "AS IS" or in a form of .MNU file that you can use automatically with RMPrepUSB tool, or add to your Grub4DOS Menu manually.
To make it easy, RMPrepUSB now includes Easy2Boot feature, explained in Tutorial #72. It allows a novice add a new Live Image to the USB Thumb in 2 easy steps, and an expert prepare .MNU file to help the novice (which is similar to small G4D Menu.lst). All you need is to format the Thumb or add Grub4DOS to it using RMPrepUSB (if not done yet), then copy a folder with your Image and posted here in reply to your request .MNU file to the Thumb, and the magic of Multiboot will open new horizons for you, allowing to repair, partition or backup your OS or HD, and easily try or install new Windows and Linux Distros you always wanted.
Copy more folders with new Image and Menu files anytime - next boot you'll see them in Boot Menu, which is auto compiled by Grub4DOS code installed by RMPrepUSB. Or delete the folders you don't need anymore. The Images you copy won't be unpacked, but instead booted directly from the original using Menu section you supplied. You can store many Images on the Thumb and boot any you choose. Just drop the folder to the Thumb - you don't have to know or do anything else for magic to work. For rare or unusual Images, you may be suggested by an expert to mount the Image with ImgDisk and extract a few files from it to make booting easier for Grub4DOS. In this case the .MNU file provided by the expert will contain instructions for Grub4DOS, where to place the extracted files - just drop them in the same folder with your original Image and copy to the Thumb.
Make sure you have enough contiguous space on your Thumb for new Images. If in doubt, use defragmenter like WinContig to check copied Images for fragmentation and defrag, or use a similar tool to defrag free space on the Thumb, making room for new Images. If you have suggestions how to improve this feature or bug reports, drop them in Easy2Boot project thread.
↧
Wipe Ram
I'm trying to use ImDisk to fill with zero the memory ram unused.
If I create a ramdisk with all available memory, I get this result?
I must also create a file of the same size?
There is another more direct software for this purpose?
↧
Not booting to isosel
Hey Guys,
So far I love my stick! I just have one question that's been bugging me....
According to my understanding, when you load the isosel bin file in the config folder you should be able to boot to isosel when you boot from the CD drive.
Right now my isostick just boots to what ever CD i have listed in the iso_filename file.
It's not a HUGE deal, but not having to edit that file every time I want to change CDs would be nice. Can I make the flash drive portion boot to ISOsel? is there something I'm missing?
So far I love my stick! I just have one question that's been bugging me....
According to my understanding, when you load the isosel bin file in the config folder you should be able to boot to isosel when you boot from the CD drive.
Right now my isostick just boots to what ever CD i have listed in the iso_filename file.
It's not a HUGE deal, but not having to edit that file every time I want to change CDs would be nice. Can I make the flash drive portion boot to ISOsel? is there something I'm missing?
↧
Add bluetooth Support in windows PE
Hi fnds!
I m new To reboot Forum. Today i fell great Cause of greate Project & Tools in reboot forum...ok fnds i have made a Pe with win7PESE Project. EveryThing Seems To work ok without bluetooth. I know which file are responsible with BLUETOOTH (IT may with bT**.* extention) i was able To install Bluetooth but was unable To Start bluetooth Support Service! I Also Tried greate Tool " MakePe3" but it also doesn't have bluetooth support! Is There Any Way To run BLUETOOTH under windows PE 3 ?????
@@@wimb, i Think Ur makePE3 IS SIMPLY AWOESOME BUT ITS needs To be improved...i found ur Media Version of PE was unable To load wdm graphics & Audio Driver... I Get *no Output Audio device installed* hope To fix it!
I m new To reboot Forum. Today i fell great Cause of greate Project & Tools in reboot forum...ok fnds i have made a Pe with win7PESE Project. EveryThing Seems To work ok without bluetooth. I know which file are responsible with BLUETOOTH (IT may with bT**.* extention) i was able To install Bluetooth but was unable To Start bluetooth Support Service! I Also Tried greate Tool " MakePe3" but it also doesn't have bluetooth support! Is There Any Way To run BLUETOOTH under windows PE 3 ?????
@@@wimb, i Think Ur makePE3 IS SIMPLY AWOESOME BUT ITS needs To be improved...i found ur Media Version of PE was unable To load wdm graphics & Audio Driver... I Get *no Output Audio device installed* hope To fix it!
↧
↧
Two scripts error
@ChrisR
Error with this two scripts 1-Explorer.script 039 and 3-Postconfig 026
[// we need to add Additional Options interface variables for the script to see] Run - Processing section: [CapiCommand] From file: [%BaseDir%\Projects\Win7PESE\Build\Common_Api.script] with parameters: [AddInterface],[%BaseDir%\Projects\Win7PESE\Shell\1-explorer.script],[Interface-Additional] Run - Failed to find section [CapiCommand_AddInterface] in file: [%BaseDir%\Projects\Win7PESE\Build\Common_Api.script] Halt Run - Processed section [CapiCommand] in file: [%BaseDir%\Projects\Win7PESE\Build\Common_Api.script] .......
[//- Write IsoName in Internal ini file MountPEmedia.ini. ISO boot, at startup MountPEmedia.exe checks if imdisk exist, if yes and if Iso filename (set in in MountPEmedia.ini) is available on CD-USB drives, it will mount it on drive Y.] Run - Processing section: [CapiCommand] From file: [%BaseDir%\Projects\Win7PESE\Build\Common_Api.script] with parameters: [AddInterface],[%BaseDir%\Projects\Win7PESE\Finals\4-iso.script],[Interface] Run - Failed to find section [CapiCommand_AddInterface] in file: [%BaseDir%\Projects\Win7PESE\Build\Common_Api.script] Halt
Regards
↧
New outdated Antivirus 7PE project!
outdated
↧
Layout of Modern Syslinux
Here is a bit of detail regarding the on-disk and in-memory layout of modern Syslinux, such as 4.06 and 5.00. This only applies to SYSLINUX- and EXTLINUX-based installations (the so-called "HDD variants").
- ldlinux.bin's physical (file) layout:
- Volume boot record (512 bytes).
BIOS or an MBR is typically responsible for loading a VBR and executing its code.
This contains code which the installer patches into a volume's actual boot record. The code ranges are:- [0, 2]
- [0x5A, 0x1FD]
- 512 bytes of padding, used for alignment purposes
- ldlinux.sys, which is:
- "Sect1" code (494 bytes). This contains a patch area, checksum, and code which is responsible for loading the rest of ldlinux.sys.
- At the end of "Sect1" is enough room (18 bytes) for at least one extent (10 bytes), which the installer populates with the location of the next chunk of ldlinux.sys. "Sect1" ranges from [0x400, 0x5FF] relative to ldlinux.bin or, relative to only ldlinux.sys, [0, 0x1FF]
- The entire extent map (which includes the previously-described 18 bytes of "Sect1") ranges from [0x5EE, 0xD6E] relative to ldlinux.bin or, relative to only ldlinux.sys, [0x1EE, 0x96D] (1920 bytes).
- The rest of the ldlinux.sys code is the rest of the Syslinux core. It includes the filesystem drivers, for example.
For Syslinux 5.00, some of what used to be "core" in Syslinux 4.06 has been moved out into ldlinux.c32, but this fact should be irrelevant, as long as that file is available in the filesystem that Syslinux is installed to.
- Volume boot record (512 bytes).
- ldlinux.bin's in-memory layout:
- VBR @ 0:0x7C00 (or wherever else a crazy BIOS might put it)
- 512 bytes of padding @ 0:0x7E00
- ldlinux.sys @ 0:0x8000
- "Sect1" @ 0:0x8000 (ranging [0x8000, 0x8200]
- Extent pointers @ 0:0x81EE (ranging [0x81EE, 0x896D])
- The rest of the code @ 0:0x896E
Enjoy!
So the sequence of events [roughly] goes:
- Syslinux VBR is loaded and executed by BIOS or MBR (or whatever else)
- VBR has an 8-byte LBA describing where the first sector (hence "Sect1") of ldlinux.sys lives. It loads and executes this sector
- "Sect1" has at least one extent (8-byte LBA + length) describing where the next sector of ldlinux.sys lives. It loads this sector.
- That next sector has more extents, so "Sect1" is able to load the rest of ldlinux.sys
↧
More Pages to Explore .....
