Author Topic: Waiting to scan folders (Read 6097 times)

itsme · « **on:** October 24, 2010, 02:38:54 pm »

And after 20 minutes, still waiting.

I did add a folder to the library and instead of seeing all the files in this folder, WinMX comes with "waiting to scan folders" but doesn't do anything with it.

What is keeping WinMX from doing it work (showing the contents and share this to the world)???

itsme · « **Reply #1 on:** October 24, 2010, 07:53:23 pm »

Update:

After waiting for an hour, still nothing (WinMX still told me "waiting to scan folders"). Unfortunately I had two download going. But my queue was empty and it did look like I wasn't sharing any files anymore.
So I re-started and everything woks again. Only for my 2 downloads .... (remotely queued 101 and 98).

It seems to me that WinMX isn't very stable if you let it run 24/7. Sometimes after 2 days things start to go wrong. Even if you don't restart the computer but only re-start WinMX everything works perfect for another 2 to 6 days. So far I must re-start the program at least ones every 6 days but mostly even sooner.

Version: WinMX 3.54 beta 4 - community patch 1.0 installed
System: Win XP English with SP 2 installad
Connection: ADSL 6mbit down / 1mbit up

White Stripes · « **Reply #2 on:** October 24, 2010, 10:43:27 pm »

ive not been able to run winmx for more than a week.. so yes its very leaky/unstable in the long run....

btw, you should install SP3... SP2 is nolonger supported...

GhostShip · « **Reply #3 on:** October 24, 2010, 11:02:32 pm »

I havent had any of these stability problems and used to host a chat room as well as sharing etc so I wouldnt look at winmx for problems in fact the only time I see folks complain about stability is when they use items like mxmoni or leech hammer those do create a largish memory leak, having to restart winmx once a week is more than I remember having to do.

As for the sharing files issue I have never heard of anyone suffering that, I would look a bit more at your individual setup for an answer to that problem, likely you have some third party protection running that doesnt like winmx scanning your folders.

itsme · « **Reply #4 on:** October 24, 2010, 10:02:59 pm »

The machine running WinMX is an old Pentium 4 with 2800 Mhz processor and 1.5 GB internal memory. Clean install on Windows XP with SP 2 (and I don't ever want to try SP 3 again). The Windows firewall isn't active. There isn't any anti-virus software installed. In fact, the only software installed is WinMX. Support for Japanese characters is also installed.

The only two programs that I run on this are WinMX and IE 6 (that comes with Windows XP) to go to the Google translate page (I can't read or write Japanese).

The folder for incomming files as well as the folders I share are all on a Samba network (Linux server). As soon as a file completes downloading I move it to an other location and scan it with a virus scanner. Have more computers and none ever has a problem with connecting to my Linux server. Even when WinMX comes with this strange "waiting to scan folders" message, Explorer can still see and access the network share. WinMX probably also as up- and downloads aren't affected.

@GhostShip, Consider yourself very lucky if you never experience stability problems. Windows (any version) isn't very stable by itself. Have 2 Windows servers running at my workplace and they need to be reset once a week to keep running smoothly while the Linux servers only re-start after a hardware failure (on average once per 3 years).

White Stripes · « **Reply #5 on:** October 25, 2010, 01:34:39 am »

sounds like youd be better off using the machine to run winmx using wine on linux than using a 'dedicated' winmx box...

itsme · « **Reply #6 on:** October 25, 2010, 06:29:58 am »

Quote from: Silver Stripes on October 25, 2010, 01:34:39 am

sounds like youd be better off using the machine to run winmx using wine on linux than using a 'dedicated' winmx box...

Have thought about that, but the big problem are the Japanese characters. I collect Jade movies and most of them don't have any English in the file name, only Japanese. So it is essential to have support for Japanese. A dedicated Windows machine for this is the easiest way. Now it doesn't matter if things look strange in other programs (like the back-slash in Explorer that is replaced by a Japanese symbol)

Bluey_412 · « **Reply #7 on:** October 25, 2010, 09:56:23 am »

Somebody should tell my systems that they are supposed to be unstable...
Win 7 64-pro, Core-2 Duo, 4gb of Ram, counless HDD's, with one IDE for boot, rest are USB or SATA raid arrays,, the NIC in this thing is also a 4-port switch to keep my 2 laptops online, and this rig runs for weeks at a time, winmx and all, and WPCC...

Ahhhhhhhhhhhhhhh, but it doesn't run Facebook...

GhostShip · « **Reply #8 on:** October 25, 2010, 11:37:47 am »

I havent ever used Google translate but I have used Google desktop search a few times and its a pain in the ass keep demaning outside connections to Google looking for daily updates as if there are going to be that many and even worse it has caused problems within the shell system settings , I would definitely try losing any Google app for a test if you want to see how a system works , as I can attest with Google apps installed using a windows machine becomes an annoyance instead of a joy.

silicon_toad2000 · « **Reply #9 on:** October 25, 2010, 02:11:21 pm »

I'm not 100% sure on this, but have you mapped the network drives to the samba network or just let windows discover them?
Maybe mapping a drive to the network folder might help windows/winmx.

Other than that I could only think of maybe using virtualbox on the the linux machine to run winmx and ie6 rather than wine and do away with the dedicated box.

itsme · « **Reply #10 on:** October 25, 2010, 05:14:43 pm »

Maybe my old Pentium 4 is what it is, OLD.

Have installed vmware on my Linux server (Slackware 12.1) and in it, Windows XP. WinMX seems to run smoothly but it only runs for 20 hours now. The version on my dedicated box has developed a new problem. It disconnects and re-connect every 6 to 7 hours. But it looses everything in between. All my blue files turn red, the queue goes empty and it looks like it is starting all over (finding sources, entering remote queues etc). This way it will never ever download anything.

The version that runs inside vmware has no problems so far. Have to see how it goes after a couple of days / weeks ....

Quote

I'm not 100% sure on this, but have you mapped the network drives to the samba network or just let windows discover them?

Samba runs as PDC and the shares are all mapped. There is a netlogon share and in it batch files to make that happen.

White Stripes · « **Reply #11 on:** October 25, 2010, 08:30:42 pm »

Quote

The version on my dedicated box has developed a new problem. It disconnects and re-connect every 6 to 7 hours.

(imagine how i feel on dialup with 6hr session timeouts... lol...)

primary or secondary? btw, if you are running the vmware and the dedicated box both as primary there will be problems...

does the vmware winmx run for 20hrs then crash or 20hrs and reconnect?

Quote

Maybe my old Pentium 4 is what it is, OLD.

i use a p3 with a 1tb 'external' drive for a file server/winmx runner/bittorrent box .... so i dont think winmx alone is too much for a p4...
(also a p1 .. very first version of the pentium running at 5volts and 60mhz as a webserver running linux... so... depends on how you configure things)

oh btw,

https://help.ubuntu.com/community/Japanese_Input_and_Fonts_in_Ubuntu_7.04 -- just an example -- but linux already uses utf8 for its internal encoding... its just really a matter of getting the right fonts and keyboard layout setup..

linuxが日本語を話す

@GS

Quote

I havent ever used Google translate

http://www.google.com/translate --- its a site not an app.... turn off instant translation and it waits for you to hit translate rather than translating as you go to lessen the 'load' should you wish...

その簡単

itsme · « **Reply #12 on:** October 25, 2010, 10:33:45 pm »

@Silver Stripes
Both instances of WinMX run as secondary.

A Pentium 4 is not by definition old. I wrote that mine is old (meaning not functioning anymore as it should)

I'm using Slackware since version 3.0 (1996) and have used even 386 machines (with 1.2 GB hard disk and 128 MB memory) that worked as a router with dhcp/dns and sendmail. Or a Pentium I, 75 Mhz running Samba in an environment with 60 workstations. I have no doubt that WinMX isn't that heavy that it can't run on a Pentium 4, but it seems not to run smoothly on mine.

The WinMX that runs inside vmware runs perfect so far. If it keeps running like this, the Pentium 4 will be assigned an other task. It is the WinMX version that runs on the Pentium 4 that disconnects and reconnect every 6 to 7 hours.

The reason for running WinMX in Windows is simple. It is a Windows application and installing support for Japanese in Windows is just a matter of some mouse clicks. I know that Japanese character support is also possible in Linux (what isn't) but this is one of the few things that is really easy in Windows.
If there ever comes a real Linux version of WinMX I certainly will install Japanese character support on my server.

White Stripes · « **Reply #13 on:** October 25, 2010, 11:08:46 pm »

Quote

WinMX isn't that heavy that it can't run on a Pentium 4, but it seems not to run smoothly on mine.

i still doubt its your hardware ... esp if youve had that much linux experence then i know youve run memtest on it...

that being said... winmx isnt really stable anywhere for long periods of time.... sure it'll run smooth for a couple of days then suddenly spring a memory leak that soaks up about 400mb+ ram.. and very quickly climbing... forcing the need to kill the app with taskmgr (happened to me not to long ago) ... or its UI will just plain stop responding... or its text flicker to the point of being obnoxious... or suddenly decide not to connect to anything... you name it winmx has done it...

its... moody... to say the least.... regardless of what hardware you feed it... and thats without mxmoni or leechammer attached.... add either of those two... or worse.. both... and be prepared for a weird ride in winmx land....

the exception being running it on windows 7 due to that os having in-memory fixes for flaky apps...

...kinda tempting to run it in a debugger to see how long that lasts...

as for your desire for a proper linux winmx.... its not as far off as you might think....

White Stripes · « **Reply #14 on:** October 26, 2010, 05:51:08 am »

....actually... winmx works quite well when running in a debugger o.O

has anyone else tried this??

GhostShip · « **Reply #15 on:** October 26, 2010, 07:58:09 am »

It is a beta version so theres no harm running it in that mode, just a pity the actual release never arrived.

White Stripes · « **Reply #16 on:** October 26, 2010, 08:14:16 am »

the amount of winsock errors is staggering.....

itsme · « **Reply #17 on:** October 26, 2010, 02:19:14 pm »

@Silver Stripes

Quote

as for your desire for a proper linux winmx.... its not as far off as you might think....,

Are you sure?? And will it also allow us to:

copy file names and user names
block leechers without using an external program
search in the queue
do several searches without disturbing the rest of the program
use Japanese character support by simply selecting it in the settings

And all the other things that would make this program really great.

White Stripes · « **Reply #18 on:** October 26, 2010, 07:23:56 pm »

basics first... then feature creeps later... but eventually yes....

itsme · « **Reply #19 on:** October 28, 2010, 09:40:08 pm »

Update:

The WinMX running inside vmware is still going great. The other (on the Pentium 4) has developed even more nasty behavior. Had about 15 blue files with good queue numbers when I decided to browse a user list of somebody I was uploading to. Unfortunately this user shared 3000+ files and as a result, all my blues went red. I have successfully browsed long list before,... But not this time.
Well, running WinMX inside vmware (on Linux) seems the way to go, no problems and can even browse long list without loosing my place in remote queues.