Hello RegB,
thank you for testing!
On Nov 25, 5:05 am, RegB <2regburg...@earthlink.net> wrote:
> The .exe version appeared to install and detect my grub loader, which
> I was told to edit a file for. I was "paperless" at the time, so
> didn't write
> anything down. I wasn't remembering the specific instructions the
> next time I booted.
About the editing a file: this happens if you already have grub
installed as your bootloader.
In this case it is easier to add the system to your existing menu.lst
file. But that just involves to copy the lines
title Sage Live
find --set-root --ignore-floppies /Sage Live 511.46/initrd.gz
kernel /Sage Live 511.46/vmlinuz psubdir="Sage Live 511.46"
initrd /Sage Live 511.46/initrd.gz
into it.
>
> The .iso file booted OK from a CD and the browser came up fine.
> The notebook APPEARED to connect to port 8000, but <shift enter>
> didn't
> cause the cells to be evaluated.
About the browser not evaluating with shift-enter - this is completely
new to me, it had always worked so far. What are your keyboard
setting? [Menu]->[Desktop]->[Country Settings]
A small quirk of the "notebook Icon" is, that the browser starts some
(i think 6) seconds after the sage server, so eventually if the sager
server is to slow to start up you will get a "page not found" error.
In that case just hit the "Reload" button.
>
> I hope to have more time to put to it tomorrow - in the mean time, I
> agree
> it could pose reputation risk if folks get their MBR corrupted, or
> similar.
Hm, it is a missconception that the programm alters the mbr, that is
exactly not what the programm does (thats why it stopped in your case
and you have to edit your grub menu.lst by hand).
If there is the original Windows bootloader than it just adds the
entry to that bootloader (thats what I mean with: "hooks in"). In
Windows XP it will create an entry in the file boot.ini.
it will look like (example)
[boot loader]
timeout=5
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
c:\grldr="Start Sage Live"
in Windows 7 the following commands are executed:
bcdedit /export "C:\BCD Backup"
(backs up the BCD, for safety)
bcdedit /create /d "Start Puppy Linux" /application bootsector
(Adds the puppy entry)
This command returns an ID, The installer gets the ID.
bcdedit /set {ID} device "partition=C:"
bcdedit /set {ID} path \grldr.mbr
bcdedit /displayorder {Insert ID here} /addlast
(adds it to the menu)
bcdedit /timeout 10
(sets the timeout to 10 seconds)
So there is not really something *very* dangerous happening in the
code. NO repartitioning and NO messing with the mbr.
The grub is installed "after" the windows bootloader, so if you add
entries to the menu.lst you get a second boot menu.
In fact this can be used to very easily have several versions of the
system running. Just make a new folder and copy the files over. You
could make a "Sage Live Dev" Folder. And do your experimental work in
it. Or if the next version comes out, and you can spare 600 MB of
diskspace, keep the old sage version on the computer (its just +1
folder).
Do you want to move this discussion over to sage-windows or do you
want to discuss it here on sage-devel?
kind regards,
emil
>
> On Nov 24, 12:41 pm, David Kirkby <david.kir...@onetel.net> wrote:
>
--
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org
