We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience. Necessary Necessary. Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
The cookie is used to store the user consent for the cookies in the category "Analytics". The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary".
The cookie is used to store the user consent for the cookies in the category "Performance". It does not store any personal data. Functional Functional. Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
Performance Performance. Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors. Analytics Analytics. Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
Advertisement Advertisement. Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. The computer starts and I just get a text cursor blinking whenever I try to boot from it. I solved this by installing grub manually from another linux.
You can know the device name using fdisk -l run it only as root. Note: As I was doing this with many other things I'm not sure whether it's boot-directory or root-directory. Please edit the question if you know the answer. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?
Re: USB install no cd-rom error Post by bw » That's a common problem so be sure to search the forum. Offhand I'd say boot a live system from that tool and use dd to make a good usb like this?
Re: USB install no cd-rom error Post by bw » No, you can't use dd on windows that i know of. Can you boot a live system using that infernal utool, then use dd on another usb? There are probably several ways to solve the problem, search. They also have instructions on how to use tools in Windows to install Mint, or at least create, bootable media. The menu below gives the user 3 seconds to press the ESC key no timeout is displayed, the screen is just blank for 3 seconds.
If ESC is not pressed, then the submenu. If a key is pressed then the timeout will stop and the main menu menu. You can also require the user to enter a password after hitting F10 in order to get to the secret hidden main menu.
To determine what scan code you need for the any particular key combination, press c whilst in the grub4dos menu to get to the grub4dos command prompt, and then type. To have a single menu which contains some hidden entries that you can only see by pressing F10, use a menu. You will need to add the hotkey utility to the root of your USB drive which can be downloaded from here.
Note : To obscure the text in the menu. So before you go to the bother of reading this section, unless you really, really want to use GFXBoot, you should skip this section.
Although GFXBoot is good for providing attractive high resolution and high colour backgrounds, the menu features are limited and are not as flexible as the grub4dos menu system. Pressing F1 will produce some help mainly for linux users , F2 will allow you to change language but only English is available in the files I have provided.
More info on GFXmenu can be found here. This is how to change it and have your own picture:. The colours are specified in hexadecimal and are in three groups of two hexadecimal numbers — 0xrrggbb — 0x means that we are specifying a hex number, then we have rrggbb the first two numbers specify the red brightness, the second the green brightness and the third the blue brightness.
Hexadecimal numbers can thus range from 00 which means 0 in decimal and thus off to ff which means in decimal and thus maximum brightness — here are some colours and their hexadecimal equivalents:. Tip: You may have noticed that any error will make grub4dos go back to its default menu list when using a GFXMenu. Use the following lines at the top of the menu.
Alternatively, omit the title line but not the other 4 lines of text and the grub4dos text-based menu will never be displayed — it will always load the GFXMenu, even after an error. Now you can try some of the other tutorials on this website and add an extra menu entry into your menu.
Just pick any tutorial that takes your fancy and add the menu entries into your existing menu. See the reference section at the top of this page. Note that some of these options are not available when using the GFXMenu menu system — i. I suggest that once you have your GFXMenu background working, you comment out the line for it in your menu.
The instructions above should allow you to make a nice user menu, but what do the commands in the menu. Lets look at what we have, now that you have added Ylmf to the USB drive:.
What do these commands mean? The first line in each section begins with title xxxxx, and is fairly obvious! It is the text that is presented to the user as a menu item.
The second line in all these examples is a find —set-root command. Note that this command can cause problems if you happen to have the file it is looking for on both your hard disk and your USB pen. It is often better to create a file with a unique name e.
When grub4dos finds the file, it sets the current search path to that path — for instance if you had. Possible devices are u,p,n,h,f,c. If no floppy drive or cd drive is present, then using the —devices switch to force grub4dos to search those devices may cause long timeouts of several minutes! See the bottom of this page for how to avoid this.
The next line is a map command. BIOS devices are numbered where are floppy disks fd0-fd3,0xx9F are hd0-hd31, cd0 is 0xA0, etc. Here are the grub4dos device references and numbers:. A detailed explanation of these map ped virtual device names and lots more can be found here.
The map command takes effect when grub4dos comes to the end of a menu entry or executes the boot command. It will also take effect immediately within grub4dos if a map —hook command is executed.
It is important to understand how grub4dos maps your image. If this code tries to access a floppy disk drive, it will be accessing your image file instead.
So you can map a 1. However, if you try to map memtest. Similarly, if you try to map a binary program instead of a floppy disk image as fd0 it will fail to load. The map command will cause the file specified or device to be treated as a virtual device — any access to the device will cause a block seek to the correct place in the file — for this reason the file must be contiguous i.
The best way to fix this is run WinContig. Another way to get around this, is to use the map —mem command — If you use this command the ISO file does not need to be contiguous but the whole ISO will be loaded into memory by grub4dos which will be much slower and also requires the system to have more memory. For instance, the line. Note that if you map an ISO file or any file and the media is writable, it is possible to modify the contents of the ISO file, for instance.
If you then run the same line again then it will produce. Using ;; in a line is the equivalent of splitting the line into separate command lines, i. The grub4dos map command also supports. Only works if cd device is present.
If they do not boot correctly e. Here is the menu. Next line checks to see if we booted as a hard disk 80 and if so maps the boot device as a floppy disk. Note that this also maps your internal hard disk hd1 to hd0 and so when it boots from the new floppy device fd0 , DOS will see only one hard disk your internal hard disk and one floppy disk your USB drive. The next line is map —hook. This is where any previous map commands actually become activated and hooked into the BIOS.
The map —hook command changes the BIOS interrupt pointers so that an access to the virtual device will actually access the file or device specified by the map device commands. If no map —hook command is specified in the menu, it will be automatically executed when grub4dos boots, so there is no need to use map —hook unless you need to access the mapped device first. When setting a directory path, you must always include a device in the full path when using the root command e.
It is good practice to always use root before you use chainloader , because root can establish some parameters when the device is mounted which is then used by the chainloader command. If root fails then use rootnoverify instead, e. The kernel command is an instruction to load a linux kernel which expects to be loaded into memory in a certain way; also we can pass parameters and values to the kernel by using a command line type syntax on the same menu line which will get passed to the linux kernel.
The kernel and initrd commands should always be the last two commands. If you wish to suppress the loading messages produced by kernel and initrd then precede the kernel and initrd lines with. The final line in the Ylmf menu is initrd , this is an initial ramdrive which is a temporary filesystem used in the boot process of the linux kernel — initrd and initramfs are both commonly used to make preparations before the real root filesystem can be mounted. In this case it is set to the first partition of the virtual floppy disk drive which is the memtest As the memtest As we have mapped the whole file as a virtual floppy disk, when that boot sector code executes, it will try to access floppy disk sectors, but grub4dos has just mapped the floppy disk to the memtest Add —force if grub4dos gives an error due to a bad signature or incorrect format.
In this example, this line is actually not needed and the USB drive will boot to memtest without this line. Using root fd0 would fail though Error cannot mount selected partition.
When grub4dos finishes a sequence of commands in a menu. To check if a file is contiguous from within grub4dos, use the blocklist command. In the grub4dos menu, type C to get to the grub4dos command prompt and then use the blocklist command as shown below:.
With grub4dos, you can have multiple menus. The menu shown below will allow the user to load one of three sub-menus. TAG which you should place on the grub4dos boot drive. TAG anywhere, then it looks for menu. System memory locations can be read and obtained as a grub4dos variable like this:. The value obtained and placed in the variable m will be a bit 8 byte value.
Often you may wish to read the value of a single byte, word or dword 4 bytes , you can do this as follows. The md memory drive is directly mapped to system memory also.
Note : The physical memory address range from 1M to 32M is reserved for grub4dos internal code and data. The default drive number for rd is 0x7F which is a floppy device. Note that the ram drive base address will be set to the top of available memory by the map command regardless of what rd-base has been set. In and later versions of grub4dos, you can precede dd with the raw command which will prevent auto-decompression. Normally rd-size is set to 0x 4GB by grub4dos.
You do not need to change rd-size it in normal use. If you do change it, set it back to 0x afterwards. Recent versions of grub4dos see near end of the grub4dos readme file for more details also have the ability to set and use variables. Variable names can be a maximum of 8 characters.
0コメント