| ID | 
Date | 
Author  | 
Topic | 
Subject | 
Text | 
  | 
| 
  318  
 | 
08 Jan 2007 | 
Stefan Ritt | Suggestion | Access to out_info from mana.c | I changed out_info into a global structure 
definition ANA_OUTPUT_INFO and put it into
 
midas.h, so it can be accessed easily from | 
   | 
| 
  320  
 | 
11 Jan 2007 | 
Stefan Ritt | Forum | Shared memory problems | > Hello,
 
> 
 
> Just did a fresh install of MIDAS from | 
   | 
| 
  322  
 | 
11 Jan 2007 | 
Stefan Ritt | Forum | Shared memory problems | That sounds like you mix versions: You have 
an old executable (maybe your mlogger) which
 
has been linked against the old midas version, | 
   | 
| 
  326  
 | 
22 Jan 2007 | 
Stefan Ritt | Bug Report | buffer bugs | [quote="Denis Bilenko"]1. Blocking calls to 
midas api aren't usable when client is connected 
through mserver. This is true at least for | 
   | 
| 
  328  
 | 
23 Jan 2007 | 
Stefan Ritt | Bug Report | buffer bugs | [quote="Denis Bilenko"]1 & 3 - thanks for 
the fix and the explanation, as for 2 - I've 
tried consume and produce
 | 
   | 
| 
  329  
 | 
24 Jan 2007 | 
Stefan Ritt | Bug Report | buffer bugs | I tried again and could [U]not[/U] reproduce 
the problem. Last time I was probably confused 
by some old mserver.exe executable I had | 
   | 
| 
  333  
 | 
30 Jan 2007 | 
Stefan Ritt | Bug Report | Large files under Windows XP | Hello,
 
 
We have problems analyzing large files under | 
   | 
| 
  339  
 | 
06 Feb 2007 | 
Stefan Ritt | Bug Report | wrong version in include/midas.h? | > The present .../include/midas.h contains
 
> [alpha@laddvme06 ~/online]$ grep 1.9.5 
/home/alpha/packages/midas/include/*
 | 
   | 
| 
  340  
 | 
06 Feb 2007 | 
Stefan Ritt | Bug Fix | Problem solved by Re-define _syscall0(...) | [quote="Exaos Lee"]Maybe it's not the perfect 
way, but it works. :-)[/quote]
 
 | 
   | 
| 
  341  
 | 
06 Feb 2007 | 
Stefan Ritt | Bug Report | segmentation violation of analyzer on a x86_64 | > Hello,
 
> 
 
> When I  connect to analyzer on a x86_64 | 
   | 
| 
  349  
 | 
26 Feb 2007 | 
Stefan Ritt | Info | RFC- history system improvements | I agree to what you propose. I'm pretty sure 
you are right in getting a significant improvement 
in readout speed
 | 
   | 
| 
  350  
 | 
26 Feb 2007 | 
Stefan Ritt | Info | RFC- support for writing to removable hard disk storage | In the MEG experiment, we simply installed 
100TB of RAID disks and don't need to change 
anything ;)
 | 
   | 
| 
  351  
 | 
26 Feb 2007 | 
Stefan Ritt | Info | Usage of event channel for improved throughput | Starting from SVN revision 3642, sending events 
from the front-end has been revised. 
 
 | 
   | 
| 
  352  
 | 
26 Feb 2007 | 
Stefan Ritt | Info | Fragmented polled events | Fragmented polled events have been implemented 
in SVN revision 3625.
 
Fragmentation is a method of breaking down | 
   | 
| 
  354  
 | 
27 Feb 2007 | 
Stefan Ritt | Forum | event builder scalability | > Hi there:
 
> I have a question if there's anybody out 
there running MIDAS with event builder
 | 
   | 
| 
  356  
 | 
27 Feb 2007 | 
Stefan Ritt | Forum | event builder scalability | > Our bottle neck is (a) compactPCI backplane 
reading data from waveform digitizers
 
> to the frontend CPUs and (b) CPU power | 
   | 
| 
  359  
 | 
03 Mar 2007 | 
Stefan Ritt | Forum | event builder scalability | > It seems that there's no problem running 
MIDAS with event builder assembling
 
> data from ~10 front-ends. How about ~100? | 
   | 
| 
  362  
 | 
15 Mar 2007 | 
Stefan Ritt | Info | mhdump: a standalone MIDAS history dump utility | > I hope people find this program useful. 
If you have any feedback (patches, bug
 
> reports, requests for improvements), please | 
   | 
| 
  365  
 | 
03 Apr 2007 | 
Stefan Ritt | Info | Switch to Visual C++ 2005 under Windows | I had to switch to Visual C++ 2005 under Windows. 
This required the upgrade of
 
all project files under \midas\nt\ and fixing | 
   | 
| 
  366  
 | 
03 Apr 2007 | 
Stefan Ritt | Bug Fix | SIGABT of "mlogger" and possible fix | [quote="Exaos Lee"]Version: svn 3658
 
Code: mlogger.c
 
Problem: After executation of "mlogger", | 
   |