Andlinux Does Hard Reset


Bad_Bob

Still Fresh
Joined
Mar 15, 2006
Messages
1
I've seen andLinux in use and was really impressed by it.

I ran the "run_to_install.bat", and then "startup.bat" aper the instructions, but every time I run the "startup.bat" my box does a hard reset.

I've got Windows XP SP2.

Here is the output of the install bat file:
Code:
C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
un_to_install.bat

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
olinux-daemon.exe --install-driver
Cooperative Linux Daemon, 0.7.1-hn11
Compiled on Sun Jan  8 22:52:08 2006

driver already installed
daemon: driver installed

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em (For Beta1 - BUG316) colinux-daemon.exe @c:\and_gp2x\servicesettings.conf --
nstall-service andLinux

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em BUG316: Fix autodetection of (l)kernel memory vs. (w)available memory for In
o.  Make paths static until CoLinux corrects

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em         windows path issues (wa) and dynamic there-after (fx).

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em FTR112: Add detection of service status and alert on needed modifications (w
) or prompt for auto correction (fx???).

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em         Possibly post vote.

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
 
Bad_Bob posted on Mar 15 2006 at 04:00 PM said:
I've seen andLinux in use and was really impressed by it.

I ran the "run_to_install.bat", and then "startup.bat" aper the instructions, but every time I run the "startup.bat" my box does a hard reset.

I've got Windows XP SP2.

Here is the output of the install bat file:
Code:
C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
un_to_install.bat

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
olinux-daemon.exe --install-driver
Cooperative Linux Daemon, 0.7.1-hn11
Compiled on Sun Jan  8 22:52:08 2006

driver already installed
daemon: driver installed

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em (For Beta1 - BUG316) colinux-daemon.exe @c:\and_gp2x\servicesettings.conf --
nstall-service andLinux

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em BUG316: Fix autodetection of (l)kernel memory vs. (w)available memory for In
o.  Make paths static until CoLinux corrects

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em         windows path issues (wa) and dynamic there-after (fx).

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em FTR112: Add detection of service status and alert on needed modifications (w
) or prompt for auto correction (fx???).

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>
em         Possibly post vote.

C:\Documents and Settings\badbob\My Documents\bob\Downloads\linux\andLinux>

If the new download doesn't work for you, try lowering the amount of RAM for andLinux. andLinux requires at least 128MB of free memory to run. Open settings_static.txt and change mem=128 to mem=96. Also, try moving it to a folder that is shorter in length. i.e. c:\andLinux or something. Let me know if either works for you. I am working on the new version and will hold off on release until we find the cause.

David
 
Last edited by a moderator:
Bad_Bob posted on Mar 15 2006 at 11:00 AM said:
I ran the "run_to_install.bat", and then "startup.bat" aper the instructions, but every time I run the "startup.bat" my box does a hard reset.

I've got Windows XP SP2.
My system did the same thing, my solution was found at colinux's wiki. colinux wiki
coLinux 0.6.1 and XP SP2

Version 0.6.1 has an issue with PAE, which is enabled by XP SP2 (it implements DEP/NX, which activates PAE as well). If you want to use 0.6.1 with XP SP2 disable DEP/NX and PAE, by adding the switches /noexecute=AlwaysOff /NOPAE to your boot.ini BEFORE you install coLinux 0.6.1.
When it was all said and done, my boot.ini looked like this. Be sure to reboot after you make the changes.

[boot loader]
timeout=0
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" /fastdetect /noexecute=AlwaysOff /NOPAE
 
Last edited by a moderator:
zaq121 posted on Mar 20 2006 at 03:35 AM said:
My system did the same thing, my solution was found at colinux's wiki. colinux wiki
coLinux 0.6.1 and XP SP2

Version 0.6.1 has an issue with PAE, which is enabled by XP SP2 (it implements DEP/NX, which activates PAE as well). If you want to use 0.6.1 with XP SP2 disable DEP/NX and PAE, by adding the switches /noexecute=AlwaysOff /NOPAE to your boot.ini BEFORE you install coLinux 0.6.1.

I have emailed Henry to find out if this bug is back. It was fixed, but it is possible it is back. andLinux uses a modified version of CoLinux with many fixes/patches applied that aren't in the main branch yet.

David
 
Last edited by a moderator:
LordDavon posted on Mar 20 2006 at 08:27 AM said:
I have emailed Henry to find out if this bug is back. It was fixed, but it is possible it is back. andLinux uses a modified version of CoLinux with many fixes/patches applied that aren't in the main branch yet.
My guess is that it is. The very next paragraph after the one I quoted above...

This might apply to coLinux 0.6.2 too (FIXME: verify that claim) (Windows XP SP2 machines yielded very different results for me. The main machine I had been working on would reboot if I attempted to run coLinux without the bootflags. The other machine operated perfectly fine without them and would start coLinux without a hitch. The hardware was very similar but apparently different enough - the troublesome machine's behavior continued after a fresh install of XP. -- asmclean)
 
Last edited by a moderator:
zaq121 posted on Mar 20 2006 at 01:47 PM said:
LordDavon posted on Mar 20 2006 at 08:27 AM said:
I have emailed Henry to find out if this bug is back. It was fixed, but it is possible it is back. andLinux uses a modified version of CoLinux with many fixes/patches applied that aren't in the main branch yet.
My guess is that it is. The very next paragraph after the one I quoted above...

This might apply to coLinux 0.6.2 too (FIXME: verify that claim) (Windows XP SP2 machines yielded very different results for me. The main machine I had been working on would reboot if I attempted to run coLinux without the bootflags. The other machine operated perfectly fine without them and would start coLinux without a hitch. The hardware was very similar but apparently different enough - the troublesome machine's behavior continued after a fresh install of XP. -- asmclean)

You are correct, except that the bug was thought to be corrected in CoLinux 0.6.3. andLinux uses CoLinux 0.7.1. andLinux POC v1.0 was based on CoLinux 0.7.0 and this issue was never reported. This is not to say that it didn't exist, just that it is only being reported in POC v2.1. I am wondering if it is the move to a higher version of gcc that could be causing it.

Following the mailing lists it seems that CoLinux 0.6.3 does still have this issue. Most can correct with only /NoExecute=AlwaysOff. It looks like this affects recent Intel P4 machines (according to the documentation). I will update the Wiki.

David
 
Last edited by a moderator:
Back
Top