Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - MarkV

Pages: [1] 2 3 ... 50
1
Beta / Re: version 2.4
« on: May 26, 2020, 10:30:17 PM »
Yes, the 2.3m build #300 works fine on that vanilla W2K SP4. So, there is at least a working fallback build.

No clue if it helps. but here's the Dr. Watson (drwtsn32.exe) report for the crash:
Code: [Select]


Application exception occurred:
        App:  (pid=1140)
        When: 5/27/2020 @ 00:10:25.788
        Exception number: c0000025
()

*----> System Information <----*
        Computer Name: VBX-W2KTEST
        User Name: Test
        Number of Processors: 1
        Processor Type: x86 Family 15 Model 2 Stepping 0
        Windows 2000 Version: 5.0
        Current Build: 2195
        Service Pack: 4
        Current Type: Uniprocessor Free
        Registered Organization: *
        Registered Owner: Test

*----> Task List <----*
   0 Idle.exe
   8 System.exe
 180 smss.exe
 208 csrss.exe
 228 WINLOGON.exe
 256 SERVICES.exe
 268 LSASS.exe
 392 VBoxService.exe
 480 svchost.exe
 508 spoolsv.exe
 536 AvastSvc.exe
 568 svchost.exe
 608 regsvc.exe
 624 mstask.exe
 540 winmgmt.exe
 704 svchost.exe
1168 explorer.exe
1280 VBoxTray.exe
1336 AvastUI.exe
1340 internat.exe
1564 explorer.exe
1140 hfs.exe
 784 drwtsn32.exe
   0 _Total.exe

(00400000 - 00979000)
(77F80000 - 77FFC000)
(77570000 - 775A0000)
(77E10000 - 77E6F000)
(7C570000 - 7C624000)
(77F40000 - 77F7D000)
(7C2D0000 - 7C335000)
(77D30000 - 77D9F000)
(77800000 - 7781E000)
(76620000 - 76631000)
(76B30000 - 76B6E000)
(70A70000 - 70AD6000)
(78000000 - 78045000)
(71710000 - 71794000)
(7CF30000 - 7D176000)
(77820000 - 77827000)
(759B0000 - 759B6000)
(779B0000 - 77A4C000)
(7CE20000 - 7CF0F000)
(7CDC0000 - 7CE10000)
(7C340000 - 7C34E000)
(77BF0000 - 77C01000)
(77980000 - 779A5000)
(75050000 - 75058000)
(75030000 - 75044000)
(75020000 - 75028000)
(77950000 - 7797B000)
(751C0000 - 751C6000)
(75150000 - 75160000)
(75E60000 - 75E7A000)
(6E420000 - 6E426000)
(7C950000 - 7C9DF000)
(64E40000 - 64E61000)
(78B20000 - 78DDE000)
(77840000 - 7787E000)
(770C0000 - 770E3000)
(772B0000 - 7731D000)
(782C0000 - 782CC000)
(77340000 - 77353000)
(77520000 - 77525000)
(77320000 - 77337000)
(773B0000 - 773DF000)
(77380000 - 773A3000)
(77830000 - 7783E000)
(77880000 - 7790E000)
(7C0F0000 - 7C154000)
(774E0000 - 77514000)
(774C0000 - 774D1000)
(77530000 - 77552000)
(77360000 - 77379000)
(777E0000 - 777E8000)
(777F0000 - 777F5000)

State Dump for Thread Id 0x5b8

eax=0012f914 ebx=0012ffb0 ecx=00000000 edx=ffffffff esi=0012f98c edi=00000000
eip=77facc94 esp=0012f908 ebp=0012f974 iopl=0         nv up ei pl nz na pe nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00200202


function: RtlTraceDatabaseEnumerate
        77facc6f eb23             jmp RtlConvertUlongToLargeInteger+0x10c4 (77fbc294)
        77facc71 f6460401         test    byte ptr [esi+0x4],0x1       ds:00bb9872=??
        77facc75 742a             jz      wcstombs+0x16a9 (77fb93a1)
        77facc77 c745a0250000c0                                  ss:00bb985a=????????
                                  mov     dword ptr [ebp+0xa0],0xc0000025
        77facc7e 8d45a0           lea     eax,[ebp+0xa0]         ss:00bb985a=????????
        77facc81 c745a401000000   mov   dword ptr [ebp+0xa4],0x1 ss:00bb985a=????????
        77facc88 50               push    eax
        77facc89 8975a8           mov     [ebp+0xa8],esi         ss:00bb985a=????????
        77facc8c 894db0           mov     [ebp+0xb0],ecx         ss:00bb985a=????????
        77facc8f e80cf8ffff       call    RtlRaiseException (77fac4a0)
FAULT ->77facc94 8b1b             mov     ebx,[ebx]              ds:0012ffb0=0012ffe0
        77facc96 83fbff           cmp     ebx,0xff
        77facc99 0f8540ffffff     jne     RtlTraceDatabaseEnumerate+0xb3 (77facbdf)
        77facc9f eb08             jmp     wcstol+0x183 (77fb7ca9)
        77facca1 b001             mov     al,0x1
        77facca3 eb06             jmp     allmul+0xb (77fb4fab)
        77facca5 834e0408         or     dword ptr [esi+0x4],0x8 ds:00bb9872=????????
        77facca9 32c0             xor     al,al
        77faccab 5f               pop     edi
        77faccac 5e               pop     esi
        77faccad 5b               pop     ebx
        77faccae c9               leave

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0012F974 77F91BC6 0012F98C 0012F9BC 0012F98C 0012F9BC ntdll!RtlTraceDatabaseEnumerate
0012FCE0 00682EE2 0EEDFADE 00000001 00000007 0012FCF8 ntdll!KiUserExceptionDispatcher
0012FD4C 00683D83 0012FDD8 00000000 012B948C 0012FD88 !TMethodImplementationIntercept
0012FD60 006AD7DB 0012FE04 0012FD94 006AD7F1 0012FD88 !TMethodImplementationIntercept
0012FD88 006B5341 0012FE04 0012FDA0 006B5486 0012FE10 !TMethodImplementationIntercept
0012FE10 00799606 00000000 0012FE48 007A1D2B 0012FE50 !TMethodImplementationIntercept
0012FE1C 007A1D2B 0012FE50 007A1DA3 0012FE48 0089050C !TMethodImplementationIntercept
0012FE48 007A9AF7 0012FED8 007A9C8C 0012FED0 00000000 !TMethodImplementationIntercept
0012FED0 007BF53B 0012FF00 007BF5ED 0012FEF4 01396A7C !TMethodImplementationIntercept
0012FEF4 007BFA28 0012FF8C 0012FF94 007BFF1E 0012FF8C !TMethodImplementationIntercept
0012FF8C 007D653E 0012FFB0 007D6560 0012FFC0 00000000 !TMethodImplementationIntercept
0012FFC0 7C5989D5 00000000 00000000 7FFDF000 00000000 !TMethodImplementationIntercept
0012FFF0 00000000 007D6380 00000000 000000C8 00000100 kernel32!ProcessIdToSessionId

*----> Raw Stack Dump <----*
0012f908  c0 fc 12 00 14 fd 12 00 - 8c f9 12 00 25 00 00 c0  ............%...
0012f918  01 00 00 00 8c f9 12 00 - 94 cc fa 77 00 00 00 00  ...........w....
0012f928  e8 56 13 00 f8 f9 12 00 - 64 f9 12 00 60 f9 12 00  .V......d...`...
0012f938  88 f9 12 00 00 00 00 00 - cc fc 12 00 00 00 00 00  ................
0012f948  48 31 f8 77 ff ff ff ff - a8 f6 12 00 14 00 00 00  H1.w............
0012f958  8c f9 12 00 1f 00 00 00 - 14 00 16 00 38 b4 16 00  ............8...
0012f968  00 00 13 00 00 70 12 00 - 00 00 00 00 e0 fc 12 00  .....p..........
0012f978  c6 1b f9 77 8c f9 12 00 - bc f9 12 00 8c f9 12 00  ...w............
0012f988  bc f9 12 00 de fa ed 0e - 01 00 00 00 00 00 00 00  ................
0012f998  b1 bc 59 7c 07 00 00 00 - e2 2e 68 00 e0 45 2a 01  ..Y|......h..E*.
0012f9a8  a8 3d 68 00 00 00 00 00 - d8 fd 12 00 4c fd 12 00  .=h.........L...
0012f9b8  14 fd 12 00 3f 00 01 00 - 00 00 00 00 00 00 00 00  ....?...........
0012f9c8  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
0012f9d8  72 13 ff ff 00 01 ff ff - ff ff ff ff 02 74 40 00  r............t@.
0012f9e8  1b 00 3a 07 74 ba 29 01 - 23 00 ff ff 00 00 00 00  ..:.t.).#.......
0012f9f8  00 00 00 00 00 00 00 d4 - 01 d0 01 e8 00 80 34 40  ..............4@
0012fa08  00 d2 00 da 00 ca 00 de - 35 40 00 c8 00 e6 00 40  ........5@.....@
0012fa18  00 e8 35 40 00 e6 00 e8 - 00 c2 00 dc 35 40 00 cc  ..5@........5@..
0012fa28  00 de 00 ea 00 dc 35 40 - 00 de 00 ea 00 dc 00 c8  ......5@........
0012fa38  35 40 00 50 01 a0 01 94 - 01 80 34 40 00 00 00 00  5@.P......4@....

State Dump for Thread Id 0x3fc

eax=77d37dd0 ebx=00145560 ecx=0012dce8 edx=00000000 esi=00145400 edi=00000100
eip=77f88b37 esp=015bfe28 ebp=015bff74 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000206


function: ZwReplyWaitReceivePortEx
        77f88b2c b8ac000000       mov     eax,0xac
        77f88b31 8d542404         lea     edx,[esp+0x4]          ss:02049d0f=????????
        77f88b35 cd2e             int     2e
        77f88b37 c21400           ret     0x14
        77f88b3a 8bff             mov     edi,edi

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
015BFF74 77D58E4A 77D3AEED 00145400 77D50101 00130000 ntdll!ZwReplyWaitReceivePortEx
015BFFA8 77D37DE8 00144C38 015BFFEC 7C57B3BC 00145560 rpcrt4!TowerConstruct
015BFFB4 7C57B3BC 00145560 77D50101 00130000 00145560 rpcrt4!I_RpcConnectionInqSockBuffSize2
015BFFEC 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW

State Dump for Thread Id 0x2f8

eax=7ce20000 ebx=00000102 ecx=00147b28 edx=00000000 esi=77f88398 edi=016bff74
eip=77f883a3 esp=016bff60 ebp=016bff7c iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000206


function: NtDelayExecution
        77f88398 b832000000       mov     eax,0x32
        77f8839d 8d542404         lea     edx,[esp+0x4]          ss:02149e47=????????
        77f883a1 cd2e             int     2e
        77f883a3 c20800           ret     0x8
        77f883a6 8bff             mov     edi,edi

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
016BFF7C 7C59A2CC 0000EA60 00000000 7CE89ACC 0000EA60 ntdll!NtDelayExecution
00007530 00000000 00000000 00000000 00000000 00000000 kernel32!Sleep

*----> Raw Stack Dump <----*
016bff60  01 a3 59 7c 00 00 00 00 - 74 ff 6b 01 31 a0 59 7c  ..Y|....t.k.1.Y|
016bff70  28 7b 14 00 00 ba 3c dc - ff ff ff ff 30 75 00 00  ({....<.....0u..
016bff80  cc a2 59 7c 60 ea 00 00 - 00 00 00 00 cc 9a e8 7c  ..Y|`..........|
016bff90  60 ea 00 00 a7 5b e8 7c - 00 00 00 00 00 00 e2 7c  `....[.|.......|
016bffa0  28 7b 14 00 ec ff 6b 01 - 28 7b 14 00 ff 5a e8 7c  ({....k.({...Z.|
016bffb0  85 7d e3 7c 70 7d e3 7c - bc b3 57 7c 28 7b 14 00  .}.|p}.|..W|({..
016bffc0  85 7d e3 7c 70 7d e3 7c - 28 7b 14 00 00 c0 fd 7f  .}.|p}.|({......
016bffd0  62 00 64 00 c0 ff 6b 01 - 62 00 64 00 ff ff ff ff  b.d...k.b.d.....
016bffe0  60 21 5c 7c 08 2b 57 7c - 00 00 00 00 00 00 00 00  `!\|.+W|........
016bfff0  00 00 00 00 e5 5a e8 7c - 28 7b 14 00 00 00 00 00  .....Z.|({......
016c0000  c8 00 00 00 00 01 00 00 - ff ee ff ee 02 10 00 00  ................
016c0010  00 00 00 00 00 fe 00 00 - 00 00 10 00 00 20 00 00  ............. ..
016c0020  00 02 00 00 00 20 00 00 - 9e 01 00 00 ff ef fd 7f  ..... ..........
016c0030  06 00 08 06 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
016c0040  00 00 00 00 98 05 6c 01 - 0f 00 00 00 f8 ff ff ff  ......l.........
016c0050  50 00 6c 01 50 00 6c 01 - 40 06 6c 01 00 00 00 00  P.l.P.l.@.l.....
016c0060  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
016c0070  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
016c0080  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................
016c0090  00 00 00 00 00 00 00 00 - 00 00 00 00 00 00 00 00  ................

State Dump for Thread Id 0x41c

eax=778321fe ebx=00000003 ecx=0012f258 edx=00000000 esi=77f88ef8 edi=00000003
eip=77f88f03 esp=0182fd24 ebp=0182fd70 iopl=0         nv up ei pl zr na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=0038  gs=0000             efl=00000246


function: NtWaitForMultipleObjects
        77f88ef8 b8e9000000       mov     eax,0xe9
        77f88efd 8d542404         lea     edx,[esp+0x4]          ss:022b9c0b=????????
        77f88f01 cd2e             int     2e
        77f88f03 c21400           ret     0x14
        77f88f06 8bff             mov     edi,edi

*----> Stack Back Trace <----*

FramePtr ReturnAd Param#1  Param#2  Param#3  Param#4  Function Name
0182FD70 7C59A180 0182FD48 00000001 00000000 00000000 ntdll!NtWaitForMultipleObjects
0182FFB4 7C57B3BC 00000004 000B000A 7C3280D0 0016D3D0 kernel32!WaitForMultipleObjects
0182FFEC 00000000 00000000 00000000 00000000 00000000 kernel32!lstrcmpiW


Version 2.4 beta05 seems to work fine on vanilla XP SP3 (no POS hack).

Edit: 2.4beta05 crashes with the same report on my old W2K, too. Think it's end of the line and will keep using 2.3m.

Minimum OS is now Windows XP SP3!

2
Beta / Re: version 2.4
« on: May 26, 2020, 09:37:50 AM »
First results are in:

I couldn't get it to run on Windows 2000 SP4, so far. Have to check what the fresh system still lacks, in comparison to the established one that runs HFS fine. Maybe it is the IPv6 TP.

Important hint for Windows XP users:

On a standard Windows XP installation with SP3, HFS will start, no problem, but it will be disabled and unable to be put online. That's because a standard install is missing the IPv6 component.
Server will be permanently OFFLINE until you:
1. Open a command prompt,
2. issue a
Code: [Select]
netsh int ipv6 install command, and
3. reboot.

With activated IPv6, HFS will  be started and online.

3
Beta / Re: version 2.4
« on: May 26, 2020, 05:19:16 AM »
hi MarkV! win98? wow :D thanks for reporting.
I'm glad we are still ok with XP, since some people here still use it. I'll do my best without killing me tho. Time is short.

I hope you've seen the smileys. Just checked some old VMs and PCs and noticed. Personally, I'll start complaining when it stops working on Windows 7, OK? :)

Currently, Windows 2000 and up are still OK (last tested 2.4beta1). Please note that IPv6 support is an addon package for Windows 2000 and Windows XP. No idea how HFS will perform if the IPv6 package is not installed on these OS.
Might check it out. That's what we did in the old days, correct? ;)

4
Beta / Re: version 2.4
« on: May 24, 2020, 03:27:33 AM »
Hi,

thanks for the IPv6 support, think I was one of the folks bringing up the subject, some time ago.  ;) Great to see that there is still progress and the project alive.
Github repo is another nice addon, no need to search the whole forums for the one download you might have missed...  :)

However, there is no light without shadow, so I have to announce that the 2.4 versions of HFS finally, and officially, stopped working on Windows 98 SE!  ::)
Absolutely nothing needs to be done about this, it was inevitable. 2.3m works fine on 98SE, and it's amazing that it outlived the OS by many years.  8)
Just FYI, 2.4beta1 still runs fine on Windows 2000 SP4. :o

Gotta stop now, running out of smileys.  :P Keep up the good work and stay safe! Bye for now.

5
Beta / Re: version 2.4
« on: November 08, 2018, 10:37:16 PM »
Hi, just passing by, and I see you are all still busy. HFS has come a long way (I still remember the good old days when it started). No reason to stop it. :)

6
HFS ~ HTTP File Server / Re: New version: 2.3i
« on: June 15, 2016, 11:07:07 PM »
First time I've seen a warning message at update time. Unfortunately that very warning message blocks the auto-update that would have brought HFS up to date without much adoe!  ;)

Gratz for fixing that fast.

7
Although the topic is old, here's one addendum: Port 80/443 might also be blocked by the Skype application.

8
One problem is semantics here. You can technically run many applications on port 80 if you want, but you can't run more than one per socket. Network applications listen on sockets, not ports.

In Windows, you can apply multiple IPs to one NIC. So you can run one process per IP+port (=socket). If you apply IPs 192.168.0.10 and 192.168.0.11 to the NIC, you can run Apache on 192.168.0.10:80 and HFS on 192.168.0.11:80.

Sadly, there is one major blocking issue: Anyone behind a router can only forward each port once - to one dedicated target IP. Forwarding the same port to multiple IPs would be ambiguous.
So the Apache Forward/Reverse Proxy thing is still the best solution.

Disclaimer: IPv6 ought to solve all of this by restoring the network end-to-end principle.

9
Bug reports / Re: Zero filesize and Unauthorized
« on: March 18, 2016, 10:27:09 AM »
Little Addendum: Seeing a zero-Byte sized file in Explorer does not necessarily mean that the file doesn't have any contents or meaning.

1. Might be write-opened by any process. File size information might not be updated immediately.
2. The file's main data stream might be empty, indeed, but further data can also hide in Alternate Data Streams.
3. It may encode information through its attributes like timestamp or size, also its mere presence might be a switch (flagfile).

Just something to consider.

10
Bug reports / Re: [SOLVED] Uploading a MD5 file is forbidden?...
« on: March 18, 2016, 09:54:50 AM »
I'm reasonably sure it's in order to not allow uploading of fake MD5 files that would confuse users and might even hide dangerous malware.

Besides, MD5 is broken for a long time. HFS should change to SHA512.

11
HFS ~ HTTP File Server / Re: IPv6 not possible
« on: September 20, 2015, 07:55:33 PM »
For testing IPv6 in LAN:
- All adapters in Windows should have their respective fe80:: addresses already. One of the strengths of IPv6 - self configuration of at least the basic IP addresses.
- You can distribute ULAs (equvalent to LAN IPs in IPv4) via tools like dibbler or Jagornet. Use IPv6 addresses in the fd00::1 to fdff:ffff:ffff:ffff:ffff:ffff:ffff:ffff range.
- Many Routers can already distribute ULAs even if the ISP doesn't support IPv6, yet. So you can test in LAN without using one of the tools mentioned above.

Check IPv6 addresses:
Code: [Select]
netsh int ipv6 show addr or
Code: [Select]
ipconfig /all

12
HFS ~ HTTP File Server / Re: This page can’t be displayed
« on: September 20, 2015, 07:45:53 PM »
Also, some Network Cards and WiFi equipment might go into a "link down power save" mode after being idle.

Next possibility: The router at the server side does hang up the Internet connection after being idle for xx minutes. Note that, in case that happens, only connection attempts from the inside will cause the router to re-dial, connections from the outside will be dropped instead.

13
HFS ~ HTTP File Server / Re: This page can’t be displayed
« on: September 17, 2015, 11:46:58 PM »
Do you see anything logged, server-side, when the side appears to be offline? Could be a firewall blocking so the client doesn't even make it to the server.

14
HFS ~ HTTP File Server / Re: This page can’t be displayed
« on: September 17, 2015, 11:20:50 PM »
@bmartino1: Terayon is a "RAWR Designs" Template. Obviously, rejetto and TSG would be the right people to speak to.
http://www.rejetto.com/forum/rawr-designs/latest-releases/

@DigitaLWizarD: The VFS (Virtual File System) is the tree of resources people can access. It is stored as a *.vfs file. It can become corrupted so you were asked if you have a backup.

15
HFS ~ HTTP File Server / Re: IPv6 not possible
« on: September 15, 2015, 08:41:11 PM »
There is *much* more than just a difference in number of possible IPs. The restoration of the "end-to-end" principle, requiring no more NAT or port forwarding, for example. No requirement of DHCP due to automatic self-configuration of IP addresses, another one.

There's even the problem of transitioning technologies like DS-Lite. With DS-Lite, HFS users are out of luck since they won't get any public IPv4 address anymore, only an IPv6. That makes HFS unreachable in those environments.

Pages: [1] 2 3 ... 50