[bledd]

mcfly


..

Supported Vista version is minimum Build 5744 (RC2) and newer, RTM build 6000 recommended and it will be only one supported from the next version, you can run it on older on your own risk

[dexter.inside]

Supports Codename Longhorn Server 5600 too... I got Enterprise Core down to 409 Mb, practically equivalent to having Windows PE 2.0 installed.

I really like the way user accounts are handled in it, I always go for Administrator.

nuhi, what program are you using to diff between registry data? I really could use a good one. I think the "Core" builds are the solution to my Vista problems. I have a lot of C# code tryouts to handle the builds, I'll see if I can get them altogether into a working application.

Up to this point, I think I got the general idea how Microsoft originally has put together all that stuff that makes Vista what it is... I was thinking to develop something that can complement the functionality of vLite, like auto comparison between different builds and add/remove/migrate stuff. Maybe the equivalent of BartPE for the stuff in boot.wim, who knows what might come up of this?

Quick hint: look at the bitmap resources in msgina.dll, they are quite intriguing...

This post has been edited by dexter.inside: 14 December 2006 - 05:48 AM

[Mcfly000]

ok so if the people are going to laugh every time i make a post becuse i speak bad english and its really hard to me write in english when im ASKING FOR HELP , i do better dont post any more , and i dont have anoy photo of the error , becuse it took me by SUPRISE and IM NOT A REVEERSE INGENEER COMPUTER EXPERT THAT KNOW ALL THE ERRORS A PROGRAM CAN DO and im not going to MAKE IT AGAIN TO GET THE SAME ERROR to make a photo BECUSE IT TAKE ABOUT 1 HOUR TO REBULD the iso


.... thanks and good bye

[3aces]

Mcfly000, on Dec 14 2006, 12:56 PM, said:

ok so if the people are going to laugh every time i make a post becuse i speak bad english and its really hard to me write in english when im ASKING FOR HELP , i do better dont post any more , and i dont have anoy photo of the error , becuse it took me by SUPRISE and IM NOT A REVEERSE INGENEER COMPUTER EXPERT THAT KNOW ALL THE ERRORS A PROGRAM CAN DO and im not going to MAKE IT AGAIN TO GET THE SAME ERROR to make a photo BECUSE IT TAKE ABOUT 1 HOUR TO REBULD the iso


.... thanks and good bye

relax mate....we are all tryin to help.......

[nuhi]

Jeremy, are you serious?

Mcfly000, thx for trying better but that "tipical mesaage registry error report" is the thing which is like solution to me. What is it the exact error message? Maybe you could try apply method 1, it could work, only thing different is larger ISO.

3aces, again you with WLM Ok I'll try it...I would do it sooner if anyone else confirmed it. Thx

dexter.inside, I have no intentions of making tutorial how to mimic vLite. Worked on it for months until I got it. Call me selfish but that's how it is.
Way as the vLite develops seems perfect to me, I don't see the point in removing all at once, that would have so much bugs that no one would be able to keep track of.
Gonna check that dll but I'm not that keen on changing pics to prove control.
And sorry for my tone in case you don't like this direct approach.


edit: oh I see you p***ed the Mcfly000...note to self: less jokes.

[Mcfly000]

Jeronimo, on Dec 14 2006, 03:02 AM, said:

@Mcfly000
Without knowing the exact error, there is no link to start and help you. If you do not know how to create and post a screenshort, tehn with all due respect I do not know what you are doing here in this beta-section (some computer skills can be expected). Only Idea I have is that you might overclocked your pc and that 0.6 worked by coïncidence or it was less stressful on hadware and performance of the whole operation has been improved. Then you can get strange errors, but without the exact error, there is really nothing to say about it.

and what are you doing here ????

ok nuhi thank's for your help , i try to make a photo the next time and some more facts about the error

[3aces]

but seriosuly nuhi....i cannot be the only person having this error....i mean.....80% of people with windows use office and WLM, so unless my computer is at fault with i higly doubt most people should generate these errors....and this still happens with office 2007

[Mcfly000]

ohh and i forgett To tell that i have a brand new P4 3.6 watercooled with 2.046 mb memory

and i think it get's f***ed up , becuse i install version b.07 over version b.06

becuse i have just make a compliation of Vista 6. final version SPANISH iso with b06 .. and it work good


( i do have the same problems as usual iT dont make it bootable but i fix that with oscdimg.exe and a Command script)


now im going to make a new complitation with b 07 and vista 6


( AND I HAVE DOC HERE BESIDE ME WITH A CAMERA IF I GOT ANY ERROR )

This post has been edited by Mcfly000: 14 December 2006 - 07:17 AM

[Mcfly000]

bledd, on Dec 14 2006, 05:26 AM, said:

mcfly


..

Supported Vista version is minimum Build 5744 (RC2) and newer, RTM build 6000 recommended and it will be only one supported from the next version, you can run it on older on your own risk

THATS NOT TRUE , BECUSE I DID A PERFECT ISO OF LONGHORN BETA 2 5472 AND VISTA RC1 5600.16384 spanish iso AND IT WORK GOOD NO PROBLEM TO COMPILATE IT

and i have betatested VISTA since version 4736 when it was almost the same as XP


( K I KNOW IT WAS NOT PERFECT AFTER INSTALL BUT IT NEVER GOING TO BE A PERFECT VISTA NEITHER WITH THIS PROGRAM OR WITHOUT THIS PROGRAM)

[Mcfly000]

another thing i have just make an ISO of WINPE 2.0 that come with Windows Vista and its bootable WORKS PERFECT you can use all the commands to format and so but it's very poor ..but its better than WINPE 1.6 becuse it let you install vista from hardisk , and i think you should do a TOOL to make a good WINPE BOOT ISO so people can BOOT and install from hardisk

(i know that you can do that with vista install DVD , but there are people that dont have DVD-ROM and want to install vista from hardisk ) and with WINPE you only need a 200 mb / 700mb CD


thanks for all you do

[nuhi]

3aces, don't worry I'll check it, and if you haven't modified it with anything else, and it's RTM then I'll fix it.

Mcfly000, ok. Lets reset. Obviously you are not stupid, it's just you didn't know how to post a bug report. So, the point is to post what the error was, no need for anything else until asked for more details around it. Thanks.

[3aces]

cheers nuhi your a legend, by the way i also use msn plus live, but i still get the same error when i dont use it

and also after i installed Vista this time, when you set up user name and stuff my computer crashed and rebooted its self after bout 3 or 4 minutes, im not sure....could be a vlite issue....thought i better let you know

[idioteque]

so whats the count on 0.7

install size and files with everything removed ?

[dexter.inside]

nuhi, on Dec 14 2006, 02:59 PM, said:

I have no intentions of making tutorial how to mimic vLite. Worked on it for months until I got it. Call me selfish but that's how it is.
Way as the vLite develops seems perfect to me, I don't see the point in removing all at once, that would have so much bugs that no one would be able to keep track of.
Gonna check that dll but I'm not that keen on changing pics to prove control.
And sorry for my tone in case you don't like this direct approach.

Hey, no problem... you have every right to be acid on your own application... I'd be the same over mine. I know the time required by something like this. I just wish I had more time for "hobby programming"
The worst part is when you know exactly what you want to code and don't have time to do it, gets me very annoyed.

I do chemical engineering for a living and I am currently involved in 4 different projects, more or less related to programming. I've been following the NT 6.0 project since it was at build 4008, so quite naturally I have developed my own idea of doing things with it. Hopefully this winter holiday I will find a good excuse to get rid of my life and do some real coding.

You're lucky to have the time to spend with vLite, I wish I could say the same...

[Mcfly000]

nuhi, on Dec 14 2006, 08:35 AM, said:

3aces, don't worry I'll check it, and if you haven't modified it with anything else, and it's RTM then I'll fix it.

Mcfly000, ok. Lets reset. Obviously you are not stupid, it's just you didn't know how to post a bug report. So, the point is to post what the error was, no need for anything else until asked for more details around it. Thanks.

ok nuhi no need to bug report , i did de-install version b06 and i did a clean b07 and
i think that here was the problem I ALSO DE-INSTALL my SYMANTEC ANTIVIRUS v10.xxx

and this time it didn't give me any error
i didn't use the makeboot part after it re-build , becuse you said that someDVD-ROM still have problems to burn
so i did made the iso with oscdimg.exe like always

this photo is TAKEN BY DOC HIMSELF




thanks nuhi you are the best , and i hope you made that TOOL for making WINPE 2.0 costumized just with a few program like a webbrowser becuse not everybody have a DVD-ROM , only CD-ROM, but they still want vista installed from hardisk

[dexter.inside]

Mcfly000, on Dec 14 2006, 05:12 PM, said:

becuse not everybody have a DVD-ROM , only CD-ROM, but they still want vista installed from hardisk

Regarding that, how about the "Create Spanned Shares" method, nuhi ?
I've tried it once, exported the WIM to 2 SWM pieces and replaced them in a spanned share set from Microsoft. The setup routine reconstructs the original WIM locally on the target machine

[3aces]

dexter.inside, on Dec 14 2006, 03:27 PM, said:

Mcfly000, on Dec 14 2006, 05:12 PM, said:

becuse not everybody have a DVD-ROM , only CD-ROM, but they still want vista installed from hardisk

Regarding that, how about the "Create Spanned Shares" method, nuhi ?
I've tried it once, exported the WIM to 2 SWM pieces and replaced them in a spanned share set from Microsoft. The setup routine reconstructs the original WIM locally on the target machine

to be fair isint this a little bit pointless....becuase vlite will remove so many componants that it will be able to fit on a CD, and also im only 92 mb away from a 700MB installation source, but maybe it will come in handy for when the time comes to intergrate addons and drivers and things

[dexter.inside]

3aces, on Dec 14 2006, 05:29 PM, said:

but maybe it will come in handy for when the time comes to intergrate addons and drivers and things

For me it certainly will... let's say for example that I were to install Visual Studio 2005, Sysprep /generalize the machine, capture the WIM and pack it back in the setup. I could use a newer vLite onto it that way without having to reconstruct the image. And if the WIM gets bigger than 1 DVD, this would be really useful.

[3aces]

yeah i guess so.....butt bigger than one DVD, hmmm......8gb is a huge image, i suppose that would also be slow, you could play around with it and get it to a external drive

[Cronner]

At the end when i click finish i get this error:
Making the image on vista x64 rtm and the image is vista x64 rtm to.
Image works perfectly


See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at ..
(IntPtr )
at ..
(Boolean , Boolean )
at ..
(Boolean )
at ..(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
----------------------------------------
vlite
Assembly Version: 0.7.0.0
Win32 Version: 0.7.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe
----------------------------------------
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
vLite
Assembly Version: 0.7.0.0
Win32 Version: 0.7.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vLite.exe
----------------------------------------
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
MCDBNET2
Assembly Version: 1.32.0.0
Win32 Version: 1.32.0.1302
CodeBase: file:///C:/Program%20Files%20(x86)/vLite/MCDBNET2.DLL
----------------------------------------
msvcm80
Assembly Version: 8.0.50727.312
Win32 Version: 8.00.50727.312
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.312_none_10b2ee7b9bffc2c7/msvcm80.dll
----------------------------------------
vhelper
Assembly Version: 1.0.2478.3773
Win32 Version: 1, 0, 0, 1
CodeBase: file:///C:/Program%20Files%20(x86)/vLite/vhelper.DLL
----------------------------------------
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.312 (rtmLHS.050727-3100)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

This post has been edited by Cronner: 14 December 2006 - 12:54 PM