User tests of the windows installer iorel1-setup.exe and the zip archive iorel1-bin-win32.zip revealed a nuber of problems.

1. missing python tools library
2. missing dlls xalan, xerces and msvcrtd libraries

These modifications were made, tested and applied to the distributions at source forge and google. Assuming the user has a working python distribution the new installation configures iome correctly.

Mike Tolley, Principal Consultant at Cogent (fm) Solutions, looks at the issues that concern the CCTV industry. Today Mike identifies a worrying trend that ‘cheapest is best’.

I believe that the more recent companies entering the marketplace, seeing the amount of CCTV that is being installed, are turning to the cheap end of the market, but some established installers are also coming very close to falling foul of ‘cheapest wins’.

Many end users are now also falling into the trap of ‘cheapest is best’. There are some excellent products out there that are not leading brand names, but excellent quality products at reduced prices, and I don’t rule out their place in our industry. But ‘fit for purpose’ must be considered. Under DPA guidelines it states that it must be adequate – for the sake of poor old Dannie Parkes and many others like him who are expected to perform ‘Mission Impossible’ or ‘The Bill’ type miracles on useless CCTV images.

If you care, consider for just one moment how your customer feels. They have had a CCTV system installed by your company with products recommended by you. They have an incident and, due to the poor quality of images from both camera and recorder, the police have said that there is nothing they can do with the images from the new CCTV system.

Do you believe that this is the end of your relationship or an opportunity to go back and up sell them some new kit? Consider now how you felt that last time you were sold something that didn’t work. You ranted at the sales person in the store, making a big show of it and wanted the world in return for their failings. Where is the balance?

Do you agree with Mike? Let us know what you think below.

For more comment and insight about CCTV  click here to read CCTV articles.

Für alle Jailbreak Handy gibt es einen sehr interessanten Installer namens “Installous“. Mit diesem Repository lassen sich alle nur erdenklichen Apps am iPhone problemlos installieren,…
Die Handhabung ist sehr einfach und gut zu bedienen.

Zur Anleitung

Zuerst muss man im Cydia unter Verwaltung/Quellen/ das zusätzliche Repository hinzufügen:
Quelle: http://cydia.hackulo.us

Nun findet ihr im Cydia unter Kategorien/Hackulo.us/ Das Tool “Installous”
Dies ist der Installer mit dem der Zugriff auf das Repository erfolgt

Nun findet ihr am Desktop des iPhone die App Installous; diese App starten und die
gestellte Frage mit “Cavern” beantworten, und nun, los gehts!

Chrome isn’t officially out for Mac yet, but in the mean time you can get Chromium — the open source version — to give it a try. It is not recommended to use Chromium for daily browsing at this stage! (although you can of course, but don’t transfer money with it okey?)

For me the problem is that it gets developed quite fast, so instead of downloading it every day I wrote this installer to make it easy to get the latest version:

curl http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/$(curl http://build.chromium.org/buildbot/snapshots/chromium-rel-mac/LATEST)/chrome-mac.zip > chrome-mac.zip
unzip chrome-mac.zip
killall Chromium
rm -R /Applications/Chromium.app
cp -R chrome-mac/Chromium.app /Applications/Chromium.app
rm chrome-mac.zip
rm -R chrome-mac
open /Applications/Chromium.app

All you need to do is paste this in a file and run that file by dragging it into Terminal.app. You might just as well open Automator and add the ‘Run Shell Script’ action to it with this code, or make a crontab/initd to run it automatically.

Pour cause de changement de site cliquez ici pour voir cet article !

Pour cause de changement de site cliquez ici pour voir cet article !

The Optimal Flexible Architecture (OFA) standard is a set of file naming and configuration guidelines created to ensure reliable Oracle installations that require little maintenance.

You can think of Optimal Flexible Architecture as a set of good habits to adopt when organizing Oracle directories and files on your computer. All Oracle components on the installation media are Optimal Flexible Architecture-compliant; that is, Oracle Universal Installer places Oracle components in directory locations that follow Optimal Flexible Architecture guidelines. Although using Optimal Flexible Architecture is not a requirement, Oracle recommends that you use it.

Here are the steps to accomplish OFA before an Oracle installation on a Windows environment:

Step 1: Create ORACLE_BASE Directory

ORACLE_BASE is the root of the OFA compliant Oracle directory tree. It is a base for all oracle installations.  It should be in format <DRIVE_LETTER>:\oracle\product\<version>. For example:  D:\oracle\product\10.2.0\ is a good choice for an Oracle 10.2.0.1 database server installation.

Step 2: Create ORACLE_HOME Directory

ORACLE_HOME directory is the directory of the current Oracle installation and contains subdirectories for Oracle software executables and network files. Every ORACLE_HOME directory is also associated with a ORACLE_HOME name which you specify during Oracle Software installation.

ORACLE_HOME directory should be in format <ORACLE_BASE>\<type>_<counter> where type is the purpose of installation (db, app, client etc.) and counter is an identifier which shows the order of installations. For example:  <ORACLE_BASE>\db_1\ => D:\oracle\product\10.2.0\ db_1\  is a good choice for an Oracle Database installation for the first time.

Step 3: Create Admin Directory

Create an admin directory to store administration files.  It should be in format <ORACLE_BASE>\admin\<DB_NAME>\ .

For ex: <ORACLE_BASE>\admin\my_db\ => D:\oracle\product\10.2.0\ admin\my_db\

Some of the directories that the admin directory should contain are shown below:

\bdump –background process trace files
\cdump –core dump files
\create –database creation files
\exp –database export files
\pfile –initialization parameter files
\udump –user SQL trace files
\arch — archived redolog files

Step 4: Create Oradata Directory

Oracle data related files (data files, online redolog files and control files) should be kept in an directory called “ORADATA”. The oradata directory should be in format <ORACLE_BASE>\oradata\<DB_NAME> . For example:  D:\oracle\product\10.2.0\ oradata\my_db\

Step 5: Naming Files In Oradata Directory

Datafiles should be in format <tablespace_name><counter>.dbf . For example:  mytablespace01.dbf .

Online redolog files should be in format redolog<counter>.log . For example: redolog01.log, redolog02.log, redolog03.log .

Control files should be in format control<counter>.ctl . For example: control01.ctl, control02.ctl, control03.ctl .

Step 6:  Spreading Files

It is quite common to have data on multiple physical disks to spread I/O workload and thereby provide better performance and reliability. In such a situation create the same directory structure on all drives and spread the files in relevant directories.  For example the log files can be shared among the drives like:

 C:\oracle\product\10.2.0\oradata\my_db\redolog01.log
 D:\oracle\product\10.2.0\oradata\my_db\redolog02.log
 E:\oracle\product\10.2.0\oradata\my_db\redolog03.log

Rapidshare

Megaupload

Mediafire

Depositfiles

Semoga bermanfaat

Fedora 12, which is codenamed Constantine, has been released in to the Linux market. This time around, there have been a large number of enhancements built right into this version. Some of the enhancements are support for Bluetooth audio devices, better tablet support, and much more.

If you are a Fedora person, then you need to defintely grab this version.

Some more information can be obtained from here:

Download:

• Fedora 12 Installer
• Fedora 12 LiveCD

Part 1

Part 2

Part 3

Part 4

Part 5

Part 6

Semoga bermanfaat

Video Tutorial UFS  (All In One)

Part 1

Part 2

Semoga bermanfaat

Video Tutorial Flash Nokia via UB (All In One)

Part 1

Part 2

Part 3

Semoga bermanfaat

Video Tutorial Flashing SonyEricsson Via UB (All In One)

Part 1

Part 2

Semoga bermanfaat

Video Tutorial MTBox-Nokia (All In One)

Part 1

Part 2

Part 3

Semoga bermanfaat

All Video Tutorial Cruiser (All In One)

Part 1

Part 2

Part 3

Part 4

Semoga bermanfaat

Video Tutorial Cyclone (All In One)

Part 1

Part 2

Part 3

Part 4

Part 5

Part 6

Semoga bermanfaat

All Tutorial Video JAF (All In One)

Part 1

Part 2

Semoga bermanfaat (d3)

GO HERE FOR SONGBIRD INSTALLER (REDIRECT TO SKYZIM.COM)

This week the installers and basic demonstration for IOME has been developed, improved and tested.

For the IOME distribution we aim to provide

1. Easily installable applications, libraries and examples for windows, linux and other platforms
2. Demonstrations which may be run with relative ease and using open source applications
3. Source distributions for developers

We now describe the installation of the binary distributions. Installation of source distributions will be considered in a separate entry. The following linux binary distributions have been provided.

1. redhat 32 bit x86
2. redhat 64bit amd opteron
3. ubuntu 64bit amd athlon

Currently the procedure for installing IOME binary distrbutions under linux are as follows.

1. Create and move to the installation directory
2. Copy the distribution to the installation directory
3. Extract the distribution using tar -zxvf  distribname.tgz
4. Create and set the IOME_HOME  variable to point to the IOME home directory
5. Append the PATH environment variable to point to the IOME bin directory e.g. export PATH=$PATH”:$IOME_HOME/bin”
6. Append the LD_LIBRARY_PATH environment variable to point to the IOME lib directory e.g. export LD_LIBRARY_PATH=$LD_LIBRARY_PATH”:$IOME_HOME/lib”
7. As an alternative to 6 the user (as admin user) may copy the executables to /usr/bin and copy the contents of lib to the /usr/lib folder . We recommend using the cp  command with the -i interactive option which will ensure that files to be overwritten are prompted for.

For the windows installation there are two alternatives

1. Use windows installer
2. Use zipped distribution and follow procedure similar to that described above for linux. Binary (executable) and lib files will be copied to the Windows/system32 folder. Once again caution against file overwrites is recommended.

Using the windows installer the user is simply required to  double click the installer and follwo the wizard instructions.

We used inno to build the installer, available from http://www.jrsoftware.org/

Inno has quite detailed help it has a script file which the developer is required to finish. The following 4 lines, illustrate the script commands used to relocate file contents to the required folder.

Source: “src\tools\scilab\iome_toolbox\macros\*”; DestDir: “{app}\src\tools\scilab\iome_toolbox\macros”
Source: “src\tools\scilab\iome_toolbox\tests\unit_tests\*”; DestDir: “{app}\src\tools\scilab\iome_toolbox\tests\unit_tests”
Source: “Readme.txt”; DestDir: “{app}”; Flags: isreadme
http://www.jrsoftware.org/

Setting Environment Variables

On Windows NT/2000/XP/2003, environment variables are stored as string values in the registry, so it is possible to manipulate them using the [Registry] section. System-wide environment variables are located at:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

User-specific environment variables are located at:

HKEY_CURRENT_USER\Environment

[Icons]
Name: “{group}\My Program”; Filename: “{app}\MyProg.exe”

[Registry]
Root: HKCU; Subkey: “Software\My Company”; Flags: uninsdeletekeyifempty
Root: HKCU; Subkey: “Software\My Company\My Program”; Flags: uninsdeletekey
Root: HKLM; Subkey: “Software\My Company”; Flags: uninsdeletekeyifempty
Root: HKLM; Subkey: “Software\My Company\My Program”; Flags: uninsdeletekey
Root: HKLM; Subkey: “Software\My Company\My Program\Settings”; ValueType: string; ValueName: “InstallPath”; ValueData: “{app}”

The root key. This must be one of the following values:
HKCR    (HKEY_CLASSES_ROOT)
HKCU    (HKEY_CURRENT_USER)
HKLM    (HKEY_LOCAL_MACHINE)
HKU    (HKEY_USERS)
HKCC    (HKEY_CURRENT_CONFIG)

Registry Keys for Environment Variables

For those who are experienced with editing the Registry, there is another way to make changes in environment variables. User environment variables are stored in the Registry in the key:
HKEY_CURRENT_USER\Environment
System variables are found in the key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment

Note that any environment variable that is in the form that needs to be expanded (for example, %PATH%) must be stored in the registry as a REG_EXPAND_SZ registry value. Editing the Registry is primarily for scripts used by systems administrators and is not recommended for the average PC user.

Notes on modifying the path environment variables are at

http://legroom.net/software/modpath

Currently a single demonstration has been provided which is easily run. For the scilab examples a simple wave propagation example is easily run by running the steer.sh (on linux) or startdemo.bat (under windows). To be able to do this the user must

1. Install or have installed python (e.g. by visiting http://www.python.org/download/ )
2. Install or have installed scilab, at least version 5 ( e.g. by visiting http://www.scilab.org/download/ )
3. Install IOME (to be described briefly below)
4. Create and set the SCILAB_HOME  variable to point to the scilab home directory
5. Create and set the IOME_HOME  variable to point to the IOME home directory
6. Create a PYTHONPATH variable e.g. export PYTHONPATH=$PYTHONPATH”:$IOME_HOME\src\tools\python”
7. install the iome_toolbox in scilab. Copy the iome_toolbox folder from $IOME_HOME\src\tools\scilab\iome_toolbox to the $SCILAB_HOME\…\contrib\      folder.  As a user with admin rights, start scilab navigate to the iome_toolbox folder. To build and  the iome toolbox run the builder routine by typing exec(‘builder.sce’); from the scilab command line.

With the above steps and checks completed the user should be able to run  the scilab_wave_ws demonstration, which enables the user to use and develop IOME applications.

Pour cause de changement de site cet article est déplacé ici !

Merci de votre visite !

Pour cause de changement de site cet article a été déplacé ici !

   A fresh installation of Windows offers users a chance to get things clean and tidy from the beginning, but it also means a lot of work (which we literally hate) reinstalling applications you may have had on an older build. Even searching and downloading the latest versions of your favorite applications is very much time consuming and we are the fast movers and every single second counts.

  So here is a very simple tool for windows called Ninite (formely Volery) which allows you to create an unattended single installer for lots of popular software programs. You can choose the programs from a given list and it’ll create the installer for you.

  Ninite runs on Windows XP, Vista and 7 and works in the background 100% hands-free.

  It installs apps with default settings and say "no" to browser toolbars and other junk.

  Also it installs the latest versions of the apps you choose. Not even Ninite is installed.

How to work with it

 1. Just visit Ninite website.

2. Select the application you want ninite to install for you.

3. Once you selected the application then click on Get installer. You’ll be prompted to download a small .exe file. Save it to your desktop(any where you want to save it).

4. Now just run the .exe file, and leave it to the ninite to download and install your favourite software.

Now all your software installed and ready to use.

Enjoy!