How to chage the start-up timeout ?Forum: HD Install Topic: How to chage the start-up timeout ? started by: winux Posted by winux on Jan. 21 2006,09:12
Hi guysLet me explain: after a long fight, I finally succeded my starting-up on HD w/o re-entering every time all my parameters (thx to the forum). I selected just one choice in menu.lst: the 800x600 one w/ timeout=1 BUT, for any reason after this "one second wait", I've got the message: "you passed an undefined mode number, press RETURN to see video mode, SPACE to continue or WAIT 30s" If I press SPACE, everything's fine finally BUT is there any way to reduce the 30s down to one second for instance? in order to make it fully automatic It's not vital, but "nice to have"!!!! Thx for the info Posted by cyberoidx on Jan. 21 2006,10:43
type vga=normal in the boot, along with other parameterseg: dsl vga=normal desktop=twm ... etc Posted by winux on Jan. 21 2006,11:29
Thx cyberoidx, I'll check that out
Posted by larkl on Jan. 21 2006,13:03
Have you tried editing menu.lst and setting it exactly how you want? In a frugal install, it's in /mnt/hda1/boot/grub/menu.lst after mounting /dev/hda1.
Posted by winux on Jan. 21 2006,13:37
That's a good question larkl because I did it. I masked in menu.lst (which is in my case in /cdrom/boot/grub. Very strange, it took me some time to find it out!) every screen definition except the one I wish 800x600. I try this nice s/w on an old Pentium MMX 200MHz, 1.5 G, 190 M Here are the significant lines on my menu.lst default 0 timeout 1 title DSL fb800x600 kernel /boot/linux24 root=/dev/hda1 quiet vga=789 noacpi noapm nodma noscsi frugal initrd /boot/minirt24.gz I turned my vga= from 788 to 789 (to have 24 bits color depth) It worked that way in live CD 800x600x24bits, but now it says: "you passed an undefined mode number ... I don't know exactly what to add/change? any idea? That would of course resolve the 30s timeout!!! and would be great Thx for your comments Posted by cyberoidx on Jan. 21 2006,14:54
turn vga=788 to vga=normal!!!!!!!!thats what you gotta do. It only affects the console... nothing much. Posted by winux on Jan. 21 2006,16:27
Jolly good cyberoidx, you DID IT!!!! It works fine, no time out .I don't understand then the use of other vga : 788, 789 what's that for?? the console, why? Anyway you solved one of my (numerous Pb!) Thx a lot Hope I'll find another clever guy to tell me how I authorize my cookies on Dillo!!! Have a nice day, Thx again Posted by mikshaw on Jan. 21 2006,16:48
It controls the resolution....the higher you go, the more (smaller) text you can fit on the screen.Look at the f3 file in boot: Color 640x480 800x600 1024x768 1280x1024 256 8 bit 769 771 773 775 32000 15 bit 784 787 790 793 65000 16 bit 785 788 791 794 16.7M 24 bit 786 789 792 795 Dillo cookies: < http://www.dillo.org/Cookies.txt > Posted by cyberoidx on Jan. 21 2006,16:51
Lol, neither did i.
Just use the firefox included, or use Mydsl to get Opera I dont think Dillo can handle cookies... i mean if you try some sites .. it does not even place the frames / table columns in proper layout. Dillo is just a basic browser. Remeber, experiment as much as possible. Trust me, i know how happy you feel when you solve stuff on your own.. Just use google. Posted by winux on Jan. 21 2006,17:39
Thx for Opera suggestion. I thought it was big, that's why I did not go thru it. Do you think Opera is lighter than FF? In that case I'll use Opera and uninstall FF to have a light install. What do you think of that? Bye Posted by winux on Jan. 21 2006,17:45
1- got it, Thx Mikshaw 2- thx also for the link, if no solution, I might go to the other suggestion w/ Opera. I'll read your link first Bye Posted by cyberoidx on Jan. 22 2006,02:02
Opera is way lighter than current FF. (3.5Mb VS 4.smth Mb)Also FF consumes way too much ram (50mb - 100mb on frinds PIV 2 Ghz 768Mbram) Posted by cyberoidx on Jan. 22 2006,02:03
Posted by winux on Jan. 22 2006,07:03
Thx for your 2 answers cyberoidx1- I might turn to Opera which is quite nice and less resources consuming .... good for my old PC 2- this cooky blocking happens from the beginning at the 1st window. It's a pitty because it's a quite quick browser!! |