JSR 82 and jsr 185

Dear all, I'm interested in mobile phones that support both JSR 75 and JSR 82. Now I've seen that new phone models such as Nokia 3155 or Nokia 6155, and so on, support JSR 75 but not JSR 82.
Does anybody know if there is a JSR that extend JSR 82?
because in that case I can use these models as well.
Thanks a lot,
Maurizio

jcp.org is up now... latest version of JSR-82 appears to be 1.1.1. Still need an answer to question 3 though!

Similar Messages

CLDC 1.1, MIDP 2.0 and JSR-75,135 in Java(TM) ME platform SDK 3.0, EA?

Hello.
I am trying to develope a "simple" MP3 playback application using "Java(TM) ME platform SDK 3.0, EA", but I have a problem.
I need to write the program for a device that has CLDC 1.1 and MIDP 2.0 configuration, with optional JSR-75 and JSR-135 packages.
When I start a new MIDP application project, I can choose the platform. Then I have 3 options:
DefaultCldcMsaPhone 1&2 --- CLDC-1.1 & MIDP-2.1 with MMAPI and File Connection (among others)
DefaultCldcPhone 1&2 --- CLDC-1.1 & MIDP-2.1 with MMAPI and File Connection (among others)
DefaultCldcJtwiPhone 1&2 --- CLDC-1.1 & MIDP-2.0 with only MMAPI and Wireless Messaging.
The other options are greyed, so I can not select a combination that has CLDC-1.1, MIDP-2.0, MMAPI and File Connect at the same time... I have tryied switching to the full NetBeans and then I have more flexibility choosing the device configuration and profile, using "Sun Java(TM) Wireless Toolkit 2.5.2 for CLDC" emulator platform. But when I run my application in the emulator, it takes some seconds to start playing the MP3. When I change to SDK 3.0, it plays inmediately.
So my question is, can I create a custom device that has everyting I need with "Java(TM) ME platform SDK 3.0, EA"?
Thank you in advance.
Marc Vallribera i Ros

Hi,
This problem is known and will be resolved in Final Release of SDK.
Now you can try to change configuration in <your_project_path>/project.properties file.
platform.bootclasspath and platform.profile parameters should be changed.
Igor

SAP Enterpirse Portal Development standards (JSR 168 and JSR 286)

Hi
I am working on SAP Entperprise Portal Assessment. I heard SAP-EP not supporting JSR 168 and JSR 286 standards.
Can anyone please let me know what JSR 186 and JSR 286 standards are and impact in SAP development work.
Thanks everyone.

Hi Ravi,
SAP EP is definitely not supporting JSR 168.
The next release (Portal on NetWeaver 7.1) will support JSR 286.
You have to consider that the huge amount of SAPs standard portlets / iViews (addressing Knowledge Management, Employee Self Service, Business Intelligence, etc.) will not be implementations of JSR 286 but so called portal applications or Web Dynpro applications.
HTH,
Carsten

Spring and JSR 168 Portlet

I have an application which uses Spring beans and JSR 168 based portlet. I want to know how can i get access to the my spring beans in the portlet controller. I am trying to do the following
public WebApplicationContext getSpringContext(PortletRequest request) {
HttpServletRequest servletRequest = (HttpServletRequest)request.getAttribute("javax.servlet.request");
WebApplicationContext appContext = WebApplicationContextUtils.getWebApplicationContext(servletRequest
.getSession().getServletContext());
return appContext;
Actually a NPE happens @ "servletRequest.getSession()"
The spring beans are initialized during deployment using the spring contextListener
This code works in other J2EE container which have JSR 168 support, like BEA, JBOSS
Any help is greatly appreciated.

OMG!
Today, I wanted to build a really simple portlet with spring, and deploy it on oc4j / iAS10gR2 - since it hoped it will ease development in the future.
Your post, doesn't motivate so much - but let's hope I've a bit more luck getting it running :)
-> Have you looked at the spring-framework 2.0.3 release demos? In the 2.0.3 release a new demo: petportal is included - maybe this helps :)

WSRP and JSR 168 Docs

Can anyone tell me where to find some good documentation (especially tutorials) for WSRP and JSR 168?
Thanks

This is a good document for WSRP understanding.
http://xml.coverpages.org/WSRP-Primerv0920040830a.pdf

URL generation - Https and JSR 168

We have some JSR 168 complaint portlets that are working fine under http. However,
when we switch to https (with a webserver front-end), the edit button functionality
generates incorrect urls. It tries to use http and then append port 443. These
urls do not work with the web server front-end.
I know all urls for JPF portlets etc are controlled through the url-template-config.xml
file, but it seems that the JSR 168 portlets do not use this file. Any idea what
these portlets use and what configuration change I could make to resolve this
issue?
Thanks
Kunal

Hi Subbu -
I have modified the template to use relative paths - maybe that will solve my
issue. Here is my modified template.
Thanks
Kunal
Subbu Allamaraju <[email protected]> wrote:
Hi Kunal,
In WLP, all portlets rely on url-templates-config.xml to create URLs.
The edit button is independent of the type of the portlet you are using.
For Java portlets, could you make sure you have the following snippet
in
this file:
<java-portlet-url-templates>
<url-template-ref type="action" name="portlet-default"/>
<url-template-ref type="secure-action" name="portlet-default"/>
<url-template-ref type="resource" name="portlet-default"/>
<url-template-ref type="secure-resource" name="portlet-default"/>
</java-portlet-url-templates>
</url-template-config>
where the name of the template should be mapped to one of the templates
defined in this file.
If you still face issues with this, please post the templates specified
in this file so that I can take a look. Also, let me know if you are
using GA or SP2.
Subbu
Kunal Mittal wrote:
We have some JSR 168 complaint portlets that are working fine underhttp. However,
when we switch to https (with a webserver front-end), the edit buttonfunctionality
generates incorrect urls. It tries to use http and then append port443. These
urls do not work with the web server front-end.
I know all urls for JPF portlets etc are controlled through the url-template-config.xml
file, but it seems that the JSR 168 portlets do not use this file.Any idea what
these portlets use and what configuration change I could make to resolvethis
issue?
Thanks
Kunal
[url-template-config.xml]

Support of JSR 168 and JSR 286 portlets

Hi,
As far as I know there is no direct support for JSR 168 compliant portlets in the SAP portal. Remote portlets can be consumed using WSRP. I was wondering whether the SAP portal will provide direct support for JSR 168 or even JSR 286 portlets in future releases?
Regards,
Kevin

Hi Kevin,
Long time ago SAP promised to implement JSR 168. Nowadays, you don't find much official documentation stating SAP portal is JSR168 compliant.
SAP introduced the Federated Portal Network (Consumer and Producer portals), also with WSRP support.
Check:
cheers,
Noë

SAP NW BRM and JSR 94 support?

Hello,
Can someone please provide some insight on SAP NW BRM's plan to support JSR 94?
I believe the support does not exist in SAP NW BRM 2007 (NW ver 2004s)
Thanks,
Nitin

Arti, this was quite an open question, I'm aware. Thanks for replying though.
We would like to offer Business Users (probably BPXs) the ability to modify rules. For example, approval amount for PO.
BRM seems the most likely candidate in this respect, especially since we use BPM heavily. But of course we use ERP functionality (with its customizing) as well.
We see an overlap in BRM decision tables and ERP Customizing Tables ("steering" tables, also Masterdata, non-transportable data). A lot of decisions / checks require the same data, but we don't want to maintain this both in ERP and BRM.
Any ideas on this?

JDeveloper Extensions and JSR-198

I have been looking at the feature set provided by the JDeveloper Extension SDK and have read a little bit about what JSR-198 is meant to achieve. Is the current Extension SDK a JSR-198 reference implementation and how many of the supporters of the standard have started moving in the direction of implementing this APIs? Would if be safe to say that the current JDeveloper ESDK represents the era of write once run anywhere in IDE integration?
Regards
Chucks

Hi,
It will be available before the end of the year. More information here:
10.1.3 Production, are we there yet ?
Thanks,
Brian

Oracle Content Management and JSR 170

Does anbody know whether latest Oracle Content Management SDK have implemented support for JSR 170?
I cannot find this information a anywhere.

hi tom,
this is the portal content management forum. could you please post your question in the CM SDK forum here:
http://forums.oracle.com/forums/forum.jsp?forum=152
thanks,
christian

Oracle 10 and JSR 170

Does anbody know whether latest Oracle Content Management SDK have implemented support for JSR 170?
I cannot find this information a anywhere.

hi tom,
this is the portal content management forum. could you please post your question in the CM SDK forum here:
http://forums.oracle.com/forums/forum.jsp?forum=152
thanks,
christian

Multihead not working with 2.6.31 and nvidia 185

Right, hi all.
I've been having trouble for the past few days, when I came back home the machine had hung up. Then after booting it hanged in kdm. I've done various attempts at fixing this, with nvidia 190 driver, downgrading to 2.6.30, tested xorg-server 1.7 from testing and I've been running X -configure like crazy. I also had a problem getting in to kde. Currently I have my main screen working with kdemod and also strangely one auxiliary screen, that's all black and gets REALLY slow when I move my mouse there. Normal speed on the main screen. I'd like to get all four screens working if possible. If I start with all four screens (old config) enabled it hangs after nvidia logo.
Here's the log spam. Xorg.log.0
This is a pre-release version of the X server from The X.Org Foundation.
It is not supported in any way.
Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
Select the "xorg" product for bugs you find in this release.
Before reporting bugs in pre-release versions please check the
latest version in the X.Org Foundation git repository.
See http://wiki.x.org/wiki/GitPage for git access instructions.
X.Org X Server 1.6.3.901 (1.6.4 RC 1)
Release Date: 2009-8-25
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.30-ARCH x86_64
Current Operating System: Linux helsinki 2.6.31-ARCH #1 SMP PREEMPT Fri Oct 23 10:03:24 CEST 2009 x86_64
Build Date: 04 September 2009 05:45:43PM
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 29 21:51:48 2009
(==) Using config file: "/etc/X11/xorg.conf"
(==) ServerLayout "X.org Configured"
(**) |-->Screen "Screen0" (0)
(**) | |-->Monitor "Monitor0"
(**) | |-->Device "Card0"
(**) |-->Screen "Screen1" (1)
(**) | |-->Monitor "Monitor1"
(**) | |-->Device "Card1"
(**) |-->Input Device "Mouse0"
(**) |-->Input Device "Keyboard0"
(==) Automatically adding devices
(==) Automatically enabling devices
(**) FontPath set to:
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
/usr/share/fonts/misc,
/usr/share/fonts/100dpi:unscaled,
/usr/share/fonts/75dpi:unscaled,
/usr/share/fonts/TTF,
/usr/share/fonts/Type1,
built-ins
(**) ModulePath set to "/usr/lib/xorg/modules"
(WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
(WW) Disabling Mouse0
(WW) Disabling Keyboard0
(II) Loader magic: 0x1d40
(II) Module ABI versions:
X.Org ANSI C Emulation: 0.4
X.Org Video Driver: 5.0
X.Org XInput driver : 4.0
X.Org Server Extension : 2.0
(II) Loader running on linux
(++) using VT number 7
(!!) More than one possible primary device found
(--) PCI: (0:1:0:0) 10de:0402:1462:0881 nVidia Corporation G84 [GeForce 8600 GT] rev 161, Mem @ 0xe8000000/16777216, 0xc0000000/268435456, 0xe6000000/33554432, I/O @ 0x0000c000/128, BIOS @ 0x????????/131072
(--) PCI: (0:2:0:0) 10de:0402:10de:0439 nVidia Corporation G84 [GeForce 8600 GT] rev 161, Mem @ 0xe4000000/16777216, 0xd0000000/268435456, 0xe2000000/33554432, I/O @ 0x0000d000/128, BIOS @ 0x????????/131072
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) System resource ranges:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) "extmod" will be loaded. This was enabled by default and also specified in the config file.
(II) "dbe" will be loaded. This was enabled by default and also specified in the config file.
(II) "glx" will be loaded. This was enabled by default and also specified in the config file.
(II) "record" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri" will be loaded. This was enabled by default and also specified in the config file.
(II) "dri2" will be loaded. This was enabled by default and also specified in the config file.
(II) LoadModule: "glx"
(II) Loading /usr/lib/xorg/modules/extensions//libglx.so
dlopen: libGLcore.so.1: wrong ELF class: ELFCLASS32
(EE) Failed to load /usr/lib/xorg/modules/extensions//libglx.so
(II) UnloadModule: "glx"
(EE) Failed to load module "glx" (loader failed, 7)
(II) LoadModule: "extmod"
(II) Loading /usr/lib/xorg/modules/extensions//libextmod.so
(II) Module extmod: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension MIT-SCREEN-SAVER
(II) Loading extension XFree86-VidModeExtension
(II) Loading extension XFree86-DGA
(II) Loading extension DPMS
(II) Loading extension XVideo
(II) Loading extension XVideo-MotionCompensation
(II) Loading extension X-Resource
(II) LoadModule: "record"
(II) Loading /usr/lib/xorg/modules/extensions//librecord.so
(II) Module record: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.13.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension RECORD
(II) LoadModule: "dbe"
(II) Loading /usr/lib/xorg/modules/extensions//libdbe.so
(II) Module dbe: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
Module class: X.Org Server Extension
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DOUBLE-BUFFER
(II) LoadModule: "dri"
(II) Loading /usr/lib/xorg/modules/extensions//libdri.so
(II) Module dri: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension XFree86-DRI
(II) LoadModule: "dri2"
(II) Loading /usr/lib/xorg/modules/extensions//libdri2.so
(II) Module dri2: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.1.0
ABI class: X.Org Server Extension, version 2.0
(II) Loading extension DRI2
(II) LoadModule: "nvidia"
(II) Loading /usr/lib/xorg/modules/drivers//nvidia_drv.so
(II) Module nvidia: vendor="NVIDIA Corporation"
compiled for 4.0.2, module version = 1.0.0
Module class: X.Org Video Driver
(II) NVIDIA dlloader X Driver 185.18.36 Fri Aug 14 17:51:02 PDT 2009
(II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(II) Primary Device is:
(II) Loading sub module "fb"
(II) LoadModule: "fb"
(II) Loading /usr/lib/xorg/modules//libfb.so
(II) Module fb: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "wfb"
(II) LoadModule: "wfb"
(II) Loading /usr/lib/xorg/modules//libwfb.so
(II) Module wfb: vendor="X.Org Foundation"
compiled for 1.6.3.901, module version = 1.0.0
ABI class: X.Org ANSI C Emulation, version 0.4
(II) Loading sub module "ramdac"
(II) LoadModule: "ramdac"
(II) Module "ramdac" already built-in
(II) resource ranges after probing:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
(==) NVIDIA(0): RGB weight 888
(==) NVIDIA(0): Default visual is TrueColor
(==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(0): Enabling RENDER acceleration
(EE) NVIDIA(0): Failed to initialize the GLX module; please check in your X
(EE) NVIDIA(0): log file that the GLX module has been loaded in your X
(EE) NVIDIA(0): server, and that the module is the NVIDIA GLX module. If
(EE) NVIDIA(0): you continue to encounter problems, Please try
(EE) NVIDIA(0): reinstalling the NVIDIA driver.
(II) NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:1:0:0 (GPU-0)
(--) NVIDIA(0): Memory: 524288 kBytes
(--) NVIDIA(0): VideoBIOS: 60.84.51.00.00
(II) NVIDIA(0): Detected PCI Express Link width: 8X
(--) NVIDIA(0): Interlaced video modes are supported on this GPU
(--) NVIDIA(0): Connected display device(s) on GeForce 8600 GT at PCI:1:0:0:
(--) NVIDIA(0): BenQ T241WA (CRT-0)
(--) NVIDIA(0): ViewSonic VA2626wm (CRT-1)
(--) NVIDIA(0): BenQ T241WA (CRT-0): 400.0 MHz maximum pixel clock
(--) NVIDIA(0): ViewSonic VA2626wm (CRT-1): 400.0 MHz maximum pixel clock
(II) NVIDIA(0): Assigned Display Device: CRT-0
(==) NVIDIA(0):
(==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(0): will be used as the requested mode.
(==) NVIDIA(0):
(II) NVIDIA(0): Validated modes:
(II) NVIDIA(0): "nvidia-auto-select"
(II) NVIDIA(0): Virtual screen size determined to be 1920 x 1200
(--) NVIDIA(0): DPI set to (93, 92); computed from "UseEdidDpi" X config
(--) NVIDIA(0): option
(==) NVIDIA(0): Enabling 32-bit ARGB GLX visuals.
(==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
(==) NVIDIA(1): RGB weight 888
(==) NVIDIA(1): Default visual is TrueColor
(==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
(**) NVIDIA(1): Enabling RENDER acceleration
(II) NVIDIA(1): NVIDIA GPU GeForce 8600 GT (G84) at PCI:2:0:0 (GPU-1)
(--) NVIDIA(1): Memory: 524288 kBytes
(--) NVIDIA(1): VideoBIOS: 60.84.38.00.00
(II) NVIDIA(1): Detected PCI Express Link width: 8X
(--) NVIDIA(1): Interlaced video modes are supported on this GPU
(--) NVIDIA(1): Connected display device(s) on GeForce 8600 GT at PCI:2:0:0:
(--) NVIDIA(1): Acer AL1916 (DFP-0)
(--) NVIDIA(1): Acer AL1916 (DFP-0): 330.0 MHz maximum pixel clock
(--) NVIDIA(1): Acer AL1916 (DFP-0): Internal Dual Link TMDS
(II) NVIDIA(1): Assigned Display Device: DFP-0
(==) NVIDIA(1):
(==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
(==) NVIDIA(1): will be used as the requested mode.
(==) NVIDIA(1):
(II) NVIDIA(1): Validated modes:
(II) NVIDIA(1): "nvidia-auto-select"
(II) NVIDIA(1): Virtual screen size determined to be 1280 x 1024
(--) NVIDIA(1): DPI set to (85, 86); computed from "UseEdidDpi" X config
(--) NVIDIA(1): option
(==) NVIDIA(1): Enabling 32-bit ARGB GLX visuals.
(--) Depth 24 pixmap format is 32 bpp
(II) do I need RAC? Yes, I do.
(II) resource ranges after preInit:
[0] -1 0 0xffffffff - 0xffffffff (0x1) MX[b]
[1] -1 0 0x000f0000 - 0x000fffff (0x10000) MX[b]
[2] -1 0 0x000c0000 - 0x000effff (0x30000) MX[b]
[3] -1 0 0x00000000 - 0x0009ffff (0xa0000) MX[b]
[4] -1 0 0x0000ffff - 0x0000ffff (0x1) IX[b]
[5] -1 0 0x00000000 - 0x00000000 (0x1) IX[b]
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(II) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(II) Loading extension XINERAMA
(==) RandR enabled
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(1): configuration option may not be set correctly. When the
(II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(1): try to use it to receive ACPI event notifications. For
(II) NVIDIA(1): details, please see the "ConnectToAcpid" and
(II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(1): Config Options in the README.
(II) NVIDIA(1): Setting mode "nvidia-auto-select"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(1): Disabling shared memory pixmaps
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(1): Backing store disabled
(==) NVIDIA(1): Silken mouse enabled
(II) NVIDIA(1): DPMS enabled
(==) RandR enabled
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(II) Initializing built-in extension Generic Event Extension
(II) Initializing built-in extension SHAPE
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension BIG-REQUESTS
(II) Initializing built-in extension SYNC
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension XC-MISC
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse
(II) LoadModule: "evdev"
(II) Loading /usr/lib/xorg/modules/input//evdev_drv.so
(II) Module evdev: vendor="X.Org Foundation"
compiled for 1.6.3, module version = 2.2.5
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 4.0
(**) Logitech USB-PS/2 Optical Mouse: always reports core events
(**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event6"
(II) Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
(II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
(II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
(II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
(**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Logitech USB-PS/2 Optical Mouse" (type: MOUSE)
(**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter chain progression: 2.00
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter stage 0: 20.00 ms
(**) Logitech USB-PS/2 Optical Mouse: (accel) set acceleration profile 0
(II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Natural® Ergonomic Keyboard 4000
(**) Microsoft Natural® Ergonomic Keyboard 4000: always reports core events
(**) Microsoft Natural® Ergonomic Keyboard 4000: Device: "/dev/input/event9"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found 1 mouse buttons
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found scroll wheel(s)
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found keys
(II) Microsoft Natural® Ergonomic Keyboard 4000: Configuring as keyboard
(II) Microsoft Natural® Ergonomic Keyboard 4000: Adding scrollwheel support
(**) Microsoft Natural® Ergonomic Keyboard 4000: YAxisMapping: buttons 4 and 5
(**) Microsoft Natural® Ergonomic Keyboard 4000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Microsoft Natural® Ergonomic Keyboard 4000" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(EE) Microsoft Natural® Ergonomic Keyboard 4000: failed to initialize for relative axes.
(II) config/hal: Adding input device Microsoft Natural® Ergonomic Keyboard 4000
(**) Microsoft Natural® Ergonomic Keyboard 4000: always reports core events
(**) Microsoft Natural® Ergonomic Keyboard 4000: Device: "/dev/input/event8"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found keys
(II) Microsoft Natural® Ergonomic Keyboard 4000: Configuring as keyboard
(II) XINPUT: Adding extended input device "Microsoft Natural® Ergonomic Keyboard 4000" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device "Macintosh mouse button emulation" (type: MOUSE)
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) NVIDIA(1): Initialized GPU GART.
(II) Logitech USB-PS/2 Optical Mouse: Close
(II) UnloadModule: "evdev"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Close
(II) UnloadModule: "evdev"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Close
(II) UnloadModule: "evdev"
(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
(II) No APM support in BIOS or kernel
(II) Screen 0 shares mem & io resources
(II) Screen 1 shares mem & io resources
(II) NVIDIA(0): Initialized GPU GART.
(II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(0): configuration option may not be set correctly. When the
(II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(0): try to use it to receive ACPI event notifications. For
(II) NVIDIA(0): details, please see the "ConnectToAcpid" and
(II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(0): Config Options in the README.
(II) NVIDIA(0): Setting mode "nvidia-auto-select"
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(0): Disabling shared memory pixmaps
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(II) NVIDIA(0): DPMS enabled
(==) RandR enabled
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
(II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
(II) NVIDIA(1): configuration option may not be set correctly. When the
(II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
(II) NVIDIA(1): try to use it to receive ACPI event notifications. For
(II) NVIDIA(1): details, please see the "ConnectToAcpid" and
(II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
(II) NVIDIA(1): Config Options in the README.
(II) NVIDIA(1): Setting mode "nvidia-auto-select"
(II) NVIDIA(1): NVIDIA 3D Acceleration Architecture Initialized
(==) NVIDIA(1): Disabling shared memory pixmaps
(II) NVIDIA(1): Using the NVIDIA 2D acceleration architecture
(WW) NVIDIA(1): WAIT (2, 6, 0x8000, 0x0000bc94, 0x0000bd78)
(WW) NVIDIA(1): WAIT (0, 6, 0x8000, 0x0000bd78, 0x0000bd78)
(II) NVIDIA(1): DPMS enabled
(WW) NVIDIA(1): WAIT (0, 6, 0x8000, 0x0000bda0, 0x0000bda0)
(==) RandR enabled
(II) Entity 0 shares no resources
(II) Entity 1 shares no resources
(EE) XKB: No components provided for device Virtual core keyboard
(WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
[config/dbus] couldn't register object path
(II) config/hal: Adding input device Logitech USB-PS/2 Optical Mouse
(**) Logitech USB-PS/2 Optical Mouse: always reports core events
(**) Logitech USB-PS/2 Optical Mouse: Device: "/dev/input/event6"
(II) Logitech USB-PS/2 Optical Mouse: Found 12 mouse buttons
(II) Logitech USB-PS/2 Optical Mouse: Found x and y relative axes
(II) Logitech USB-PS/2 Optical Mouse: Found scroll wheel(s)
(II) Logitech USB-PS/2 Optical Mouse: Configuring as mouse
(**) Logitech USB-PS/2 Optical Mouse: YAxisMapping: buttons 4 and 5
(**) Logitech USB-PS/2 Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) Logitech USB-PS/2 Optical Mouse: (accel) keeping acceleration scheme 1
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter chain progression: 2.00
(**) Logitech USB-PS/2 Optical Mouse: (accel) filter stage 0: 20.00 ms
(**) Logitech USB-PS/2 Optical Mouse: (accel) set acceleration profile 0
(II) Logitech USB-PS/2 Optical Mouse: initialized for relative axes.
(II) config/hal: Adding input device Microsoft Natural® Ergonomic Keyboard 4000
(**) Microsoft Natural® Ergonomic Keyboard 4000: always reports core events
(**) Microsoft Natural® Ergonomic Keyboard 4000: Device: "/dev/input/event9"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found 1 mouse buttons
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found scroll wheel(s)
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found keys
(II) Microsoft Natural® Ergonomic Keyboard 4000: Configuring as keyboard
(II) Microsoft Natural® Ergonomic Keyboard 4000: Adding scrollwheel support
(**) Microsoft Natural® Ergonomic Keyboard 4000: YAxisMapping: buttons 4 and 5
(**) Microsoft Natural® Ergonomic Keyboard 4000: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(EE) Microsoft Natural® Ergonomic Keyboard 4000: failed to initialize for relative axes.
(II) config/hal: Adding input device Microsoft Natural® Ergonomic Keyboard 4000
(**) Microsoft Natural® Ergonomic Keyboard 4000: always reports core events
(**) Microsoft Natural® Ergonomic Keyboard 4000: Device: "/dev/input/event8"
(II) Microsoft Natural® Ergonomic Keyboard 4000: Found keys
(II) Microsoft Natural® Ergonomic Keyboard 4000: Configuring as keyboard
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Macintosh mouse button emulation
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: "/dev/input/event0"
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(**) Macintosh mouse button emulation: (accel) keeping acceleration scheme 1
(**) Macintosh mouse button emulation: (accel) filter chain progression: 2.00
(**) Macintosh mouse button emulation: (accel) filter stage 0: 20.00 ms
(**) Macintosh mouse button emulation: (accel) set acceleration profile 0
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event2"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) config/hal: Adding input device Power Button
(**) Power Button: always reports core events
(**) Power Button: Device: "/dev/input/event1"
(II) Power Button: Found keys
(II) Power Button: Configuring as keyboard
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "evdev"
(**) Option "xkb_layout" "us"
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(II) NVIDIA(1): Initialized GPU GART.
(EE) NVIDIA(1): Error recovery failed.
(EE) NVIDIA(1): *** Aborting ***
Section "ServerLayout"
Identifier "X.org Configured"
Screen 0 "Screen0" 0 0
Screen 1 "Screen1" RightOf "Screen0"
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/TTF"
FontPath "/usr/share/fonts/Type1"
EndSection
Section "Module"
Load "glx"
Load "extmod"
Load "record"
Load "dbe"
Load "dri"
Load "dri2"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Protocol" "auto"
Option "Device" "/dev/input/mice"
Option "ZAxisMapping" "4 5 6 7"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Monitor Vendor"
ModelName "Monitor Model"
EndSection
Section "Device"
Identifier "Card0"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G84 [GeForce 8600 GT]"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Card1"
Driver "nvidia"
VendorName "nVidia Corporation"
BoardName "G84 [GeForce 8600 GT]"
BusID "PCI:2:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
Section "Screen"
Identifier "Screen1"
Device "Card1"
Monitor "Monitor1"
SubSection "Display"
Viewport 0 0
Depth 1
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 4
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 8
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 15
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 16
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection
and old xorg.conf with all four screens
# /etc/X11/xorg.conf (Xorg X Window System server configuration file)
# This file was generated by fll_xorgconfig, the F.U.L.L.S.T.O.R.Y.
# Xorg Configuration tool.
# Edit this file with caution, and see the xorg.conf(5) manual page.
# (Type "man xorg.conf" at the shell prompt.)
Section "ServerLayout"
Identifier "Xorg Configured"
# Screen "Screen 0"
Screen 0 "Screen0" RightOf "Screen2"
Screen 1 "Screen1" RightOf "Screen0"
Screen 2 "Screen2" LeftOf "Screen0"
Screen 3 "Screen3" RightOf "Screen1"
InputDevice "Keyboard 0"
InputDevice "Logitech USB-PS/2 Optical Mouse 0"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "true"
Option "Xinerama" "1"
Option "DontZap" "false"
EndSection
#Section "Module"
# SubSection "extmod"
# Option "omit xfree86-dga" # don't initialise the DGA extension
# EndSubSection
#EndSection
Section "InputDevice"
Identifier "Keyboard 0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "fi,ca"
Option "XkbOptions" "lv3:ralt_switch,compose:lwin,grp:alt_shift_toggle"
EndSection
Section "InputDevice"
Identifier "Logitech USB-PS/2 Optical Mouse 0"
Driver "auto"
Option "Device" "/dev/input/mice"
Option "Protocol" "auto"
Option "Emulate3Buttons" "true"
Option "CorePointer"
EndSection
Section "Device"
Identifier "Device 0"
Driver "nvidia"
Option "IgnoreDisplayDevices" "TV"
Option "Coolbits" "1"
Option "AddARGBGLXVisuals" "true"
Option "TripleBuffer" "false"
BoardName "nVidia Corporation GeForce 8600 GT"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Device1"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GT"
BusID "PCI:2:0:0"
Screen 0
EndSection
Section "Device"
Identifier "Device2"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GT"
BusID "PCI:1:0:0"
Screen 1
EndSection
Section "Device"
Identifier "Device3"
Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "GeForce 8600 GT"
BusID "PCI:2:0:0"
Screen 1
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "BenQ T241WA"
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 76.0
Option "DPMS"
EndSection
Section "Monitor"
Identifier "Monitor3"
VendorName "Unknown"
ModelName "IFC InFocus X16"
HorizSync 31.0 - 82.0
VertRefresh 48.0 - 85.0
EndSection
Section "Monitor"
Identifier "Monitor1"
VendorName "Unknown"
ModelName "ViewSonic VA902"
HorizSync 30.0 - 82.0
VertRefresh 50.0 - 85.0
EndSection
Section "Monitor"
Identifier "Monitor2"
VendorName "Unknown"
ModelName "Acer AL1916"
HorizSync 30.0 - 83.0
VertRefresh 55.0 - 75.0
EndSection
Section "Screen"
# Removed Option "TwinView" "True"
# Removed Option "MetaModes" "1280x1024,1280x1024;1280x1024,;1024x768,;800x600,;640x480,;"
# Removed Option "metamodes" "CRT: 1920x1200 +1280+0, DFP: 1280x1024 +0+0; CRT: 1280x1024 +0+0, DFP: NULL; CRT: 1024x768 +0+0, DFP: NULL; CRT: 800x600 +0+0, DFP: NULL; CRT: 640x480 +0+0, DFP: NULL"
# Removed Option "metamodes" "CRT: 1920x1200 +1280+0, DFP: 1280x1024 +0+0; CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0; CRT: 640x480 +0+0"
# Removed Option "TwinView" "1"
# Removed Option "metamodes" "CRT: 1920x1200 +1280+0, DFP: 1280x1024 +0+0; CRT: 1280x1024 +0+0, DFP: NULL; CRT: 1024x768 +0+0, DFP: NULL; CRT: 800x600 +0+0, DFP: NULL; CRT: 640x480 +0+0, DFP: NULL"
# Removed Option "metamodes" "CRT: nvidia-auto-select +0+0; CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0; CRT: 640x480 +0+0"
# Removed Option "metamodes" "nvidia-auto-select +0+0; 1280x1024 +0+0; 1024x768 +0+0; 800x600 +0+0; 640x480 +0+0"
# Removed Option "metamodes" "CRT-0: nvidia-auto-select +0+0; CRT-0: 1280x1024 +0+0; CRT-0: 1024x768 +0+0; CRT-0: 800x600 +0+0; CRT-0: 640x480 +0+0"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
Option "AddARGBGLXVisuals" "True"
Option "NoTwinViewXineramaInfo" "False"
# Option "MultiGPU" "True"
Option "SLI" "0"
Option "TwinView" "0"
Option "TwinViewXineramaInfoOrder" "CRT-0"
Option "metamodes" "CRT: nvidia-auto-select +0+0; CRT: 1280x1024 +0+0; CRT: 1024x768 +0+0; CRT: 800x600 +0+0; CRT: 640x480 +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "TwinView" "0"
# Removed Option "metamodes" "nvidia-auto-select +0+0"
# Removed Option "metamodes" "CRT: nvidia-auto-select +0+0, DFP: nvidia-auto-select +1280+0"
# Removed Option "metamodes" "CRT: nvidia-auto-select +1280+0, DFP: nvidia-auto-select +0+0"
# Removed Option "TwinView" "1"
# Removed Option "metamodes" "CRT: 1280x1024 +1280+0, DFP: nvidia-auto-select +0+0"
# Removed Option "metamodes" "CRT: 1280x1024 +0+0"
# Removed Option "metamodes" "CRT-0: 1280x1024 +0+0"
Identifier "Screen1"
Device "Device1"
Monitor "Monitor1"
DefaultDepth 24
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "SLI" "0"
Option "TwinView" "0"
Option "metamodes" "CRT-1: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "metamodes" "DFP: 1280x1024 +0+0"
# Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
# Removed Option "metamodes" "CRT-1: nvidia-auto-select +0+0"
Identifier "Screen2"
Device "Device2"
Monitor "Monitor2"
DefaultDepth 24
Option "SLI" "0"
Option "TwinViewXineramaInfoOrder" "DFP-0"
Option "TwinView" "0"
Option "metamodes" "DFP: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
Section "Screen"
# Removed Option "metamodes" "CRT-1: nvidia-auto-select +0+0"
# Removed Option "metamodes" "DFP: nvidia-auto-select +0+0"
# Removed Option "metamodes" "CRT-1: nvidia-auto-select +0+0"
# Removed Option "metamodes" "CRT-0: 1280x1024 +0+0"
Identifier "Screen3"
Device "Device3"
Monitor "Monitor3"
DefaultDepth 24
Option "TwinView" "0"
Option "metamodes" "CRT-0: nvidia-auto-select +0+0"
SubSection "Display"
Depth 24
EndSubSection
EndSection
# Section "Screen"
# Identifier "Screen 0"
# Monitor "Monitor 0"
# DefaultColorDepth 24
# SubSection "Display"
# Depth 8
# EndSubSection
# SubSection "Display"
# Depth 15
# EndSubSection
# SubSection "Display"
# Depth 16
# EndSubSection
# SubSection "Display"
# Depth 24
# EndSubSection
# EndSection
Section "Extensions"
# Option "Composite" "disable"
# Option "RENDER" "disable"
EndSection

bump

Jsr 82 and portability

Hello,
I'm currently writing a MIDP application which uses some
optional packages, namely JSR 75 (FileConnection API) and
JSR 82 (Bluetooth API).
I'm aware you can test the presence of those APIs with
<code>
System.getProperty("microedition.io.file.FileConnection.version")
</code>
and since there is no System property to indicate JSR 82 presence
you can try to load a class from that package:
<code>
try{Class c = Class.forName("javax.bluetooth.DiscoveryAgent")} catch (ClassNotFoundException e) {}
</code>
Now that I know that JSR 82 is present, I could use a btspp:// connection to communicate with a server. If JSR 82 not present,
then I would use a socket:// connection.
But my code fails, if JSR 82 is not present. It's somewhat strange --
I can use the LocalDevice and DiscoveryAgent classes in my code
when I make sure they are not reached if JSR 82 not present (see code below). I Think this is only possible, because the KVM itself doesn't verify if all classes as this is done in a preverification process. So using these classes is not a clean solution, but I have no other idea right now.
<code>
if (jsr82present) {
     //do device discovery
     LocalDevice local = LocalDevice.getLocalDevice();
     local.setDiscoverable(DiscoveryAgent.GIAC);
     DiscoveryAgent agent = local.getDiscoveryAgent();
     //fails in the next line, although this code is
     //never reached when jsr 82 not present
     agent.startInquiry(DiscoveryAgent.GIAC, new DiscoveryListener(){
          //interface methods here
} else {
     //establish socket connection
</code>
My code fails as soon as I use "new" to instantiate a DiscoveryListener (which is also part of JSR 82) -- even if the instance will never be created, since a device with no JSR 82 support would never reach this code. See my problem now?
Does this mean I have to write two different applications, one for bluetooth communication and the other one for sockets?
I've tried to get around this with dynamic classloading, but didn't work either:
<code>
Class c = Class.forName("mypckg.MyDiscoverListener");
c.newInstance(); //<-- fails here
</code>
Has anyone an idea how to write one application for different devices with different optional packages installed, which uses all functionality
the device offers through it's optional packages?
Or is it just impossible?
Regards,
Torben

try this link
http://www.jcp.org/aboutJava/communityprocess/final/jsr082/

JSR 168 and UIX.

Hi,
Iam a newbie working on an JSR 168 app that makes an existing portlets as JSR 168 compatible. The portlets was orginaly developed usign the JPDK api and to incorporate standards we are making it as JSR 168 compatible.
We used the UIX pages as the front end for showing portlet content. Is it possible to leverage the existing UIX pages using the JSR 168 API. For Rendering the UIX content we used the JPDK classes like the RenderManager , PortletContainerRenderer etc.
As i understand JSR 168 provides the RenderRequest which represents the request sent to the portlet to handle a render. Can this RenderRequest be used to display UIX pages.
Just wanted to know a couple of things.
a) JPDK providers RenderManager , PortletContainerRenderer etc are there equivalents in the JSR 168 API
b) Difference between the RenderRequest of the JSR and the PorletRenderRequest class .
At a brief Iam looking for an equivalents of in the JSR 168 API which can accomplish this.
Thanks
Mouli

Hi Mouli,
In case of JPDK always you will get single request i.e., HttpServletRequest from the portlet.you can get the PortletRenderRequest from HttpServletRequest.
Way to get PortletRenderRequest from HttpServletRequest :
===========================================
PortletRenderRequest portletRenderRequest=(PortletRenderRequest)oHttpServletRequest.getAttribute("oracle.portal.PortletRenderRequest");
[NOTE : you need to import the following class.
import oracle.portal.provider.v2.render.PortletRenderRequest;]
In case of JSR 168 generally you will get two kinds of request ie., RenderRequest & ActionRequest.Where PortletRequest is the parent interface for this two interfaces.
For Ex.whenever the portlets first time loaded on portalpage the portlet will get RenderRequest & it will create its own portlet markup.When ever you perform any operation in any portlet then it will have ActionRequest & remaining portlets will have RenderRequest.
Please feel free to ask anything related to portal technology..Let me know if i specified anything wrong.....
Thanks & Regards.,
Bala S Murugan.,
sendrequestgetresponse At Gmail Dot Com
http://balamurugan-portlets.blogspot.com/

Are the JSRs working for the 'public'?

Part of the JCP/JSR review process is a 'public' draft, where anyone can comment on it. Comments on this are then supposed to lead to possible changes in the reference implementation followed up by a final draft and a final acceptance.
1.5 (tiger) is supposed to be released this summer. And JSR 201 which includes autoboxing and a lot of other stuff ( http://jcp.org/en/jsr/detail?id=201 ) is in that. There is a beta (or alpha) program right now for 1.5. Yet 201 is not in the review stage yet. That isn't too unexpected given that they have to work the kinks out. I suspect it just isn't done yet.
However, it does make me wonder what point the 'public review' serves. I doubt that by the time it is released that any comment, other than perhaps documentation changes, will be incorporated. It simply will be too late.
I have reason to believe that at least one other JSR will end up being handled in the same way.
Does anyone else have reason to believe that comments received during a public review of any JSR in 1.5 would result in either a major or even minor change?

To be honest, I am not sure. I considered joining the
JAI experts group (A long while back). It did not
appear to be free. At the very least it requires you
have funding available to attend meetings and work on
the proposals (which tends to limit contributors to
those working for supportive companies). That may
have just been JAI though.In the past it cost - I looked into joining as well.
What I looked at a couple of days ago says there is no cost to join.
I don't know if they have on-site meetings. I figured most of it was electronic.
>
JSR's are evaluated by SUN as to whether they will
provide market share/utility/cost/detrement/whatever
for SUN. If
it does not satisfy thier criteria it does not happen.
(Many JSR's are additional/optional packages so they
don't
generally have these problems). Represenatives and
proposals from larger companies (who
are heavily invested in java) do tend to get more
attention (which is not surprising) especially when it
comes
to changes to critical parts of java.
Interesting point.
The JSR process does not include that (or at least it specifically seems to not be that way) but that doesn't mean that Sun has to implement any JSR. However, as far as I know they have implemented everyone that impacted the JVM/API directly.
>
All in all I've found that if you have a good point
then it will be considered. However, it is often the
case
that it is a good point which has already been made.
I don't know why 1.5 additions have not been opened
for public comment. (Are you sure they haven't
already?)
I am sure that the one I listed has not.

JSR 82 and jsr 185

Similar Messages

Maybe you are looking for