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

Difference between ESXI and IPXE

0
0

Dear All,

               I got help from this forum and booting images from ipxe.

But I came to know about esxi.

Will it also can be booted diskless from pc? like ipxe booting from lan?

 

Or it works like remote destop connection?

 

Aim is to boot from lan without hard disk? Can it be done in esxi?

 

plz let know...


Boot VHD or WinPE with grub2

0
0

I am trying to create a dual boot system for my public library computers using Steadier State as my starting point to boot Windows 7 Ultimate from a VHD file. The other OS is Linux Mint 17.

 

I have figured out how to do this, but I'm trying to perfect the approach.

 

Steadier State (SS) is a set of scripts designed by Mark Minasi to convert a system to run from a VHD file. It uses WinPE as a sort of "supervisor" that decides if bootmgr should boot the VHD file or WinPE. It does NOT provide the ability to always reboot to a standard "template" version of the OS, thereby ALWAYS discarding the snapshot.VHD file. However, I got around that by creating a one line shutdown script in Windows that uses bcdedit to switch the default bootmgr entry, so on shutdown that script sets the default to boot WinPE, which will perform the "rollback" and reboot to the snapshot.VHD file.

 

As I said it all works OK, except every system restart requires 2 boot cycles: 1) Boot WinPE; if no maintenance flag is set delete the snapshot.VHD file and use diskpart to recreate a new one against the parent image.VHD file. It then changes the boot\BCD file so the next boot will be the new snapshot.VHD boot entry in bootmgr. 2) Reboot to the freshly created snapshot.VHD file. This effectively "rolls back" all changes done in the last session of running Windows from the snapshot.VHD file.

 

Unlike wioski, which avoids this "double reboot" scenario using clever tricks with /unattend.xml and MDT in the setup / deployment, SS is not as sophisticated.

 

Now grub2 is a very capable bootloader that includes some limited scripting capabilities. If I could put the SS logic of what to boot into a grub2 script I might be able to eliminate the need for WinPE and therefore reduce the process to a single boot cycle.

 

I recompiled grub2 to include support for lua, a small scripting language used by many applications. I was hoping to copy into place the appropriate BCD and snapshot.VHD files before chainloading to bootmgr, which would put grub2 in the drivers seat completely in controlling whether to reboot to a pristine, new snapshot.VHD file or to boot WinPE if the maintenance flag (a file of a specific name is present or not) is set.

 

Unfortunately I discovered grub2 has zero filesystem write functionality, and therefore neither does the lua module as it relies on grub.run (there is no os. or io. object) to access the filesystem. So lua under grub2 won't help me it seems.

 

Could bootmgr be made to look in different places or in different files for its BCD info? If so can different grub2 menuitems be defiined to invoke bootmgr so it uses BCD.a for one menuitem but BCD.b for a different menuitem?

Help Choosing HDD Duplicator and Sanitizer

0
0

Hello! I'm looking an 2.5''/3.5'' SATA HDD duplicator and sanitizer. I'm interested in the following specifications:

  • display
  • sanitizer
  • duplicator
  • 2.5/3.5 SATA HDD support
  • USB 3.0 connection
  • maximum HDD size, right now we only use up to 2TB drives but in the future it will change to large disks
  • 3 or less slots (we only need two, a source drive and a destination drive)
  • interested in the lowest cost possible but if it is worth it, i'll buy it

 

Please make 2 recommendations: one being the best, and one being a cheap alternative that does some of the above. Also please make them from ebay as I can only buy from there.

 

Thank you

 

Command Line Tool to Create IMG Floppy Image

0
0

Hi guys! I'm looking for a way to automate the creation of a .img floppy image from a folder containing some files. 

I basically have folder X and I'd like to create an img image of 1440K size with a FAT partition containing the files from X folder. This will not be a one-time thing, it will be done very often so it needs to be automated.

 

Is there a command line tool for this job that you can share with me? 

Thank you

Create a windows system from scratch using Linux

0
0
I've been doing a lot of googling, and I feel like I am very close to an answer to the following:
 
I would like to do the following from Linux:
  • Partition a disk with NTFS, 2 partitions, a 300 MB system partition, and a 100 GB primary partition
  • Apply a wim image to the primary partition
  • do the equivalent of a BCDboot.exe command to make the system bootable.
Currently we do this in WinPE, but would like to do it in Linux because linux PXE boots a lot faster.
 
I assume I can use fdisk or gdisk in linux to do step 1, and wimlib-imagex to do step 2, but I am stuck on step 3....  Can anyone provide some insight?
 
 
Thanks!!

EDIT/NOTE - This topic has been split from the wimlib, with ImageX implementation thread.

mtools

0
0

Posted Image

File Name: mtools
File Submitter: Icecube
File Submitted: 12 Jan 2013
File Updated: 13 Jan 2013
File Category: Tools

Mtools is a collection of utilities to access MS-DOS disks from GNU and Unix without mounting them. It supports Win'95 style long file names, OS/2 Xdf disks and 2m disks (store up to 1992k on a high density 3 1/2 disk). In addition to file access, it supports many FAT-specific features: volume labels, FAT-specific file attributes (hidden, system, ...), "bad block" map maintenance, access to remote floppy drives, Iomega ZIP disk protection, "secure" erase, display of file's on-disk layout, etc.

Mtools' configurator file is stored in /etc/mtools.conf

FAQ: http://www.gnu.org/software/mtools/faq.html

Website: http://www.gnu.org/software/mtools/intro.html

Some mtools commands are shown in the following topics:
http://www.ultimatebootcd.com/forums/viewtopic.php?f=13&t=4077
http://reboot.pro/topic/14354-buidlingmodifying-floppy-images-with-mtools-as-replacement-for-winimageimdisk/

Click here to download this file

UEFI+GRUB2 where to get and how to mount

0
0

I´ve been testing EFI+GRUB2 ...

I've collected some versions of EFI´s from Windows 8/10 to test
booting from bootia32.efi or bootx64.efi and jump to bootmgr.efi, bootmgfw.efi, etc.

also grabbed the *.efi(s) binaries from Ubuntu, PartitionMagic, Tails, etc.
and tested some combinations in a UEFI boot Virtualbox VM, all working ok.
also download rEFInd and tested graphic menus... working fine


I now want to install all the stuff by hand (hard testing)
and using the most standard versions of available free tools

Anybody knows the site to get the binaries (bootia32.efi and bootx64.efi) to boot grub2...

also the best place to get the grub2 binaries...
and a good tutorial to mount this boot system

I want to make a multi-boot USB something like this...

EFI
    \BOOT
        \bootia32.efi
        \bootx64.efi
        \<grub-binaries>
        \<grub-background-image>
        \<grub-configuration-file>

    \Microsoft
    \Ubuntu
    \Tails
    \Kali
    ...

 

Possible bug or incompatibility in ImDisk

0
0

I use ImDisk to create a RAM drive for my %TEMP% folder in Windows. I was working on a NodeJS application which creates temporary files, and the latest version of NodeJS no longer works when attempting to write the files. Apparently they switched to another library which doesn't work with ImDisk, some more information is available here:

 

https://github.com/nodejs/node/issues/6861#issuecomment-226982491

 

My question is regarding the comment in that discussion:

 

I speculate that the GetFinalPathNameByHandle(VOLUME_NAME_DOS) call fails with ERROR_INVALID_FUNCTION. Libuv maps it to EISDIR for historic (and arguably wrong) reasons.

 
I can't say for sure but it's quite possibly a bug in the ramdisk driver. For example, if it doesn't support CreateFile(FILE_FLAG_BACKUP_SEMANTICS), then the GetFinalPathNameByHandle call is going to fail for directories and empty files.

 

Can anyone confirm if this might be a bug in ImDisk or if it's a compatibility problem? I read the Compatibility section on the ImDisk web site, and tried Arsenal Image Mounter, and that worked. Unfortunately AIM doesn't have any of the features that I use in ImDisk so it isn't really a viable replacement as far as I can tell... I've had other weird problems in the past with other applications as well, which may be due to something similar, which is really disappointing.

 

This is the command I use to create the RAM disk, in case it is something I am doing that causes this (I've tried various alternative commands and nothing solved the problem):

imdisk -a -t file -o awe,rem -s 4096M -S 4096 -m R: -p "/fs:ntfs /v:RAM /A:4096 /q /y"

Question about "correct" ImDisk usage/configuration

0
0

I love ImDisk and I use it for a few reasons:

  • A RAM-based system %TEMP% folder.
  • High-performance storage for downloads, compiling, or anything else.
  • Avoid slamming my SSDs with tons of writes (browser caches, temp files, etc.).

This is the command I use to create the RAM disk in a Scheduled Task that has a trigger set to run at startup:

imdisk -a -t file -o awe,rem -s 4096M -S 4096 -m R: -p "/fs:ntfs /v:RAM /A:4096 /q /y"

The questions I have (which I didn't see on the FAQ) are:

  1. I recently added "rem" to see if avoiding write caching would be faster, since RAM should be pretty darn fast on its own. Does anyone know if this is true?
  2. Is there a better way to create the RAM disk at startup than a Scheduled Task? I worry that it may not be early enough in the startup sequence. How does the toolkit create disks at startup?
  3. I "aligned" the sectors for performance by using 4K sector sizes, but I really don't know if this matters like it does with aligning partitions on physical disks. Does anyone know if this is useful?
  4. I don't want a file-backed disk, just RAM. The whole point (for me) is to use RAM instead of disk. I use "awe" without an image file so it actually uses physical RAM and not virtual memory. My understanding is that a "vm" type RAM disk could potentially be swapped to physical disk by the system. It this correct and can it be prevented?
  5. When using "vm", it doesn't allocate the RAM when you create the disk, so I don't really know how much free memory my system has. In the past, before "awe" was an option, I created the disk, filled it up with an empty file, then deleted the file in order to pre-allocate the memory... Is there a way to make it allocate the RAM without this when using "vm" type?
  6. The toolkit UI doesn't seem to support "awe" disks, based on the screenshots I've seen. Is this correct?

FAQs and How-Tos

0
0

This is a topic where I will collect frequently asked questions about ImDisk and related projects, together with answers or links to other topics with explanations, documentation etc.

  • I want a RAM disk to be automatically created and formatted when Windows starts up.

    Spoiler


     
  • I want my auto-created RAM disk to be pre-loaded with a disk image file.

    Spoiler


     
  • Image file for my auto-created RAM disk is small and I want RAM disk expanded to larger size automatically.

    Spoiler


     
  • How do I save a RAM disk as a disk image file from command line?

    Spoiler


     
  • I want a RAM disk that uses memory above 4 GB in 32 bit Windows. Can ImDisk do that?

    Spoiler


     
  • When I delete files from my RAM disk memory still seems to be used. What is wrong?

    Spoiler


     
  • I would like to mount a vhd file from Microsoft Virtual PC, Virtual Server, Hyper-V etc. Can ImDisk do that?

    Spoiler


     
  • I would like to mount an image file of another format, for example vmdk or vdi. Could ImDisk do that?

    Spoiler


     
  • I try to mount an image file named something.bin and it does not work. What could be wrong?

    Spoiler


     
  • My image file has a master boot record with partition table. When I mount it using Control Panel applet it asks me which partition to mount, but this does not seem to work from command line.

    Spoiler


     
  • I would like to mount a virtual disk to a subdirectory on my hard disk instead of using a drive letter. How to do that?

    Spoiler


     
  • When I try to use the rawcopy program to save disk contents as image file, I get corrupt image files that cannot be mounted later. What is wrong?

    Spoiler


     
  • I would like to script a silent install of ImDisk, but when I try imdiskinst.exe -y it still shows a message box at end of setup. Is there a way to avoid all kind of user interaction during setup?

    Spoiler


     
  • Is there any step-by-step guide to creating a RAM disk at system startup?

    Spoiler

"Ejecting" a removable ImDisk caused my drives to disappear

0
0

Another possible bug in 2.0.9. I'm using Win 8.1. I just created a "vm" type disk via:

imdisk -a -t vm -o rem -s 4096M -m E: -p "/fs:ntfs /v:RAM2 /q /y"

I did my test, then went into the explorer context menu and selected "Eject". The drive disappeared after 5-10 seconds, but so did all my other removable drives, even empty ones! I normally have about 8 of them due to a card reader, plus my normal RAM disk R. Now I only have C and D. I can still get to R if I type it in, but it doesn't show on the list of drives.

 

Has anyone else seen this behavior?

How to create BSOD Dump

0
0

Hi there

 

its not only because i have now an specific BSOD - but the question is interesting (for me)

 

First of all I defined a variable for the USB-Drive. In my case drvUSB.

Then I changed in the Registry in HKLM\System\Currentcontrolset\Control\CrashControl\DumpFile to %drvUSB%\memory.dmp

 

But even after booting and getting the BSOD there is no DumpFile here...

 

What have I´ve done wrong?

 

WinPE no longer working in legacy mode

0
0

In the past few days I had updated my WinPE image to the latest codebase and made a number of changes - all was working fine. Suddenly, the image no longer works in legacy mode - but loads fine in EFI.

 

What happens is the loading bar gets to the end, then as soon as the splash screen appears, it changes to the "Windows failed to start screen", with an 0xc0000098 error stating that \windows\system32\ntoskrnl.exe 'couldn't be loaded because the kernel is missing or contains errors'.

 

I can't for the life of me figure out what is causing this. It is not a bootloader problem (all MD5 hashed). The only thing I haven't been able to hash is the base image I use to compile the current image, but that loads fine on its own. So presumably one of the regkeys I am adding is broken (I don't know how since I didn't change anything since I last compiled an image!). 

 

Obviously noone here has the time to scratch their heads over all my modifications lol, I just made this post to see if anyone has encountered this problem before, as that may help me figure out what is doing it!

 

Cheers

multiPE

0
0

Posted Image

File Name: multiPE
File Submitter: pscEx
File Submitted: 28 Sep 2011
File Updated: 23 Nov 2015
File Category: Projects

multiPE is the first WinBuilder project which builds a PE from XP, Win2003, Vista, Win7 sources.
Currently only x86 sources are supported. From history, x64 source use is included in some scripts and perhaps may work. But full support of x64 is not intended for the near future.
x64 PEs do not offer remarkable advantages compared with x86 PEs (Which PE adresses more than 3 GB of memory?).
And they do not run on older 32-bit hardware.
Win8 is not taken into account as source. For me is is not suited to build a working rescue PE. And multiPE does not claim to build a light-weight Windows OS.

The project has three main parts:
  • Building the core. Depending on the source, fundamental files and registry entries are added to the target.
  • Adding custom apps and drivers
  • Building the final PE with PEFactory, either as single boot or as part of a multiboot media.
    boot media is optionally ISO (CD / DVD) or UFD
The build is 'complete' including shortcuts, associations, etc. No shortcut generation, registry entries etc. are necessary during boot. That decreases boot time.

Several 'Speed Up Functions' are new developed for the multiPE project. Revolutionary is the 'RamTarget' functionality. A small PE3 including internet access can be built in less than one minute (On my system in 40 seconds).

multiPE is one of the very few projects which support the standard WinBuilder 'Certificate' functionality. That helps the user to proof whether the used scripts are 'from author'.

Server for single script downloads with WinBuilder's Download Center: http://multipe.exec-se.de/
You should use the download center after a download of the whole project.
Maybe in the mean time some fixes / addons are added to the project.
Caution: To upgrade to a newer version, never use the "single file download of all files". In a new version sometimes structures / folder trees etc. are changed, and a single file upgrade can destroy the structures.
To upgrade to a new version, only use the download offered here, and download into an empty directory.

This page's internal download links for older versions do not work.
Older versions you can download from http://multipe.exec-se.de/Complete/

Actual (living) documentation: http://multipe.exec-...ltiPE/index.htm

The package contains WinBuilder 083, a slightly modified clone of the official WinBuilder 082.
Do not use WinBuilder 083 for other projects. It cannot be guaranteed that it works and does not cause any harm.

Click here to download this file

OpenWith.exe now working in WinPE 10

0
0

I have got OpenWith.exe working in WinPE 10, build 10.0.586.122, both 32-bit and 64-bit.

 

Only thing I haven't got working is the icons displayed next to the 'Open with' programs - I will update when I figure this out. The program itself works fine.

 

Registry dependencies

 

The below CLSID keys and their subkeys are accessed by a functional OpenWith.exe. Note that not all of these may be necessary - these are just the 'hits' I identified during analysis. I have added the necessary keys to a .reg file here (configured for HKLM\software) - http://www.mediafire.com/download/qh4i5tp5wd5ax55/OpenWith.reg

 

NOTE: I had to deploy the above from startnet.cmd. For some reason I couldn't add it during image build (some kind of odd permissions bug?)

 

All the other keys were already in my base image.

 

{00020424-0000-0000-C000-000000000046}
{0DEC7D0C-BD63-4759-AA64-ADEFD70DCF9A}
{1F486A52-3CB1-48FD-8F50-B8DC300D9F9D}
{20D04FE0-3AEA-1069-A2D8-08002B30309D}
{2155FEE3-2419-4373-B102-6843707EB41F}
{228826AF-02E1-4226-A9E0-99A855E455A6}
{4DB26476-6787-4046-B836-E8412A9E8A27}
{54E211B6-3650-4F75-8334-FA359598E1C5}
{603D3800-BD81-11D0-A3A5-00C04FD706EC}
{66742402-F9B9-11D1-A202-0000F81FEDEE}
{6E29FABF-9977-42D1-8D0E-CA7E61AD87E6}
{76765B11-3F95-4AF2-AC9D-EA55D8994F1A}
{83D6F579-4A45-439F-994E-7EC23C46B13E}
{83E94DBF-7F97-46B0-A6F0-360FE982BF83}
{94B23D4D-1040-4C4B-9081-85D8D6FA36C4}
{9AC9FBE1-E0A2-4AD6-B4EE-E212013EA917}
{A2C25004-96F4-4D49-B38E-6A52BE7E2F51}
{B196B286-BAB4-101A-B69C-00AA00341D07}
{B77B1CBF-E827-44A9-A33A-6CCFEEAA142A}
{C2F03A33-21F5-47FA-B4BB-156362A2F239}
{C90250F3-4D7D-4991-9B69-A5C5BC1C2AE6}
{D25D8842-8884-4A4A-B321-091314379BDD}
{E44E9428-BDBC-4987-A099-40DC8FD255E7}
{F324E4F9-8496-40B2-A1FF-9617C1C9AFFE}
 
DLL dependencies
 
I had to add the following:
 
\system32\OpenWith.exe and its MUI
\system32\twinapi.appcore.dll and its MUI
\system32\windows.ui.immersive.dll and its MUI
 
A number of other modules are loaded, but all of these were present in my base image.

UEFI W10 add another boot image

0
0
Hi,
 
I have a UEFI usb created for W10 install and I want to add another boot image (ISO) Sergei Strelec WinPE8.0 (x86/Native x86) WinPE10 (x64) English version
 
I was using it on the same bootable USB build for W8.1 setup (not UEFI): I've installed grub with RMPrepUSB,then copy Sterec files,W8.1 files and a .mnu file,all worked great
how to do trhe same but for UEFI?
thanks

Cannot find grldr in all drives

0
0

Try (hd0,0): NTFS5: No grldr

Try (hd0,1): NTFS5: non-MS: skip

Try (hd0,2): NTFS5: No grldr

Try (hd0,3): NTFS5: 2

BIOS: Drive=0x0, H=0, S=0

 

Try (fd0): non-ms: skip

Cannot find grldr in all drives. Press Ctrl+Alt+Del to restart.

 

I saw this error for the first time today. I am using GRUB4DOS 0.4.6a 2015-05-08. This is my computer in question (when it worked) You can see grub version if you pause it at exactly 24 seconds.

 

The error occured after I ran a check disk on the NTFS partition from OSX, Immediately I thought somehow my partition had wiped the grldr file so booted into PE environment command line and I copied it back to the partition and for safe measure re ran grubinst.exe --no-backup-mbr --skip-mbr-test -t=0 -v (hd0). But I could see the partition there, the files were untouched and a reboot continued to have the problem.

 

The issue persists, even though the grub files are sitting there and the MBR is obviously still grub4dos, and I can't see why this is the case?

 

I could just toast the whole thing and start again, but I would like to resolve it incase of future issues.

Odd issue with drive mounting

0
0

I have a few USB drives here of varying model. Using a script I compile my WinPE images and Windows installers onto them, add an NT6 MBR and bootsector using bootsect.exe, then set the drive as active. So they are all compiled in the same way.

 

Sometimes, after compiling, the WinPE images will work wonderfully - but installers won't work. They are mounted via ImDisk which is called from winpeshl.ini (a bit like the arrangement in the WinSetupFromUSB project)

 

I'm not sure if this is a bug with ImDisk, but what seems to happen is the mounted drive becomes inaccessible seconds after mounting. You can still view root folders but most of the time can't go inside them. This causes setup.exe to bug out in weird ways with various errors about not being able to install, sometimes even rendering artifacts.

 

The kicker:

 

a) Everything on these drives is MD5-hashed, and the working drives have identical contents to the non-working drives.

 

b ) Performing a diskpart clean on the non-working drives, then recompiling, will usually make them work properly again. However, the problem eventually seems to reoccur.

 

I don't think it's directly something with ImDisk, possibly some kind of weird MBR issue since the MD5s were the same? Has anyone ever had this problem?

 

Happens with the latest version of ImDisk and various older versions too.

 

Cheers

Eset Password Decoder

0
0

Posted Image

File Name: Eset Password Decoder
File Submitter: DarkPhoeniX
File Submitted: 17 Dec 2011
File Updated: 08 Mar 2015
File Category: Security

This tool Will decode the ESET password hidden in the registry.
It will also show you the ESET User Name And Create a log file.
This Software Cannot show The Password That Protects settings

So if you have forgotten your password you can get it back with this.
All alphanumeric passwords will be decoded as long as the password dose not exceed 20 characters.
Special characters are not Supported for Decoding
Note That Your Anti-Virus may Detect this as a False positive
Tested on Windows 7 32bit & Windows 8.1 64bit

Go to Support topic For Support

Notes:
ESET has detected this tool as "HackWare" but it is completely save.
Please Disable the antivirus.
if you are using V8 and up : go to Advanced Settings>Computer>HIPS and Disable "Advanced memory scanner"
Run as Administrator, if your UAC is on
The ZIP Password is: reboot.pro

Click here to download this file

project with grub4dos xp/xubuntu dual boot with hard drives

0
0

hello,

please allow me to fast-forward to today in the project, this requires attention/correction.
I don't see any sign of grub4dos.  all I see is grub2 in the title bar.  
I also need a prepared menu.lst (something I don't know how to do) placed in /boot/grub/

from the beginning:

the motherboard is an A8N-LA
it is working with 2g of pc3200 ram
two IDE/pata hard drives are being used because of the sata driver issue (an issue that has blocked me every time).

the project is a dual-boot xp and xubuntu using grub4dos to eventually boot both OS's.
to partition a hard drive and  install xp on a hard drive by itself.
the xp hard drive will be on the end connector on a ribbon cable, jumpered as master.
then connect another hard drive to the middle connector, jumpered as slave and partition and install xubuntu.  grub2 will, at this time, be the bootloader.
then install grub4dos on the hard drive, with the intention of using grub4dos as the boot manager.  I prefer to remove grub2 entirely, but am willing to wait and see how this goes.  if leaving grub2 has any benefit, I am open to leaving it on.

I have now installed xp on a maxtor 6L020L1 and xubuntu on a quantum fireball ct1515

below I provide more relevant info

in the bios, under main tab
------------------------------------------------------------------------------------------
*first channel device 0                 maxtor 6L020L1
*first channel device 1                 quantum fireball
*second channel device 0                none
*second channel device 1                none
*third channel device 0                 plextor dvdr
*fourth channel device 0                none
*fifth channel device 0                 none
*sixth channel device 0                 none
------------------------------------------------------------------------------------------
under boot tab

------------------------------------------------------------------------------------------
1st boot device                         HDD group
2nd boot device                         CD-ROM group
3rd boot device                         floppy group
4th boot device                         network boot group

*floppy group boot priority             not installed
*CD-ROM group boot priority             plextor dvdr
*HDD group boot priority                maxtor 6L020L
*network group boot priority            not installed
------------------------------------------------------------------------------------------
when highlighting 'HDD group boot priority' and pressing 'enter', this is offered

1. 1st master:                          maxtor 6L020L
2. 1st slave:                           quantum fireball ct1515
------------------------------------------------------------------------------------------

more:
1. boot.ini from xp

[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
 
2. fdisk -l  from xubuntu

ed@ed-ER919AA-ABA-SR1820NX-NA620 ~ $ sudo fdisk -l
[sudo] password for ed:

Disk /dev/sda: 20.5 GB, 20547841536 bytes
255 heads, 63 sectors/track, 2498 cylinders, total 40132503 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00051fc1

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *          63    20482874    10241406    7  HPFS/NTFS/exFAT

Disk /dev/sdb: 17.4 GB, 17360093184 bytes
255 heads, 63 sectors/track, 2110 cylinders, total 33906432 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000643db

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048    17577983     8787968   83  Linux
/dev/sdb2        17577984    20508671     1465344   82  Linux swap / Solaris

Disk /dev/sdc: 4022 MB, 4022337024 bytes
124 heads, 62 sectors/track, 1021 cylinders, total 7856127 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0004cd04


3. installation of grub4dos
 a. grldr placed in root of /dev/sdb1
 b. bootlace.com installed at /dev/sdb - NOT installed on sda, xp hard drive maxtor 6L020L  
 


sudo su

cd Desktop

./bootlace.com /dev/sdb

in case of permission error message:
 


sudo chmod 0777 bootlace.com

extra info.
to place grldr in root:
it should also be on desktop
 


sudo su

cd Desktop

cp grldr /


the OS's boot up fine with grub2, but, of course, that's not what I want.  all hardware is working properly.

problems that now exist:
I don't see any sign of grub4dos.  all I see is grub2 in the title bar.  
I also need a prepared menu.lst (something I don't know how to do) placed in /boot/grub/


any advice, suggestions, or info is most appreciated.

 

Viewing all 6812 articles
Browse latest View live




Latest Images