Similar to HAL

Hi,
In the past I used to create exe (for building hieararchy in sql, update dimensions, refresh essbase, load data and run calc scripts) using HAL and scheduled it.
Can I do all of the above with any other tool?
Thanks

Yes ODI (Oracle Data Integrator) can do all of that and much more.
Have a read of my blog if you go down the route of using ODI.
If you don't choose that route then in version 11 you have the Outline loader utility which can load dimensional information from a text file.
Cheers
John
http://john-goodwin.blogspot.com/

Similar Messages

HAL-9000 Voice

I was looking for a voice to get for my computer similar to HAL-9000 from Space Odyssey. You'd figure with this being one of Apple's older ads, they would have included it.
http://www.youtube.com/watch?v=nHJkAYdT7qo
Anyway, does anyone know where I could get such a voice?

My guess is it's rather involved.
If you have the Xcode Developer tools installed, there are a couple of apps provided in /Developer/Applications/Utilities/Speech/:
Repeat After Me.app (and a brief User's Guide)
SRLanguageModeler.app

A Question about Hyperion Application Link (HAL)

Do we recomand to use HAL to load data?
I noticed that I should use a program named "Vignette® V7 Business Integration Studio" to use HAL. But I can not foud it in the edelivery. Where can I download it?

HAL was a Hyperion branded version of Vignette, so hence the name.
HAL is a reasonable tool for simple to medium complexity integrations into Essbase or Planning and works pretty well.
As the other poster mentioned it will soon not be supported and you need to look into ODI, DIM or FDM options. DIM and FDM are purchasable options, but you should get a a reduced license ODI included (similar to HAL) on v9.3+. ODI and DIM are more robust ETL/ELT tools, where as FDM is a slightly different proposition that allows local entities to take control of loading and mapping their source data, with robust auditing etc.
Hope this helps
Andy King
http://www.analitica.co.uk

[Solved] Can't mount internal, or external, partitions in Thunar.

Hello.
After my most recent full system update, I seem to e missing the ability to mount partitions, and drives, through Thunar.
I'm running a minimal Openbox, with Thunar, desktop.
I haven't uninstalled anything, and here's my '/etc/xdg/openbox/environment' file with the settings I used.
# Set system-wide environment variables here for Openbox
# User-specific variables should be placed in $HOME/.config/openbox/environment
# To set your language for displaying messages and time/date formats, use the following:
#LANG=en_CA.UTF8
# To set your keyboard layout, you need to modify your X config:
# http://www.google.com/search?q=how+to+set+keyboard+layout+xorg
# User added
if which dbus-launch >/dev/null && test -z "$DBUS_SESSION_BUS_ADDRESS"; then
eval `dbus-launch --sh-syntax --exit-with-session`
fi
Yes, dbus is still enabled in the daemons, and I have gvfs installed.
EDIT;
Bit by bit, I started to try reinstalling all the auto-mount related packages unsuccessfully, but then I got impatient.
I probably should have done it sequentially, but I forced reinstalled (pacman -Sf *) these dbus packages. After doing those, everything is back to normal.
dbus-core-1.4.16-1-x86_64
dbus-1.4.16-1-x86_64
dbus-glib-0.98-1-x86_64
Last edited by *nixer (2012-01-19 19:50:28)

peterb wrote:
I had a similar problem with an internal SATA drive. This is what helped me out:
https://wiki.archlinux.org/index.php/Ud … ormal_user
I had to install udisks and create the policy as described in the wiki page.
To allow other users to write on the disk i logged in as root and changed the permissions to the drive in Thunar.
thanks man it did the trick... thanks so much.
now i realize that i could easily find this on the wiki like you but didn't know what to look for.....very confused by devices managing since there are many programs that does similar things: hal,dbus,policy,udev,udisks,etc.....
solved problem....and thread

Guide to overcome hal.dll error - disk error & other errors.

Okay to start off with - guide for installing bootcamp.
DISCLAIMER:
I take no responsibility at all - whatsoever for any damage the following steps cause to anything. If you follow this guide and then are annoyed at me in any way - don't be - you followed these steps knowing they could be dangerous to your hard drive / computer / sanity / etc. That said - good luck & these steps should work for everyone.
requirements: XP SP2 CD & a copy of parallels would be useful. Also a non-apple usb keyboard for step 1 if the apple one doesn't work during xp bootup.
1. First try the usual bootcamp assistant method. Insert the xp disk, in the setup make sure you format the drive to NTFS (not quick). If you don't get this option - skip to step 3.
2. Reboot and hopefully everything will go without a hitch. If it doesn't and you get a hal.dll error or any other kind of error go on to the next step.
3. Boot up mac os x. Install parallels desktop.
4. Insert your windows xp sp2 cd.
5. Create a new virtual machine using a virtual hard drive saved in your documents folder somewhere.
6. Configure it so that the bootcamp drive is added as an extra secondary drive in the virtual machine. (Little plus button down at the bottom).
7. Install XP onto the virtual machine - don't activate or anything, just get to the desktop stage as fast as possible.
8. Parallels will have already asked for your password to dismount the boot camp drive.
9. Double click my computer in the virtual machine, then hold down ctrl+shift and click on the BOOTCAMP partition in the my computer window.
10. Click format.
11. Select NTFS as file format, check enable compression - do not check quick format.
12. Wait till its finished and then power down the virtual machine.
------- The following steps are taken from http://communities.vmware.com/thread/114529 and were written by MandarMS from the vmware forums. I have edited the guide a little - (you'll see where). Thanks and all credit to MandarMS.----
13. (James: Close parallels)
14. Quit all applications in Host Mac OS X
15. Open Terminal utility from Macintosh HD : Applications : Utilities folder.
16. Key-in the following command
$ sudo fdisk /dev/rdisk0
17. Preferably take the screenshot of the output or Note down the output (for restoring MBR).
18. Key-in the following command
$ sudo fdisk -e /dev/rdisk0
setpid 3
Choose 07 (as the partition type)
write
Y
Restart your Mac System
(James: EDIT - BELOW IS AN EXAMPLE OF THE OUTPUT OF THE PROGRAM IF YOU ARE UNSURE OF WHAT TO TYPE IN WHERE - This confused me at first but really helped in the end - James)
For more details please check the example shown below:
$ sudo fdisk -e /dev/rdisk0 (this will help to change the MBR)
$ fdisk: could not open MBR file /usr/standalone/i386/boot0: No such file or directory
Enter 'help' for information
fdisk: 1> setpid 3 (Enter “setpid 3” press enter key)
Starting Ending
#: id cyl hd sec - cyl hd sec start - size
*3: 0B 1023 254 63 - 1023 254 63 1127792680 - 337356448 Win95 FAT32L
Partition id ('0' to disable) 0 - FF: [C] (? for help) 07 (Enter 07 Partition table)
fdisk:*1> write (enter “write” press enter key, This will change the MBR)
Device could not be accessed exclusively.
A reboot will be needed for changes to take effect. OK? [n] Y (Press Y to modify changes)
Writing MBR at offset 0.
$ fdisk: 1> exit (enter “exit”, press enter key)
19. Restart your Mac System
------ Back to me again.
20. Welcome back - your drives have just been fixed. Reboot again and insert the windows xp sp2 cd. Hold down option at startup and boot from the cd.
21. Go through the setup again - this time don't do anything to the drives when it asks you to format.
22. wait...
23. It'll reboot......
24. It'll install..... if it doesn't - skip to step 26
25. Welcome to windows, install your drivers and reboot a couple more times. You're good.
26. (it didn't work... you got the hal.dll error or something similar) Boot up mac os x again and launch parallels.
27. Start up the virtual machine - open up BOOTCAMP in my computer.
28. Click view - folder options
29. View types > make sure you can see hidden files and folders, view system files and etc.
30. Right click boot.ini and click properties
31. Uncheck read-only.
32. Click okay - open boot.ini in notepad.
33. If you're on a mac with 2 partitions: 1 mac hd, 1 bootcamp, delete everything in the boot.ini file and copy and paste the following into it:
\[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(3)\WINDOWS
\[operating systems]
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect
Obviously change the name to suit. Save it and reboot - you should be good to go now.

Hi. Your bootcamp drive should be drive C. It shouldn't matter what drive letter it is really, you make the virtual machine disk as a virtual disk saved in your documents folder and hook it in to use your physical bootcamp drive.
Ensure you've typed in the correct command and correct password. Press enter after you type in the password. You won't see it as you type it in, and you may need to wait some time afterwards before you'll see the next prompt. Leave it 2 minutes.
Sorry I've been abroad.. hope you have it worked out by now anyway mate.

Problem in Planning Adapter in HAL

Hii have the following problem in HAL"When i drag the planning adapter on to flow diagram andgive the server address.it gave me an error " HspBeanFactory" andclosed off.did anyone faced similar problem. help me please 

First try restarting the Hyperion Planning Server and HBR Server, and verifying that the Hyperion RMI Registry Service is set to Automatic start and that it has started correctly. If that doesnt solve the problem, open the "hyperionRMI_Classpath.properties" file (Hyperion\Common\RMI\1.0.0\) and make sure that you have the path to the HspJS.jar file. It should look something like this (your file will have more entries then the following example) %HYPERION_HOME%\common\RMI\1.0.0;H:\Planning\Utils\HspJS.jar;...;... Make sure to restart the RMI service or rebooth the server before testing. C. Logan InterTech Solutions Inc. [email protected]

Cant boot missing hal.dll file - HELP!

I have just installed my new MSI board, and I have a dreadful problem. I cannot get my computer to boot. It tells me that windows cannot start because the following file is mssing or corrupted: Hal.dll
In fact the file is there. I know this because if |I leave the windows install disk in the computer it boots ok. I have tried using the rebuild command from the recovery console, and the repair option, but so far it does not work.
Has anyone else had a similar problem? I had no problem with my old board, and so I thought it might be something to do with this new board. Are my settings incorrect?
I have SCSI as well as IDE drives, and I cannot tell if the boot.ini file is pointing to the right drive, but I suspect it is.
Please help!
Dan

hal.dll is a dll which interfaces your hardware to the operating system (Hardware Adapter Layer).
I don't know which operating system you are using, so I can't tell you the total answer to your problem.
When you boot from your hard drive (as opposed to floppy disk or cd-rom), it will always look for the initial hardware loaders ($ldr$, ntldr, etc) from the boot drive (normally "C") prior to looking at boot.ini. From there it will give you a choice of which operating system to load.
Incidentally, the loader is a dos based program so only knows about drives 1 & 2.
the easiest way to get the operating system on the second drive, is to use the install disk from windows by executing "cd-rom":/setup.exe from the start menu.
After removing the current version of the OS from the scsci drive, you may then install onto the scsi drive. Ensure that the scsi controller is enabled for booting, so it's BIOS is enabled.
Hope this helps.
kd1im (MCSE)

[CLOSED] CD/DVDs not recognized (hal-less KDE)

Hello everyone,
after the last system upgrade last week CDs and DVDs are not recognized when I insert them in the drive.
I'm running hal-less KDE 4.6 with udisks installed.
I removed hal after the upgrade, however the drive could not recognize the disks even when hal was running.
I searched the forum but haven't found any discussion reporting the very same problem.
Can anyone help me to debug this?
Thanks!
Last edited by elnigno (2011-02-22 12:43:43)

I had the same / similar problem. Just that given that I build my own kernel I thought this was what was causing it. That's why I rebuilded the kernel and enabled ISO and UDF modules in Filesystems. If you're using the standard kernel I have no idea what could be the problem.

Udev update: udev.rules file contains errors [was: dbus+hal update]

I am aware of the fact that there are already a few topics and a bug report (http://bugs.archlinux.org/task/6351) concerning the recent dbus & hal upgrades. However, my case seems different and more complex. I am not even sure if this is directly related to the others' issues.
Since the update to dbus-1.0.2-2 my system does not follow some dbus rules any more. The recent follow-up update to dbus-1.0.2-3 did not remedy my problems, either.
I think that this is due to the /etc/udev/rules.d/udev.rules file having become corrupted with the recent updates. Under the sections
#pty and tty legacy devices
and
#vc devices
several KERNEL=[...] lines have errors, at least the final double quotation marks are missing!
So far my problems are as follows:
- Intel i810 video driver fails to load: "No matching device [...] found".
- Thinkpad's nvram is not get created in /dev
- no pty devices / no ttyp devices are created in /dev. Therefore, none of my X-based consoles will start. Konsole, for example, exits with "Konsole is unable to open a PTY [...]".
I will investigate further and report. Anyone eslse experiencing similar problems?
Btw., contrary to the experience of others, removable devices are recognized and mounted.
Last edited by mutlu_inek (2007-02-07 02:52:34)

Those errors I found were actually introduced a few days ago by udev-105-1! The /etc/udev/rules.d/udev.rules provided by that package has errors!
Correcting those errors brought back my beloved pseudo teletypes in /dev/pts/X. But the nvram device is still not created.
Update:
Here is the diff output of udev-105-1's udev.rules compared with what it should be:
--- udev.rules 2007-02-06 21:20:06.000000000 -0500
+++ udev.rules_corrected 2007-02-06 21:16:36.000000000 -0500
@@ -143,8 +143,8 @@
SUBSYSTEMS=="scsi", KERNEL=="sg[0-9]*", ATTRS{type}=="6", GROUP="scanner"
# pty and tty legacy devices
-KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
-KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule
+KERNEL=="pty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
+KERNEL=="tty[a-z][a-z,0-9]*", NAME="legacy/%k", OPTIONS="last_rule"
# md block devices
KERNEL=="md[0-9]*", NAME="md%n", SYMLINK+="md/%n"
@@ -166,8 +166,8 @@
KERNEL=="vcs[0-9]*", NAME="vcc/%n", OPTIONS="last_rule"
KERNEL=="vcsa", NAME="vcc/a0", OPTIONS="last_rule"
KERNEL=="vcsa[0-9]*", NAME="vcc/a%n", OPTIONS="last_rule"
-KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule
-KERNEL=="tty", MODE="0666", OPTIONS="last_rule
+KERNEL=="ptmx", MODE="0666", OPTIONS="last_rule"
+KERNEL=="tty", MODE="0666", OPTIONS="last_rule"
# video devices
SUBSYSTEM=="video4linux", GROUP="video"
Last edited by mutlu_inek (2007-02-07 02:44:24)

Synaptics: /etc/hal/fdi/policy/11-x11-synaptics doesn´t work anymore

Hello everyone!
Three weeks ago I installed Arch one my old "Acer Travelmate 243".
It was my first Laptop-Install, so I was sure to experience some problems especially with the Touchpad.
But hey, no problems at all, Touchpad worked.
One week ago I made a system-update. Also the Kernel was updated to version 2.6.30.
I did a reboot and everything worked ok. Everything, but not the "two-finger-scroll" on the touchpad (which I had enabled when I configured the touchpad and worked before the update).
So I checked /etc/hal/fdi/policy/11-x11-synaptics, but everything looked like before the update.
The problem is that "11-x11-synaptics" apparently isn´t read anymore, cause I can do whatever I like to this file and it simply doesn´t matter (Touchpad works in the standard way). BTW I don´t have a xorg.conf.
So here are some files:
/etc/hal/fdi/policy/11-x11-synaptics.fdi
<?xml version="1.0" encoding="ISO-8859-1"?>
<deviceinfo version="0.2">
<device>
<match key="info.product" contains="ETPS/2 Elantech Touchpad">
<append key="info.capabilities" type="strlist">input.touchpad</append>
</match>
<match key="info.capabilities" contains="input.touchpad">
<merge key="input.x11_driver" type="string">synaptics</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.TapButton2" type="string">3</merge>
<merge key="input.x11_options.TapButton3" type="string">2</merge>
<merge key="input.x11_options.VertTwoFingerScroll" type="string">true</merge>
</match>
</device>
</deviceinfo>
Output of "hal-device":
18: udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input'
input.device = '/dev/input/event7' (string)
input.product = 'PS/2 Synaptics TouchPad' (string)
access_control.file = '/dev/input/event7' (string)
access_control.type = 'mouse' (string)
info.callouts.add = { 'hal-acl-tool --add-device' } (string list)
input.x11_driver = 'evdev' (string)
info.callouts.remove = { 'hal-acl-tool --remove-device' } (string list)
linux.sysfs_path = '/sys/devices/platform/i8042/serio4/input/input7/event7' (string)
info.parent = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port' (string)
info.subsystem = 'input' (string)
info.product = 'PS/2 Synaptics TouchPad' (string)
info.category = 'input' (string)
info.capabilities = { 'input', 'input.mouse', 'access_control' } (string list)
linux.device_file = '/dev/input/event7' (string)
info.udi = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port_logicaldev_input' (string)
linux.hotplug_type = 2 (0x2) (int)
input.originating_device = '/org/freedesktop/Hal/devices/platform_i8042_i8042_AUX3_port' (string)
linux.subsystem = 'input' (string)

I have similar problem, I have recently switched from radeon to fglrx driver and in order to do so I had to downgrade kernel to 2.6.29 and xorg-server to 1.5. After that my Alps touchpad stopped working. I also tried this method and it is no good. And there's another weird thing: if I try to read /dev/input/mouse2 vith cat and touch the touchpad I get an output which shows, that I ought to be able to use it via this device pointer. Here's my xorg.conf
#Section "InputDevice"
# Identifier "Serial Mouse"
# Driver "mouse"
# Option "Protocol" "Microsoft"
# Option "Device" "/dev/ttyS0"
# Option "Emulate3Buttons" "true"
# Option "Emulate3Timeout" "70"
# Option "SendCoreEvents" "true"
#EndSection
#Section "InputDevice"
# Driver "synaptics"
# Identifier "PS/2 Mouse"
# Option "Device" "/dev/psaux"
# Option "Protocol" "auto-dev"
# Option "LeftEdge" "120"
# Option "RightEdge" "830"
# Option "TopEdge" "120"
# Option "BottomEdge" "650"
# Option "FingerLow" "14"
# Option "FingerHigh" "15"
# Option "MaxTapTime" "180"
# Option "MaxTapMove" "110"
# Option "EmulateMidButtonTime" "75"
# Option "VertScrollDelta" "20"
# Option "HorizScrollDelta" "20"
# Option "MinSpeed" "0.3"
# Option "MaxSpeed" "0.75"
# Option "AccelFactor" "0.015"
# Option "EdgeMotionMinSpeed" "200"
# Option "EdgeMotionMaxSpeed" "200"
# Option "UpDownScrolling" "1"
# Option "CircularScrolling" "1"
# Option "CircScrollDelta" "0.1"
# Option "CircScrollTrigger" "2"
#EndSection
#Section "InputDevice"
# Identifier "Synaptics"
# Driver "synaptics"
# Option "Device" "/dev/input/mouse2"
# Option "Protocol" "auto-dev"
# Option "Emulate3Buttons" "yes"
# Option "LeftEdge" "120"
# Option "RightEdge" "830"
# Option "TopEdge" "120"
# Option "BottomEdge" "650"
# Option "FingerLow" "14"
# Option "FingerHigh" "15"
# Option "MaxTapMove" "110"
# Option "VertScrollDelta" "20"
# Option "HorizScrollDelta" "20"
# Option "MinSpeed" "0.5"
# Option "MaxSpeed" "1.5"
# Option "SHMConfig" "true"
#EndSection
# Auto-generated by Archie mkxcfg
# Auto-generated by Archie mkxcfg
Section "ServerLayout"
#InputDevice "USB Mouse" "CorePointer"
#Option "AIGLX" "True"
# Serial Mouse not detected
# USB Mouse not detected
Identifier "Xorg Configured"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "PS/2 Mouse" "CorePointer"
EndSection
Section "Files"
# Additional fonts: Locale, Gimp, TTF...
# FontPath "/usr/share/lib/X11/fonts/latin2/75dpi"
# FontPath "/usr/share/lib/X11/fonts/latin2/100dpi"
# True type and type1 fonts are also handled via xftlib, see /etc/X11/XftConfig!
ModulePath "/usr/lib/xorg/modules"
FontPath "/usr/share/fonts/misc:unscaled"
FontPath "/usr/share/fonts/misc"
FontPath "/usr/share/fonts/75dpi:unscaled"
FontPath "/usr/share/fonts/75dpi"
FontPath "/usr/share/fonts/100dpi:unscaled"
FontPath "/usr/share/fonts/100dpi"
FontPath "/usr/share/fonts/PEX"
FontPath "/usr/share/fonts/cyrillic"
FontPath "/usr/share/fonts/Type1"
FontPath "/usr/share/fonts/ttf/western"
FontPath "/usr/share/fonts/ttf/decoratives"
FontPath "/usr/share/fonts/truetype"
FontPath "/usr/share/fonts/truetype/openoffice"
FontPath "/usr/share/fonts/truetype/ttf-bitstream-vera"
FontPath "/usr/share/fonts/latex-ttf-fonts"
FontPath "/usr/share/fonts/defoma/CID"
FontPath "/usr/share/fonts/defoma/TrueType"
EndSection
Section "Module"
Load "ddc" # ddc probing of monitor
Load "dbe"
Load "dri"
Load "extmod"
Load "glx"
Load "bitmap" # bitmap-fonts
Load "type1"
Load "freetype"
Load "record"
Load "synaptics"
EndSection
Section "ServerFlags"
Option "AllowMouseOpenFail" "false"
Option "AIGLX" "True"
Option "AutoAddDevices" "True"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "latitude"
Option "XkbLayout" "cz"
Option "XkbVariant" ""
EndSection
Section "InputDevice"
Identifier "PS/2 Mouse"
Driver "mouse"
Option "Protocol" "Auto"
Option "ZAxisMapping" "4 5"
Option "Device" "/dev/psaux"
Option "Emulate3Buttons" "true"
Option "Emulate3Timeout" "70"
Option "SendCoreEvents" "true"
EndSection
Section "InputDevice"
Identifier "USB Mouse"
Driver "mouse"
Option "Device" "/dev/input/mouse2"
Option "SendCoreEvents" "true"
Option "Protocol" "GlidePointPS/2"
Option "ZAxisMapping" "4 5"
Option "Buttons" "5"
Option "Emulate3Buttons"
EndSection
Section "Monitor"
# Warning: This may fry old Monitors
# Very conservative. May flicker.
# VertRefresh 50.0 - 62.0 # Extreme conservative. Will flicker. TFT default.
# Default modes distilled from
# "VESA and Industry Standards and Guide for Computer Display Monitor
# Timing", version 1.0, revision 0.8, adopted September 17, 1998.
# $XFree86: xc/programs/Xserver/hw/xfree86/etc/vesamodes,v 1.4 1999/11/18 16:52:17 tsi Exp $
# 640x350 @ 85Hz (VESA) hsync: 37.9kHz
Identifier "Monitor0"
HorizSync 28.0 - 96.0
VertRefresh 50.0 - 75.0
ModeLine "640x350" 31.5 640 672 736 832 350 382 385 445 +hsync -vsync
ModeLine "640x400" 31.5 640 672 736 832 400 401 404 445 -hsync +vsync
ModeLine "720x400" 35.5 720 756 828 936 400 401 404 446 -hsync +vsync
ModeLine "640x480" 25.2 640 656 752 800 480 490 492 525 -hsync -vsync
ModeLine "640x480" 31.5 640 664 704 832 480 489 491 520 -hsync -vsync
ModeLine "640x480" 31.5 640 656 720 840 480 481 484 500 -hsync -vsync
ModeLine "640x480" 36.0 640 696 752 832 480 481 484 509 -hsync -vsync
ModeLine "800x600" 36.0 800 824 896 1024 600 601 603 625 +hsync +vsync
ModeLine "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync
ModeLine "800x600" 50.0 800 856 976 1040 600 637 643 666 +hsync +vsync
ModeLine "800x600" 49.5 800 816 896 1056 600 601 604 625 +hsync +vsync
ModeLine "800x600" 56.3 800 832 896 1048 600 601 604 631 +hsync +vsync
ModeLine "1024x768" 44.9 1024 1032 1208 1264 768 768 776 817 +hsync +vsync interlace
ModeLine "1024x768" 65.0 1024 1048 1184 1344 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 75.0 1024 1048 1184 1328 768 771 777 806 -hsync -vsync
ModeLine "1024x768" 78.8 1024 1040 1136 1312 768 769 772 800 +hsync +vsync
ModeLine "1024x768" 94.5 1024 1072 1168 1376 768 769 772 808 +hsync +vsync
ModeLine "1152x864" 108.0 1152 1216 1344 1600 864 865 868 900 +hsync +vsync
ModeLine "1280x960" 108.0 1280 1376 1488 1800 960 961 964 1000 +hsync +vsync
ModeLine "1280x960" 148.5 1280 1344 1504 1728 960 961 964 1011 +hsync +vsync
ModeLine "1280x1024" 108.0 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 135.0 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync
ModeLine "1280x1024" 157.5 1280 1344 1504 1728 1024 1025 1028 1072 +hsync +vsync
ModeLine "1600x1200" 162.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 175.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 189.0 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 202.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1600x1200" 229.5 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync
ModeLine "1792x1344" 204.8 1792 1920 2120 2448 1344 1345 1348 1394 -hsync +vsync
ModeLine "1792x1344" 261.0 1792 1888 2104 2456 1344 1345 1348 1417 -hsync +vsync
ModeLine "1856x1392" 218.3 1856 1952 2176 2528 1392 1393 1396 1439 -hsync +vsync
ModeLine "1856x1392" 288.0 1856 1984 2208 2560 1392 1393 1396 1500 -hsync +vsync
ModeLine "1920x1440" 234.0 1920 2048 2256 2600 1440 1441 1444 1500 -hsync +vsync
ModeLine "1920x1440" 297.0 1920 2064 2288 2640 1440 1441 1444 1500 -hsync +vsync
ModeLine "1800x1440" 230.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "1800x1440" 250.0 1800 1896 2088 2392 1440 1441 1444 1490 +hsync +vsync
ModeLine "640x480" 43.2 640 680 744 848 480 481 484 509 -hsync +vsync
ModeLine "768x576" 35.0 768 792 872 976 576 577 580 597 -hsync +vsync
ModeLine "768x576" 42.9 768 800 880 992 576 577 580 601 -hsync +vsync
ModeLine "768x576" 45.5 768 808 888 1008 576 577 580 602 -hsync +vsync
ModeLine "768x576" 51.8 768 808 888 1008 576 577 580 605 -hsync +vsync
ModeLine "768x576" 62.6 768 816 896 1024 576 577 580 611 -hsync +vsync
ModeLine "800x600" 68.2 800 848 936 1072 600 601 604 636 -hsync +vsync
ModeLine "1024x768" 113.3 1024 1096 1208 1392 768 769 772 814 -hsync +vsync
ModeLine "1152x864" 81.6 1152 1216 1336 1520 864 865 868 895 -hsync +vsync
ModeLine "1152x864" 119.7 1152 1224 1352 1552 864 865 868 907 -hsync +vsync
ModeLine "1152x864" 143.5 1152 1232 1360 1568 864 865 868 915 -hsync +vsync
ModeLine "1280x960" 124.5 1280 1368 1504 1728 960 961 964 1001 -hsync +vsync
ModeLine "1280x960" 129.9 1280 1368 1504 1728 960 961 964 1002 -hsync +vsync
ModeLine "1280x960" 179.0 1280 1376 1520 1760 960 961 964 1017 -hsync +vsync
ModeLine "1280x1024" 191.0 1280 1376 1520 1760 1024 1025 1028 1085 -hsync +vsync
ModeLine "1400x1050" 122.6 1400 1488 1640 1880 1050 1051 1054 1087 -hsync +vsync
ModeLine "1400x1050" 149.3 1400 1496 1648 1896 1050 1051 1054 1094 -hsync +vsync
ModeLine "1400x1050" 155.8 1400 1496 1648 1896 1050 1051 1054 1096 -hsync +vsync
ModeLine "1400x1050" 179.3 1400 1504 1656 1912 1050 1051 1054 1103 -hsync +vsync
ModeLine "1400x1050" 214.4 1400 1512 1664 1928 1050 1051 1054 1112 -hsync +vsync
ModeLine "1600x1200" 280.6 1600 1728 1904 2208 1200 1201 1204 1271 -hsync +vsync
Option "DPMS" "true"
# HorizSync 28.0 - 78.0 # Warning: This may fry very old Monitors
EndSection
Section "Device"
#Option "Capabilities" "0x00000000"
#Option "VideoOverlay" "on"
#Option "OpenGLOverlay" "off"
#Option "FSAAScale" "0"
Identifier "Card0"
Driver "radeon"
VendorName "All"
BoardName "All"
Option "DRI" "True"
Option "NoDDC" "True"
Option "XAANoOffscreenPixmaps" "True"
Option "EnablePageFlip" "True"
Option "RenderAccel" "True"
Option "AccelMethod" "EXA"
#Option "FSAAEnable" "off"
EndSection
Section "Device"
Identifier "Card1"
Driver "fglrx"
VendorName "All"
BoardName "All"
Option "NoDDC" "true"
Option "Centermode" "off"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "OverlayOnCRT2" "0"
Option "PseudoColorVisuals" "off"
Option "UseFastTLS" "off"
BusID "PCI:1:0:0"
EndSection
Section "Device"
Identifier "Card2"
Driver "fglrx"
VendorName "All"
BoardName "All"
Option "DRI" "True"
Option "NoDDC" "True"
Option "XAANoOffscreenPixmaps" "True"
Option "EnablePageFlip" "True"
Option "RenderAccel" "True"
Option "AccelMethod" "EXA"
Option "FSAAEnable" "off"
Option "Capabilities" "0x00000000"
Option "VideoOverlay" "on"
Option "OpenGLOverlay" "off"
Option "FSAAScale" "0"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
# SubSection "Display"
# Depth 16
# Modes "1024x768" "800x600" "640x480"
# EndSubSection
Identifier "Screen0"
Device "Card2"
Monitor "Monitor0"
DefaultDepth 24
Option "DisableGLXRootClipping" "True"
Option "AddARGBGLXVisuals" "True"
Option "LIBGL_ALWAYS_INDIRECT" "True"
SubSection "Display"
Depth 24
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
# Group 0
Mode 0666
EndSection
Section "Extensions"
# Option "DAMAGE" "True"
Option "Composite" "Enable"
EndSection
and here's my /etc/hal/fdi/policy/11-x11-synaptics.fdi
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
# <match key="info.product" contains="Synaptics TouchPad">
<match key="info.product" contains="AlpsPS/2 ALPS GlidePoint">
<merge key="input.x11_driver" type="string">synaptics</merge>
<merge key="input.x11_options.AlwaysCore" type="string">true</merge>
<merge key="input.x11_options.VertEdgeScroll" type="string">true</merge>
<merge key="input.x11_options.HorizEdgeScroll" type="string">true</merge>
<merge key="input.x11_options.TapButton1" type="string">1</merge>
<merge key="input.x11_options.TapButton2" type="string">2</merge>
<merge key="input.x11_options.TapButton3" type="string">3</merge>
<merge key="input.x11_options.protocol" type="string">event</merge>
<merge key="input.x11_options.touchpadoff" type="string">0</merge>
<merge key="input.x11_options.shmconfig" type="string">on</merge>
</match>
</device>
</deviceinfo>
It really bugs me. I can use it only in windows
EDIT: my pointing stick works though.
Last edited by sDoky (2009-07-07 17:02:58)

HAL - 9.2.3 - Error when pulling Planning Adapter into a HAL workflow

I receive the following error when pulling a Planning adapter into the workflow:
error unmarshalling return; nested exception is: java.io.EOFException
I receive a similar error when trying to run one of my already created HAL integrations
VBIS Exception set by 'Planning1' in 'Flow Diagram1': java.lang.Exception: error unmarshalling return; nested exception is: java.io.EOFException
Any help that you can provide would be greatly appreciated.

Hi,
Sounds like a JRE problem.Try the following:
Go To the Hyperion\Common\RMI\1.0.0 folder and double click UninstallHyperionNTServiceRMI.cmd.
This will uninstall the RMI service. Log out of the machine and log back in.
Browse to the same folder and edit InstallHyperionNTServiceRMI.cmd.
Check the following:
set JRE_HOME=c:\Hyperion\common\JDK\Sun\1.4.2\jre (make sure the path does exist)
Further down change the following:
HyperionJavaService -install HyperionRMIRegistry "%JRE_HOME%\bin\jvm.dll"
to
HyperionJavaService -install HyperionRMIRegistry "%JRE_HOME%\bin\server\jvm.dll"
Save the changes and reinstall the RMI service.
Start the RMI service and do a telnet to port 11333: cmd->telnet servername 11333 and you should be getting a blank screen.
Then try connecting to the Planning adapter again.
Good luck.
Seb
www.taysols.com.au

Phase out of HAL

With the phase out of HAL, does anybody know what the standard seems to be for the replacement? I know ODI comes with Planning but is it the app of choice or maybe one of the other applications (EPMA, DIM, DRM, FDM)?

I would suggest moving towards ODI. DIM is basically the Informatica ETL tool and should have similar features / complexity as ODI.
I have personally used EPM Architect and it mostly works -- the mostly is the gotcha. When something goes awry it can be difficult to troubleshoot and may also result in loss of data. The more complex your application the more likely you run into issues. If I recall maximum formula size for EPMA is 2048 bytes -- planning supports 8192 bytes natively; there is an open defect/enhancement to resolve this.
If you do go down the route of EPM Architect ensure you are patched to the latest patch levels which can be obtained through Metalink3.oracle.com using your support ID.
Good Luck,
-John

Hal, usbdisk, kde - a problem with /media/* directory

Hello,
I am havng a problem with my usbdisk. At first it's mounted at /media/sda1, then during hibernation (kernel23archck, hibernate-scripts, suspend to disk) the script unloads usb modules. When I start the computer again my usbdisk becomes /media/sdb1 and the previous directory becomes empty. Is it possible to force hal to mount my usbdisk always in the same directory e.g. /media/usbdisk ???
Thanks in advance.
mdv

I have a similar problem, when ever I put in an usb pin in mounts it first as sda1, but if I take it out and put it in again, it mounts as sdb1, and sda1 is still mounted in the media directory, so now I have both sda1 and sdb1 mounted, although the sda1 directory is empty.
Why doesn't hal unmount the usb pin after I take it out?

Odd hal automounting problem

Hi
usually when I bung a dvd in my drive, hal automounts it to /media and I can see it in thunar
but all of a sudden it gets mounted to /mnt/cd and when I click on it in thunar I get the following error:
Failed to mount "stuff".
Failed to determine the mount point for /dev/hdc
nor can I eject it, I get a message saying it wasn't mounted by hal:
how can I find out what is mounting it and stop it??
I've recently installed banshee and rhythmbox, could this have anything to do with it?

In case anyone cares, or has a similar problem I fixed this
I think the problem was I had pmount installed as a dependancy of one of the mp3 players I installed (banshee I think), and it was auto-mounting dvds before hal got a chance.
When I uninstalled banshee, it didn't uninstall the huge amount of other packages it installed with it. I'm still an arch newbie, and would like to know how I would have uninstalled banshee and all the other packages that come with it using pacman.
Anyone help?

Fixed mount points for USB disks via HAL

I've been trying to figure this out on my own but I've been able to achieve my goal.
I want to setup my system so that it auto-mounts a specific hard drive and makes its contents available at a specific file system location.
I'd love to do that by identifying my hard drives by UUID or ID and assigning each one a different mount point.
I've tried the approach described in the ArchWiki:
File: /etc/hal/fdi/policy/20-$device_name.fdi
<?xml version="1.0" encoding="UTF-8"?>
<deviceinfo version="0.2">
<device>
<match key="volume.uuid" string="$device_uuid">
<merge key="volume.label" type="string">$device_name</merge>
</match>
</device>
</deviceinfo>
http://wiki.archlinux.org/index.php/HAL#About_volumes_mount_points
and this one:
<device>
<match key="info.udi" string="/org/freedesktop/Hal/devices/volume_uuid_E265_5E6A">
<merge key="volume.policy.desired_mount_point" type="string">ipod</merge>
<merge key="volume.policy.mount_option.iocharset=iso8859-15" type="bool">true</merge>
<merge key="volume.policy.mount_option.sync" type="bool">true</merge>
</match>
</device>
http://www.mythic-beasts.com/~mark/random/hal/
I restart HAL each time I change the configuration of the 20-$device_name.fdi or preferences.fdi (the second code example). Nothing at all can be found in /var/log/messages. It just silently refuses to mount the devices.
It works okay without these configurations and HAL auto-mount all these hard drives but only if I do not mess with the configs in /etc/hal/fdi/policy.
Can someone please explain what could be wrong here?

Dehir wrote:Im actually having similar difficulties. Have created etc/hal/fdi/policy/20-$device_name.fdi names for each device. But when im trying mount them from pcmanfm they get mounted every single time by random order, which is not that i want. Id prefer hal mounting over fstab but still want them to be mounted with specific names.
Yeah, that's the whole point - I want to have it done automatically with only one condition - fixed mount point names.

Similar to HAL

Similar Messages

Maybe you are looking for