I'm cross-posting this for a member of the rbsolutions list.
Thanks..
Brian
Can you tell me where I can find RedBack training?
I am a Universe Basic programmer and very well versed with it for the past
20 years.
I am in the New York area and have an open availability.
Thanks,
John
-
I got the following message-
Computed blink of 0xFF6800 does not match expected blink of 0xAAA5800
Detected within group starting at address 0x14E7800
The module of the file is 8581 so the group starting address must be in
an overflow record. I'm trying to use "uvfixfile" to trace the blocks to
The number given by the blink error will always be in "primary" space
(unless something major is broken); it always is a number that identifies
the beginning of a group. The only thing you need to know is the
separation size of the file and the file header size (in separation units).
If it's
> __
> From: MACK ANDREW, F/S
> Sent: Thursday, 31 March 2005 09:52
> To: HENDERSON MIKE, MR
> Subject: [UV] Win 2K3 Printer setup {unclassified}
>
> Mike please post the following onto the U2 user group. Cheers,
>
> Hi everyone,
>
> We a
Thanks for the reply.
That's the way I computed it. But when I entered "step 10702", I got an
error that that was past the modulo of 8581. You have to track from the
first block of a hash bucket and that is what I'm trying to find...
-- Rod Hills
-Original Message-
From: [EMAIL PROTECTED
At 10:01 AM 29/03/2005 -0500, you wrote:
Is there an easy way to configure the UniVerse spooler such that as each
print job finishes, a page eject is issued.
Greetings,
I understand what your problem is but you don't list the OS you are running
on.
We had the same sort of problem and got around i
do they support PJC, or it's own form.
I know for instance, our Canon Imagerunner uses the
Comment command in HP PJC to allow use of it's own
PJC commands (which will be ignored by non canons).
They work well for page setup, and best of all they
are in ENGLISH, not escape codes.
George
>---
Rod,
Another way to possibly determine the group number where the problem
occurs is to LIST the file using the NO.PAGE option. When LIST hits the bad
blink it will likely melt down with the same message you've been getting.
Take the last record key displayed prior to the error message and
Thanks for the response we did get the spooler fix from MS. Atleat we
hope so :)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of George Gallen
Sent: Wednesday, March 30, 2005 2:34 PM
To: u2-users@listserver.u2ug.org
Subject: RE: [U2] [UV] Win 2K3 Printer
