Despatch .exe dated 16-12-2009

Despatch.exe dtd 16/12/2009 : Download

(for 2nd Despatch not Extracted in DET Figure )
1 Replace the existing exe with new2 Update Counter Database with counter16122009.exl using Script ToolAfter appling this new Update for Despatch please check whether still that issue is there
You have to strictly follow the shiftend sequence where POS shiftend should be at last.

EBill communication upgrade 07-12-2009

Download

Procedure:
1. Copy or Replace the following files into ePayment client installation folder (C:\Program Files\ePayment Client)
a. EBillCommunication.exe
b. EBillCommunication.exe.config
c. ptcmyscs_root.cer
d. RegisterCACft.exe
2. Double click on RegisterCACft.exe for installing security certificate.
3. Now ePayment client is upgraded and ready for communicating with central server.
IMPORTANT NOTE: This procedure should be done only on 07/12/2009 before connecting to ePayment central server.

Sanchay Post

Download all update of Sanchay Post upto 12/11/2009

Signature Scanning Scanner Tool integrated with Sanchay Post software

Project Arrow Pacth Dated 12-11-2009 (For SB Branch KPI Score)

1. Download SSS Tool

2. Download Instructions
Features:

- SSSCanner is a small software tool for scanning of Specimen Signatures using WebCam/PC Camera without any third party applications.
- This software can be integrated with Sanchay Post software.
- No manual intervention for editing the generated BMP file.
- The size of the BMP file is less than 15 KB.
- Based on the selected category and the account number entered/generated the required scanned file will be generated.
- The scanned signature created can be saved directly into Sanchay Post database using Sanchay Post software.
- Low cost hardware requirement i.e. WebCam/PC Camera.

How to Join Two Domains

Domains by default are unable to communicate with other domains, which means somewhere in domain DOP1 cannot access any resource that is part of domain DOP2. Before a trust relationship is configured
(A) an administrator in DOP1 cannot give permission to any user of domain DOP2 for files or printers

(B) a user of domain DOP2 cannot sit at a workstation that is part of domain DOP1 and login

After a trust relationship is defined, say DOP1 trusts DOP2 the following happens

(A)users of domain DOP2 can sit at a workstation that is part of domain DOP1 and login to their own domain DOP2 (it will be displayed in the domain dropdown box)

(B)an administrator of domain DOP1 can grant permission to any user of domain DOP2 to file and print resources
(C)users of domain DOP2 are included in the Everyone group of domain DOP1

In the example above DOP1 is the trusting domain, and DOP2 is the trusted domain.
Also the above is a one-way trust relationship, i.e. while domain DOP2 users can use domain DOP1 resources, users of domain DOP1 cannot use domain DOP2 resources. A two-way relationship would allow each domain to access resources of the other (if given permission).
The basics of a trust relationship is to first configure domain DOP2 to allow domain DOP1 to trust it, and then configure domain DOP1 to trust domain DOP2:

(1)Log onto domain DOP2 as Administrator
(2)Start Active Directory Domains & Trusts for Domains (Start - Programs - Administrative Tools)
(3)Select "the properties" of the DOP2 domain then "Trust Tab"
(4)Click the Add button to " the domains that trust this domain" box
(5)Enter the name of the domain you want to be able to trust you, i.e. domain DOP1
(6)You can type a password in the Initial Password and Confirm Password, however this is only used when the trust relationship is started. You can leave it blank Click OK to complete the addition
(7)Close the Trust Relationship dialog box
(8)Log off of domain DOP2 and login onto domain DOP1 as Administrator
(9)start Active Directory Domains & Trusts for Domains (Start - Programs - Administrative Tools)
(10)Select "the properties" of the DOP1 domain then "Trust" tab
(11)Click the Add button to " the domains trusted by this domain" box
(12)Enter the name of domain DOP2 and the password if one was configured in step 6
(13)Click OK and close.
(14)Domain DOP1 trusts domain DOP2

Latest Patch and software

DBanalyzer dated 12-11-2009

CC Bridge Ver 4.0 Dated 12-11-2009

Sanchay Post Patches dated 12-11-2009

Postman updates Latest (Including Account MIS Solution)

Download Postman updates (Including Account MIS Solution) dated 11-11-2009

For discrepancies in Speed and BNPL figures

Download Guidelines dated 06-11-2009

Download CounterDET.Sql dated 06-11-2009

Point of Sale Submit account problem

1 Login as supervisor to Point of Sale application and change the name of the Treasury server and Click on OK button. (Though you have already configured the Treasury server name do it once again.)

2.Execute the Downloaded Treasury.exl with the ScriptTool for Treasury database

Reset Registration of eMO & ePayment

Problem In Despatch of Speed Post Articles

hereby please download Counter.sql execute the attached file in Query Analyser for the Counter DB
and please note some more point everyday please insure that
1 Flush the data of speednet after total despatch
2 Day end of Speednet and Despatch module
3 At last Point of Sale shift end

Thanks to Sh. Mohit Verma SM Naraingarh S.O Ambala for this Query

Downlaoad Counter.Sql

Despatch Local Speed Post Articles

Download Solution for Local Speed Post Article Despatch

or book the local articles without pincode and fetch the data

New Exe of Postman Module dated 24-10-09

Download new Postman updates dated 31-10-2009

1) Restriction of addresses to a single beat in Pre-sorting of RL/MO/Parcels. Now all the addresses under the delivery jurisdiction of the office will be displayed

2) Error that ‘Cash is not yet issued to postman’ coming at the time of taking eMO Returns

3) Number of Speed Post articles received (being fetched through DET) is coming wrongly

4) Automation error coming in emoàreturnsàView/modify option is rectified

5) Automatic selection of emos with up/down arrow keys

6) Returned to Sender option in Window Deposit

7) If Meghdoot server and Speednet Server are not in the same network, please check up the guidelines mentioned in page-2, so that the speednet data can also be fetched smoothly through DET

Latest DBAnalyzer dated 22-10-2009

Download Latest DBanalyzer

Account MIS

AccontMIS data Transfer & Dayend Sequence
1. SpeedNet
2. Postman
3. Pointofsale
4. Subaccounts
5. Treasury
6 SanchayPost DayEnd & Execute ( Sanchaypost Project Arrow Report : trans_time.exe available in C:\SP5\PA folder )

Then AccountMIS data Trasfer

Problem in accounts mis regarding signature scanning figures

please use "Transaction Time report" which should be installed from Sanchay Post 6.5 version and use for Sanchay Post Data generation which is generated only after Day end

use the trans_time.exe available in C:\SP5\PA folderIt will used to update SB Branch KPIs. ( The old one available in C:\SP5Comm\)

If not available install from Meghdoot 6.6 - AccountMIS folder

eMO communication Problem

eMO communication problem Download Patch Dated 16-10-2009

Download Speed Net Client

Problem and Solution Download
SpeedNet Communication Problem
1.
Open the hosts file (c:\windows\system32\drivers\etc) and check for entry Speednetmsg.ptcmysore.gov.in
if entry exists delete that and add entry 218.248.43.148 speednetmsg.ptcmysore.gov.in

2.download file ModifySpeednetURL from http://www.sendspace.com/file/6lflv6 . Please execute it on the machine where communication is installed after adding .exe extention to the file name.
Right click on file and click on run as administrator

New AccountMIS

Download New AccountMIS dated 09-10-2009

Negative List Updates Download 05-10-2009

Detail procedure for updating old eMO which are already paid but not updated

Disaster Recovery – Request for Data:
This option is used for getting the pending unpaid eMOs. Once request is processed the pending unpaid eMOs will be send to the client
Select transaction ->Disaster Recovery -> Request for Data (eMO supervisor.)
o Select office for which the request should be given.
o Enter the remarks click on OK.

Disaster Recovery – eMOs Paid entry:
This option should be used only for entering the payment details for eMOs which are paid already but not updated in the server.
Select Data Entry-> Disaster Recovery -> eMO Paid entry. (eMO Operator)
o Select Office name.
o Select PNR Numbers from the list.
o Enter Head Office Account Date.
o Enter eMO payment date and SO Account date.
o Click on OK.

o (Note: SO paid information will be transmitted to central server once the paid details are tallied with accounted figures by the supervisor.)
o View and delete option is also available for making any changes office wise.

Disaster Recovery – Paid Verification:
This option is used for verifying the disaster paid details and tallying with accounted figures.
Select transaction ->Disaster Recovery -> Paid Verification.
o Select Head Office Account Date and click on fetch.
o eMO figures and accounted figures will be displayed for all the offices.
o Select the office for which eMO figures and Account figures are tallied and click on verified button.
o If any discrepancy is noticed please enter the reason for the discrepancy in amount.
o Paid details will be verified on clicking on verify button.

Disaster Recovery – Redirection:
This option is used for redirecting eMOs received through Disaster Recovery option .
Select transaction ->Disaster Recovery -> eMO Redirection
o Select Office Name for which the Redirection should be done.
o The list of eMOs pending for that office will be displayed .
o Select the PNRnumber. Then select the reason.
o Enter the address to which it is redirected.
o Click on OK.

Disaster Recovery – eMOs not to be Paid:
This option is used to eliminate the eMOs which are already paid or redirected but received again for payment.
Select transaction ->Disaster Recovery -> eMOs not to be paid
o This option will give the list of eMOs which are neither paid nor redirected.
o If any of the eMOs is already received from other office, paid manually or redirected but not properly updated, you can update that eMOs as not to be paid with suitable remarks.
o Select PNRNumber.
o Enter Remarks.
o Click on OK
.o The eMOs which are entered as not be paid will not be available for invoicing in the Postman module or Redirection option in eMO.

CC Bridge Version 4.0

This version has the new option to
1. Import SO Discharge data from Sanchay Post database (Version 6.5)
2. Enter date of accounting while importing SO data for a single date

CC Bridge Version 4.0 Download

UPGRADATION TO MEGHDOOT VERSION 6.6 / PROJECT ARROW OFFICES

UPGRADATION TO MEGHDOOT VERSION 6.6 / PROJECT ARROW OFFICESWhile running Accounts MIS client, error message displayed as “Unable to continue due to the following error: There is a problem with SQL server. Login failed for user 'arrow'.”If Accounts MIS application was being used in Meghdoot Version 6.5 earlier and you have upgraded to Meghdoot Version 6.6, contact PTC Mysore for solution.If Accounts MIS application is installed afresh and the above mentioned error occurs, following are the possible actions:

a) If Sanchay Post Version 6.0 or earlier version is used, upgrade to Version 6.5 immediately.

b) If you are already using Sanchay Post Version 6.5, use DBAnalyzer to check whether you have upgraded to Version 6.5 successfully. While checking, if DBAnalyzer displays error code 1: Z, run 'ARROW.EXE' to create the Project database & login.

c) If you have shifted operations to a new server after upgradation to Sanchay Post Version 6.5, run 'ARROW.EXE' to create the Project database & login and then restore the Project database's backup, if available. Not restoring your backup of Project database or removal of the existing Project database and recreating it using 'ARROW.EXE' will result in loss of previous transaction data.INSTRUCTIONS FOR USING ARROW.EXE

1. Download ARROW.EXE

2. Unzip the downloaded file, copy it to the DBAnalyzer folder and run the exe file.

3. Use latest DBAnalyzer >> 'Check databases' >> Version 6.5 and verify if

Negative List upto 31-08-2009

Negative List Download (upto 31/08/2009)

eMO account Head Solution

Download eMO account head solution

Edit cash Book Progressive total

Edit cash Book Progressive total Download Script Tool

FTP Configuration ( S.O to H.O Data Transfer)

FTP SERVER CONFIGURATION
Ø Computer connect with existing server (through LAN cable)
Ø O.S. Windows 2000 Server with IE 6 & SP4 or Windows 2003
Ø Internal (or) external Dialup modem (both end HO and SO)
Ø Parallel phone connection from existing phone (both end HO and SO)

AT HO

:1. Install windows 2000 server and 2003 server and create active directory. Give server name and domain like XXXftpserver, XXXftpdomain. Give ip number (give running number in your HO domain and not to give your existing HO server IP number)

2. Install modem driver and check diagnostics.

3. Go to control panel add and remove programs windows components wizard IIS enable all services (ftp transfer protocol ftp service)

4.
a. Start -+ Program – Admin Tools – Internet Service Manager
b. Click Domain Name – It Shows Server Name
c. Right click the server name – select ‘new’ – select ‘ftp site’ – give name – give IP address (your computer).
d. Give TCP Port – 21 (always)
e. Give path – D:\SBFTP\Received (Create directory)
f. Give permission – read and write – click finish.(By default created ftp site will be stopped)
g. Right click newly created FTP site – property – check IP address and TCP port and give connections ‘unlimited’

5. a. Select admin tools – routers and remote access
b. Right click server name – configure routing and remote services – click manual selection.
c. Select server name – ports – right click – select property – click selected modem – configure – make tick in ‘inbound only and inbound and out bound’.
d. Give phone number of this server

6. a. Select admin tools – select active directory users and computers.
b. Create a new user (like XXXftp, YYYftp…) and give the password same in user name.
c. Right click created new user – select ‘dialin’ tab – make tick in ‘allow access’ – select ‘member of’ tab – make the user in domain user and give administrator rights to that user.
d. Create a network user as available in existing server and give Administratory rights (this domain) to that user.

7. Check the IIS and RRAS running correctly.
8. a. Install MSSQL 2000 client connectivity only (not to install full setup)
b. Click client connectivity – give the server name (existing old server name) alias
9. Install Bridge and Plugin. ( or Copy SB Plugis 2.5.3 Version )

AT SOS :
1. Install modem and create a dialup connection with username, password, and phone number created at HO level same as HO.
2. Install bridge and Plugin ( or Copy SB Plugis 2.5.3 Version ) and configure the FTP.

(Please delete old ‘PATCH’ database and create new thro ‘SB Plugin’ software)

Sanchay Post >> S.O to H.O Data Transfer

How to reset the sequence number to 1 at SO?
Use the option ‘DBAnalyzer >> DBUtilities >> SO - HO Data Transfer’ before doing day-end on the day data transfer is to be commenced. Select only the schemes for which data transfer is planned to be commenced.Files with sequence number 1 will be generated during day end for the initialised schemes. This option has to be executed only once at a SO for any scheme.This should not be done if transfer of data from SO to HO has already been performed for this SO through Sanchay Post.

2.How to reset the sequence number to 1 at HO for a SO?

Use the option ‘DBAnalyzer >> DBUtilities >> HO - SO Data Transfer’ before doing day end on the day data transfer is to be commenced. Use this option for the SO for which data transfer from HO is planned to be commenced.Files with sequence number 1 will be generated during day end for the initialised SO, if any data is available. This option has to be executed only once for a SO.

3.What are the preparatory steps for commencement of SO to HO data transfer?

The following points are to be ensured:a. POCode at HO & SO should be the same. If not, at SO use DBAnalyzer to change code.b. Include HO name in SOs (Using PO Name & Address Form) in a separate row.c. Designate the nodes for ‘Day end’. Files are generated in the node in which day end is performed.d. Check whether the fields ‘Name’ / ‘City’ / ‘Pincode’ are not blank for the schemes in which data transfer is to be commenced.e. Rectify the discrepancies listed in DBAnalyzer

.4.

Files for data transfer are not generated at SO in the designated system and folder and cannot be regenerated.Wait for ‘day-end completed successfully’ message. If this is not done files will not be generated and cannot be regenerated also. File creation for HO is the last task performed during day end and if the day end process is ended abruptly due to user intervention or otherwise, file creation for SO will not happen. If Files are not generated at SO for some schemes then check ‘Initialisation >> PO Name & Address’ form and ensure that the scheme is selected in ‘Set Scheme Computerisation Status’ option.

5.

Files generated at SO are without extension and hence cannot be imported at HOHO name and code to be initialized in SO. Include HO name in SOs (Using PO Name & Address Form) in a separate row.

6.

'Data does not belong to [soname]’ message displayed while importing data.Select the file again and retryLogout and login to SOSB module and retryAsk SO to re-generate the file & resend.If this problem persists, it could be due to OS mismatch (XP / Vista / Windows 2003). Re-generate file in a different system at SO or import the file in a different system at HO.

7.

RD bulk posting data not transferred.RD bulk data gets transferred only if Bulk posting is done before generation of the file (before day-end).

Meghdoot 6.6.1 Patch

Point of Sale Bulk eMO Problem Download

Meghdoot 6.6 Patch for Sub Account

Subaccount.exe dated 24-09-2009 Download
This solution will solve
a. Hos having BOs unable to make day end in subaccounts.
b. Screen appearance problem for SO Daily account / BO Daily account data entry at 800 X 600 resolution.
c. Invalid object name error at the time of ending a day prior to the date of upgradation

Certificate for Account MIS Download

SPEEDNET SERVER CHANGE

INFORMATION

Download SpeednetURL

The Speednet server is being shifted from NIC,
Delhi to the servers at PTC, Mysore.For the speedpost traffic to move to PTC, Mysore , a small exe is required to be*executed at all places where speednet communication is installed. The exe is a part of the folder attached*alongwith the mail. The steps are given below: Login to machine where speednet communication is installed as administratorCopy file ChangeSpeedNetURL to any folder on this machine add ".exe" extension to file right click on this exe and click on* run as administrator The Speednet communication*is a part of Speednet and Meghdoot Point of Sale. This shifting will take place on 29
September 2009. From 29th morning onwards, speednet communication will need to connect to new servers at PTC, Mysore. Hence please ensure that new exe is installed on 29 September 2009 F/N.

Treasury 6.6 Patch dated 17-09-2009

Trasury 6.6 Patch Download dated 17-09-2009

Megdoot 6.6 Released on 14-09-2009

Meghdoot 6.6 Upgradation requires the following activities in the same sequence

Up gradation should be started only after completing the submission of all accounts and generation of all relevant reports and the completion of day end in all packages.

* Updating the Client installation files
*Upgrading the databases

Please go through the Check-List and act as per the check List.

One important thing to be noted is that all modules should be of version 6.6, otherwise Meghdoot applications will be out of synchronization and operations will not be executed as expected.

A. Updating the Client installation files
1. To upgrade to Version 6.6, for all packages, installation of new Server Component is not required.

2. Uninstall the client components using Add Remove Programs option from the client machines and delete the installation folder.

3. Before uninstalling ePayment client, emo Client, take the Backup of RXD,TXD folders along with config.XML file. And the above folders should be restored after the new installation. For Accounts MIS Client take the backup of data folder and “AccountsMISclient.exe.config” file (This is compulsory. Kindly adhere to this step without fail).

4. Search for pointo**.cab and subac**.cab and treasu**.cab files in the System32 folder and delete them before installing the new client component of Point of Sale, Subaccounts, treasury respectively in the client systems.

5. Install the client component on required client computers (Please follow the instruction noted above at Point number 4 without fail).

Note

If SubAccounts package is installed/ upgraded before installation/Up gradation of Point of Sale, Point of sale up gradation will not be possible. It will give an error “Script File Corrupted”.

B. Upgrading the DatabaseDatabase can be upgraded using the Script tool Software. The up gradation script should be selected from the Database upgrades folder available in the installation CD. Before upgrading the databases, please take a full backup of all the databases. (This is mandatory).

POINT OF SALE:

1 Upgrade the Counter and IPO databases using scripttool Software. The scripts to be selected from Database upgrades folder are: Counter.exl and IPO.exl,ecounter.exl,emo.exl. The actual sequence is available in the CheckList.

2 Install Speed net communication for Point of Sale, if both Speed Net and Point of Sale are not connected through Network.After Up gradation of PointOfSale Epayment option can be enabled using the option Enable additional services. If Epayment is selected ECounter database will be created and EVP and EPayment transactions will be enabled. In the case of fresh installation if Epayment option is selected then ECounter database will be created and Epayment and EVPTransactions will be enabled.To enable the eMoney Order option in Point of Sale, the eMO module should be installed and the office should be registered with Central Server for eMoney Order operations.**********************************************

TREASURY
Upgrade the Treasury database using scripttool Software. Select Treasury.exl file available in the folder Database upgrades in the Meghdoot 6.6 installation CD.POST MANUpgrade the

POSTMAN

database using scripttool. Select postman.exl available in the folder database upgrades in the Meghdoot 6.6 installation CD.

ACCOUNTS

Upgrading Accounts, Income Tax,cashbook and NPC database1 Copy the entire contents of Accountsfix folder databaseupgrades\accounts fix folder in the CD to your hard disk.

2 Right click on the copied folder and click on Properties option. Uncheck the Read Only property of the folder.

3 Open the folder and double click on AccountsFix.exe this will upgrade the Accounts and Income Tax databases. If Income Tax database does not exist, it will create it.If you want to delete NPC and Cash Book databases and want to start those modules afresh do the following:-After up gradation of Accounts package to version 6.6, if NPC to be started afresh without going for up gradation of NPC Database:Delete the NPC database through SQL Enterprise ManagerSelect NPC Module from the list and start it.When the NPC database is not available, it will ask the drive letter to create the new NPC database. Now you may specify the drive letter to create the NPC database afresh and work with fresh data entry.After up gradation of Accounts package to version 6.6, if Cash Book to be started afresh without going for up gradation of Cash Book database:Delete the Cashbook database through SQL Enterprise ManagerLogin to General Module and select Print Cash Book option under Cash Book menu.When the Cash Book database is not available, it will ask the drive letter to create the new Cash Book database. Now you may specify the drive letter to create the database afresh and work with fresh data entry.

ACCOUNTS PBS:

Accounts must be installed and configured properly before the Up gradation of Accounts PBS package.Upgrading Schedule DatabaseUpgrade the Schedule database using scripttool application. Select the file schedule.exl available in the folder database upgrades available in the installation CD.ePayment ClientUpgrade the Ecounter database using Database workshop sites. Select the file ecounter.eql available in the folder database upgrades available in the installation CD.If Meghdoot databases are directly updated from versions other than 6.4, Please execute PTCLogins6.4.exe. to update the logins. Otherwise Meghdoot applications will not work properly.*********

Instructions To Administrators

1. Take a Print-out of the Check-List and carry-out the checks and mark them completed as and when one step is completed so that there will not be any miss-outs

2. Install all the relevant Pre requisites before installing any Package

3. Install or Upgrade all the packages together.

4. Ensure that all packages are upgraded to version 6.6 before starting work.

5. Upgrade/Install them strictly following the sequence mentioned in ‘up-gradation procedure’ file.

6. Before uninstalling ePayment Client Setup, Copy the Txd, Rxd, ErrorLog, Log Folders and Config.xml files to a safe location. These folders and files must be restored back to their original location immediately after Re installing ePayment Client Setup. Failing to do so will result in office registration failure.

7. Speednet 3.1.1 must be installed if you want to integrate Speednet package with Meghdoot 6.6

8. In Case, if Database is on SQLServer 2005 and your client machine is Windows 2000 Professional or Windows XP, If SQLServer 2005 Native Client is not installed then SQL2K5 Backward Compatibility Tool should be installed on the clients for connecting to the SQL Server 2005. It is available under Prerequisites folder. Either SQL Server 2005 Native Client or SQL Server 2005 backward compatibility should be available in the client machine for connecting to the SQL Server 2005.

9. For Client machines operating on Vista Operating System, right-click on the application and in the compatibility tab check “Run this program as administrator” in the privilege level option. Otherwise applications will not work correctly.

6th CPC IInd Installament Arrear software for Pensioners Download dated 09-09-09
6th CPC IInd Installment Arrear software Download dated 29-08-2009
Schedule.exe (6.6) Download Dated 26-08-2009
History Sheet Performa Download
AccountMIS : Download dated 18-08-2009

Installation Procedure for Passbook Printers

PassBook - Printer Settings1. Press station 1 + local +station2 & ON the printer (30sec)& insert the paper.

2. it shows station1=continue,station2=skip,local=config

3. Press local, it shows Menu : config

4.. Press station1 to continue until the printer name display as OLEVETTI

5. Press station2, the display changes to IBM

6. continue press station1 button until it displays save changes to Y

7. switch off the printer and swith on

Add New PASSBOOK PRINTER(It is for COM1 / Serial Port)

Start -> Setting -> printer -> Add Priner -> next -> Local Printer -> Next -> Select COM1 - Serial port -> Manufacturer ( IBM) -> Printers ( IBM Pro Printer 1 or 2) Give Name as ( PASSBOOK PRINTER) -> Next -> Next -> Finsih*

for Vista OS : Select Gereric -> 9 Pin Compatible WidePapper

Settings:Printer and Fax (Inside the Window) Right Click in the Blank space -> Server Properties -> Tick on the Create New Form -> Form Name ( give name as "PASSBOOK" ) -> Measurement ( in Inch)

Width: 8.20

Left : 0.20

Top : 0.70

Hight : 5.80

Right: 0.00

Bottom : 0.20

SaveRight Click Installed PASSBOOK PRINTER-> Properties -> 1. Device Setting -> Select PASSBOOK and Apply

2. Device Setting -> Printing Preferences -> Advanced -> Select Paper size PASSBOOK

3. Right Click -> properties -> Ports -> COM1 -> configure port -> Flow Control -> Xon / Xoff -> Apply -> OKSet as " PASSBOOK PRINTER " as DefaultTry to Print SB Passbook Best