BeBits - BeShare - Talkback

BeBits

BeShare

Talkback

Go back to the BeShare page

Post a new Talkback comment!

BeShare on BONE

By BeJay - Posted on March 20, 2004 - 10:55:13 (#11556)
Current version when comment was posted: 2.25

Monni,

I have the same problem as BeOS Freak. I'm using an AthlonXP 1200 with 786,000 mgb ram running BeOS 5.03 Pro with BONE 7a. BeShare 2.25 will appear in deskbar after doubleclicking, but no windows. Is this a problem with BONE or the combination of BONE and AMD. It works fine on my MAX partition.
Could you explain the changes you make to make BeShare run?
This is obviously a bug that hopefully Jeremy will help with.

Regards,
BeJay

BeShare on BONE

By BeJay - Posted on March 20, 2004 - 10:54:21 (#11555)
Current version when comment was posted: 2.25

Monni,

I have the same problem as BeOS Freak. I'm using an AthlonXP 1200 with 786,000 mgb ram running BeOS 5.03 Pro with BONE 7a. BeShare 2.25 will appear in deskbar after doubleclicking, but no windows. Is this a problem with BONE or the combination of BONE and AMD. It works fine on my MAX partition.
Could you explain the changes you make to make BeShare run?
This is obviously a bug that hopefully Jeremy will help with.

Regards,
BeJay

BeShare & Zeta

By Monni - Posted on March 20, 2004 - 10:23:32 (#11554)
Current version when comment was posted: 2.25

I had to recompile BeShare to get it behave under Zeta. It needs some changes in the Makefile and few source files, but not too complex ones.

Does not run in Zeta RC1 SP2 on Athlon MP Processor

By BeOSFreak - Posted on February 28, 2004 - 22:25:04 (#11268)
Current version when comment was posted: 2.24

Hi,

BeShare is de BOMB! However I can never get it to work in my Zeta Partition. Does anyone know why?

Maximum Upload Bandwidth

By Masque - Posted on November 1, 2003 - 11:24:05 (#9436)
Current version when comment was posted: 2.23

Is there a possibility to limit the maximum upload bandwidth in addition to the single uploads?
If not, could you please add that feature? It could be very useful, since beshare tends to saturate very easily the upload banwidth, slowing almost all other appication's dl/ul operations.

Jeremy has a guilty conscience

By Zaranthos - Posted on October 8, 2003 - 19:55:33 (#9109)
Current version when comment was posted: 2.23

Monni said:>
Why did only Zaranthos get the credits? I was the one who did put too many files in single queue at the first point. And it was my and Garjala's idea to
test the maximum amount of files that can be downloaded in single queue.

He's just feeling guilty for not adding the uptime code to BeShare yet. He's afraid their might be a recall election I think. :P

BeShare blowing up the stack

By Monni - Posted on October 7, 2003 - 10:00:21 (#9093)
Current version when comment was posted: 2.23

Why did only Zaranthos get the credits? I was the one who did put too many files in single queue at the first point. And it was my and Garjala's idea to test the maximum amount of files that can be downloaded in single queue.

BTW. Have you fixed the issue with downloading from firewalled users failing because it seems to try to validate the port number even when it is not necessary?

BeShare Compression Great!

By Alexander G M Smith - Posted on August 21, 2003 - 15:28:55 (#8571)
Current version when comment was posted: 2.22

Turning on compression sure improves my BeShare connection! It now starts up in a second or two, rather than a large fraction of a minute (when connecting to Tycom, which has a lot of user status data to transmit when it starts up). It seems to be more reliable too (guess there's less chance of data getting lost or the connection getting broken if there isn't as much data).

Doh

By 7 - Posted on July 21, 2003 - 03:21:36 (#8237)
Current version when comment was posted: 2.22

I should read the directions more often.

Please disregard.

Alan

Source does not appear to compile out of the box

By 7 - Posted on July 21, 2003 - 03:18:51 (#8236)
Current version when comment was posted: 2.22

I get this when I try and compile.

It looks like it needs flags of -isanta/ added.

Alan

[/boot/home/src/BeShare/source]:
$ make
gcc -I../muscle -Isanta -Isanta/BetterScrollView -Isanta/ColumnListView -Isanta/Cursors -Isanta/NewStrings -Isanta/PrefilledBitmap -Isanta/ScrollViewCorner -I../muscle/zlib/zlib -DMUSCLE_ENABLE_ZLIB_ENCODING -Wall -W -Wno-multichar -fno-exceptions -O2 -I/boot/develop/headers/be/bone -DBONE -c -o ReflowingTextView.o ReflowingTextView.cpp
In file included from /boot/home/src/BeShare/source/ReflowingTextView.cpp:1:
/boot/home/src/BeShare/source/ReflowingTextView.h:15: error: util/Queue.h: No such file or directory
/boot/home/src/BeShare/source/ReflowingTextView.h:16: error: util/String.h: No such file or directory
In file included from /boot/home/src/BeShare/source/ReflowingTextView.h:17,
from /boot/home/src/BeShare/source/ReflowingTextView.cpp:1:
/boot/home/src/BeShare/source/BeShareNameSpace.h:4: error: support/MuscleSupport.h: No such file or directory
make: *** [ReflowingTextView.o] Error 1

feature request

By jaredeldredge - Posted on July 15, 2003 - 18:32:00 (#8181)
Current version when comment was posted: 2.21

i spend a lot of time downloading very large files via beshare - i have just as many partial files as i have completed ones. when i search for these files again, it would be great to have some color highlighting in the results pane:

red: never downloaded any (or less than half) of that file
yellow: downloaded a significant amount, but still incomplete
green: don't download this file - you already have it!

perhaps there should be a buton to enable/disable this feature so that it isn't always happening - maybe some people wouldn't like it.

but hey - thats my two bits! :) rumor has it that you'll have a new version out is a day or two (rumors? i saw ya on beshare sayin it) so i figured i'd set you to task on some new stuff already!
-jared

brilliant !!!!

By gijsbert - Posted on June 29, 2003 - 01:05:24 (#7950)
Current version when comment was posted: 2.21

/setulrate 5000
thought I knew most of the commands ....

By jaf - Posted on June 28, 2003 - 21:15:44 (#7948)
Current version when comment was posted: 2.21

Try typing /setulrate 5000 into the chat window. Type /help for other options, too. That will let you set a default per-transfer bandwidth limit. A global bandwidth limit is outside the scope of my capabilities at the moment. :^/

request .... for bandwith limit

By gijsbert - Posted on June 28, 2003 - 14:14:16 (#7939)
Current version when comment was posted: 2.21

would it be possible to set a constant limit on the bandwith; at the moment you have to set it everytime someone gets a file, for this file, if the download stops you have to set it again.
Maybe a general bandwith limit option ?

thanks Jeremy !

Workspace on start ...

By cvincent - Posted on June 23, 2003 - 20:14:55 (#7861)
Current version when comment was posted: 2.21

Hi,

Can you add feature to fix the workspace where beshare must start when it will be launch (same as Mail-It)

Regards,
CKJ

Screensacer activation

By ryanknapper - Posted on June 15, 2003 - 19:29:42 (#7750)
Current version when comment was posted: 2.21

What about a BeShare screensaver which logs in and operates when the computer is idle? For when I forget to start it up...

Please email me corrections

By jaf - Posted on May 24, 2003 - 12:49:17 (#7408)
Current version when comment was posted: 2.21

Hey Escarabajo.... if you see mistakes in the Spanish translation, please let me know what they are so that i can correct them for the next release. If you wanted to, you could just edit the file beshare/source/ShareStrings.cpp and email it to me.

no SpLocale please!

By ahwayakchih - Posted on May 23, 2003 - 20:08:50 (#7395)
Current version when comment was posted: 2.21

although i understand that one easy localization preferences etc. is better, SpLocale isn't good IMHO. Last time i tried it it was buggy and crashed. If ever it should be optional (not a must). Of course Jeremy (and other authors, since You posted it to Beam and Helios as well...) has last word on it ;]

Reply to Bepage

By Escarabajo - Posted on May 23, 2003 - 18:25:45 (#7391)
Current version when comment was posted: 2.21

Yes, now you can choose language, but i think SpLocale is a better solution for localization software that the one that comes with Beshare. With SpLocale is easier create a new language or edit one that already exists. For example, Spanish translation has got some mistakes, and with SpLcale would be very easy correct them, but now is a bit more complicate.

why?

By BePage - Posted on May 5, 2003 - 20:11:29 (#7187)
Current version when comment was posted: 2.21

why, under Settings you already can choose Language?

Adapting BeShare to SpLocale

By Escarabajo - Posted on May 5, 2003 - 19:36:58 (#7186)
Current version when comment was posted: 2.21

I'd like to see this great app adapted to SpLocale.

By Jess - Posted on April 15, 2003 - 06:23:12 (#6868)
Current version when comment was posted: 2.21

Dude,
thats not even funny... pure bfs here pure bfs...

By marcone - Posted on April 15, 2003 - 03:45:44 (#6867)
Current version when comment was posted: 2.21

Jess,

Are any of your shared files located on a FAT filesystem, by any chance? Reading from a FAT filesystem (especially if it is large and fragmented) can result in a lot of high-priority CPU usage.

Runs ok here.

By Tom_Artosorse - Posted on April 14, 2003 - 23:28:45 (#6864)
Current version when comment was posted: 2.21

Well, it seems fine at my end. I am running BONE though. I am sharing 2248 files, virtually all symlinked - and doing a search presents no problems - all but no processor usage. Maybe Jess found a net_server problem?

Weary but working

By Jess - Posted on April 14, 2003 - 23:21:39 (#6862)
Current version when comment was posted: 2.21

Well I got it up by renaming my shared folder & then starting... then readding my shares... I can only speculate that this is possibly an issue when sharing lots of symlinked files or possibly 2000 or so shared files... in any case the shared scann thread took my system down in a nasty way. Jeremy says all is ok on his end & a few others say they are fine but so far those that are fine are running BONE. Just prepare for the first run incase others experiance this make sure your not downloading FreeBSD iso's or anything when you run for the first time.

THX, good to know :)

By ahwayakchih - Posted on April 14, 2003 - 23:00:39 (#6861)
Current version when comment was posted: 2.21

I've just wanted to try it out. I guess i'll have to wait for Jeremy's answer :)

DO NOT INSTALL THIS!

By Jess - Posted on April 14, 2003 - 22:37:13 (#6859)
Current version when comment was posted: 2.21

Just a quick note on top of the last post... This version of BeShare will kill your system dead or at least messed up. The share scan thread is on crack... cannot kill it by any means & it will chew your system up badly.

Major messed up...

By Jess - Posted on April 14, 2003 - 22:19:48 (#6858)
Current version when comment was posted: 2.21

I just installed the New BeShare... cpu is at 100% for like 4 5 min now on a shares scan thread & it's not letting up. It's also not finding all my shares either... I can't kill it either not with Process Controller or ctrl del... crap I'm gonna have to reboot!

Cool

By Jess - Posted on April 7, 2003 - 09:19:41 (#6754)
Current version when comment was posted: 2.20

Cool man thanks for you work.

Re: Transer death

By jaf - Posted on April 7, 2003 - 07:35:38 (#6752)
Current version when comment was posted: 2.20

Hey Jess,
The transfer death, as far as I can tell, is due to a bug in the upload-rate-limiting code. I've been working with Garjala to track down the problem and will hopefully have a fix for it soon. As for downloads resuming when people come back on line, that feature is implemented and should work as described now.

Transfer death

By Jess - Posted on April 7, 2003 - 02:29:57 (#6749)
Current version when comment was posted: 2.20

Hey,
just a quick note but whats with BeShare transfer deaths?
By this I mean I can start a DL & in a few min I've gone
from 300k /per sec to 8 bytes per second... Now before you
say it's the other person note that I can stop & restart &
be right back to 300k or what ever the intial speed was off
the host. This also happens to me here. I can start a DL
from my server to one of my internal machines & sure enough
I'm blazing along (being sarcastic as dling with beshare is
slow compared to ftp'ing) at say 3 or 400k per sec & in a few
min I'm down to bytes of BeShare just dies. This happens on Bone & net_server. I constantly have to watch dl's & restart
them. Also BeShare still does not have resume all option or
resume failed dl's properly all the time. If some one logs off
while your dling from them BeShare should look for them &
resume when they come back on line or fine another host with
the same file (possibly an md5sum check?) I'm sure many people
would dig that.

By jaf - Posted on March 10, 2003 - 22:46:30 (#6329)
Current version when comment was posted: 2.20

"My country right or wrong. When right, to be kept right; when wrong, to be put right."

-US Senator Carl Shurz

Why is BeShare a Liberal Conspiracy Theory

By Super Dave Osbourne - Posted on March 10, 2003 - 09:21:48 (#6310)
Current version when comment was posted: 2.20

Well, in summary, the author of BeShare is a Pinko Simpathizer! :P

doh

By Jess - Posted on February 8, 2003 - 16:04:52 (#5809)
Current version when comment was posted: 2.19

I should compile a list but I got to much going on ;P
one more thing would be when I restart Beshare in the morning
if I try to resume some times it sits there saysing awaiting call back... but then if I do a search for the file again & double click to dl it picks it up no problem while the first entery sits on its butt saying awaiting call back... even though it's been resumed on another attempt. (note I can halt & restart the first one & all it will ever do is say awaiting call back.

By jaf - Posted on February 7, 2003 - 23:14:19 (#5794)
Current version when comment was posted: 2.19

Hi Jess,

Most of the behaviour you are asking for regarding auto-resume should be the current BeShare behaviour... at least, how you want it to behave is how it does behave on my system. One possibility that I will look into is that BeShare isn't doing the right thing when the "auto-clear finished or failed downloads" item is checked in the Settings menu -- if you have that checked, you might uncheck it and see if things work better. I will test that option myself when I get time.

As for the file transfer speed tapering off, I will look in to that too if I can reproduce it.

By Jess - Posted on February 7, 2003 - 22:10:15 (#5792)
Current version when comment was posted: 2.19

Ok no when I restart beShare from a crash or just booting up in the morning I get the grey error boxes then it clears all my downloads. Even if the person is on to resume from it clears everything for the most part. In any case I find this really cracked out as if I wanted them cleard I'd do it myself unless this is a semi bad behaviour of the clear finnished or failed DL's. I'd like BeShare to only remove a dl if its finnished & also if it stops in the middle of a dl to auto resume every time a dl drops. If a user logs off & back on it sucks to have to watch for them to log back on & tel beshare to resume. it should do it as soon as the file is avail. Also possibly some day intergrate a corrupt dl file fixer that would analyse & chop off what was needed to get beshare to resume an other wise lost dl. I have also noticed that long downloads wind down. by this I mean they will start out at say 50k then drop too 800bytes. If I manually stop the dl & resume I'm back up to 50k. This happens off of anyone I dl from & is a new thing. In any case most file sharing apps in windows have these resume behaviours but BeShare does not & it's some what frustrating at times. In the end i know this was just a demo for Muslce that ran out of control but if you could look into fix or add these things in the future it would be appreciated... I think I'd be speaking for every one when I say booting into windows or linux to dl stuff sucks.

By jaf - Posted on February 7, 2003 - 21:57:24 (#5788)
Current version when comment was posted: 2.19

Hi Jess,

Regarding BeShare's clearing of downloads on re-launch -- I'm not sure whether you mean that the download boxes disappear, or that they appear, but show up in gray/error state. Assuming you mean the latter, this may be correct behaviour; BeShare won't try to auto-resume the download until it sees that the uploader is logged in.

Regarding the resume starting over -- this usually occurs when the downloaded fragment and the shared file don't match, which makes BeShare think they are actually different files that happen to have the same name. In normal usage this shouldn't happen, but if your machine is crashing, it's possible that the file fragments on your disk have become corrupted (this is possible because BFS journals only filesystem metadata, not actual file contents). When a download isn't resuming properly, you might try using the filechopper utility (included with BeShare; "cd BeShare/source; make filechopper" to compile it) or one of the utilities from BeBits to remove the last several hundred kilobytes from the end of the file. BeShare checksums the last 64KB of a file-fragment for resume-matching purposes, and unfortunately it is usually the last part of the file that gets corrupted if there is a sudden power outage or system crash.

By Jess - Posted on February 7, 2003 - 21:38:46 (#5787)
Current version when comment was posted: 2.19

I'd really like to see resume fixed some time. If you crash or quit BeShare then say relaunch in the morning it simply clears all your downloads instead ot trying to resume them... So I try to restart them but it wont resume even though I have 300mb of a file & decides it going to start over. This is really stupid app behaviour...

localhost probbie

By yonemoto - Posted on January 18, 2003 - 06:29:42 (#5425)
Current version when comment was posted: 2.18

Fixed it! Turned out that for some stupid reason, I had localhost set to DHCP, so it didn't really assign it correctly. Setting localhost to manual IP configuration fixed it -- perhaps this should be posted as a general "wonky networking problems" solution somewhere!!

Isaac

re: Compile error

By jaf - Posted on January 15, 2003 - 22:26:58 (#5394)
Current version when comment was posted: 2.18

Firstly, if you are compiling BeShare under Dano or some other "unofficial" version of BeOS, keep in mind that BeShare isn't really supported on those OS's, only R5.0.3 (with or without BONE). That said, try adding a line

class BList;

around line 25 of CLVListItem.h.



	Comment Pages: << prev \| 1 \| 2 \| 3 \| 4 \| 5 \| next >>













			Recent Downloads - # 76 Total Downloads - # 15 Total Views - # 11 User Ratings - # 35




			Chat & IRC NFS Clients Remote Access Clients




			1. BePodder - 9.80 2. QEMU - 9.68 3. ScummVM - 9.57 4. cpu_fix - 9.42 5. Jukebox - 9.40 6. libdl.so - 9.40 7. Haiku AGP busm... - 9.35 8. vim6 - 9.31 9. Beezer - 9.26 10. HandBrake - 9.25




			1. BeOS 5 Perso... - 13,578 2. Realtek RTL8... - 13,092 3. Ati Radeon G... - 12,551 4. Ensoniq Audio... - 7,541 5. ATI Rage 128... - 7,435 6. USB Joystick... - 5,652 7. Broadcom 440x... - 5,401 8. S3 Trio 64 v2... - 4,712 9. USB Serial dr... - 4,704 10. Intel Extreme... - 4,464




			You are not logged in. Login


	Unless otherwise noted, everything is copyright © 1999-2009 Haikuware. All Rights Reserved. For more legal trivia, take a gander at our Legal Stuff page and our Privacy Statement.