Menu
▾
▴
Re: [coLinux-users] coLinux-users Digest, Vol 68, Issue 7
|
From: Johann P. <joh...@gm...> - 2012-01-10 08:40:19
|
Letze Mail ging leider an die Falsche Adresse. Bitte löschen wenn das möglch ist. Johann Pascher 2012/1/10 Johann Pascher <joh...@gm...>: > Hallo Martin, > > sehr schön, dass du dich meldest. > > Das ist halt so, dass sich keiner meldet ich bin da keine Ausnahme. > Ich hab wohl hin und wieder mal and dich gedacht aber zu einer Mail > hat es ohne egoistischen Grund auch nicht gereicht. > Bei mir ist es halt so dass ich auch nicht unnötig blöd irgendwas > schreiben will. > Bei anderen wird es ähnlich sein, man müsste die einzelne Personen > selber ansprechen. > Jeder ist zu sehr im System eingespannt, und wir passen da halt mit > Krankheit oder Ruhestand nicht wirklich mehr hinein. > > Ich müsste mal bei dir wieder vorbeischauen dann könnte man darüber > sicher einiges ausführlicher besprechen. > Komischerweise bin auch ich wieder ziemlich eingespannt, zumindest aus > meiner Sicht, auch wenn mir direkt keiner was anschafft. > Ich unterbreche hier mal ... mein Anliegen kommt später das rennt nicht davon. > > Mal sehen was Heute anliegt, hab erst gefrühstückt. > > bis später Hannes > > > 2012/1/9 <col...@li...>: >> Send coLinux-users mailing list submissions to >> col...@li... >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> or, via email, send a message with subject or body 'help' to >> col...@li... >> >> You can reach the person managing the list at >> col...@li... >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of coLinux-users digest..." >> >> >> Today's Topics: >> >> 1. Re: Colinux Blue Screen Crashes (Bob Wheater) >> 2. Re: Colinux Blue Screen Crashes (Miller, Shao) >> 3. Re: Colinux Blue Screen Crashes (Bob Wheater) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Mon, 9 Jan 2012 15:04:08 -0500 >> From: "Bob Wheater" <bwh...@my...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: <col...@li...> >> Message-ID: <003401cccf09$d9d87a40$8d896ec0$@net> >> Content-Type: text/plain; charset="iso-8859-1" >> >>> Vincent Rivi?re wrote: >> >>>My complete boot.ini line is: >> >>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP >> Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >> >> >> >>>To check if PAE is actually on or off, look at the >system properties >> (Win+Pause), on the General tab (the >default one). Look at the bottom, >> after the line with >frequency and amount of RAM. If "Physical Address >>>Extension" >> >>>is written, then PAE is on. If there is no such text, >PAE is off. >> >> >> >>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check >> it is actually disabled and see if >coLinux works better. >> >> >> >> My general tab on the system properties does NOT have ?Physical Address >> Extension?. >> >> >> >> You seem to be confusing PAE with DEP (Data Execution Prevention). See >> http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx >> >> The /noexecute switch controls DEP. >> >> >> >> However DEP may only apply to windows server 2003 and not XP. >> >> >> >> ? The PAE mode kernel requires an Intel Architecture processor, Pentium Pro >> or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows >> Server 2003.? >> >> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 >> >> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb >> and greater systems. >> >> >> >> Regards, >> >> Bob >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 2 >> Date: Mon, 9 Jan 2012 15:13:55 -0500 >> From: "Miller, Shao" <sha...@yr...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: "Bob Wheater" <bwh...@my...> >> Cc: col...@li... >> Message-ID: >> <F0E...@YR...> >> Content-Type: text/plain; charset="iso-8859-1" >> >> Did you get my last message regarding possibly useful info you could share? If not, I'd appreciate it if you could review it. >> >> >> >> There are several kernels: >> >> * Uniprocessor, no-PAE (the default ntoskrnl.exe) >> * Uniprocessor, PAE (ntkrnlpa.exe) >> * Multiprocessor, no-PAE (ntkrnlmp.exe) >> * Multiprocessor, PAE (ntkrpamp.exe) >> >> >> >> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), highlight the System process, then choose View -> Lower Pane View -> DLLs and make sure that View -> Show Lower Pane has a check-mark. Then scroll through the list of DLLs and observe which one matches the pattern ntXXX.exe. >> >> >> >> You can be using a PAE kernel without knowing it and without the /PAE switch in BOOT.INI. >> >> >> >> - Shao Miller >> >> ________________________________ >> >> From: Bob Wheater [mailto:bwh...@my...] >> Sent: Monday, January 09, 2012 15:04 >> To: col...@li... >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> >> >> >>> Vincent Rivi?re wrote: >> >>>My complete boot.ini line is: >> >>>multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft >Windows XP Professionnel" /fastdetect >/noexecute=alwaysoff /nopae >> >> >> >>>To check if PAE is actually on or off, look at the >system properties (Win+Pause), on the General tab (the >default one). Look at the bottom, after the line with >frequency and amount of RAM. If "Physical Address >Extension" >> >>>is written, then PAE is on. If there is no such text, >PAE is off. >> >> >> >>>So please change your boot.ini to /noexecute=alwaysoff >/nopae then check it is actually disabled and see if >coLinux works better. >> >> >> >> My general tab on the system properties does NOT have "Physical Address Extension". >> >> >> >> You seem to be confusing PAE with DEP (Data Execution Prevention). See http://technet.microsoft.com/en-us/library/cc738483%28WS.10%29.aspx >> >> The /noexecute switch controls DEP. >> >> >> >> However DEP may only apply to windows server 2003 and not XP. >> >> >> >> " The PAE mode kernel requires an Intel Architecture processor, Pentium Pro or later, more than 4 GB of RAM, and Windows 2000, Windows XP, or Windows Server 2003." >> >> From: http://msdn.microsoft.com/en-us/windows/hardware/gg487503 >> >> According to this PAE does NOT apply to a 1gb system. It only applies to 4gb and greater systems. >> >> >> >> Regards, >> >> Bob >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> Message: 3 >> Date: Mon, 9 Jan 2012 16:11:22 -0500 >> From: "Bob Wheater" <bwh...@my...> >> Subject: Re: [coLinux-users] Colinux Blue Screen Crashes >> To: <col...@li...> >> Message-ID: <004201cccf13$3e4661f0$bad325d0$@net> >> Content-Type: text/plain; charset="us-ascii" >> >> Its using the default uniprocess kernel (nopae): >> >> ntoskrnl.exe NT Kernel & System Microsoft Corporation >> 5.1.2600.6165 >> >> according to process explorer. >> >> >> >> What last message? I though everything was posted to the list. I checked my >> files and the only message from you concerns posting the top part of windbg >> output which I did post when I reported the problem to the bug tracker. >> >> -Bob >> >> >> >> From: Miller, Shao [mailto:sha...@yr...] >> Sent: Monday, January 09, 2012 3:14 PM >> To: Bob Wheater >> Cc: col...@li... >> Subject: RE: [coLinux-users] Colinux Blue Screen Crashes >> >> >> >> Did you get my last message regarding possibly useful info you could share? >> If not, I'd appreciate it if you could review it. >> >> >> >> There are several kernels: >> >> * Uniprocessor, no-PAE (the default ntoskrnl.exe) >> * Uniprocessor, PAE (ntkrnlpa.exe) >> * Multiprocessor, no-PAE (ntkrnlmp.exe) >> * Multiprocessor, PAE (ntkrpamp.exe) >> >> >> >> Try using Microsoft's SysInternals' Process Explorer (ProcExp.exe), >> highlight the System process, then choose View -> Lower Pane View -> DLLs >> and make sure that View -> Show Lower Pane has a check-mark. Then scroll >> through the list of DLLs and observe which one matches the pattern >> ntXXX.exe. >> >> >> >> You can be using a PAE kernel without knowing it and without the /PAE switch >> in BOOT.INI. >> >> >> >> - Shao Miller >> >> -------------- next part -------------- >> An HTML attachment was scrubbed... >> >> ------------------------------ >> >> ------------------------------------------------------------------------------ >> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex >> infrastructure or vast IT resources to deliver seamless, secure access to >> virtual desktops. With this all-in-one solution, easily deploy virtual >> desktops for less than the cost of PCs and save 60% on VDI infrastructure >> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox >> >> ------------------------------ >> >> _______________________________________________ >> coLinux-users mailing list >> coL...@li... >> https://lists.sourceforge.net/lists/listinfo/colinux-users >> >> >> End of coLinux-users Digest, Vol 68, Issue 7 >> ******************************************** |
