Jump to content

Near giving up


Patosan
 Share

Recommended Posts

Hi guys,

I haven't used nLite for anything except iso and burning recently, so here's a new session just for you, plus the resultant install gibbersh in vpc. All I did in nLite was add a few hotfixes ... always the sane result whether it's one hotfix or 20, unattended only or anything. In this case I integrated sp3 prior using start/RUN, as a refresher integrating sp3 is the one thing that nLite can do for me without trouble ... ANYTHING else and there's trouble.

Last_Session_100208a.ini

post-232949-1265566750_thumb.jpg

Edited by Patosan
Link to comment
Share on other sites


Patosan, the only thing I see readable in your 'gibberish' is "ms-ime2002". Google says this is some kind of Japanese language input system. Perhaps you don't have VPC set up properly to run your Japanese version of Windows. There is noting in your Last Session that looks suspicious. I run XP x64, so I do not know anything about your updates. Please post a screen shot of a Windows Explorer view of your CD. Is it a real OEM CD or a recovery CD? Enjoy, John

Link to comment
Share on other sites

So finally that unattended trick didn't worked. I don't know what's failing, but here is some ideas:

- Have you tested making an unattended session without slipstreaming SP3 nor any hotfix?

- It shouldn't make any difference but you can avoid nLite to slipstream SP3 or the hotfixes, with HFSLIP, or doing it manually, prior to use nLite for the rest of the tasks.

- It seems there's still some people having some problems slipstreaming SP3.

Link to comment
Share on other sites

Perhaps you don't have VPC set up properly to run your Japanese version of Windows.
There is nothing to set up for non-English windows in vpc, just as there isn't in the main pc.

I have many times installed Jpn ver in vpc successfully : original sp2 CD and also with sp3 integrated ... no trouble.

There is noting in your Last Session that looks suspicious. I run XP x64, so I do not know anything about your updates. Please post a screen shot of a Windows Explorer view of your CD. Is it a real OEM CD or a recovery CD? Enjoy, John
We've been here before in last year's posts : the hotfixes are fine, all have been DL direct from ms I even re-DL just to check this out so many times. I have already suuplied screen shot of my source in earlier posts. Please nobody else ask about "recovery disks" I only get blank looks from people here in Jpn when I ask ... suspect they don't exist here. I bought mine source as an OEM it was sealed and labeled as such I've been back to the shop where I bought it and also to another specialist shop for confirmation on this point.

There is nothing suspicious in the Last Session ... that's exactly why after many months of testing, asking, running all over the city checking my CD ... I am so frustrated. Honestly you guys who work with English ver and/or have no troubles are blessed. Or perhaps it's that I'm cursed, must've done something really s***ty in my previous life. I will do some more nLiting and supply the sessions and shot of trouble ... I'll do a single action in each to show the results.

Edited by Patosan
Link to comment
Share on other sites

So finally that unattended trick didn't worked.
I always suspected I merely avoided "seeing" the trouble rather than avoiding it. Unattended means that I don't SEE the gibberish, problem, but it IS still there ... shows up later when I start installing other software.
I don't know what's failing, but here is some ideas:

- Have you tested making an unattended session without slipstreaming SP3 nor any hotfix?

- It shouldn't make any difference but you can avoid nLite to slipstream SP3 or the hotfixes, with HFSLIP, or doing it manually, prior to use nLite for the rest of the tasks.

- It seems there's still some people having some problems slipstreaming SP3.

I have integrated sp3 both with windows RUN and nLite both methods give identical results - GOOD. My source is sp2 and I'm NOT having sp3 trouble at all.

In the most recent posted session I didn't integrate sp3 with nLite. My view is I should do as much as I can outside nLite since I'm having trouble there ... removing as many variables as possible. With that in mind I am thinking integrating the hotfixes prior to nLite but I don't know the correct switches or method ... any help here is also appreciated.

I use "X"s Windows XP Post SP3 High-Priority Updates (x86) to identify which Jpn hotfixes to DL from ms, so you assume that the ones I'm using are correct ... I've installed all of them in my pc os with out trouble.

I'm sure I got trouble with unattended as the only action, even without sp3, but I will do it again just to cross that off the list.

Edited by Patosan
Link to comment
Share on other sites

Patosan,

Don't let the stinkin inanimate object get the best of you. That da@mn little murphy's law rides on my shoulders too. Try this last session I use this on all my 32 bit machines for the last couple of years and have had no issues during or after the install crop up. My 64 bit desktops run a similar one like this also with no issues. Before you use this Last Session go thru it as I have commented out monitor settings and such using a semicolon ( ; ). I worked on my nlite stuff for awhile just testing and getting things set to accommodate a wide range as I wanted to make sure it was a standardized setup for all my home stuff. This has again proven to be a very stable Last Session and everyone in the family is happy due to the standardization of it. I have done CD, DVD, HD, and network installs with this and nothing has ever went wrong. Don't forget to change this in BOLD.

[Main]

Env = 1.4.9.1 - 2.0.50727.3603.Microsoft Windows NT 5.1.2600 Service Pack 3

Target = Windows XP Professional SP3 - 5.1.2600.5512 - English (United States)

Good Luck

JD

Edited by 03GrandAmGT
Link to comment
Share on other sites

Patosan, I guess my problem here is the age of the thread and the intermittence of the replies. Sorry about that. Since the only thing in your Last Session is the hot fixes, I am going to suspect them or nLite. I have never caught wind of anyone having nLite problems with Japanese Windows before. So, a technique I learned from Kurt_Aust for determining what Windows updates are required: Run nLite against a fresh copy of your source adding only SP3 and doing an unattended install if you like, but do not apply any hot fixes. Install this on VPC and go to Windows Update and see what updates it wants to install. Copy a few of the oldest and try these on an nLite run (including SP3) and VPC. Let us know what you learn. Perhaps this has been asked before, but have you tried removing nLite, DLing (from the nLite site and checking the MD5) and installing a fresh copy? If you want to go over to a completely non-nLite unattended method, please try the Unattended Guide link above and the Unattended sub-forum. Good luck, John.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...