Re: Vista Kicking my Buttocks...Weird problems

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance


"connieharper" <guest@xxxxxxxxxxxxxxxxx> wrote in message news:e726996f6ee0eeab6fe70abb44eafe8e@xxxxxxxxxxxxxxxxxxx

For the love of God! So, Vista gets to make a "silent" decision about
what version of my file it decides to open and is allowed to ignore me
when I rename or move files to another location all because of it's
desire to enhance security? I feel sick! What about enhancing security
by sending computer hackers and those who create viruses to prison
instead.? I am mad and I am not going to take it anymore!

You had better figure out what is going on.

<http://www.securitypronews.com/news/securitynews/spn-45-20060601ASLRJoinsVistasBagOfTricks.html>
<http://technet.microsoft.com/en-us/magazine/cc162458.aspx>

Address Space Load Randomization

Despite measures like Data Execution Prevention and enhanced compiler
error checking, malware authors continue to find buffer overflow
vulnerabilities that allow them to infect network-facing processes like
Internet Explorer®, Windows services, and third-party applications to
gain a foothold on a system. Once they have managed to infect a process,
however, they must use Windows APIs to accomplish their ultimate goal of
reading user data or establishing a permanent presence by modifying user
or system configuration settings.

Connecting an application with API entry points exported by DLLs is
something usually handled by the operating system loader, but these
types of malware infection don't get the benefit of the loader's
services. This hasn't posed a problem for malware on previous versions
of Windows because for any given Windows release, system executable
images and DLLs always load at the same location, allowing malware to
assume that APIs reside at fixed addresses.

The Windows Vista Address Space Load Randomization (ASLR) feature makes
it impossible for malware to know where APIs are located by loading
system DLLs and executables at a different location every time the
system boots. Early in the boot process, the Memory Manager picks a
random DLL image-load bias from one of 256 64KB-aligned addresses in the
16MB region at the top of the user-mode address space. As DLLs that have
the new dynamic-relocation flag in their image header load into a
process, the Memory Manager packs them into memory starting at the
image-load bias address and working its way down.


I have 300 customers many of which are moving to Vista. I think I am
going to redesign my app to run on the web. What a sad state our
technology is in....

You didn't do your home work, and you didn't do any testing it seems on the Vista platform to ensure that yiur solution worked.

http://www.developer.com/net/net/article.php/3695651


Thank you for explaining the problem though. At least I know what's
going on now. It doesn't make me any happier though. I thought I was
losing my mind. So basically, I need to throw out everything I know
about computers and start all over again. Nice. Thanks Microsoft.

I wouldn't say toss out everything. But you do need to re-tool, and you should start looking at things with a different mindset, as a software developer.


P.S. How do I disable Vista's "virtualization process" or remove this
virtual store directory? I don't want vista to "silently redirect my
application" to anywhere.

You can't possibly think that you will be the only software solutions developer developing solutions to run on the Vista platform do you? What about other solutions running on the platform, used by your clients?

As a software developer, you need to understand what is happening to program viable solutions for Vista.

<http://technet.microsoft.com/en-us/library/cc709691.aspx>
<http://news.softpedia.com/news/Admin-Approval-Mode-in-Windows-Vista-45312.shtml>
<http://technet.microsoft.com/en-us/magazine/cc138019.aspx>
<http://technet.microsoft.com/en-us/magazine/cc160882.aspx>
<http://msdn.microsoft.com/en-us/library/aa382503.aspx>

You might be real interested in these links too, as a software developer.

<http://msdn.microsoft.com/en-us/library/aa382503.aspx>
<http://msdn.microsoft.com/en-us/library/aa382530(VS.85).aspx>
<http://www.computerperformance.co.uk/vista/vista_administrator_activate.htm#Summary_of_Vista_Administrator_-_Super_User_(Hidden_Account)>
<http://www.howtogeek.com/howto/windows-vista/enable-the-hidden-administrator-account-on-windows-vista/>


I am not MS. :-P



.

Relevant Pages

  • Re: Adding a reference to a COM in VS2008
    ... You know there are many features Vista has that are not know from a software developer's or computer user's standpoint on how Vista is protecting the O/S like Virtualization being one. ... For my own personal computer usage, I'll never go back to XP, and I await to see what else is being implemented in Windows 7. ... Connecting an application with API entry points exported by DLLs is something usually handled by the operating system loader, but these types of malware infection don't get the benefit of the loader's services. ... This hasn't posed a problem for malware on previous versions of Windows because for any given Windows release, system executable images and DLLs always load at the same location, allowing malware to assume that APIs reside at fixed addresses. ...
    (microsoft.public.dotnet.general)
  • Re: Application not working on other PCs
    ... I've created an application (.exe) using VC++ 2005 on my Windows Vista ... If you have a problem needing DLLs that are not part of older Windows versions then you need to build an install package that installs the DLLs. ...
    (microsoft.public.vc.language)
  • Re: Need to understand permissions and ownership
    ... I don't see Vista users posting about malware issues that much anymore as compared to the previous version on the NT based O/Swhere malware is hammering those O/S. ... Despite measures like Data Execution Prevention and enhanced compiler error checking, malware authors continue to find buffer overflow vulnerabilities that allow them to infect network-facing processes like Internet Explorer®, Windows services, and third-party applications to gain a foothold on a system. ... Connecting an application with API entry points exported by DLLs is something usually handled by the operating system loader, but these types of malware infection don't get the benefit of the loader's services. ...
    (microsoft.public.windows.vista.general)
  • XP program crashes on startup on Vista
    ... I am a software developer with my own software product. ... The program works perfectly on Windows XP but I am told it crashes ... I don't have Vista so I can't debug this. ... I compiled it using MSVC++ 6.0 on Windows XP on which it works fine. ...
    (microsoft.public.windows.vista.general)
  • Re: VB.6 Compatibility with Windows 7
    ... Based that your app works on Vista and Windows 7 is based on Vista I would expect it to work. ... Of the dlls you list in the only one I would be possibly concerned with would be the use of ieframe.dll. ...
    (microsoft.public.vb.general.discussion)