Creo M090 don't start

Hmmm. Maybe try going to the control panel to do a full uninstall, then
a clean re-install. This should force M090 to recognize your installed
video card and default display.

Also, you mentioned, "when I get back to work again..."
Maybe this is not a graphics/screen problem at all... Could this be a
licensing or adapter problem? (wired vs wireless) Are you "borrowing"
licenses from a server? I have seen Creo2 do strange things on laptops
while traveling with borrowed licenses. (WF4 worked every time... Creo2
seems a little flaky)
There is also an issue with Win7 window "focus" that won't always pop the
active window to the front... This seems to also play a part in a
successful Creo2 Launch.

I would work with your IT person on this.
Good Luck
Bernie


On Mon, Mar 3, 2014 at 9:59 AM, Sivert Wernblad <
-> wrote:

> L no luck,I hope it works as normal in the doc, when I get back to work
> again.
>
>
>
> Best regards / Med venlig hilsen
>
> Sivert Wernblad
> *Sennheiser Communications A/S*
> Direct +45 5618 0081
>
>
>
> *From:* Bernie Gruman [
> local screen, then when you connect to the dock later the M4600 should
> know how to manage that for you.
>
>
>
> Good Luck
>
> Bernie
>
>
>
> Bernie Gruman
>
> Owner / Design / Builder
>
> www.GrumanCreations.com
>
>
>
>
>
>
>
>

I doubt this has anything to do with the screen. It's a laptop correct? It's a licensing problem, and it's likely caused by how windows handles the Network Card on laptops.
There are two potential problems

1. Media sensing <-- fix this first, you may not need to adjust the card order in number 2.

2. Network card order

Media Sensing
===========
Solution Details - TPI 103538
Created Date 07-Jul-2000
Last Updated 29-Dec-2009


Title
When Not Connected to a Network, Windows Machines May Return "HostID" Errors ( -96, -15, -9) for Pro/ ENGINEER and the FLEXnet License Server Due to the Windows Media Sensing Feature.

Description
When disconnected from a network Windows machines may disable certain network cards resulting in licensing errors from Pro/ENGINEER and the PTC License Server.

Pro/ENGINEER may return
error: "(-96) License server host is down or not responding" or error: "(-15) Cannot connect to license server system" if configured to a license server
or
error: "License request failed for feature PROE_Foundation: -9: Invalid host." if configured to a locked license.

FLEXnet License Server error log may contain messages similar to the following:

Error: Wrong hostid on SERVER line for license file: <flexnet loadpoint=">\licensing\license.dat
SERVER line says PTC_HOSTID=00-11-22-AA-BB-CC, hostid is PTC_HOSTID=00-AA-11-BB-22-CC

Resolution
This issue is related to the 'media sensing' feature of Windows 2000 and later (including XP and Vista) and disabling this 'media sensing' feature will resolve the issue.

For more information on 'media sensing' see

2. Locate the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

3. Add the following registry entry to the Parameters subkey:
Name: DisableDHCPMediaSense
Data type: REG_DWORD (Boolean)
Value: 1

Note This entry controls the behavior of Media Sensing. By default, Media Sensing events trigger a DHCP client to take an action. For example, when a connect event occurs, the client tries to obtain a lease. When a disconnect event occurs, the client may invalidate the interface and routes. If you set this value data to 1, DHCP clients and non-DHCP clients ignore Media Sensing events.

4. Restart the computer.
Additional Information

***WARNING: PTC will not be responsible for damage done to a computer by incorrectly editing the registry. Using Registry Editor incorrectly can cause serious problems that may necessitate a re-installation of the operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it and also create an Emergency Repair Disk.
Related Links

See also TPI 147361: