by

رسالة من ثائر حمصي

رائعة جداً، المصدر في الموفع:
http://fb.me/UZyMdD53

وهنا النص الكامل:

مشــــــــاركة مـــؤثرة من ثائر حمـــــــصي :
من حمص /
مين منكم متشائم ؟ .. بس يقللي أنا ؟ .. لقلوا شرررف على حمص .. و خود تفاؤل .. خود عزيمة و خود همة ..

اليوم عملت فتلة بحمص .. ما شفت واحد خيفان .. ما شفت بني آدم يأســـان … شعب ما طبيعي ..
… … ابتسموا .. افرحوا … راح الكتير .. وبقيان على قولة الحجي .. عضت كوساي ..
مين حاطط صورة بروافيلوا سودي .. شيلهاااااا ..
الشهداء عم يبتسموا .. ونحنا ما نا أحسن منون ..

المغتربين .. جد عم حكيكون .. ضبوا الشناتي .. ما اشتقتولنا ولووو .. يلا ضبوا الشناتي .. وجيبولنا هدايا .. امسحوا دموعكم .. نحنا مسحناها .. من زماااااان ..

بلدنا حلووووة .. ومن زماااااان كان بدها هزة زغيرة .. لك نسيتوا شو كنت تقولوا .. هز الورد لتشم ريحتو .. وفي احلى من ريحة تراب بلدنا ..

قسما بالله العظيم نحنا مبسوطين .. ازا متنا .. أقل شي منموت كرمال هالبلد .. ههه ملينا جلطات … هههه ..

هااااااااااااااااااااااااااااااااااااانــــــــــــــــت

بدنا تعطونا دعاءكم و بسماتكم .. ما شايفين شلون بسمتي شبر ..

كرمالك يا وطــــــن لنصبر ع المحــــــــن

by

HP Printer Problem (PCL XL ERROR) with Windows 7

You might think it’s better to use the latest standards. Well, in this case it’s not.

Windows 7 x64 (64-bit) with HP Laser Jet 3600n is a nice combination when using the HP Universal driver for Windows 7

Most of things works fine except when it comes to pure pictures or graphics, then you may face the following symptom

A blank paper, followed by another paper with these lines on it:

PCL XL error

Subsystem: KERNEL

Error: IlleagalTag

Operator: 0x??     or      Operator: VendorUnique

Position: 3 or 5 or 15 or may be something else (I think this depends on the application you’re printing from and the document content)

 

However, the solution for me was simply downloading the Vista x64 driver and use it.

by

Manually Migrating from VMware vCenter 4.0 to 4.1

Well, the case is as follow:

Old vCenter server is Windows 2003 32-bit, with SQL 2005 Standard, and VMware vCenter 4.0

New vCenter server is Windows 2008 R2 64-bit, with SQL 2008 Standard, and VMware vCenter 4.1

Both are kept running, so they have different server names, and IP addresses. Which means there are NOTHING common between the two systems, but the client still want to migrate the configuration so they don’t have to re-configure everything on the new environment.

Ok, after reading too many documents and websites and other people experiences, it turned out very simple process.

On old server:

1. Stop the VMware vCenter services.

2. Backup the database using the Management Studio (make full backup)

On the new server:

1. Install SQL server (if you’ll have on the same server) and configure it for both Windows and SQL authentication

2. Create the database “VMware vCenter” (just like the old server database name)

3. Create vmware SQL user, and grant it dbo on the database created in step 2

4. Create the System DSN (64-bit) and make sure to use the account created in step 3

5. Import the backed up database from the old server, then fix the permissions on it

6. Start the vCenter setup and during the setup it will discover the exiting database, and give you an option to upgrade it (it’s version 4.0 after all)

It will take a while, the database can be easily more than 1.5GB, so don’t worry about that.