AcidStew

Tester
  • Content count

    19
  • Joined

  • Last visited

Posts posted by AcidStew


  1. I would need some kind of Wine diagnostics to see what the problematic code is, and if it can be rewritten within reason without problems for the Windows build.

    Basically I already know that it isn't doing what it should be doing, but I need some idea as to why before I can even consider looking into it. I am not familiar with Wine's implementation of WinAPI so to go in blind would be a fools errand.

     

    I did a debug on wine...

    [04/14/14 22:20:51] - Running wine-1.7.16 ApexDC-x64.exe (Working directory : /home/acidstew/.PlayOnLinux/wineprefix/ApexDC/drive_c/Program Files/ApexDC++)

    fixme:wincodecs:PngDecoder_Block_GetCount stub

    fixme:module:load_library unsupported flag(s) used (flags: 0x00000800)

    fixme:advapi:RegisterTraceGuidsW (0x14031a0d8, (nil), {f7b697a3-4db5-4d3b-be71-c4d284e6592f}, 7, 0x14047e4d0, (null), (null), 0x1404b1548): stub

    fixme:process:GetNumaHighestNodeNumber (0x22f5c0): semi-stub

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:toolhelp:CreateToolhelp32Snapshot Unimplemented: heap list snapshot

    fixme:toolhelp:Heap32ListFirst : stub

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:ver:GetCurrentPackageId (0x8ada60 (nil)): stub

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:netapi32:NetShareEnum Stub ((null) 502 0x1e57d28 -1 0x22e820 0x1e57d40 (nil))

    fixme:propsheet:PROPSHEET_UnImplementedFlags PSH_RTLREADING

    fixme:netapi32:NetShareEnum Stub ((null) 502 0x1e57d28 -1 0x22b8d0 0x1e57d40 (nil))

    err:shell:SHGetFileInfoW pidl is null!

    err:shell:SHGetFileInfoW pidl is null!

    err:shell:SHGetFileInfoW pidl is null!

    err:shell:SHGetFileInfoW pidl is null!

    err:shell:SHGetFileInfoW pidl is null!

    err:shell:SHGetFileInfoW pidl is null!

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

    fixme:file:FindFirstFileExW options not implemented 0x00000000 0x00000001

     


  2. It seems to be a Wine bug, unfortunately fixing it without breaking the build for actual Windows is probably not viable. Also we would need to know more than simply that it doesn't hash. The changes to hashing in 1.5.10 are substantial enough to make playing a guessing game an unattractive proposition.

     

    What information do you need?

    When I add a folder for sharing,the system.log shows no entries the "indexing progress" dialog shows no activity.


  3. Hi... I did the update to 1.5.11 and since that my file share is 0 bytes. I did uncheck all shared folders, restart ApexDC and add the share again... There is no hashing and the the share amount is still 0bytes.

    Im using Wine 1.7.16_x64 - the version 1.5.9 was running fine on that version! Does anybody have the same issue?


  4. Hello

    Since update to version 1.3.3 i have the problem, that finished connection does not disapper in the Transfer window. The main problem is, that no new downloads will start from the users, which are listed in the Transfer windows as disconnected or finished etc.

    See screenshot attached...

    The only way to get the list emty is to reconnect to the hub. Is it a bug?

    Thx, Acid

    post-9157-026823800 1278240429_thumb.jpg


  5. @AcidStew - Actually isn't the "slot ratio" feature what U are looking for? It is already implemented. Sorry if I look stupid by asking this, at least it is not intentional.

    The "slot ratio" share all configured slots to all hubs were are you connected. Its like faire-use and if you be connected to just one hub, this hub will use all configured upload slots. I want to overrule the global-settings for the upload slot for my favorite hubs. I will increase/decrease the upload-slots especially for hubs. I will only open so much slots as i need. If I be connected to 5 hubs, i need more upload-slots as I be connected to just one hub and this setting should help to open the slots automaticlly and first on to grant every hub the minimum requiered upload-slots. This is the fairest method for user and hub.


  6. Not existing folders are automatically removed from sharelist.

    Thats right... Existing folders are not automatically removed. This happens only if the folder is not avaliable at ApexDC startup.

    It would be more usefull to keep configured folders for sharing with a dead-link symbol or something. It sometimes happens, that i forget to turn on my external drive and if i start ApexDC, i have do reconfigure all my shared folders :D


  7. Well thats maybe true, but in some cases (like me) I get most of the time over a few days no download-slot and my upload-slots are every time taken. This is also a abuse of my upload slots. I give more as I get and thats also a kind of abuse. If i could just grant upload-slots what's requested would be the fairest way for both sides (user and hub).


  8. Hi..

    I'm using Apex DC 1.0.0B5 and my whole share is on a external USB harddisc. Sometimes (but not often :thumbsup: ), I turn of my computer and poweroff the external harddisc. Next day I've turned my computer on and try to connect to hub. I get disconnect, because i had no share. OK, I've forgot to turn on the external harddisc. So I've started the harddisc and try to connect again, but it appears the same message. After this message, I've checked my "Sharing" settings and I saw, that no directory were checked in the "Shared Directories" dialog.

    I've tried to reproduce the problem and I was able to made it...

    When you start Apex DC and your configured share drive is not avaliable, the config of this shares will be lost. I think this ist also, when your network drive is not mounted on Application startup :P

    AcidStew


  9. @spaljeni

    This feature has nothing to do with speed. I just want open more open slots, when i connect to some favorite hubs. I try to explain in my case...

    Normaly I'm connected to one hub and i have opened 2 upload slots (requested by hub). Sometime I connect to a second hub at the same time, which also requests 2 upload slots. So for all together i need 4 slots for both hub and I must set it in the global configuration. I will garantee, that every hub gets 2 slots and i cant, becaue maybe the first hub takes 3 and the second only 1 and thats a kick-reason. Further i will only have a number if upload slots open as it is requested by the hub. So if I disconnect to the second hub, I must set the upload slots back to 2, because I will only grant what is requested by hub.

    @Zlobomir

    How should this feautre get abused? Contrariwise it will help to grant every hub the solts which are requested and also it makes the life easier :-)


  10. Hello

    I think the most of us knew this problem... One hub requires e.g. 2 open upload slots and this is configured in the Settings->Sharing. So now you connect to a second hub, which need also 2 open upload slots. Now you must set the upload slots in Settings->Sharing up to 4.

    In this case it would be usefull to grant a number of upload slots in at the favorite hub proberties for each hub (if nothing is set, the gloabl value works), which override the global settings.

    Example:

    Global value in "Settings->Sharing" is set to 2

    Favorite HUB-A has a value set to 2

    Favorite HUB-B has a value set to 2

    If I have connected both hubs the upload slots are automaticlly increased to 4 and every hub gets max. 2 upload slots.

    So i hope this is realisable :-)

    Thx AcidStew