Background: I have been running ProNews/2 under eCS 1.2R, running in
a Parallels Desktop 3.0 virtual machine under Mac OS X 10.5.8. No
problems. Last weekend I upgraded to Mac OS X 10.6. Parallels
Desktop 3.0 won't run under 10.6, so I had to upgrade that to
version 4.0. Under this new configuration everything OS/2 that I
have used so far works properly, except this business of the message
IDs.
I have searched the ProNews/2 settings and can't find anything that
would seem to affect the message headers.
I reinstalled ProNews/2 but that didn't help.
I have discovered that I can go into the POSTQ folder, open the
message in the Text Editor, and delete the Message ID line from the
headers. Save the message file, go back to ProNews/2, click Execute
Now, and the message is posted. In fact, that is what I will have
to do in order to post this message. (If I don't have to do that, I
will immediately post a follow-up!)
So clearly the problem originates in ProNews/2 and its assignment of
message ID.
Any suggestions for how to make ProNews either stop inserting
Message IDs or else properly update the IDs?
--
John Varela
Trade NEWlamps for OLDlamps for email
Yes. Get your clock to work properly. We looked at this before and your OS/2
clock is stuck and is not updating.
--
Trevor Hemsley, Brighton, UK
Trevor dot Hemsley at ntlworld dot com
You have a better memory than I do. I recalled having a problem
with posting and that you solved it for me, but I couldn't recall
the problem or the solution. This time I'll make a note.
What's needed is for Parallels to synch the clock, which requires
jumping through some hoops and when it's all done Parallels reports
that it doesn't support these functions for OS/2. Parallels 3.0
did, but 4.0 doesn't. On this basis I question their claim that
they support OS/2, because I consider clock to be a pretty
fundamental function.
After fiddling with eCS settings I have the system somehow fetching
the time when it boots, but then the clock doesn't update. Thus it
appears that I can post one news group article for free with every
boot, but if I want to post more than that I'll have to edit the
headers in POSTQ.
I don't suppose there's any easy way to prevent ProNews/2 from
inserting the Message-ID line in the headers.
Well, we'll see how it goes. Even having to edit the headers,
ProNews/2 is still better than any native Mac news reader that I've
looked at.
Thank you for your help.
Have you tried it with Parallels 4 for the MAC? As I recall, the
older Parallels machines did have a clock problem.
--
Chuck McKinnis
> > Yes. Get your clock to work properly. We looked at this before and
> > your OS/2 clock is stuck and is not updating.
>
> What's needed is for Parallels to synch the clock, which requires
> jumping through some hoops and when it's all done Parallels reports
> that it doesn't support these functions for OS/2. Parallels 3.0
> did, but 4.0 doesn't. On this basis I question their claim that
> they support OS/2, because I consider clock to be a pretty
> fundamental function.
>
> After fiddling with eCS settings I have the system somehow fetching
> the time when it boots, but then the clock doesn't update.
What version of eCS? If you have 2.0 RC 6a (I think) or later, there's
a network-based clock sync utility included; check the System Setup
folder. If you have an earlier version, you can get it from the
BetaZone as long as you have Software Subscription Services (look for
the "Clock Tools" category).
If you have neither of those, try grabbing daytime or time868 from
Hobbes. (I prefer the former because it runs detached and supports
more protocols, but it requires more manual setup.)
--
Alex Taylor
Fukushima, Japan
http://www.socis.ca/~ataylo00
Please take off hat when replying.
I had no problem with Parallels 3.0, once I realized there were
hoops through which to jump. The problem is with 4.0, which does
not support clock synch (or much of anything else) with OS/2. See
"Background" paragraph above.
Recall that I'm running this system in a virtual machine. I can
connect to mail and web servers from the virtual machine but not
time servers. I don't know why. I can ping time.nist.gov but
Time868 can't connect. I'll play with settings and see if I can get
it working.
In any case, the problem is not with synch but with updating of
time. It appears that OS/2 can't access a system clock.
What about if you run a time server on the host?
>
> In any case, the problem is not with synch but with updating of
> time. It appears that OS/2 can't access a system clock.
>
Or just set the time every time you post a message, might be easier then
editing the message
Dave
> > What version of eCS? If you have 2.0 RC 6a (I think) or later,
> > there's a network-based clock sync utility included; check the System
> > Setup folder. If you have an earlier version, you can get it from the
> > BetaZone as long as you have Software Subscription Services (look for
> > the "Clock Tools" category).
> >
> > If you have neither of those, try grabbing daytime or time868 from
> > Hobbes. (I prefer the former because it runs detached and supports
> > more protocols, but it requires more manual setup.)
>
> Recall that I'm running this system in a virtual machine. I can
> connect to mail and web servers from the virtual machine but not
> time servers. I don't know why. I can ping time.nist.gov but
> Time868 can't connect. I'll play with settings and see if I can get
> it working.
Time868 is pretty old; there are three or four different commonly-used
time protocols, and it only supports TIME (RFC868, which is generally
considered deprecated). You might have better luck trying one of the
other protocols (like SNTP or DAYTIME) using a different client...
> In any case, the problem is not with synch but with updating of
> time. It appears that OS/2 can't access a system clock.
Syncing the clock will at least update the time periodically, which is
better than now...
> > In any case, the problem is not with synch but with updating of
> > time. It appears that OS/2 can't access a system clock.
>
> Syncing the clock will at least update the time periodically, which is
> better than now...
Or trying a non-broken virtualization product?
> On Sun, 6 Sep 2009 13:12:01 UTC in comp.os.os2.apps, "Alex Taylor"
> <mai...@reply.to.address> wrote:
>
> > > In any case, the problem is not with synch but with updating of
> > > time. It appears that OS/2 can't access a system clock.
> >
> > Syncing the clock will at least update the time periodically, which is
> > better than now...
>
> Or trying a non-broken virtualization product?
The only other one I know of, VMware Fusion, doesn't even claim to
support OS/2.
> On Sun, 6 Sep 2009 17:22:08 UTC, "Trevor Hemsley"
> <Trevor....@mytrousers.ntlworld.com> wrote:
>
> > On Sun, 6 Sep 2009 13:12:01 UTC in comp.os.os2.apps, "Alex Taylor"
> > <mai...@reply.to.address> wrote:
> >
> > > > In any case, the problem is not with synch but with updating of
> > > > time. It appears that OS/2 can't access a system clock.
> > >
> > > Syncing the clock will at least update the time periodically, which is
> > > better than now...
> >
> > Or trying a non-broken virtualization product?
>
> The only other one I know of, VMware Fusion, doesn't even claim to
> support OS/2.
>
You could try VirtualBox - it does run OS/2 very well and is available
fot the Mac
--
ivan
I did look at that some time ago before I went to Parallels. The
web site http://www.virtualbox.org/ doesn't claim to support OS/2.
Do you know of actual OS/2 installations under VB?
In any case, it can't hurt for me to take a look. Thanks for the
suggestion.
> Do you know of actual OS/2 installations under VB?
Mine. On a Linux host though.
> On Mon, 7 Sep 2009 09:10:42 UTC, "ivan" <iva...@free.fr> wrote:
>
> > On Mon, 7 Sep 2009 00:43:15 UTC, "John Varela" <OLDl...@verizon.net>
> > wrote:
> >
> > > On Sun, 6 Sep 2009 17:22:08 UTC, "Trevor Hemsley"
> > > <Trevor....@mytrousers.ntlworld.com> wrote:
> > >
> > > > On Sun, 6 Sep 2009 13:12:01 UTC in comp.os.os2.apps, "Alex Taylor"
> > > > <mai...@reply.to.address> wrote:
> > > >
> > > > > > In any case, the problem is not with synch but with updating of
> > > > > > time. It appears that OS/2 can't access a system clock.
> > > > >
> > > > > Syncing the clock will at least update the time periodically, which is
> > > > > better than now...
> > > >
> > > > Or trying a non-broken virtualization product?
> > >
> > > The only other one I know of, VMware Fusion, doesn't even claim to
> > > support OS/2.
> > >
> >
> > You could try VirtualBox - it does run OS/2 very well and is available
> > fot the Mac
>
> I did look at that some time ago before I went to Parallels. The
> web site http://www.virtualbox.org/ doesn't claim to support OS/2.
>
> Do you know of actual OS/2 installations under VB?
>
> In any case, it can't hurt for me to take a look. Thanks for the
> suggestion.
>
I have OS/2 running as guest on win XP, SUSE linux and OS/2. The
latter is for test purposes.
--
ivan
Downloaded VirtualBox from the Sun site and installed.
Set up an eCS virtual machine, then put the eCS install CD in the
drive and ran the VM.
It starts to run from the CD, then freezes after producing this
screen:
MemDisk 2005.08.23
Startup drive is CD-ROM in 'No Emulation' mode (E0).
Detecting extended memory size... using INT 15 EAX=E820 'SMAP'
12 MB starting a 1 MB
[red] Not enough memory
What do you make of that? I've rechecked the VM configuration and
can't find anything that looks wrong.
Sorry John, I can't help you there. All my instances of OS/2 in
VirtualBox are OS/2 4.52 not eCS.
I do have the feeling you need much more memory than 12 MB. Try
giving your VM about 250 MB and see what happens.
--
ivan
You're correct; the manual says it needs a minimum of 48 MB but 64
is better.
I'll go try again.
--
John "RTFM RTFM RTFM..." Varela
And so, on to the next problem. The virtual machine booted from the
eCS installation CD, read the first two disks (those would be
floppies) from it, then crashed with a trap D in module RESOURCE.
Several times. I suspect a bad CD -- I had some trouble getting
through the installation on Parallels. I'm sure that at one time I
had backup copies of the install CDs but if so I can't find them.
I tried various things, including downloading a brand new update of
VB, trashing the original VM, and starting over from scratch. Now
when we start to read the installation CD we don't get that far: VB
halts with this error pane:
Failed to start the virtual machine eCS
PIIX3 cannot attach drive to the Secondary Master
(VERR_SHARING_VIOLATION)
Unknown error creating VM (VERR_SHARING_VIOLATION)
The secondary master would be the CD/DVD drive. Settings for that
drive are the same as they were for the earlier version of VB.
I assume that the new update to VB broke something. Given that the
installation CD doesn't want to work, I'm abandoning this approach
for now. I'll check from time to time to see if there's another
update to VB and then maybe I'll try again.
Thank you to those who tried to help...
--
John Varela
ProNews uses a unique message id that allow to detect answers to your
posts because the answer contains a "References:" header referring to
your special pn2 message id.
Jens Martin Schlatter