Results 1 to 40 of 1295

Thread: Getting the ball rolling. Which VB6 projects are you working on?

Hybrid View

  1. #1
    The Idiot
    Join Date
    Dec 2014
    Posts
    3,002

    Re: Getting the ball rolling. Which VB6 projects are you working on?

    yeah. its a problem.
    theres no 16bit emulator, instead we need to run it using a virtual machine.
    but a 32bit windows can run 16bit applications. and a 64bit windows can run 32bit
    when we get 128bit (or whatever next) maybe 32bit will be out or reach.
    so until than it will not be a problem to run 32bit.
    and the problems will just be some old ocx/dll that are not updated and obsolete.

    I have answered this many times in the past.
    when VB6 stop working, it will be the day, all 32bit will stop working. and that include everything made in 32bit. all the tools we have, theres TONS of that. its nothing microsoft just want to stop supporting.

    I hope by than, TB will be up and running for everybody where we can just update our projects to use 64bit.

  2. #2
    PowerPoster PlausiblyDamp's Avatar
    Join Date
    Dec 2016
    Location
    Pontypool, Wales
    Posts
    2,958

    Re: Getting the ball rolling. Which VB6 projects are you working on?

    Quote Originally Posted by baka View Post
    yeah. its a problem.
    theres no 16bit emulator, instead we need to run it using a virtual machine.
    but a 32bit windows can run 16bit applications. and a 64bit windows can run 32bit
    when we get 128bit (or whatever next) maybe 32bit will be out or reach.
    so until than it will not be a problem to run 32bit.
    At the moment there isn't likely to be a drive beyond 64-bit for a long time, moving from 16-bit to 32-bit was driven by the need to get away from the horrible segmented architecture of 16-bit apps only being able to access memory in 64K blocks (if you have never had to deal with code involving near / far pointers you have no idea how bad this could get)

    The move from 32-bit to 64-bit was driven by the need to remove the 4Gb Ram limit (effectively 2G or 3G usable by an app), 64-bit theoretically has a limit of around 16 exabytes (about 16 billion Gigabytes) so this isn't an immediate limit we are likely to hit.

    Sooner or later 32-bit will gradually fade away, I remember the initial move to 32-bit, 16-bit compatibility and support was a major consideration; these days it is almost never a consideration outside of some specialist areas. The same will happen to 32-bit software as 64-bit becomes more and more the norm.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  



Click Here to Expand Forum to Full Width