rejetto forum

Software => HFS ~ HTTP File Server => Bug reports => Topic started by: Heps on July 12, 2008, 10:42:39 PM

Title: HFS 2.3 beta (190)
Post by: Heps on July 12, 2008, 10:42:39 PM
EXCEPTION REPORT:

Cannot open clipboard
HFS 2.3 beta (190)
----------------------------------------------------------------
System   : Windows XP Professional, Version: 5.1, Build: A28, "Dodatek Service Pack 2"
Processor: AMD, AMD Athlon(tm) 64 Processor 3200+, 2020 MHz MMX
Display  : 1280x800 pixels, 16 bpp
----------------------------------------------------------------
----------------------------------------------------------------
Product Versions

Autorun.exe: Build: 0 2000-12-24 21:24:06
FoxitReader.exe:1.3.0 Build: 1621 2006-04-21 17:43:10
hfs.exe: Build: 0 2008-07-12 21:55:20
Power Defragmenter.exe:6.0.1 Build: 4 2005-02-16 16:40:36
Title: Re: HFS 2.3 beta (190)
Post by: rejetto on July 13, 2008, 01:31:37 AM
can you tell me what was you doing when the error came up?
or, are you able to reproduce the problem?
Title: Re: HFS 2.3 beta (190)
Post by: opal on July 14, 2008, 05:21:33 AM
Same problem here. I'm doing nothing, this message keeps pop up. This only happens after upgrade to 190.

Cannot open clipboard
HFS 2.3 beta (190)
----------------------------------------------------------------
System   : Windows Server 2003 Enterprise, Version: 5.2, Build: ECE, "Service Pack 2"
Processor: Intel,               Intel(R) Pentium(R) 4 CPU 2.40GHz, 2350 MHz MMX
Display  : 1024x768 pixels, 16 bpp
----------------------------------------------------------------
----------------------------------------------------------------
Product Versions

hfs.exe: Build: 0 2008-7-13 0:45:00
Title: Re: HFS 2.3 beta (190)
Post by: TSG on July 14, 2008, 02:56:12 PM
http://www.rejetto.com/forum/index.php?topic=6005.msg1035667#msg1035667

Can you please not post Beta bugs in the Bug reports board, post them with the beta, so rejetto can easily track the bugs for the next build.
Title: Re: HFS 2.3 beta (190)
Post by: rejetto on July 14, 2008, 03:17:24 PM
this should be fixed in 191 (coming soon)