From: Digest To: "OS/2GenAu Digest" Date: Fri, 4 Jul 2003 00:02:01 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600 Subject: [os2genau_digest] No. 655 Reply-To: X-List-Unsubscribe: www.os2site.com/list/ ************************************************** Thursday 03 July 2003 Number 655 ************************************************** Subjects for today 1 OS/2 SIG Report for June 2003 : John Angelico" 2 Unable to register : Peter L Allen" 3 Re: Unable to register : Mike O'Connor" 4 Re: Unable to register : Paul Smedley" **= Email 1 ==========================** Date: Thu, 03 Jul 2003 08:51:58 +1000 (AEST) From: "John Angelico" Subject: OS/2 SIG Report for June 2003 Hello, everyone. Copy of Melbourne OS/2 SIG report from our June meeting. Best regards John Angelico OS/2 SIG talldad at melbpc dot org dot au or talldad at kepl dot com dot au _________________________________________ Melbourne PC SIG Meeting Report To: G Taig Features Editor PC Update Report Date: 27 June 2003 Meeting Date: 24 June 2003 Report by: John Angelico (03) 9544 8792 Winter has set in and our June meeting attendance was down to the faithful few. However, we welcomed Paul Smedley from the SA OS/2 group who was in Melbourne with his work. We all enjoyed the opportunity to meet someone who was up till then only a signature on an email! Following a pause for setup, we introduced our guest presenter Ian Manners from the iPrimus Support Centre and ComKal Consulting, who took us through the concept of a Journaling File System, plus some of the history of the eCS JFS, and then demonstrated the latest beta but one of bootable JFS partition code. In response to questions, Ian explained the design of the JFS, how it differed from other data integrity schemes such as transaction logging in a database system, and some of the performance statistics comparing HPFS to JFS. There are clear advantages in file reading/file serving situations as well as in recovery of file integrity after a power loss. However, there is no substitute for a UPS with orderly shutdown for actual data protection, since any loss of power loses cached data. Tech-Talk in the second half of the meeting would have covered problems members were having with eCS installations, but was deferred given the small numbers. Next meetings: July 22nd Aug 26th ---------------------------------------------------------------------------------- **= Email 2 ==========================** Date: Thu, 03 Jul 2003 10:53:29 +1000 (EST) From: "Peter L Allen" Subject: Unable to register One box pauses a few seconds before announcing the NIC driver and bleats "Unable to register" then carries on with boot - peer networking with netbios appears OK. FP 12 inetver 4.02y Other box with same NIC (IBM/Intel PCI 10/100) boots normally. What's "Unable to register" trying to tell me? Regards, allenpl ---------------------------------------------------------------------------------- **= Email 3 ==========================** Date: Thu, 03 Jul 2003 14:25:06 +1000 From: "Mike O'Connor" Subject: Re: Unable to register Peter L Allen wrote: >One box pauses a few seconds before announcing the NIC driver and bleats >"Unable to register" >then carries on with boot - peer networking with netbios appears OK. >FP 12 inetver 4.02y >Other box with same NIC (IBM/Intel PCI 10/100) boots normally. >What's "Unable to register" trying to tell me? > > Hi Peteri, Maybe IRQ conflict with something else on the motherboard or in a slot [ISA/PCI]. Check your IRQ settings in the BIOS. HTH -- Regards, Mike Failed the exam for -------------------- MCSE - Minesweeper Consultant and Solitaire Expert -------------------- ---------------------------------------------------------------------------------- **= Email 4 ==========================** Date: Thu, 03 Jul 2003 19:43:53 +0950 (CST) From: "Paul Smedley" Subject: Re: Unable to register Heya Mike & Peter, On Thu, 03 Jul 2003 14:25:06 +1000, Mike O'Connor wrote: >>What's "Unable to register" trying to tell me? > >Maybe IRQ conflict with something else on the motherboard or in a slot >[ISA/PCI]. Check your IRQ settings in the BIOS. The message rang a bell but couldn't quite remember of first read - but I think Mike is right. I got a similar message with the Via 686 audio drivers - it basically means that the driver is unable to register the IRQ with Resource Manager - nothing major to worry about AFAIK. Cheers, Paul. ----------------------------------------------------------------------------------