[BLACKBOX] FW: [BLACKBOX] Windows 7

From: [at]} <Marc>
Date: Wed, 29 Aug 2012 19:22:32 +0000

For folks willing to help testing the corrections mentioned in my last mail, I herewith forward the patch we previously sent out to Robert.

Thank you very much in advance,

Marc

-----Original Message-----
From: Blackbox Support Oberon microsystems AG
Sent: Mittwoch, 22. August 2012 12:01
To: robert.d.campbell{([at]})nowhere.xy
Subject: RE: [BLACKBOX] Windows 7

Dear Robert,

finally, we have a patch ready that should fix critical errors in several cases of memory allocations that led to integer overflows in the kernel and compiler. We still cannot entirely explain the differences between 32-bit Windows XP and 64-bit Windows 7 you have been observing but it would be very valuable if you could try this patch with your software on your system:

- Please download and install a fresh copy of BlackBox 1.6-rc6 from

  
http://www.oberon.ch/zip/SetupBlackBox16-rc6.exe

- Apply the StdCoder encoded text in the attachment.

- Link a new version of BlackBox with the following command

DevLinker.Link BlackBox2.exe := Kernel$+ Files HostFiles StdLoader
1 Applogo.ico 2 Doclogo.ico 3 SFLogo.ico 4 CFLogo.ico 5 DtyLogo.ico 6 folderimg.ico 7 openimg.ico 8 leafimg.ico 1 Move.cur 2 Copy.cur 3 Link.cur 4 Pick.cur 5 Stop.cur 6 Hand.cur 7 Table.cur

- Quit BlackBox, delete the old BlackBox.exe and rename BlackBox2.exe to BlackBox.exe.

- Start the new BlackBox.exe and recompile all your modules. It is possible that you will encounter new compiler errors in cases of memory allocations with statically detectable integer overflows.

- Test your recompiled modules. It is possible that you will encounter memory allocations that return NIL pointers in cases where there is not enough memory available but there should be no low-level traps in the module Kernel anymore. You should handle the out of memory situations indicated by NIL pointers returned from NEW in your application code. (BlackBox cannot allocate more than a total of approximately 1.5GB of heap memory.)

Thank you very much for your help and kind regards,
Marc
 

> -----Original Message-----
> From: BlackBox [mailto:BLACKBOX{([at]})nowhere.xy
> Campbell, Robert (SELEX GALILEO, UK)
> Sent: Montag, 6. August 2012 13:14
> To: BLACKBOX{([at]})nowhere.xy
> Subject: [BLACKBOX] Windows 7
>
> Hello
>
> We are migrating our computers to Windows 7.
>
> I have previously run a few simple BlackBox test programs,
> and not seen any problems.
>
> Today we ran a real application for the first time, and are
> swamped by hundreds of low-level TRAP windows

> (the ones without clickable links) complaining of illegal
> memory accesses. This happens every time. The
> application is about 10 years old, and has always been

> stable. It is not particularly memory or CPU greedy.
> I don't think it does any risky 'low-level' things, but it
> will possibly have some WinApi calls.
>
> The entire BlackBox directory is an exact copy of one that
> runs reliably on XP machines.
>
>
> Have other people had similar problems? Is there something
> like a Windows 7 'compatibility' mode I should
> know about?
>
>
> Regards
>
> Robert
>
> SELEX Galileo Ltd
> Registered Office: Sigma House, Christopher Martin Road,
> Basildon, Essex SS14 3EL
> A company registered in England & Wales. Company no. 02426132
> ********************************************************************
> This email and any attachments are confidential to the intended
> recipient and may also be privileged. If you are not the intended
> recipient please delete it from your system and notify the sender.
> You should not copy it or use it for any purpose nor disclose or
> distribute its contents to any other person.
> ********************************************************************


----
To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy




Received on Wed Aug 29 2012 - 21:22:32 UTC

This archive was generated by hypermail 2.3.0 : Thu Sep 26 2013 - 06:29:58 UTC