RyanVM Forum

NFM's Website

Edited August 19, 200620 yr by nfm

Also, any mirrors would be greatly appreciated!

1.07b? that isn't even out yet, unless you're working with an internal beta.

1.06 is the latest.

Yes, you will have to wait for 1.0 b7 to come out, although it will actually be renamed to 1.0 RC1 when it is released. Kamil has been working with nuhi to add support for the x64 pack in upcoming nLite.

Unfortunately most plans are stalled until new nLite is released. Because current version has many problems with x64.

I am still waiting for that before I integrate the NFM update pack into my x64.

Thanks for keeping the pack updated Kamil, very good job so far.

There's new hotfix that was made available to the public today, http://support.microsoft.com/kb/907865

To download Link

This hotfix will be included in the next pack.

How often does the patches come out? When does the new Nlite come out or can that not be released at this time... I just built a new 64 machine....

Usually something comes once a month. You can always use manual integration, and about nLite as nuhi said, it will be out when it's done.

mirror

Here ya go peeps a nice mirror with no irritating ads

Edited October 2, 200520 yr by Anon5710

I am trying to integrate these packs into my win xp x64 pro corp.

1.

When I only integrate the updatepack everything seems to be going fine.

2.

However, when I try to integrate the update pack with addons I get a error message saying that: " Setup can not set the required Windows configuration information... " right after copying files is completed and gui part should start.

I am working as described above: clean install source using the script and afterwards using latest nlite 1.0b6(I believe) to disable the SFCOS.

I am testing this on VMWARE beta5.5 (support for x64guest OS) on AMD 64bit CPU equiped with win2k3 server x64.

I have tried everything: not using nlite at all, manualy editing txtsetup.sif etc..., nothing seems to work.

What I would like to know: is anybody using VMWARE in combination with these packs?

Hi @devilrunner

I'm afraid tha HIVCLS32.INF and HIVSFT32.INF get corrupted with nLite 1.06b. This does not happen with next version 1.0RC1, that was one I was beta testing. Right after integration of both pack and addon check HIVCLS32.INF and HIVSFT32.INF in amd64 dir to see if they're still ~300KB, nLite could wipe out all entries from it. If it did, recopy them from clean source. And yes I use the same version of Vmware.

This all could be fixed by just one file: hacked sfc_os.dll, but I had no success hacking it, that way nLite has to do this when addons used.

@Anon5710 Thanks for mirror!

EDIT: I confirm, this is a major 1.06b bug, either wait for 1.0RC1 or try to use 1.05b nLite.

Edited October 2, 200520 yr by Kamil

All x64 users should really wait for next nlite before making disks. There are just too many problems with the current version.

Yeps, i am waiting for the next version

Got any clue when that will be

(last time you said taht i would be there arround thursday )

@Kamil

So If I understand correctly;

A clean source with just your pack and the addons integrated with the script should just work fine as nlite isn't used then.

The only problem then is the SFC?

Why don't you just modipype your addon files so that windows doesn't b***h about it anymore?

Anyway gonna try that very soon

You got it right devilrunner,

I would like to include patched sfc_os.dll with my addon to disable WFP, but I didn't have success hacking that file, nobody till today hacked that file. There's one for WinXP SP2 but no for x64 . Just don't use addons for now, wait till nLite 1.0RC1 comes out. Or PM me and I will send you 1.0RC1 beta so everything will work.

Right now I need your help to hack sfc_os.dll for x64!

Edited October 2, 200520 yr by Kamil

Yeps, i am waiting for the next version

Got any clue when that will be

(last time you said taht i would be there arround thursday )

<{POST_SNAPBACK}>

I said it could be released then at the earliest.

Nuhi said recently that it will be out tomorrow or the next day probably.