Jump to content











Photo
- - - - -

How to remove 72h limitation ?


  • Please log in to reply
98 replies to this topic

#1 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 14 June 2011 - 08:51 AM

I know, i ask a lot of questions. I promise to disappear in 2 weeks ^^

So, i'd like to remove the 24-hour limitation, because of PXE's clients which can run while many hours (data recovery is a long process sometimes ^^).

I've found that topic, but it's for LiveXP and it doesn't really help me.

#2 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 14 June 2011 - 11:32 AM

I know, i ask a lot of questions. I promise to disappear in 2 weeks ^^

So, i'd like to remove the 24-hour limitation, because of PXE's clients which can run while many hours (data recovery is a long process sometimes ^^).

I've found that topic, but it's for LiveXP and it doesn't really help me.

When I saw the topic title, I remembered my opinion

A PE is not an OS clone, it is a minimized OS imitation to allow several actions.


But your "recovery" aspect is reality!

Just a crazy idea:

When your PE is up, use the date command to change the date some days back.

This should work when the 24h-limitation is based on logon time.
It does not work when the limitation is based on ticks since logon.
I do not know ...

That's only an idea and I cannot test, because I need my system (and also the emulator) and cannot block it for one day.

But when you need the functionality, perhaps you have a separate system to try ...

I would be glad if tomorrow afternoon the result appears here ...

Peter :cheers:

#3 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 14 June 2011 - 11:35 AM

I've searched in registry, i've found nothing.

It would be largely better if there were a built-in solution. And i think it's based on logon time.

#4 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 14 June 2011 - 04:03 PM

When it works in Win7, like it does in XP, then the time, till reboot, is set in milliseconds in, i think, winlogon.exe.
In theory the XP approach, of killing the monitoring processes should work in Win7 too. At least worth a try.

:cheers:

#5 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 07:02 AM

@allanf : btw, it still is not enough.

When it works in Win7, like it does in XP, then the time, till reboot, is set in milliseconds in, i think, winlogon.exe.
In theory the XP approach, of killing the monitoring processes should work in Win7 too. At least worth a try.

:thumbsup:


I've seen something like that, i.e killing smss.exe => BSoD ^^

#6 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15106 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 June 2011 - 08:29 AM

In PE 2.x and 3.x the limit is 72 hours (and not 24 hours as in PE 1.x).

Whilst there are solutions/workarounds for PE 1.x, there are none for pe 2.x/3.x AFAIK.

The only (vague) positive report I know of is here:
http://www.msfn.org/...-72-hour-limit/

Old thread about the matter:
http://reboot.pro/7646/

:thumbsup:
Wonko

#7 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 08:49 AM

Yeah, i've already seen the msfn's post.

Does anyone know how that behaviour is set ? I mean, which processus takes the decision to reboot the computer ? winlogon, like in PE 1 ?

#8 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 15 June 2011 - 12:26 PM

In XP it was winlogon, i'm pretty sure. But i can't find the explained patch online. Maybe our Finder can. :cheers:

I expect winlogon to be the guilty party in Win7 too. Question is which process protects winlogon.

:cheers:

#9 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 15 June 2011 - 12:30 PM

In xp pe both smss.exe and winlogon.exe were killed. In addition the desktop was switched to the "default" desktop.

#10 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 01:43 PM

And in Seven, killing smss.exe triggers a BSoD ^^

And winlogin.exe is not killable.

I'm trying something else, i'll feedback if it works :cheers:

Edited by neeko, 15 June 2011 - 01:44 PM.


#11 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 15 June 2011 - 01:57 PM

As I’m curious concerning the 72 hours limit, a win7pe
with BsExplorer as shell has just started (15:24) in my VirtualBox.
Will report here on Saturday afternoon.
My vote: It will not reboot.

EDIT:
Test aborted june 16!

#12 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 02:11 PM

Let's see :cheers:

However, it's a fact : we were working on something when, the day after, we've seen that the PC had rebooted. It did it twice.

So, that's reality, for us anyway.

#13 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 15 June 2011 - 02:21 PM

Let's see :cheers:

However, it's a fact : we were working on something when, the day after, we've seen that the PC had rebooted. It did it twice.

So, that's reality, for us anyway.

Sorry, if it IS a fact, then I can stop this little test, ok?
But, perhaps it was a PE1 with the limit = 24 hours you where talking about?
:cheers:

#14 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 15 June 2011 - 02:26 PM

I thought it was 24h, but appearently, it is 72.

I didn't see it by myself, it's a tech guy who tell it to me. I don't know exactly the PC's uptime.

#15 MedEvil

MedEvil

    Platinum Member

  • .script developer
  • 7771 posts

Posted 15 June 2011 - 03:35 PM

In xp pe both smss.exe and winlogon.exe were killed.

smss needs to be killed before winlogon is killed, because else it will cause a(nother) reset, because it thinks winlogon has 'crashed'.

And in Seven, killing smss.exe triggers a BSoD ^^

In Win7 or in a Win7PE?

:cheers:

#16 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 15 June 2011 - 05:07 PM

Just thinking ”loud”:
If all the files in the Win7PE are coming from the Win7 installation
DVD and not from the Waik; How can there be a 72h limit?
Probably thinking “wrong” as usual and will be quiet until tomorrow…
:cheers:

#17 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15106 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 15 June 2011 - 05:16 PM

Just thinking ”loud”:
If all the files in the Win7PE are coming from the Win7 installation
DVD and not from the Waik; How can there be a 72h limit?


I guess the same way that in PE 1.x all the files come from an actual XP and NOT from a WAIK.... :cheers: :)

Maybe the (still talking of PE 1.x's) the /minint parameter passed to the kernel triggers *something* .... ;)

:cheers:
Wonko

#18 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 16 June 2011 - 04:23 AM

Ok, still thinking “loud”:
If there really is that limit (still in doubt) it must be registry related, correct?
If yes, what about this key: “dolicenseconsume”? It’s “0” right now.
:smiling9:

Attached Files



#19 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 16 June 2011 - 07:26 AM

I was thinking the same thing than you, al_jo.

I have no idea where this limitation comes from. And i've looked for the file / value / wtf where that limit is registered.

I'm gonna take a look in the registry.

Edit : well, i also have 0 as value of this key. So i don't think it is that.


@MediEvil : killing smss triggers BSoD in Win7PE.

Edited by neeko, 16 June 2011 - 07:34 AM.


#20 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 16 June 2011 - 07:54 AM

Edit : well, i also have 0 as value of this key. So i don't think it is that.


This is what I was thinking: If changing that key to “1” , what will happen?
:smiling9:

#21 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 16 June 2011 - 07:58 AM

According to the key's name, i would say that the value 0 would disabled licence.

But, why not try it ? ^^

#22 joakim

joakim

    Silver Member

  • Team Reboot
  • 912 posts
  • Location:Bergen
  •  
    Norway

Posted 16 June 2011 - 09:12 AM

I have my doubts it is as easy as a registry tweak. I believe 1 or more executables need to be patched, but do not have any time at the moment to attempt locating the "bug" with debugging.

#23 neeko

neeko

    Frequent Member

  • Advanced user
  • 112 posts
  •  
    France

Posted 16 June 2011 - 10:06 AM

It doesn't work.

But, i've found a solution. Re-but : that solution requires .NET 4.0, and yet i only have a .NET 3 script. If anyone has a working .NET 4 script, i'll post my solution :smiling9:

#24 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 16 June 2011 - 10:08 AM

Sorry, double posts.

#25 al_jo

al_jo

    Gold Member

  • Members
  • 1218 posts
  • Location:Tellus

Posted 16 June 2011 - 10:09 AM

I have my doubts it is as easy as a registry tweak. I believe 1 or more executables need to be patched, but do not have any time at the moment to attempt locating the "bug" with debugging.

@Joakim
What about the 30 days limit in win7?
Isn’t that easy to extend even to 360 days without
“patching” any .exe files, just doing some “tweaks”?
:smiling9:




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users