-
Posts
38,265 -
Joined
-
Days Won
168
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Pete Dowson
-
-
>> What means error 10050? Does anybody know what to do? <<
According to the Winsock documentation, 10050 means "Network is down". This is why I include that text in the error message. All WideClient is doing is attempting to start the service, yet when it tries, Windows replies with that error. In case it is useful, here is some expanded text from MS sources:
----------------------------------------------
WSAENETDOWN
(10050)
Network is down.
A socket operation encountered a dead network. This could indicate a serious failure of the network system (that is, the protocol stack that the Windows Sockets DLL runs over), the network interface, or the local network itself.
----------------------------------------------
I must admit I don't like WinME and regard it as the biggest mistake Microsoft ever made. I tolerated it for a full two days when it came on a new Notebook of mine a while back -- then I reformatted the HD and went back to Win98SE.
Howwever, that said, there must be some way of resolving your problem. Maybe the ServerNode you are specifying is wrong? Maybe you are not specifying a ServerNode and Windows ME wants one?
A friend of mine who had Win98SE on one PC and WinME on his notebook NEVER ever managed to get the ME machine to see the other -- he eventualy upgraded to XP instead.
You could also try changing everything over to TCP/IP instead. If you ever intend to move on to XP in the future that would probably be needed in any case. Version 5.41 performas quite well on TCP/IP, much more smoothly than it used to. That's where I've been doing most of the recent work on it.
Regards,
Pete
-
Hi again Ulisses,
After more testing, it looks like PM's MCP is interpreting the bits differently to the way they are documented. This is the results I got:
ND Map Arc (bit 1) --> does nothing
ND Map Ctr (bit 2) --> Sets ROSE mode
ND ROSE (bit 3) --> Sets Map Arc mode
ND PLAN (bit 4) --> Sets PLAN mode (yippee!).
I'm afraid it is definitely over to Enrico for a solution now, sorry...
Regards,
Pete
-
Hi Ulisses,
>> I'm trying to assign a button in FSUIPC to PM ND Map Ctr Mode but it isn't working, the FSUIPC doc shows it as:
2098 PM ND Map Ctr Mode
My fsuipc.ini shows the correct value: 2098, but it isn't working, it's showing ND Rose instead. <<
This is really more of a question for PM support. All FSUIPC does with that control is toggle bit 4 in offset 541C. The PM MCP program should recognise the change and then tell the ND to set MAP CTR mode. This is precisely as documented in Enrico's "Project Magenta FSUIPC Offsets", which is my only reference for this stuff.
I've just checked the same here and, with the latest PM builds, it looks like none of those bits at offset 541C are recognised any more. I can see them changing (e.g. using FSInterrogate), but they are ignored.
If Enrico has withdrawn these, he hasn't mentioned it to me and it will involve quite a lot of reprogramming, both in FSUIPC and PFC.DLL. I'm copying this message to him and asking for urgent clarification.
Regards,
Pete
WideClient refuses to start
in FSUIPC Support Pete Dowson Modules
Posted
>>just a small clarification: IPX/SPX works beautifully on XP, but you have to have WinXP Professional - it's not supported on XP Home <<
Well I had it working on XP Home, but not very well. It is supported, but badly. I think it is all right if you can get by using IPX/SPX only, no TCP/IP or NetBeui or anything.
With any mixed network (Win98SE, Win2K, WinXP) then a 100% only TCP/IP Network seems to be the only way to get everything working really smoothly. Since I made that decision and change I've not looked back!
Regards,
Pete