vacuum in standalone mode

This is a windows installation postgresql 8.5.1

trying to start postgresql provides the following:

2006-12-03 08:58:11 LOG: database system was shut down at 2006-12-02
11:01:55 Mountain Standard Time
2006-12-03 08:58:11 LOG: checkpoint record is at 13/173572B0
2006-12-03 08:58:11 LOG: redo record is at 13/173572B0; undo record is
at 0/0; shutdown TRUE
2006-12-03 08:58:11 LOG: next transaction ID: 2146484148; next OID:
59499
2006-12-03 08:58:11 LOG: next MultiXactId: 11951; next
MultiXactOffset: 26281
2006-12-03 08:58:11 LOG: database system is ready
2006-12-03 08:58:11 LOG: transaction ID wrap limit is 2147484148,
limited by database "postgres"
2006-12-03 08:58:11 WARNING: database "postgres" must be vacuumed
within 1000000 transactions
2006-12-03 08:58:11 HINT: To avoid a database shutdown, execute a
full-database VACUUM in "postgres".
2006-12-03 08:58:11 ERROR: database is not accepting commands to avoid
wraparound data loss in database "postgres"
2006-12-03 08:58:11 HINT: Stop the postmaster and use a standalone
backend to vacuum database "postgres".
2006-12-03 08:59:11 ERROR: database is not accepting commands to avoid
wraparound data loss in database "postgres"
2006-12-03 08:59:11 HINT: Stop the postmaster and use a standalone
backend to vacuum database "postgres".
2006-12-03 08:59:23 FATAL: database is not accepting commands to avoid
wraparound data loss in database "postgres"
2006-12-03 08:59:23 HINT: Stop the postmaster and use a standalone
backend to vacuum database "postgres".
2006-12-03 08:59:55 LOG: received fast shutdown request
2006-12-03 08:59:55 LOG: shutting down
2006-12-03 08:59:55 LOG: database system is shut down
2006-12-03 08:59:56 LOG: logger shutting down

The database will start up in startAlone mode via the postgres command

But at this point I can not connect via psql to issue a vacuum.

How do I issue a vacuum while in standalone mode?

Thank,
Roger