Definieren van USB printer op Apple Airport Express

't is ni voor het één of het ander ... maar de Apple spullen zijn dik onderwaardeerd.

Sinds een half jaar in het bezit van een airport express en de funcitionaliteit is omonwonden verbluffend: 

• draadloos netwerk tot draft-n 
  
• usb connectie voor het aansluten van een netwerk printer
  
• aansluiten van uw hifi keten om uw mp3 tjes overal af te spelen
  

Dit laatste stukske is wel gelimiteerd omdat dit enkel werkt in iTunes maar soit ... het zij wat het zij ... dat werkt dan ook zoals het moet en niet anders ...

Afin het probleem is hoe een usb printer die aan de Apple Airport Express hangt te registreren onder uwen old fashion Windows xxxx.

FF rondsurfen in google en hopla : volgende link ... hierbij gezet onder het motto 'ere wie ere' toekomt ...  : http://www.macosxhints.com/article.php?story=2003072510530643

Het gaat daar wel om de zwaardere broer van de express ... de extreme.

Dus de stappekes:

• ga naar control panel > printers en faxes
• rechts klik in de lijst van printers (of gebruik een eventueel beschikbare shortcut) en selecteer 'add printer';
• Selecteer (na next geklikt te hebben in een weer overbodig Microsoft scherm) locale printer en deselecteer autodetect, klik next
• In het scherm 'selecteer een printer poort', selecteer voor de creatie van een nieuwe poort, en zet het type naar een tcp/ip poort, klik next
• in de wizard (weeral een nieuwe) klik eerst next. In het scherm voor de host. Vul hier het IP adress in van de airport express. Pas eventueel de naam aan. (dit is de nieuwe poort naam);
• Dan wordt er gevraagd welk het type van apparaat is, omdat het default type niet automatisch kan bepaald worden. Het gaat hier over het protocol dat moet gehanteerd worden ... en ik veronderstel ook de default poort die gebruikt zal worden. Gebruik hier het 'hewlett packard jet direct' (wat een printer software laag over tcp/ip definieerd die door de apple airport express gebruikt wordt)
• Daarna wprdt de poort gevraagd .. maar hier kan je de default nemen, gezien die een gevolg is van het protokol dat in de vorige stap ingesteld werd; klik daar dus next;
• Dan wordt de printer gevraagd. Hier moet je het juiste merk en type instellen. Na selectie, klik next;
• Dan kan je de naam instellen hoe de printer gekend is op je Windows brol; klik daarna next 
• Blijf next klikken ... Tot het ding gedefinieerd is.
• Indien je de printer als default printer wil gebruiken defineer hem dan ook zo.

Hierna kan je je printer rustig gebruiken.

Om toch maar weer de vergelijking te maken,De installatie op de macbook pro is beschrijfbaar in twee stappen, waarvan er één nog niet eens in de voorvermelde lijst staat:

• Sluit de printer aan de airport express en zet hem aan
  
• Verifieer, ja ... dus niet configureer, in de airport setup utility of the printer herkend werd.

Het speelt waarschijnlijk wel in mijn voordeel dat de printer een HP vrij standaard model is ... maar dan nog, het is een klein verschil ... maar telkens je iets op de apple computer moet doen denk je twintig stappen te ver. Ik vraag me ten stelligste af welke depressies mensen ondergaan die van een Apple noodgedwongen en overhoeds overschakelen op een of andere windows brol.

Afin de groeten;

 

VNCServer op Ubuntu Server/Desktop

This topic ... it was missing.
For the sake of all the Tims and Toms I still have some work here.
I want to point them for the moment to a number of documents that already exist and which I have used in the past to get it working on Ubuntu.
So here they come
http://ubuntuforums.org/showthread.php?t=795036

Valid xorg.conf file for linux OBI for DELL 630 Laptops

Seems like the next piece of text may be rather important if you are running the linux OBI on your laptop.
Everybody knows Marc De Weerdt ...(hope his name is in the correct tense) who provided the piece of plain ascii characters to be posted on this Hawtoes blog. Caught him correcting the file for one of our most junior people who came only just out his egg and started working with Linux. At least ... it's an intelligent chicken.
After you used it, be so kind to sent him all the honors. As well as ...any complaints and questions ...

# Xorg configuration created by pyxf86config

Section "ServerLayout"
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
InputDevice "Synaptics" "CorePointer"
EndSection

Section "InputDevice"
Identifier "Keyboard0"
Driver "kbd"
Option "XkbModel" "pc105"
Option "XkbLayout" "be"
EndSection

Section "InputDevice"
Identifier "Synaptics"
Driver "synaptics"
Option "Device" "/dev/input/mice"
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.3"
Option "MaxSpeed" "0.75"
EndSection

Section "Monitor"
# VertRefresh 56.0 - 75.0
# HorizSync 60.0 - 60.0
### Comment all HorizSync and VertSync values to use DDC:
Identifier "Monitor0"
ModelName "Dell E228WFP"
### Comment all HorizSync and VertSync values to use DDC:
HorizSync 30.0 - 83.0
VertRefresh 56.0 - 60.0
Option "dpms"
EndSection


Section "Device"
Identifier "Videocard0"
Driver "vesa"
VideoRam 393216
EndSection

Section "Screen"
Identifier "Screen0"
Device "Videocard0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Virtual 1440 900
Depth 8
Modes "1440x900"
EndSubSection
SubSection "Display"

#Modes "1680x1050" "1440x900" "1280x800"
Viewport 0 0
Virtual 1024 768
Depth 16
Modes "800x600"
EndSubSection
SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection

Windows Explorer extremely slow to open

Symptoms:
When pressing the Windows+E key - which should open windows explorer immediately - it takes a long time before something happens.
Consequently opening a word document or excel sheet are also slow.

Reason for slowness
The reason is not known to me ... but the solution may work in your case ...

Solution
After ruling out a number of straith forward reasons like unavailability of network paths ... one of your last resolutions may be a problem in some Microsoft - or what had you thougth - temporary files.

Solution
In order to solve the problem, it is very well possible that you must create an other windows local admin user, if none accessible user exists. The next scenario foresees the steps including the creation of the extra account

Solution Steps

• Create a local admin user if none exists yet which is different from the user who has the problem;
• Log off as the user having the problem;
  
• Log on as this admin user;
• Go to the following directory
  c:\Documents and Settings\<profile>\local settings\application data\microsoft
  ;
  
• Locate in that folder a folder named 'windows' ... what had you thought ;o)
• Rename - or delete if you want to - the folder to something else (eg windows.old)
• Log off as the newly created or exisiting other admin user;
• Log in as the user who had the problem;
• The windows folder will be created again;
• For some wonderful reason ... this will solve the problem;

Hope this helps ... don't ask why it helps ...

Overwriting files in use by Forms Server

Problem
This is standard behaviour since the server uses memory mapped i/o or ... it considers the file as
part of the working memory environment.
This method is ideal for a production environment but ... not for a development environment.

Solution
Setting the environment variable FORMSxx_MMAP to a particular value (0 or False, depending on the version of the server) will disable the memory mapped i/o mechanism.
Depending on the version of the server other variable

The variable
Forms version 4.5, 5.0, 6.x and 9.x use the FORMSxx_MMAP variable.
Later versions use the variable FORMS_MMAP

The value
Upto version 6.x the value has to be set to 0 for disabling and 1 for enabling the memory mapped i/o.
From version 9.x onward, the values are TRUE for enableing and FALSE for disabling the feature.

An example:
In a 10g environment you would have to insert a line in the .env file for your environment like the following
FORMS_MMAP=FALSE

Vista and Samba

Mandatory Shouting

Well ... nice trick of MS again to try and be incompatible with the rest of the world.

What's the problem?

You have a new pc (or already an old one) with Windows Vista on it and you are not able to connect to Samba drives, either by windows explorer or by the 'net use' command. A typical symptom you will notice on protected drives is the fact that the username/password combination is never accepted.

If you have Windows Vista Home you will not be able to connect to Samba Shared drives. Nice ... hmmm ... Just Microsoft alike.

How to solve it?

After looking around the internet some solutions are available but most of them seem not to be valid work arounds.

1. Upgrade Vista to a "Professional" level
The Vista standard installed on most private customers' pc's is a basic version from which MS has seen it appropriate to remove some tools from the more professional versions which you need to solve these kinds of problems.

An upgrade costs ... 100 € at least ... so ... to me not valid.

In case you have the more expensive version you should use a program which lets you handle the local securi!ty policies on Windows Vista: secpol.msc. This is missing from the Vista Home versions.

2. Go to a an OS which is worthwhile and not purely commercially oriented.

The solution can be reduced to a choice for the best distribution for your particullar situation.

Ubuntu linux has some flavors for any kind of objective ...

This is a challange too ... but it will work out fine unless MS-depending programs need to be run, which would be a strategic error since everything is moving to open-internet technology.

3. Change a registry value ...

Found this on the following link : http://forums.techarena.in/windows-vista-network/670498.htm and is valid for the Vista Home distribution

In short:

• go to the registry (windows-R type regedit and press the run button)
  
• select in the left pane registry key HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Control/LSA
  
• Select in the right pane the value LmCompatibilityLevel (the value will be 3, stored in hex)
  
• Doubleclick on the LmCompatibilyLevel item, a box with the value will apear.
  
• change the value to 2 (some say 1) I set it to 2 and this seemed to work (maybe this depends on the version of Samba your target is running)
  
• press the OK button
  
• exit the registry editor
  
• Some say a reboot is required some don't. Quess the best thing to do is reboot.
  
• Then try connecting by the command "Net use" from the command line or by mapping the network drive in windows explorer.
  
• This should have solved it.

The fact is that MS is considering that a certain security protocol is in place for all external sources ... which seems not to be the case. This is where the '3' comes from. (see also http://www.linux-watch.com/news/NS4434907782.html )

Hope this did the trick for you.

Oracle Jinitiator - Left handed mouse bug

As if I would like to tell that a mouse is a bug.

Problem:
See metalink bug 2200274
When the functions of the left and right mouse buttons are switched under ms-windows, the function of the selection mouse button, originally the left button, is lost, resulting in having only a context button on the left button.

Research< style="font-weight: bold;">Solution:
A valid solution is to go to a JPI configuration, for the newbies, 'a java plug in'.
This makes the deployment of Jinitiator obsolete but makes the presence for the correct JRE mandatory.
A test with version 1.6.0.10 worked very fine and solved the left-right mouse button problem.

Steps:

First,
Create in your formsweb.cfg file a new configuration section ... or better copy the one you were using. For those of you who did not use configurations ... this is a good time for starting doing so.
A config is identified by squarebrackets like this:
[ MyJPIConfig]

Second,
Point the basehtml files to point to the jpi files:

baseHTMLJInitiator=basejpi.htm
baseHTMLie=basejpi.htm
baseHTML=basejpi.htm

Third,
Configure the archives to be loaded by means of the archive_jpi tag:
archive_jpi=frmall.jar,laf.jar,

Fourth,
And ... this should come first ... But since people only remember the last thing they are told ... I'm putting this as the last thing to do.
Enable the correct download of the JRE to be used and set the set the correct identifications for the plugins to be used.
Normally you would download it and then put it on your intranet with the correct url.

Fifth,
This is optional ... but gives some additional configuration possibilities:
envFile=
form=
userid= if no connectstring has to be used.
pageTitle=
width=
height=
separateFrame=
lookAndFeel=
colorScheme=

Now you should have something like the following:

[ MyJPIConfig]
baseHTMLJInitiator=basejpi.htm
baseHTMLie=basejpi.htm
baseHTML=basejpi.htm
jpi_download_page=http://jan.hellings.be/jre/jpi_16010_windows.exe
jpi_classid=clsid:CAFEEFAC-0016-0000-0010-ABCDEFFEDCBA
jpi_codebase=http://java.sun.com/update/1.6.0/jinstall-6-windows-i586.cab#Version=1,6,0,10
jpi_mimetype=application/x-java-applet;jpi-version=1.6.0_10
envFile=ApplicationEnvFile.env
form=startform.fmx
userid=defuser/defpassword@defconnectstring
otherparams=buffer_records=%buffer% debug_messages=%debug_messages% array=%array% obr=%obr% query_only=%query_only% quiet=%quiet% render=%render% record=%record% tracegroup=%tracegroup% log=%log% term=%term%
pageTitle=MyPageTitleTexteke
width=1280
height=750
separateFrame=true
lookAndFeel=Oracle
colorScheme=blaf

Conclusion
It seems to me that performance is much better using the newer version of JRE than the one provided by Jinitiator.

Greetz,
Jan.

Designer export reinstall

This document to indicate the steps required to re-install a backup from the designer repository

Two scenario's are possible:
- import into a new schema
- import into an old schema - first clean the schema

logic:

B
A --< > D --> B --> D .....
C
A. Decide on the scenario

The first thing to do is to decide on wheather to reinstall the existing schema or create a new one. The result of the decision will depend on the reason for reinstallation.
If you are reinstalling from scratch you will need to create everything again.
In case something went wrong or as for the reason I am currently writing this guide, with a patchset, it may come out handy to keep the complete schema and create a new one too.
If however you created a new environment and something went wrong during the import for example, you will need to clean up the schema again.

B. Clean the schema

In order to reinstal in the same schema, all the objects of the schema must be dropped.
Run the next script and make sure the number of bytes in the dbms_output buffer is high enough.


set serveroutput on

declare
cursor c_obj
is
select object_name
, object_type
from user_objects
where object_type in ('TABLE', 'VIEW', 'PACKAGE', 'SEQUENCE', 'FUNCTION', 'SYNONYM', 'TYPE')
order by decode ( object_type
, 'FUNCTION', 1
, 'PACKAGE', 2
, 'SEQUENCE', 3
, 'VIEW', 4
, 'SYNONYM', 5
, 'TABLE', 8
, 'TYPE', 9
)
, object_name
;
begin
--
for r_obj in c_obj
loop
if ( r_obj.object_type = 'TABLE' )
then
dbms_output.put_line ( 'Drop '
|| r_obj.object_type
|| ' '
|| r_obj.object_name
|| ' cascade constraint purge;'
);
else
dbms_output.put_line ( 'Drop '
|| r_obj.object_type
|| ' '
|| r_obj.object_name
|| ';'
);
end if;
end loop;
--
end;


Paste the output into a new script file and ... execute this script.
Repeat this process until only two objects remain.


B. Create a new environment

B.0 Create the tablespaces

First create the tablespaces that are required.
Here are scripts ... change where needed

create tablespace designer_data datafile 'd:\oracle\product\10.2.0\oradata\jhelling\designer_data1.dbf' size 200M autoextend on next 100M maxsize 512M / create tablespace designer_index datafile 'd:\oracle\product\10.2.0\oradata\jhelling\designer_index1.dbf' size 200M autoextend on next 100M maxsize 512M /

B.1 Create the user

Alternatively you can create a new repository owner.

create user des identified by oradev default tablespace users temporary tablespace temp;
alter user des default tablespace designer_data;

B.2 Assign the correct roles:

grant connect, resource to des;
-- grant dba to des; // not realy needed so leave it out

B.3 Give system privileges

grant alter session to des;
grant create any synonym to des;
grant drop any synonym to des;
grant create database link to des;
grant create procedure to des;
grant create role to des;
grant create sequence to des;
grant create table to des;
grant create trigger to des;
grant create type to des;
grant create view to des;
grant select any sequence to des;
grant unlimited tablespace to des;

B.4 Give sys privileges

grant select on dba_rollback_segs to des;
grant select on dba_segments to des;
grant execute on dbms_lock to des;
grant execute on dbms_pipe to des;
grant execute on dbms_rls to des;
grant select on v_$nls_parameters to des;
grant select on v_$parameter to des;

C Importing the dump file.

C.1 Create types.

When creating two repositories on the same database while using imp, the import will fail during the first lines with the error ORA-2304 which is caused by the 'stupid' constraint that object types must have a unique ID within the same database instance. See herefor notes 1066139.1 and 113335.

Currently looking for a workaround ...

These are the types that are defined in script jrtypes.sql in the repadmxx directory of the installation. Seems that the export of the designer does not take these types as user objects and they are therefor lost in the export (create any type privilege)
The content of the scripts is as follows :

create or replace type jr_num_list as table of number
/
create or replace type jr_str_list as table of varchar2(300)
/
create or replace type sdd_acc_priv_list as varray(25) of varchar(1)
/
create or replace type sdd_sys_priv_list as varray(25) of varchar(1)
/

C.x Create role CKR_DESIGNER

Create this role before import because a lot of grants are done to this role.

C.2 Verify tablespaces

This is a step you should not foreget, surely when you are installing an additional schema.
As you will have noticed I explicitely changed the default tablespace of the owner to designer_data. I use to have an other tablespace designer_indexes.
The import will assume the tablespaces exist so, verify into detail what your requirements on this will be.

C.3 Start the import

Now it is time to import the backup-export from the designer owner.
Here you can use the following command

imp userid=system/xxxx@xxxxx fromuser=designer touser=des file=desdump.dmp log=import.log

In this example you should specify the system connect string, the correct owner of the exported objects (fromuser) and the future owner of the newobjects (touser). The filename, desdump.dmp, should be changed to the correct value.

Start this command.
In parallel you will be able to find the results of the import in the import.log file.

D Upgrade to the correct version.

If your software is of a higher version than the one loaded ...

D.1 Be sure to use the correct imp.exe.
Before you do so however, you should check if it is not required to perform the steps indicated in the chapter on import problems. See below for this.

D.2 Upgrade the repository

Go the RAU (repository administration utility)
Normally you will only see some buttons enabled if the version of the repository is not compatible with the version of the designer software installation.
Press the upgrade button and the upgrade of the repository will start.

D.3 Verify all the objects.
On the RAU press the 'view objects' button and select then 'all objects'.
You should see the number 5711 of objects.
When you select the invalid and missing objects from the dropdown, no objects may be shown.

Problems encountered

IMP hangs when upgrading the repository

When upgrading repository the import hangs
I guess this is documented in note 5236740 bug 5236740 base bug 5225496
The import loaded data in two tables and then stopped ... and waits ...
I clicked in the cmd window and pressed ctrl-c ... which made the import stop and the real upgrade of the repository start.
These are the symptoms of the problem.
The solution is to set registry variables to point to an other version of imp and exp.
It comes to this:
Lookup the registry key for the iDS s
- HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_\REPOS61
Now change the values of the string values EXECUTE_EXPORT and EXECUTE_IMPORT to the full path of imp.exe and exp.exe to be used, so the one in the different Oracle_Home.
Be aware that the path for this variable can be too long. You should than solve this by creating a subst drive ...
subst :
for example subst x: D:\Oracle\product\10.2.0\db_1
The command to put into the EXECUTE_EXPORT and EXECUTE_IMPORT entries becomes rather simple : x:\bin\exp.exe and x:\bin\imp.exe
Remember however that a 'subst'ed drive is only valid until you reboot the windows OS.

ORA-28100
While opening my ER diagram I got the error ora-28100.
The sql statement that failed was:
SELECT cel.id, cel.ivid, cel.name, cel.container_subtype FROM ci_container_elements cel WHERE cel.root_flag = 'Y' ORDER BY 3;
Running this script in sql gave the following error:
ORA-28100: policy function schema DESIGNER is invalid

The original owner of the designer repostitory, so the one owning the original objects, was designer. I imported the export into the des schema.
On metalink you can look for note 602437.

Execute the following sql statement (change designer in your provious repository owner)
select * from dba_policies where pf_owner = 'DESIGNER'

Ubuntu Server - Defining Screen resolution

Problem Statement

After installation Ubuntu servers screen is not in synch with the resolution of the display

Solution

Found this document on the internet.
Thanks to the author ...

The resume of this article is as follows:

Howto

The screen resolution is determined at startup ... when the kernel is loaded.
An option can be specified to the kernel to indicate the required screen resolution.
So ... three steps:
- determine parameter
- change menu.lst and the parameter
- reboot the system

Determine the correct vga parameter

Determine the argument using the following table

          640x400 640x480 800x600 1024x768 1152x864 1280x1024 1600x1200
--------+--------------------------------------------------------------
4 bits |    ?       ?     0x302      ?        ?        ?         ?
8 bits |  0x300   0x301   0x303    0x305    0x161    0x307     0x31C
15 bits |    ?     0x310   0x313    0x316    0x162    0x319     0x31D
16 bits |    ?     0x311   0x314    0x317    0x163    0x31A     0x31E
24 bits |    ?     0x312   0x315    0x318      ?      0x31B     0x31F
32 bits |    ?       ?       ?        ?      0x164      ?

Look up the coorect vga indicator in the following table:

Edit the menu.lst file

Edit the /boot/grub/menu.lst file
Look for the correct line that defines the kernel to use with the correct options and if not already present add a parameter vga=0xyyy
The value 0xyyy is the vga parameter that you determined in step 1.

Reboot the system

Enter the following command:

#> reboot


A reboot is required to enable the setting.

Ubuntu Server - SSH configuration

Found the information on the following this link
Here follows a resume where I left out the sudo command because personally I always set a root password.

Check sshd service is running:

#> netstat -tulpln | grep -i ssh

Configure ssh port to something nonstandard

go to /etc/ssh
edit the sshd_config file (with vi for example)
Search for the keyword 'Port' which will be followed with 22 because this is the default
Change 22 to for example 512

Restart SSH deamon

#> /etc/init.d/ssh restart

Verify that the port is enabled by running netstat -tulpn | grep -i ssh again.

Firewall blocking

Verify with the following command that the port is open for connection through the firewall

#> iptables -L -n

This should give a list of all listening ports ... including as in the example 512.

If it is not in, configure it <>

Now you should configure your SSH client tool to connect to the server.

Look at this link to see how to configure PuTTY