Unoffical empeg BBS

Quick Links: Empeg FAQ | RioCar.Org | Hijack | BigDisk Builder | jEmplode | emphatic
Repairs: Repairs

Topic Options
#51264 - 24/12/2001 14:39 First Sync with 2.0b7 - Error 0x80072736
charcoalgray99
enthusiast

Registered: 14/05/2001
Posts: 279
Tried my first sync with 2.0b7, and got this error message:

An operation was attempted on something that is not a socket. 0x80072736 (See attached screenshot).

Sync'ed with WinXP Pro, over ethernet. The player's display locked up on the sync'ing screen, the arrows did not move and the player was unresponsive to buttons. Emplode also locked up and was not responding.

Seems like my changes were uploaded. Cosmetic only? (besides locking everything up)

Every sync since has been no problem, this was a one time thing.

Tom


Attachments
50027-80072736.gif (192 downloads)


Top
#51265 - 24/12/2001 16:38 Re: First Sync with 2.0b7 - Error 0x80072736 [Re: charcoalgray99]
rob
carpal tunnel

Registered: 21/05/1999
Posts: 5335
Loc: Cambridge UK
There do seem to be problems with restarting the player during the sync - I experienced this with internal builds recently as well.

Rob

Top
#51266 - 05/01/2002 09:25 Re: First Sync with 2.0b7 - Error 0x80072736 [Re: rob]
jloew
journeyman

Registered: 26/12/2001
Posts: 87
Loc: SF Bay Area
Yep, had the same problem - this error on restart and on any attempt to connect until disconnect and restart both player and application.
_________________________
MkIIa [blue]BLUE[/blue]

Top
#51267 - 08/01/2002 04:53 Re: First Sync with 2.0b7 - Error 0x80072736 [Re: jloew]
meast
stranger

Registered: 30/12/2001
Posts: 48
Same here...
_________________________
MEast 40GB MK2a in '04 BMW 330CiC with BSW 300w Amp & 10" Custom Sub

Top
#51268 - 09/01/2002 02:25 Re: First Sync with 2.0b7 - Error 0x80072736 [Re: meast]
keil
new poster

Registered: 28/12/2001
Posts: 23
Loc: Los Angeles,CA

Top
#51269 - 09/01/2002 02:42 Re: First Sync with 2.0b7 - Error 0x80072736 [Re: keil]
keil
new poster

Registered: 28/12/2001
Posts: 23
Loc: Los Angeles,CA
Well waddya now...I was writing away about this sync lockup and the mk2 has cleared the error itself. I can't be any more specific than that, I looked over at the RIO and the locked "synchronizing" display had disappeared. I was writing on the BBS on a second monitor (win2000 multi system) and emplode unfroze as well. This event from start/finish took about 25 min. Sooo...maybe interface (10bT) stack timeout in IF module or ICMP issue, idunno? Wish I'd netstat'ed the RIO during the lockup.

Keil


Top