Isn't the latest version 0.49.1?
Is this a buffer problem w/ the PC or the XBOX??
ON AVALAUNCH...v0.49.1
under SETTINGS=>MAIN OPTIONS=>HARDWARE INFO
It reads: Xbox Memory 64mb
Virtual Memory 2047mb
free memory 36mb
I was wondering if the free memory was too low not allowing Qwix to allocate enough for this buffer space it "errors" about .......or if that's way off and something to do w/ the PC??
I'm really just stretching for ideas because this problem is starting to annoy me.
Any help on this socket error 10055 would be great!!
Scratch my last post.....its definetly the PC
used my friends lab top and worked fine.
hi everybody,
i had the same trouble with Qwix and XP-SP2.
Ever i tried to use the "browse" button in Qwix, i got the message SOCKET ERROR # 10055.
If anyone is interested in my solution for this:
I solved the problem by changing the network settings.
I changed the speed/duplex Mode from "Auto" to "100MBit/s Fullduplex"-Mode.
Now it works fine!
so long...
Skyw@lker
QUOTE(skyw@lker @ Jan 12 2007, 04:16 PM)

You have to change the properties of your network adapter.
Right click your network connection and click properties and then configure.
In the advanced settings you normally can change the duplex-mode.
...sky
Socket Error # 10055
No Buffer Space Avaliable
When trying to Load ISO onto Xbox or Manage XBOX titles.
Win2000 Adv Server (with ALL UPDATES)
1024Mb Memory
And Virgin Quix Used too, (No old ini File)
GENERAL ERROR INFO
Application...
Start Date : 11/19/2003 15:33:46
Name/Description: Qwix
Version Number : 1.0.1.0
Exception...
Date : 11/19/2003 15:34:50
Address: 0050EF8F
Module : Qwix.exe
Type : EIdSocketError
Message: Socket Error # 10055 No buffer space available.
[Unnecessary info removed.]
I've used another PC in the meantime, So this is really just a Bug Report for you guys.
This post has been edited by Devenic on Nov 20 2003, 07:58 PM
What dashboard are you using for the transfers?
You might also want to check out this article. The error you're getting is a Winsock error, and you're the first person to report this problem. I've never seen or heard of an error 10055 even when working on xFER.
If you're not using Avalaunch with Boost, I'd try it first. It'll be faster for you, and it shouldn't encounter this error unless there's something really weird going on with your box. There's also a setting in the Avalaunch XML that could help you tweak the port range used.
If you're still not going to use Avalaunch (which is the only way I could even imagine this error happening) then I could suggest turning on passive mode, which forces the the dashboard to become the server, so the port problem shouldn't occur. I know, it sounds weird, but normally with FTP, an FTP client becomes the server, but like all good things that came from the UNIX world, they did it backwards. Passive mode reverses this and tells the FTP server to actually be the server. :)
If you use EvoX don't bother with passive mode because it doesn't support.
Nope, the Dashboard is the latest 0.48 Version on the Xbox.
I know its NOT Dashboard dependant as Quix works fine from another pc on the network.
Saying that, I've just flattened the Rogue PC to put XP Pro on as I didn't know Win2K didn't do "IP via Firewire"
Like I said before, it was only a bug report and Not a major heartache.
Keep me posted. As I said, I've never heard of this error until you reported it (and I've been developing software for a long time) so I'd be interested if you had it happen again.
Did you, by chance, do multiple batches in one session?
It may have just been a rogue install of Win2k Adv Svr. The machine in question was of Massive Spec, designed for Audio/Video work.
The only reason I was trying Quix out, was to see how it coped with the PC being faster than my AMD2100+ Machine. (I have 3 PC's of my own and the faster the CPU doesn't always mean Faster FTPing, it seems VERY memory Dependant.)
Anyways, I digress ....
Quix fired up fine without any errors and would compress and decompress ISO's at an amazing rate, but if ANY connection was attempted to the Xbox it would give the error about Buffer space. Multiple reboots and fresh installs of quix didn't help.
The errors appeared when any of the following happened;
FTP UPLOAD ALL (with just 1 ISO or more) and the ISO was confirmed to be ok, not faulty
CREATE ISO (from FTP source)
and SCANNING TITLES when managing titles ...
Unfortunatly, as previously said, the PC was re-installed with XP Pro as he needed extra speed (Network wise) so we made a Firewire network instead.
As no other faults have been reported of similar nature, Maybe this was just a one off.