submix8c

Diskless Workstation - an old concept and used at one time "back in the day". http://www.webopedia.com/TERM/D/diskless_workstation.html http://www.computerhope.com/jargon/d/diskwork.htm All the way back to Windows 3.x. http://en.wikipedia.org/wiki/Diskless_node You need a better terminology/synonym book. Or maybe (after a google of "netboot") you confuse Linux terminology?

Well my point was (and I wonder why J3 was never released) that sometimes Beta BIOS files fix some things, e.g. RAM detection. I have (had) a MoBo that specifically stated a max of 512mb but it did, indeed, accept 728mb (3x256). Notice that the Beta one doesn't say what "got fixed", but Jan stated "fixes" (as I quoted). Whether the "J3" is what "fixed" it or not, I don't know, however, look at this for a "clue" - http://rays-place.net/Extras/PCTechGuide/27chipsets.htm Just be happy it works and if you can contact Jan and get an answer, you might ask why it wasn't released or if he will.

Yeah, I have it and won't redistribute it. You can get the AutoPatcher (mDGX) still or get the latest USP3 (newer and incorporates most, of not all Updates and then some with updated files). UBCD for 98SE used the EXACT SAME FILES as AutoPatcher. I know this for a fact, since I was one of the contributors to both Projects. http://www.msfn.org/board/topic/80800-auto-patcher-for-windows-98se-english AutoPatcher Downloads - http://www.mdgx.com/web.htm#AP98 Latest USP98 Thread with link to the Download File - http://www.msfn.org/board/topic/61749-98-se-sp-332/ It appears that the USP98 may be more dependable at this time. UBCD98SE has/had what could be construed as "warez" and the thread was removed, as well as every single link to downloads "disappearing". I -suppose- I could revamp it so that it didn't contain those items, but I deem that to be pointless due to USP98.

No, it is NOT compatible! Dude! The Links are FALSE (when installing on "vanilla" Win9x/2000)! Post #2 Now Post #5 Just... STOP it, please! I will, however, note that I do not use Kex since I don't use any software on my 98SE/Win2000 that requires it. Therefore, I admit I was "slightly" wrong. (I despise others spreading erroneous information more than I anger myself at having done the same. :angrym: )

To LostInSpace2012 - WTH are you talking about? Fixing a PC or ranting and giving obvious information? AGAIN, problem is SOLVED by a Reinstall! (Read the Etiquette/Rules about bumping post counts. )

I am SOOOOOOO glad for you, even if you TOTALLY DISREGARDED my findings and instructions TO THE LETTER and report back (should I have translated to Deutsch for you? I took 2 years in HS. ). I will now proceed to treat your posts as I have done with others of your mindest - disregard you back. Good luck with the next problems you may encounter.

So it says, but then the Download link says otherwise.

From ASUS - TX97-X Beta BIOS 0112.001 The latest Beta BIOS. From the link (I've used some of them before) 0112X_J2.ZIP - "Apart from K6plus support, this "patch J.2" BIOS has a fix for the 32GB harddisk limit and supports IDE drives upto 128GB!" Note that he had patched the BETA above, meaning the "Beta" may have had some kind of additional "fix"?

I just downloaded German Service Pack 3. - fp40ext.in_ (fp40ext.inf) is incorrect (but see below for maybe not) - ims.in_ (ims.inf) is incorrect - layout.inf is correct <<-- leave it alone Whether this is the case for the "original" SP2 Home "DEU" CD I don't know. If so, then it, too, is wrong. My "ENU" one is not wrong (nor is the ENU SP3 Package). This link (that you gave) has erroneous instructions, as far as the string to change->to is concerned. http://support.microsoft.com/kb/897128/en-us The string "XP Professional" should be changed everywhere to "XP Home Edition" (where the link says just to "Home"). Oddly, in ENU "Full" SP3 Package, it appears to also have "XP Professional" in the "fp40ext.inf" file (it goes directly into the I386 folder), so I have my doubts that. The other two are in different folders in the SP3 Package and are different between the Home (IC folder) and Professional (IP folder) and should have that string changed only in the "ims.inf" file. Regarding "ims.inf" cdtag values the should be as follows (near the end of the file): cdtagfile = "\win51ic" cdtagfilei = "\win51ic" cdtagfilem = "\win51mc" spcdtagfilei = "\win51ic.sp3" <-- in the case of the original CD, its should be "sp2" instead These will be the values found in the "layout.inf" file and correspond to what you should have in the Root of the CD/DVD.. The original files (when opened with an Editor) will have a value of "Windows" and the integrated one (win51ic.sp3) will have nothing (empty). In other words, for the cdtag values above, change the "p" in the string to "c" (remainder of the strings are exactly the same). Regarding the "fp40ext.inf" file (for "FrontPage 2000 Server Extensions") my XP Home SP2 has the file(s) in it as well as it being in the SP3 Package (with "Professional" as the string). In other words, why would you need to change it (since it's dropped directly into I386)? And why did the MS Article say to? For the two files above, as far as I can tell, only the "ims.inf" file needs changed and should be recompressed after fixing. The other two (again, as far as I can tell) do not need changed. The fixes described will apply to both the original CD/DVD file (if the values are incorrect) and the Slipstreamed CD/DVD file (which is definitely incorrect). 7-zip will open the compressed filename "ims.in_" and allow extraction. Move that file (after Slipstream) to a temporary folder for modification before extraction then modify as indicated above. There is an "ims.ca_" ("ims.cat") Catalog file as well but it appears to be common beteen Home and Professional and hopefully it won't affect installation with the modified INF file. Sometimes it matters - I don't know in this case. (Checksums, etc?) After modification, rename the "ims.in_" to (e.g.) "imsSAVE.in_" before recompression (see below). To recompress the modified "ims.inf" to "ims.in_", open a CMD Prompt, change ("CD") to the temporary folder (the full path, e.g.: CD "C:\TEMPMOD"), enter the Drive Letter of the Folder (e.g.: C:) and enter the following: makecab /D CompressionType=LZX /D CompressionMemory=21 ims.inf The resulting replacement "ims.in_" should be copied (or moved, whichever) back to the I386 folder before final ISO creation. Create the ISO (as you wish - I'm out of that subject), test, and burn (if you wish). That's it, that's all, that's Microsoft for you. HTH and good luck. I'm done here.

@Kel - exact-a-mundo! BUSTED! I'd say this exercise in futility is over, seeing as how this mix-and-match "DVD - or is it a CD" issue is ovah!

??? That does NOT look like an "original" if the label says "HOME" and the INF has PRO in it! Could you scan your "original" and post the scan image? You NEVER provided a Directory Listing, so who KNOWS what you really have? (I googled "GER_HOME_SP2" - fishy...) "cdtagfile" IS the values for the one in question and are the TAG files in the ROOT of the CD! MY IMS.INF For HOME Edition is cdname = "Windows XP Home Edition CD-ROM"productname = "Windows XP Home Edition"bootname1 = "Windows XP Home Edition SP2 Setup Boot Disk"bootname2 = "Windows XP Home Edition SP2 Setup Disk #2"bootname3 = "Windows XP Home Edition SP2 Setup Disk #3"bootname4 = "Windows XP Home Edition SP2 Setup Disk #4"bootname5 = "Windows XP Home Edition SP2 Setup Disk #5"bootname6 = "Windows XP Home Edition SP2 Setup Disk #6"cdtagfile = "\win51ic"cdtagfilei = "\win51ic"cdtagfilem = "\win51mc"boottagfile1 = "\disk101"boottagfile2 = "\disk102"boottagfile3 = "\disk103"boottagfile4 = "\disk104"boottagfile5 = "\disk105"boottagfile6 = "\disk106"spcdname = "Windows XP Home Edition Service Pack 2 CD"spcdtagfilei = "\win51ic.sp2"so I find it HIGHLY unlikely that it's a kosher CD. Post#7 by jaclaz - you REFUSE to answer!

@cottonlane: Really? Take a look back at post #9.

More than one year later, whocares02 bumps a topic for no apparent reason. The OP has long since gone and undoubtedly won't respond back. (Are you stalking me? )

Wouldn't happen to have the Beta BIOS in it, would it? http://support.asus.com/download.aspx?SLanguage=en&p=1&s=5&m=TX97-X&os=&hashedid=n/a (see Downloads for OS="other") Mobo here? http://www.baber.com/baber/411/asustx97x.htm EDIT - According to this, you can (if proper RAM and position is observed) go to 512mb - http://www.wimsbios.com/forum/notebook-bios-and-other-problems-f38/thinkpad-770x-the-maximum-memory-saga-continues-t6493-15.html

Well, to note that Windows98/SE/ME still allowed Windows Update past EOS (with the "tricks" to push into the Older Updates site) I would say that unless MS completely "pulls the rug" I'd say that you'd still be able to use it to get the "older" updates (at EOS and back) using said WUA (Win98/SE/ME was different, natch). IMHO... edit - Found the reference. It, too, had some of the "glitch" that was occuring for accesses (remember the links to Events not working as well?). http://www.msfn.org/board/topic/94225-windows-update-fix-for-win9xme/ (note - still available within AutoPatcher at Mdgx, FWIW, but the MS v4 website is defunct, so pointless.)

I believe -X- has chosen to -not- update the UDC script at this time since EOS is at hand, and only providing the -last- one on or immediately after Patch Tuesday. You can download the Latest Files and replace the Superseded ones via this MS Article. Note whether XP is affected or not and replace older ones accordingly. http://technet.microsoft.com/en-us/security/bulletin/ms14-mar

??? Cross-post to keep things together. http://www.msfn.org/board/topic/171458-windows-update-2k/

Ummm... which "variation" are you using? Can you point to the Post to clarify? edit - look this thread over with the corresponding CMD Post link. http://www.msfn.org/board/topic/158904-windows-update-on-windows-2000/

Hmmm... You juste earned yourself a Report Button for not reading the rules and vulgarly chastising me. This is NOT "a different forum" but MSFN instead. You're welcome. BTW, My name isn't Wipi - it's submix8c.

Are you using the Latest Greatest Windows Update Agent?

1 - Kel is correct. One post did mention warez. Please do not discuss warez of any kind. If you haven't already doens so, pleae read the rules: http://www.msfn.org/board/index.php?app=forums&module=extras&section=boardrules 2 - There are two items of note (AFAIK) in the construction of a CD/DVD: File System and Character Set. Here gives a simple explanation of Character Set per File System, albeit rather confusing because of the last Joliette statement: http://www.cdrinfo.com/forum/tm.asp?m=900 The topic is about Nero but still "kind of" applies. The "erroneous" statement actually refer to the Character Set applicable to the Joliette. The following is Wikipedia (mostly, but not always, dependable reference): http://en.wikipedia.org/wiki/ISO_9660 TextMode -only- reads ISO-9660 (via the ElTorito Booting - via the BIOS Boot Selection). After TextMode the Joliette is read. UDF is -not- necessary -unless- you have -very- large files (AFAIK). Please note that -most- ISO-creating/burning softwares -usually- convert non-valid Characters depending on the FileSystems being created/used. I -personally- use ASCII for the Character Set. Please also note that NEWER MS OS DVD's use UDF -but- has a -different- BootImage than XP/2K3 and earlier. Win9x -generally- does NOT care about Joliette when Clean Installing, hence the reason I use ASCII, since it -prevents- conversion of (e.g.) "-" to "_". The Wikipedia link has further links and is -only- given as a reference point for your edification. You're becoming -very- confused and -again- randomly wandering around with a blindfold on. Indeed, -many- of the MKISOFS parameters you're using (e.g. the System Architecture) are totally unnecessary. Use the K.I.S.S. method instead of Overkill. HTH P.S. Also note the difference between DVD+R and DVD-R when using it for Real Hardware and the ability to Boot from it. I don't believe DVD-RW is generally supported. You can look that up further for yourself via Google: dvd+r vs dvd-r

(<<==head smacks desk... why does this pathway look familiar?) ROFL! Please quit attempting to prove that you know more than everyone else. NOBODY is in such a position on the planet Terra. When you are finally able to pin the tail on the donkey, please let us know which direction you took and by what method ("I smelled my way there...").

Hmmm... And I said and that was my preference as opposed to MKISOFS, since it has a GUI and functions very well (IMHO) similar to NERO, which DOES have "Ignore Read Errors" under "Copy Options", which "apparently" you are MOUNTING an ISO image (we don't know that). Please note that nLite uses its OWN parameters INTERNALLY to pass to it (MKISOFS), which is a COMMAND LINE tool. This is where you are erring, among the fact that you missed the remainder of the thread CLARIFYING what would need to be done, regardless of the tool to be used. Also note that "?" wherever I had used it means (UNSURE). I do tend to do that occasionally rather than use an emoticon. Randomly attempting to create a CD/DVD/ISO outside of SPECIFIC instructions by ANY member (INCLUDING corrections by other members) and expecting it to work will continue to result in failures. You are not being clear which will ALSO result in "bad advice". The USUAL method is to clearly state WHAT you want to do thusly (to borrow jaclaz' now-famous link) - http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/problem-report-standard-litany.html Otherwise, the best that can be done is give EXAMPLES and continue going in circles. Thank you, and HTH.

So far, you've been helped with other subjects requiring more information, so... What version of Grub4DOS and how did you set up the DVD? "It doesn't work because" is not enough. Please give a link to what you used as far as software and the "how-to" you used to better assist.

Aside from "uninstall a program", what "mounting" software? Or are we supposed to guess?