Jump to content
Muxe Inc Forums

GPFault

Members
  • Content count

    66
  • Joined

  • Last visited

Community Reputation

0 Обычный

About GPFault

  • Rank
    Advanced Member
  1. bugs in 3.00.0004

    For me gpm in console works - both clicks and drags. Thanks. But in konsole (KDEs terminal) - mouse clicks works, but mouse drags didn't. In prevous ndn build - both drags and clicks worked in konsole However - with current build both clicks and drags works in gnome-terminal (like previous build too). The difference between konsole and gnome-terminal is not obvious - both sets $TERM to xterm-256color.
  2. bugs in 3.00.0004

    This starts fine without crashing, thanks. GPM mouse doesn't work however (nothing happens on mouse input, only moving mouse rendered by gpm is visible). But really I can't remember it ever woked with ndn. Experimenting with NDN on linux more, i found 2 more problems. Problem 1. Crash when pressing Tab to switch to another panels. This is really strange problem which doesn't reproduce fine. It appears: only on one of my machines (ndn is started as non-root in konsole terminal) only if a folder or .. is currently under cursor (not appear on files) only if I switch to another panel by pressing Tab. Switching by mouse clicking works fine. This is really strange, since the backtrace points to some rendering. only if I switch fron left to right. Switching same panes with ctrl-U - and bug didn't appear. It appears on both v3.00.0006f/LINUX64 and todays binaries. Same behaviour. On todays binaries no any settings were changed, all is default. Attaching Err-file Problem 2. On a real linux console without terminal emulator - NDN fails displaying anything after runing external command. Steps: run ndn on a real console (like the yestedays problem with gpm) type ls press enter command executes, mostly file (some tty settings are broken, but thats another story) after command execution only the cursor is visible, all other screen is black. However, NDN continue working, since Alt-X Enter quites it. Note that running ndn on the same console wrapped in a tmux terminal emulator - doesn't have such problem. So, for this problem from a user point of view workaround exists - just run ndn inside tmux. Also some notes about debugging. On linuxs case-sensetive filesystems - ndn searches for debug file with .dbg extension, so it have to be renamed from .DBG to .dbg if the binaries archive contains file ending in ".DBG" Both v3.00.0006f and todays binaries are compressed with upx. However, while v3.00.0006f can be decompressed with upx -d (standard official upx decompressor), and todays binaries can't be - upx -d reports error. This theoretically can complicate debugging for some cases... crash-tab-when-right-is-folder.ERR
  3. bugs in 3.00.0004

    Tried NDN ndn_3_00_0006_l64 on linux. Much better, than 14 years ago when I tried it last time) However, I have a quite niche usage scenario - running kernel-based framebuffer (efifb) console with gpm mouse on modern hawrdware and modern kernel. X11 is not used since it can introduce unwanted side effects in my usage scenarious. ndn starts fine in terminal emulators, but in real console - it starts only with /NOMOUSE option. Without this option ndn crashes with printing stacktrace (btw, getting working stacktraces on craches is great!): I kept decodedc escape qequences, maybe they are somehow related to mouse init. Necromancer's Dos Navigator v3.00.0006f/LINUX64. Based on Dos Navigator by Ritlabs... [DEFINES/CPUX64/LINUX/FREEPASCAL] * Linux (v5.10) detected * TTY: /dev/tty5 (linux) * Process ID = 813 ... * PCRE Version 8.44 2020-02-12 * Berkeley (BSD) socket API fESC[HESC[?25hESC[?0cESC[?0cESC[?25hESC[?0cESC[0mESC[HESC[Jor Unix/Linux Caught SIGSEGV: Segmentation Fault error at 0x0000000000000000 r8 =0000000000000000 r9 =0000000000000000 r10=78716D6A6B6C6E74 r11=0000000000000213 r12=0000000000401A70 r13=00007FFDA71864B0 r14=00007FFDA71866D8 r15=00007FFDA7185708 rdi=00007FFDA7185B64 rsi=0000000000000000 rbp=00007FFDA7185A08 rbx=0000000000000000 rdx=0000000000000000 rax=0000000000000000 rcx=0000000000000000 rsp=00007FFDA71859D8 $00000000004D916D GPM_OPEN, line 118 of RTL/LNX64/GPM.PAS $00000000004D87AB SYSDETECTMOUSE, line 295 of NEWLNX/MOUSE.PP $00000000004D7D69 DETECTMOUSE, line 65 of NEWLNX/mouse.inc $000000000045C6FE SYSTVDETECTMOUSE, line 52 of DRIVERSL.INC $000000000045BCD1 DETECTMOUSE, line 349 of DRIVERS.PAS $000000000045C5CD INITEVENTS, line 1310 of DRIVERS.PAS $0000000000463801 RESUME, line 1548 of DNAPP.PAS $00000000004638AC INIT, line 1569 of DNAPP.PAS $00000000004D967F INIT, line 248 of DNUTIL.PAS $000000000041B527 RUNMAINPROGRAM, line 424 of MAIN.PAS $00000000004010F3 main, line 38 of NDN.pas $0000000000401B1C _FPC_MAINCRTSTARTUP $0000000000000001 line 185 of RTL/OBJPAS/objpas.pp
  4. Collaboration on source code

    Дальше будет много букв - поэтому общая суть и вопросы - сначала: Писал ли кто-то в последнее время письмо CandyMan с прямым вопросом о разрешении на открытие? Если нет, то на мой взгляд уместно (и я готов) написать ему по английски что-то в духе - "если вы откроете исходники, то у вас вероятно появятся новые... пользователи, как минимум я". Garl, есть ли принципиальные возражения против написания такого письма? Или это настолько глупо/странно/абсурдно, что и писать не стоит? Если CandyMan даст добро - будет ли согласие со стороны Garl? Теперь подробнее. Я возможно покажусь путаным/навязчивым/эгоистичным, но попробую донести точку зрения немного с другой стороны. Пользовался NDN 13 лет назад, и помню что он удобен. Сейчас я активно пользуюсь linux, в том числе во многих ситуациях терминалом/консолью. MC - не перевариваю, крайне малофункционален. Но NDN я уже давно не "щупал". Какая по факту причина? Без исходников присутствует абсолютно полная неуверенность в завтрашнем дне. Приучишься пользоваться, привыкнешь, потом что-нибудь поменяется в ОС что надо будет пересобрать с минорным изменением, а к этому времени авторы утратят интерес к проекту - и в результате ни исходников, ни улучшений от авторов. Открытость исходников - это по крайней мере гарантия того что получается избежать глупой ситуации "нужно минорное изменение, но его сделать некому, исходники утрачены или остались только у полностью незаинтересованных лиц". Такие заморочки наверное только у разработчиков) У тех кто сам "в случае чего" пересобрать не сможет в любом случае - таких заморочек нет. Исходя из написанного выше - что я могу сказать насчёт пользы от открытия исходников? Оценивая статистику я наверное что-то контрибьючу только в ~0.1-1% от проектов которыми я пользуюсь. Так что говоря честно - в случае открытия исходников - шанс что я что-то залью - статистически мал) Так что же произойдёт от открытия? Весьма вероятно что я попробую пользоваться ndn на linux, в тех задачах, которые у меня возникают. В случае успеха- может покажу паре знакомых. Понимаю, что всё звучит очень глупо, но получается что "открытие исходников принесёт проекту ndn некоторое количество пользователей, как минимум меня" )) Почему я например вообще не заинтересовался dn2l, даже как пользователь? Потому что по описанию мне показалось что для пользователя он гораздо менее доделан, чем ndn. Осознанно выбирать менее удобный инструмент когда есть более удобный ndn - ощущается странной идеей. Да и с проектом которым ещё нельзя пользоваться, я например связываться не готов. Большинство моих вкладов - это доработки уже вполне активно испльзуемых проектов. Более того, идея дописывать что-то в dn2l сильно демотивируется... перспективой что ndn откроют, и написанное для dn2l в этот момент станет или неактуальным (станет жалко потраченного времени) или придётся делать сложный и мучительный merge. В общем, совсем не факт что открытие принесёт хоть одного контрибьютера, это так. И если разработка делается только "для души под свои нужды" - то открытие вам ничего и не даст. А если она делается "для души для себя И для потенциальных пользователей" - то открытие исходников - это способ их привлечь) По крайней мере тех кто в подобных продуктах выбирает преимущественно открытые решения.
  5. Collaboration on source code

    Hi. I'm back to this forum after 13 (!) years of inactivity. I'm not a DN user anymore (due to becoming a linux user, and ndn on linux wasn't stable 13 years ago), however, I still think that DN UI is tuned better then any other file manager, so I'm still inetersted in the "NDN on Linux" future. Recently I found information about somebody investing thier time into porting DN variant called DNOSP to linux - https://www.linux.org.ru/news/opensource/15971481 (text is in russian) The project link is https://www.linux.org.ru/news/opensource/15971481 The project developer said that he treated NDN as closed source-project. But technically, I think NDN has more mature linux support that the project I linked above, and it's a pity that human developer resources related to Dos Navigator was spent to less advanced variant (DNOSP) instead of more advanced NDN. As far as I know 13 years ago the source code was available to "anybody who really want to edit & contribute". I asked for it, ans Stefan provides me the archive (I've lost it many years ago). In modern days, such semi-private code development sometimes leads to waste of human resources (due to work on another variant as a I pointed above). Do nowdays ndn developers have any objections to publishing the entire source code? Are there any formal licencing issues? If the only thing that stops you from publising sources are technical - the lack of time or "dont want to investigate how to create git history" etc - I'd be glad to help in publishing it. For example: you choose the public hosting platform (gitlab, github, sourceforge or choose any other) send me the sources of several versions as archives and I create organization account on the hosting platform convert the archives to git history, publish sources on that hosting, and add your account on the platform as an administrator of that project. My actual e-mail is galkin.vv@remove.anti.spam.org@yandex.ru (English or Russian).
  6. Moving Directories Inside One Drive

    The problen I described in first post looks to be another problem - it applies only to F6 (renaming with alt+F6 works correctly) and it applies to directories and not files. Maybe I hadn`t described it clearly in first post. I have folder named BigFolder containing 1000 files. It is located in C:\FirstDir I want to move it to another place in drive C: - to the C:\SecondDir C:\FirstDir is in one panel, C:\SecondDir is in other one. I put cursor to the BigFolder and press F6, Enter. What happens: -NDN creates folder BigFolder in C:\SecondDir -NDN does 1000 renaming operations - it renames C:\FirstDir\BigFolder\file1 to C:\SecondDir\BigFolder\file1 and makes such operations for each of 1000 files. -NDN removes empty C:\FirstDir\BigFolder aybe even 1000 files. But for directory with complex subdirectory structure and a dozen thousands files in it the operations maybe really slow (a few minutes) Allmost all other filemanagers do this operaion instantly - they use only one OS filesystem call - renaming C:\FirstDir\BigFolder to C:\SecondDir\BigFolder and does not any recursion. So, the problem in whatsnew/todo looks to me as another one. If it`s really the same, I'm sorry. About recreation - I have this problem with both: -2.30.6778 in windows with custom settings on NTFS -old ndn v4000 in dos with default settings on FAT so it`s really strange if you hadn`t it
  7. Hi. There is a problem in v2.30.6778/RUS (06-07-2007) WIN32, os - win2k3 (and as far I know in most previous versions in other operating systems): When I try to move folder within single drive (with F6) - NDN does recursive renaming. But it`s too slow if there is a lot of files in folder (>1000). Why single rename of the folder is not used? It`s a lot faster. If single renaming fails for some reason (locked files etc) - yes, in such case recurive renaming may be good idea, but not in general case, i think. Far, for exaple use single renaming and it works fine. In non-Windows OS's doing this with a single renaming is also possible. Thanks.
  8. Hi! There is an error with deletion of directories with long names in NDN/W32. Unfortunately, I can`t say what is the first version where it appears, but it is some from last 0.75 year, maybe version where background deletion were introduced. Steps to reproduce bug: On LFN-only drive cretate a directory with long name like 12345678901234567890 Try to delete it - the following error occured ╔══════════ Erase ══════════╗ ║ ║ ║ Erasing the directory ║ ║ 123456789012 ║ ║ subdirs: 1 ║ ║ files: 0 ║ ║ Total: 1 ║ ║ ║ ║ Stop ▄ ║ ║ ▀▀▀▀▀▀▀▀▀▀ ║ ╚════════════ 0 ════════════╝ ╔═[■]════════════ Error ═════════════════╗ ║ ║ ║ Could not delete the directory ║ ║ D:\123456789012 ║ ║ ║ ║ OK ▄ ║ ║ ▀▀▀▀▀▀▀▀ ║ ╚════════════════════════════════════════╝ Looks like name is truncated to 8.3 Note: this error occures only on NTFS drives with disabled short names, not in regular drives Files with long names are deleted properly. Subdirectories with long names are deleted properly too, for example: I have folder d:\short\12345678901234567890 I go to d:\short\ , try to delete 12345678901234567890 - get error lioke above I go to d:\ , try to delete short - it is deleted correctly NDN: Version v2.30.3829/ENG (25-12-2006) WIN32 (W9x/WinNT) with all settings default OS: Win2003 SP1
  9. It`s feature: here: http://forums.muxe.com/index.php?showtopic=766 ... [+] concurrent/background Copy/Delete is possible ... ([+] ôîíîâîå Êîïèðîâà íèå/Óäà ëåíèå)
  10. You have chosen correct forum, so, it seems nobody knows how to change drive letters in linux version of ndn
  11. Hi, alouette I haven`t any problems with FF1.5.0.7 (win32) So, it seem`s to be bug in your FF settings (though i`m not sure). Maybe it`s AdBlock( http://forums.muxe.com/index.php?showtopic...st=0&p=1892 ) Try to disable it. Please let us know if this helps. 2WebMaster(Stefan or somebody else(?)): if alouette confirm download link to be cut out by adblock it may be a good idea to change link. This seems to be common problem.
  12. Unfortunately, I don`t know a way to change NDN directory from a batch file. (Though, I`m not sure it doesn`t exist). For directory in a fixed drive it`s simple: Go to directory, press Ctrl+Alt+Shift+1 (2..9) - and add directory in quick-change list Now you can access it with Alt+1 (2..9) I don`t know special feature to make it work as you want, but there is an ugly hack that works, eee... sometimes works :) Go to wanted directory on some of your drives (D:\Users\GRPROG1\ for example) press Ctrl+Alt+Shift+1 and add directory in quick-change list Select in main menu File->Restart NDN Now, select Options->Initialization file Search for QuickDir1 ... [Quick Directories] QuickDir1=D:\Users\GRPROG1 ... Change it to ... [Quick Directories] QuickDir1=\Users\GRPROG1 ... Save file and restart ndn again Now pressing Alt+1 will go to \Users\GRPROG1 directory in current drive. The only situation I found when this hack fails is when *:\Users\GRPROG1 already is current directory - there is unwanted extra error message. Also I`m not sure that this way is portable between different OS, even between different versions of windows.
  13. new release: 2.30.0000

    Looks like http cache is misconfigured somewhere (in ndn.muxe.com, your provider or some proxy, or in your browser) Archive size for last windows version (2.30.0024) is 1 084 839 You may try to download it here: http://gpfault.smtp.ru/_w32.rar (link is NOT permanent, I delete it next week)
  14. new release: 2.30.0000

    Hi, coucou maybe this topic helps you http://forums.muxe.com/index.php?s=&sh...post&p=1892
  15. Unfortunately I can`t reproduce this bug (I tried in 2000 without SP and in XP SP1), so I can only guess for solution. You have Ctrl+Shift+[ (should switch panel directory, without modifying cmdline) working as Ctrl+[ (put directory name to cmd line), if I understand you clearly. I have similar problem with buggy national keyboard driver for DOS that I add to my autoexec.nt The reason was that it comletly catch Ctrl+Shift combination. So, do you use some non-standard keyboard driver for DOS? Does other combinations with Ctrl+Shift work (Ctrl+shift+left/right arrows in editor for by word selection)? What symbol you get in english keyboard mode when you press Shift+[ (is it '{' or something other)? Does Ctrl+Shift+[ work if you use other (left/right) Ctrl or Shift? NDN dos32 is not recommended for use under win2000 (it has some other bugs and does not support clipboard in win2000). So, imho, you should try win32 version (v2.30.0024) (for user point of view there is very few differences between dos32 and win32 versions), and maybe you will not have your bug in it.
×