How to remove 72h limitation ?
#1
Posted 14 June 2011 - 08:51 AM
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
Posted 14 June 2011 - 11:32 AM
When I saw the topic title, I remembered my opinionI 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.
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
#3
Posted 14 June 2011 - 11:35 AM
It would be largely better if there were a built-in solution. And i think it's based on logon time.
#4
Posted 14 June 2011 - 04:03 PM
In theory the XP approach, of killing the monitoring processes should work in Win7 too. At least worth a try.
#5
Posted 15 June 2011 - 07:02 AM
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.
I've seen something like that, i.e killing smss.exe => BSoD ^^
#6
Posted 15 June 2011 - 08:29 AM
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/
Wonko
#7
Posted 15 June 2011 - 08:49 AM
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
Posted 15 June 2011 - 12:26 PM
I expect winlogon to be the guilty party in Win7 too. Question is which process protects winlogon.
#9
Posted 15 June 2011 - 12:30 PM
#10
Posted 15 June 2011 - 01:43 PM
And winlogin.exe is not killable.
I'm trying something else, i'll feedback if it works
Edited by neeko, 15 June 2011 - 01:44 PM.
#11
Posted 15 June 2011 - 01:57 PM
with BsExplorer as shell has just started (15:24) in my VirtualBox.
My vote: It will not reboot.
EDIT:
Test aborted june 16!
#12
Posted 15 June 2011 - 02:11 PM
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
Posted 15 June 2011 - 02:21 PM
Sorry, if it IS a fact, then I can stop this little test, ok?Let's see
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.
But, perhaps it was a PE1 with the limit = 24 hours you where talking about?
#14
Posted 15 June 2011 - 02:26 PM
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
Posted 15 June 2011 - 03:35 PM
smss needs to be killed before winlogon is killed, because else it will cause a(nother) reset, because it thinks winlogon has 'crashed'.In xp pe both smss.exe and winlogon.exe were killed.
In Win7 or in a Win7PE?And in Seven, killing smss.exe triggers a BSoD ^^
#16
Posted 15 June 2011 - 05:07 PM
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…
#17
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....
Maybe the (still talking of PE 1.x's) the /minint parameter passed to the kernel triggers *something* ....
Wonko
#18
Posted 16 June 2011 - 04:23 AM
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.
Attached Files
#19
Posted 16 June 2011 - 07:26 AM
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
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?
#21
Posted 16 June 2011 - 07:58 AM
But, why not try it ? ^^
#22
Posted 16 June 2011 - 09:12 AM
#23
Posted 16 June 2011 - 10:06 AM
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
#24
Posted 16 June 2011 - 10:08 AM
#25
Posted 16 June 2011 - 10:09 AM
@JoakimI 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.
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”?
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users