The V8i file format is not licensed to work with the current version of Windows 10.

I had had an email from a vender in the UK which reads as follows:

"As a Bentley user, you will be aware that Bentley Systems’ technical support for V8i versions of applications will discontinue after 31st December 2019.

The V8i file format is not licensed to work with the current version of Windows 10. Should there be a Windows 10 update V8i may no longer be compatible"

I understand that support is being stopped but that but assumed that the file format will not change and that files could be opened and edited in v8i and CONNECT. My version of v81 works on win10.

Please could someone confirm that this is to be the case.

  • The V8i file format is not licensed to work with the current version of Windows 10

    That's an absurd statement.  A file format is not licensed to work with a particular operating system.  An operating system is agnostic about the files it stores.

    You license an application, which uses files in one or more formats.  The data you create in those files is your intellectual property (IP).

    I assumed that the file format will not change

    Bentley Systems have made no statement about the file format changing.  They favour longevity over format changes, unlike some other software developers.  The V7 (IGDS) format was unchanged for three decades.  The V8 format is approaching the end of its second decade.  As you comment, it is compatible with MicroStation CONNECT and MicroStation V8i.

    I had an email from a vender in the UK

    I would ask to be removed from that vendor's mailing list.  If they write fake news or misinformation about another entity's IP, what other chicanery might they be perpetrating?

    Could someone confirm that this is to be the case?

    Go back to the source of that misinformation and ask them to write a letter of confirmation signed by a director of that vendor.  Otherwise, you're conceding to the source of that fake news that it's some other person or organisation that's responsible for its correction. 

     
    Regards, Jon Summers
    LA Solutions

  • It's complete nonsense. The file format is not changing. I got the same email. I think they got the office junior to write it.

  • @Stuart and Duncan 

    Could you provide the email you got from the vendor ?

    Ping me privately if you wish.

    Timothy Hickman

    CADD Manager | CADD Department

    timothy.hickman@colliersengineering.com

    Main: 877 627 3772| 

    1000 Waterview Drive Suite 201 | Hamilton, New Jersey 08691

  • Jut has this in from the vendor in question:

    Thank you for contacting us regarding the incorrect wording included in the email which was circulated with the subject line ‘Bentley Systems V8i Support is ending – five reasons to upgrade’.

    The email was sent on the 15th of October and this miswording was picked up shortly afterwards. We apologise for the confusion caused by this. A revised version of the email with the correct wording was sent on the 17th of October, however this was not issued to all recipients on the original mailing list.

    I realise that the wording in the original email may have caused some confusion and inconvenience - the paragraph ought to have read:

     

    What does this mean for me?

    From 31st December 2019, Bentley’s V8i Series generation products will no longer be supported (excluding SELECT Series 10). This does not affect the usage or licencing status of your existing products.

    However it does mean that updates, patches and user assistance will be discontinued and only available with CONNECT Edition, which is fully certified to work with Windows 10.

    For V8i SELECT Series 10 Applications, support will commence expiry on 31 December 2019 and discontinue on 31 December 2020. For all V8i SELECT Series prior to SS10 support discontinues as at 31 December 2019.


    Thank you again for bringing this to our attention. I will re-issue the updated version of email to all recipients, to ensure that everyone has the correct information.

    Please be assured that this was indeed a copy error, and we will be more cautious in future to avoid a repeat incident