Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!cs.utexas.edu!uunet!mcvax!ukc!axion!tigger!mjr From: mjr@tigger.planet.bt.co.uk (Martyn Reason) Newsgroups: comp.windows.ms Subject: Re: Windows 2.03 & Network Timing Message-ID: <218@tigger.planet.bt.co.uk> Date: 2 May 89 08:54:29 GMT References: <4005@sybase.sybase.com> Organization: RT5111, BTRL, Martlesham Heath, England Lines: 40 From article <4005@sybase.sybase.com>, by marc@mercury.sybase.com: > I hope this hasn't been previously discussed but: > > We're attempting to implement a Windows .DLL library for use > with Excelan's EXOS TCP/IP networking routines. These has been a lot > of speculation around here that in fact (with out modification) > Excelan can't be implemented under Windows. Our reasoning ? Well... > Windows grabs and controls all the timers right ? The network wants > to grab a timer for its own timing requirements and hence you have a > resource conflict. Are these assumption fact or fiction. Has anyone > else done work with Window running in a network environment > (other than > MS-NET or DOS Lan Man ??). > > Thanx, > _Marc > Some time ago I attempted to write a Windows 2.03 application which contacted a server process running on a VAX host using Sun's PC-NFS. I ran into the same timing problems with Windows taking the timers calls. A call to the NFS callrpc () function caused to machine to hang. Having contatcted the Sun support people here in England, they told me that there was nothing that could be done - it is up to the guys at Microsoft to fix the problem. +----------------------------------------+ | Martyn Reason | | | | British Telecom Research Labs. | | RT5111 | | Martlesham Heath, IPSWICH | | Suffolk, IP5 7RE. | | ENGLAND | | | | National: Ipswich (0473) 646779 | | International: +44 473 646779 | | email: mjr@planet.bt.co.uk | +----------------------------------------+