Reboot loop just before login.

Thank you for the feedback, Tournicoti. If you compare the files against the other secondary that's working, are they the same?

Are there any entries in the Event Viewer that indicate if it's the MP service blowing out? You may need to go into safe mode on the secondary to see that and/or rename the directory if appropriate to prevent the service loading.

Is there any apparent difference installing using the standalone installer?

Kris

I have no idea how to get the 1.21.017 stand alone installer.

I presume they are the same files , though right clicking on the exe and checking version information tells me it's 1.2.1.0 on all computers .. impulse confirms the installs as being .017 and needing no upgrade.

A way to get out of the loop is to start up in vga mode ( i know it's strange) ive repeated this with the nvidia beta drivers and the whq drivers and an older driver i had on the install cd , the same each time , after install , the computer boots and reboots infinately , untill i start up in vga mode (not safe mode )
This makes me think it could be your screen switch routine that has some issues maybe.

Anyway , after i start up in vga mode , and check services , the service doesn't even seem to have installed itself. i check the services list and it's not listed in there.

When i check listening ports , nothing is listening on 30564 either .

When I uninstall , and install a plain 1.21 , i get a listening port on 30564 after install and no infinite reboot loop.

so , if i can get the 1.21.017 stand alone installer I'll do the whole thing over again and reply with what it did.

in the end , i still can't use that computer with multiplicity with whatever version i install now , since i upgraded to 017 on that computer , and downgraded back to 1.21 , every time i move my mouse to that screen , it disconnects instantly.

Tournicoti.

Also . in can you set the system not to reboot after it bluescreens so that we can see the stop error?

There are no BSOD's

It reboots right after the blue login screen appears , you know , the one with the icon , the name , and the editbox to type in your password..

The service just isn't there after install.

No entries related to multiplicity in event viewer.



If I don't have a solution in 2 or 3 days , I'll install a virgin windows on that computer and see what gives from that .

I just had this using 1.21.017 afaik
Very bad indeed.   
I have XP64 with SP2 and all up to date windows update.

Just installed today.
Could net get Multiplicity working
Installed Stardock Central
Installed upate Stardock Central
Installed update Multiplicity with StarDock central.
Reboot
Nolonger boots as describer by initial post.

Not sure if it was StarDock central or Multiplicity.
Uninstalled both, waiting on feedback.

Also:
Nothing in the eventlog relating to Stardock programs.

Tournicoti

Any success?
I am affraid to try again because that machine is a server.
Having it hang on boot is sort of deadly.
What a drag, i just bought multiplicity and now this. :/
Switched back to Synergy for the time being but it does not have file copy, wich i realy want.

What Sever OS is on the secondary and what version of Multi Pro are you currently running?

1.21.017

XP64bit is the secondary.
Win2k3 is the primary.

Although the secundairy won't boot properly when it has 1.21.017 on it.
Installed programs are many, however the previous version of Multiplicity (The 1st 1 i downloaded and installed it did boot/login fine).

That machine, the XP64 one, does have autologin enabled though.
Perhaps that's causing a problem?

That would be my guess. As an experiment reverse the roles of the comptuers with primary and secondary. The trouble here is that XP64 is no longer supported and I am wondering if the latest update is any reflection of that. Are you currently SP3?

That's not so nice, i just bought multiplicity pro about a week ago and yet have to see it working on my setup. The normal Multiplicity trial version i used worked ok.

There is no SP3 for XP64 out yet.

I already tried the reversal, it did not help. It apppears to be something multiplicity pro does to the login or just before the login dialog is shown.

Where can i download older version of multiplicity pro that did work on xp64?

Just tried with the AutoAdminLogin set to 0. (So no auto login)
And it still hangs at the blue (not BSOD!!!) screen and the login prompt never appears.
As described in the initial posters comments.

It (multiplicity pro) apparently causes winogon.exe to crash.


Event Type: Error
Event Source: VsJITDebugger
Event Category: None
Event ID: 4096
Date: 30/05/2008
Time: 18:35:50
User: NT AUTHORITY\SYSTEM
Computer: 64BIT
Description:
An unhandled win32 exception occurred in winlogon.exe [408]. Just-In-Time debugging this exception failed with the following error: Debugger could not be started because no user is logged on.

Check the documentation index for 'Just-in-time debugging, errors

Caused by:
C:\Program Files (x86)\Stardock\ThinkDesk\Multiplicity\multiwin64.dll

If i remove that notify entry from WinLogon section in registry it boots fine.
Si it's that specific DLL that apparently misbehaves inside an XP64 environment.
Ironically called 'MultiWin'

i 'fixed' it by replacing the multiwin64.dll reference to multiwin32.dll in the winlogin notify DllName.

Seems like multiwin32 is more multiwin than multiwin64.

Monk-E, great info!

Your answers save my, I've not associated the reboot loop with multiplicity, but now everything make senses.
After search a little in regedit, I found the registry info you told and changeÇ voilá! restart is fine now.

No more support for XP64 are very bad news... maybe is time to try Input Director, if confirm that are no more support for XP 64.

Sorry for my English, I'm trying to write better....