Purpose: Allow GRUB to Be Booted from NT/2K/XP This Tool Modifies

Total Page：16

File Type：pdf, Size：1020Kb

GRUBINSTALL README Purpose: allow GRUB to be booted from NT/2K/XP This tool modifies the GRUB stage1 and stage2 image files located on an NTFS or FAT volume, to make them bootable by NTLDR. Author: [email protected] Acknowledgements: * The AUTHORS of GNU GRUB 0.93 for creating GRUB * Samuel Leo for writing fsys_ntfs.c * Leonid Lisovskiy for writing fsys_iso9660.c * Gary Ng for updating the GRUB makefiles for NTFS+ISO9660 * Chris Semler and Tobias Svensson for testing Limitations: booting OS'es from NTLDR requires stage1 to be on the same partition as NTLDR itself. Make sure that stage1 and stage2 are NOT on a compressed volume, and that the files are NOT compressed by Windows. Usage: let's say C: is the first partition on the first harddisk hence (hd0,0) is the GRUB name of this partition and C:\boot\stage1 is the NT name of the boot file * To make the files stage1 and stage2 bootable from NTLDR: C:\> grubinstall -d (hd0,0) -1 C:\boot\stage1 -2 C:\boot\stage2 When stage1, stage2, menu.lst are in C:\, use the following C:\> grubinstall -d C: * To make the installer detect the install location itself: C:\> grubinstall -a -1 C:\boot\stage1 -2 C:\boot\stage2 * To make a boot floppy in A: (B: is not supported) C:\> grubinstall -b -1 C:\boot\stage1 -2 C:\boot\stage2 Changes: 0.3: - first released version 0.4: - added experimental FAT support (not released) - added support for DOS partition names (ie. "C:" instead of "(hd0,0)") this works only on windows XP 0.5: - fixed bug with NTFS: hardcoded partition offset and clustersize replaced by information exposed by fsys_ntfs.c - fixed FAT support - added support for DOS path names (ie. C:\boot\stage1 instead of "C:/boot/stage1"); - code cleanup 0.6: - removal of quotes from command line - support for writing to a diskette 0.7: - bugfixes for win32_filepos and current_pos - corrected debug info: use format %I64u (MSVCRT.DLL) instead of %llu (glibc) - added option to write to a bootdisk image to a file 0.8: - added autodetect '-a' command line option to probe disks+partitions 0.9: - renamed ntfsinstall to grubinstall - improved support for DOS names grubinstall -d C: - somewhat improved (?) error messages - added an alternate grub name option 0.9b: - corrected GRUB names (use PartitionNumber instead of entry number) - added '-B' option, so now it can be installed on any drive - -m '' now works to install without menu 0.9c: - fix bug in using PartitionNumber (of OBI1 type :-) 0.9d: - no changes. 9c contained a debug-version of stage2 1.0: - no changes. 1.01: - compile in bugfix for fsys_ntfs.c from original author (http://savannah.gnu.org/bugs/?func=detailitem&item_id=8669) .

Copy Link

Recommended publications

Operating System Boot from Fully Encrypted Device
Masaryk University Faculty of Informatics Operating system boot from fully encrypted device Bachelor’s Thesis Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot- ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de- scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction ............................1 1.1 Thesis goals ..........................1 1.2 Thesis structure ........................2 2 Boot Process Description ....................3 2.1 Early Boot Process ......................3 2.2 Firmware interfaces ......................4 2.2.1 BIOS – Basic Input/Output System . .4 2.2.2 UEFI – Unified Extended Firmware Interface .5 2.3 Partitioning tables ......................5 2.3.1 MBR – Master Boot Record .
[Show full text]
Version 7.8-Systemd
Linux From Scratch Version 7.8-systemd Created by Gerard Beekmans Edited by Douglas R. Reno Linux From Scratch: Version 7.8-systemd by Created by Gerard Beekmans and Edited by Douglas R. Reno Copyright © 1999-2015 Gerard Beekmans Copyright © 1999-2015, Gerard Beekmans All rights reserved. This book is licensed under a Creative Commons License. Computer instructions may be extracted from the book under the MIT License. Linux® is a registered trademark of Linus Torvalds. Linux From Scratch - Version 7.8-systemd Table of Contents Preface .......................................................................................................................................................................... vii i. Foreword ............................................................................................................................................................. vii ii. Audience ............................................................................................................................................................ vii iii. LFS Target Architectures ................................................................................................................................ viii iv. LFS and Standards ............................................................................................................................................ ix v. Rationale for Packages in the Book .................................................................................................................... x vi. Prerequisites
[Show full text]
Estudio De Producción Multimedia Con GNU/Linux”
No. 03 Vol. 02 ABRIL / 2008 /etc/init.d/uxi start Y Cuba qué con el: “¿Por qué escoger Symfony?” MaryanLinux Noticias Migración .::página 8::. “Estudio de Producción Multimedia con GNU/Linux” Soluciones de esta edición “Instalar GRUB no en el Master Boot Record” Programación “Replicación Master-Master con MySQL 5.0 en Debian Etch”(Parte I) Entrevista ¿X? “Al Software Libre ¿por qué migrar?”(Parte II) 22000088 Humor Libre .::página 22::. Eventos “Cuba en el FLISoL 2008” Informática 2007 “Revisión de la legislación cubana para el uso y desarrollo del Software Libre Estudio de Producción en Cuba” Multimedia con GNU/Linux “Syslog Centralizado con detección de eventos” “Firewall de alta disponibilidad” .::página 9::. “Publicar nuestro software: único camino hacia la libertad plena” Jefe Consejo Editorial: Arte y Diseño: Abel García Vitier Angel Alberto Bello Caballero [email protected] [email protected] Editores: David Padrón Álvarez [email protected] Jorge Luis Betancourt González [email protected] Ezequiel Manresa Santana [email protected] Gustavo Javier Blanco Díaz [email protected] Karla Reyes Olivera [email protected] Félix Daniel Batista Diñeiro [email protected] Yosbel Brooks Chávez [email protected] Redacción: Yailin Simón Mir [email protected] Elisandra Corrales Estrada [email protected] Marisniulkis Lescaille Cos [email protected] Revisión y Corrección: MSc. Clara Gisela Scot Bigñot [email protected] Dunia Virgen Cruz Góngora [email protected] MSc. Graciela González Pérez Coordinadores: [email protected] Ing. Abel Meneses Abad [email protected] Rislaidy Pérez Ramos [email protected] Eiger Mora Moredo [email protected] Victor Frank Molina López [email protected] Patrocinadores: Proyecto de Software Libre Grupo de Producción FEU MaryanLinux: Distro de Facultad X Linux basada en Ubuntu Estimado Lector: Llega a usted otro número de UXi cargado de información referente al Software Libre.
[Show full text]
Aurora Documentation Release 0.2.0
Aurora Documentation Release 0.2.0 Luis Felipe López Acevedo, aka sirgazil March 20, 2014 Contents 1 Audience 3 2 Contents 5 2.1 Overview.................................................5 2.2 Installation................................................5 2.3 Configuration...............................................5 2.4 Appendix A: Copying.......................................... 11 i ii Aurora Documentation, Release 0.2.0 Aurora is a visual theme for gNewSense. The current documentation describes a proposal for version 4 of the operating system. Contents 1 Aurora Documentation, Release 0.2.0 2 Contents CHAPTER 1 Audience This project files and the accompanying documentation are intended for developers of gNewSense 4. These files are probably not suited to end users of gNewSense. They will, however, be able to use Aurora as the default theme on the system if it is accepted. External links: Source files| Downloads| Report issues 3 Aurora Documentation, Release 0.2.0 4 Chapter 1. Audience CHAPTER 2 Contents 2.1 Overview gNewSense is an operating system based on Debian. The upcoming version of gNewSense, version 4, will be based on Debian 7, also known as Wheezy. As a derivative, gNewSense needs to modify some components of the system so that they look like gNewSense and refer to gNewSense resources instead of Debian’s. Aurora is a visual theme for gNewSense made to replace Debian’s default appearance. It includes wallpapers, back- ground images for different components of the system, an icon theme and themes for different desktop environments such as GNOME, KDE and Xfce. 2.1.1 System installer 2.1.2 Boot loader 2.1.3 Desktop themes 2.2 Installation Download and install Aurora’s packages: • aurora-backgrounds_0.2.0-1_all.deb • aurora-icon-theme_0.2.0-1_all.deb • gnome-aurora-theme_0.2.0-1_all.deb • grub-aurora-theme_0.2.0-1_all.deb Or download the source tarball if you prefer to install the files manually.
[Show full text]
Author: Angelo Fraietta (Angelo [email protected]) Address
Author: Angelo Fraietta ([email protected]) Address: PO Box 859, Hamilton NSW, 2303 Submission Category: Paper – Abstract reviewed Title: “Smart budgeting for a Smart Controller” Keywords: Algorithmic Composition; MIDI Controllers; Recycled Hardware; Software In 1998, I was involved in two collaborative projects -- the “Laser Harp1” and the “Virtual Drum Kit”2 -- where performers controlled MIDI sound engines using MAX and analogue to MIDI converters. In both cases, analogue signals were converted into MIDI messages, manipulated with an algorithm through MAX, converted back to MIDI, and finally sent to an external sound engine. At least three separate pieces of equipment3 were required for a performance; each introducing associated software and hardware costs, physical space requirements, and latency in performance. Space restrictions could be reduced by using alternative control voltage (CV) to MIDI converters, such as the I- Cube or some other custom device; however, these devices still require the use of an algorithmic or programmable logic control (PLC) software package on a host computer in order to execute all but the simplest of algorithms or patches. Although one could use a laptop computer, “weight and size isn't everything when it comes to stage (or touring) fitness. The plastic casing and the display on hinges sure don't encourage one to drop the PB [Power Book] from a table.”4 Ultimately, some sort of stand-alone device or “Smart 1 Alex Cockburn. The Laser Harp is an instrument that is performed by cutting laser beams with the body. 2 Guy Robinson. The Virtual Drum Kit entails a performer playing an invisible drum kit.
[Show full text]
Server Support Interview Questions and Answers Guide
Server Support Interview Questions And Answers Guide. Global Guideline. https://www.globalguideline.com/ Server Support Interview Questions And Answers Global Guideline . COM Server Support Job Interview Preparation Guide. Question # 1 Tell me where are cluster logs stored? Answer:- Please share your answers. Read More Answers. Question # 2 What are the Logical / Physical Structures of the AD Environment? Answer:- Active Directory Logical components are Forests, Trees, Domains, OUs and Objects. Active Directory Physical components are Domain Controllers, Sites and subnets. Read More Answers. Question # 3 What applications or services use AD application partitions? Name a couple? Answer:- Application partition contains the information of application data and other data related to application as well. But it does not contain any data related AD object such as USER, COMPUTER and GROUP. The saved data will be replicated to some of the particular DC not to all the DCs. Read More Answers. Question # 4 What are the types of hard disks used in servers? Answer:- Mostly we use scsi hardrive in server due few reason to it, high scalability & flexibility in raid array, faster from other type of hdd interface like-sata,ata,ide also it reliable & compatible with older scsi devices Read More Answers. Question # 5 What are some of the command-line tools available for managing a Windows 2003 Server/Active Directory environment? Answer:- Command Line Tools 1) GPupdate 2) Where 3) SystemInfo 4) CSVDE 5) LDIFDE 6) CMDCONS 7) Ipconfig 8) RoboCopy 9) CMDHere 10) PathPing Read More Answers. Question # 6 What if a FSMO server role fails? Answer:- FSMO roles are important role in server .
[Show full text]
How Will You Troubleshoot the Issue? What Are the Steps to Followed? A
1. A user in a corporate network contacts service desk saying he/she has lost network connectivity: How will you troubleshoot the issue? What are the steps to followed? A. First I will check the network cable is plugged in or not. Then check the network connections and the ip address is assigned or not. Then check connecting to website or not. IP conflict. 2. A User calls in and complains that her computer and network is running very slow. How would go about troubleshooting it? A. 3. How would you create an email account for a user already in AD? A. Open Microsoft Outlook if you are using office 2000, and click on "Tools" tab. Go to "Email Accounts". There you can find two option like Email and Directory. Click on "Add a new Account" and click next. If you are using Exchange Server then click over there, this depends on that particular Organization. According to the their setup you have to choose. And if you are using POP3 server then next popup will come along with your name, email address POP3 and SMTP IP address, Password etc. and after that click on Next and finish it..... 4. A PC did not receive an update from SMS. What steps would we take to resolve this? A. If SMS not updated in client system. 1. Need to check system getting IPaddress or not. 2. Need to check system in domain or not 3.Ensure that windows firewall should be off. 5. How do you set the IP address by using the command prompt A.
[Show full text]
Boot Problem Solutions B 102/1
B102.qxp_July 2018 25/05/2018 10:00 Page 23 BcdEdit: Boot Problem Solutions B 102/1 If Windows Goes on Strike while Booting Up: Use BcdEdit to Take Back Control Using the information given in this article you will be able to: Edit your Windows system’s boot configuration, Remove an old operating system from the boot menu, Restore a faulty boot sector using BootRec. On Windows XP, you could change the boot menu and configure the process simply by editing the BOOT.INI file. This was especially useful if you had a multi- boot system, and needed to quickly change the options displayed in the menu when you start up your PC. With the introduction of Windows 7, everything changed, and modifying your boot menu became much more complicated than editing a single file. That’s because Microsoft replaced the BOOT.INI file with the BCD (Boot Configuration Data) database. Unfortunately, this data could no longer be edited with a text editor and now it is only possible to make configuration changes using the BcdEdit tool. In this article, I’ll show you how to use the BcdEdit program in order to add operating systems to the boot configuration data, or remove entries from the list of displayed operating systems. • BcdEdit: The New Boot File Editor in Windows .... .......... B 102/2 • BcdEdit: The Boot Configuration Data Editor .... ............. B 102/4 • You Should Know these BcdEdit Parameters ..... ............. B 102/5 • Manage Multi-boot Systems Using BcdEdit .... ............... B 102/8 • How to Rescue Windows 10, 8.1 & 7 Multi-boot Systems ..
[Show full text]
Windows Embedded Standard 2009 Prepkit
MCTSi Exam 70-577 Windows Embedded Standard 2009 Preparation Kit Certification Exam Preparation Automation Not for resale. ii Published by Microsoft Corporation One Microsoft Way Redmond, Washington 98052-6399 This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT. The information contained in this document represents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publica- tion. Information in this document, including URL and other Internet Web site references, is subject to change with- out notice. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmit- ted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any pur- pose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. Copyright © 2009 Microsoft Corporation. All rights reserved. Internet Explorer, Microsoft, MS-DOS, Visual Studio, Win32, Windows and Windows Vista are trademarks of the Microsoft group of companies.
[Show full text]
The Evolution of TDL: Conquering X64
The Evolution of TDL: Conquering x64 Revision 1.1 Eugene Rodionov, Malware Researcher Aleksandr Matrosov, Senior Malware Researcher 2 2 CONTENTS 3 INTRODUCTION ..................................................................................................................................................... 4 1 INVESTIGATION ............................................................................................................................................. 5 1.1 GANGSTABUCKS ............................................................................................................................................... 6 2 INSTALLATION ............................................................................................................................................. 11 2.1 INFECTING X86 SYSTEMS .................................................................................................................................. 11 2.2 INFECTING X64 SYSTEMS .................................................................................................................................. 13 2.3 THE DROPPER’S PAYLOAD ................................................................................................................................ 14 2.4 COMPARISON WITH TDL3/TDL3+..................................................................................................................... 15 3 THE BOT .....................................................................................................................................................
[Show full text]
The Multiboot Specification Version 1.6
The Multiboot Specification version 1.6 Yoshinori K. Okuji, Bryan Ford, Erich Stefan Boleyn, Kunihiro Ishiguro, Vladimir 'phcoder' Serbinenko Copyright c 1995,96 Bryan Ford <[email protected]> Copyright c 1995,96 Erich Stefan Boleyn <[email protected]> Copyright c 1999,2000,2001,2002,2005,2006,2009,2010 Free Software Foundation, Inc. Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided also that the entire result- ing derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified versions. Chapter 1: Introduction to Multiboot Specification 1 1 Introduction to Multiboot Specification This chapter describes some rough information on the Multiboot Specification. Note that this is not a part of the specification itself. 1.1 The background of Multiboot Specification Every operating system ever created tends to have its own boot loader. Installing a new operating system on a machine generally involves installing a whole new set of boot mech- anisms, each with completely different install-time and boot-time user interfaces. Getting multiple operating systems to coexist reliably on one machine through typical chaining mechanisms can be a nightmare. There is little or no choice of boot loaders for a particular operating system | if the one that comes with the operating system doesn't do exactly what you want, or doesn't work on your machine, you're screwed.
[Show full text]
[ [ [ {[email protected]}
UNDERSTANDING WINDOWS 2K SOURCES (part 1) Written By: AndreaGeddon [www.andreageddon.com] [www.reteam.org] [www.quequero.org] {[email protected]} :: INTRO :: This is the first of a series of articles in which I will deal a little bit in detail with the windows 2000 kernel. In particular I will refer to the stolen sources that have been published. For obvious causes I shall not write the code directly in this article, but I will make precise references to the files I will describe, so if you have the sources you will find easy it easy to understand this text. :: REQUIREMENTS :: Well, first of all it would be good if you have the sources, if you don’t have them you can read the article the same as it will have a quite generic stamp. Second, you have to know hardware x86 architecture basics, infact I will not deal with things like IDT etc, so get your Intel manuals and study them! Last, I will assume you have some basic knowledge about an operating system, that is you know what is a file system, what is a scheduler and so on. Now we can begin. :: BIBLIOGRAPHY :: Here are some books on the argument that I advise you to read: • The Windows 2000 Device Driver Book - Art Baker, Jerry Lozano • Inside Windows 2000 - Russinovich, Solomon (sysinternals) • Windows driver model - Oney • Windows NT Native Api - Gary Nebbett • Undocumented Windows NT - Dabak, Phadke, Borate • Windows NT File SYstem Internals - Nagar • Windows NT Device Driver Development - Viscarola :: THE BEGINNING :: The source leak is dated on the first ten days of february, with the direct responsibility for it, being Mainsoft; an old partner of Microsoft.
[Show full text]