dencorso

Well, duffy98, if you have Ghost 2003 installed in your Win 98SE, you'll find the Iomega drivers in the folder C:\WINDOWS\All Users\Application Data\Symantec\Ghost\Template\common\ and, BTW, the latest version of USBASPI.sys from Panasonic is not a .sys anymore, it is USBASPI.EXE v2.28 (released in 2007), which you can find at MDGx's site.

And, speaking of MD5 (and SHA1), one must not forget FCIV (KB841290), a great command-line utility from Microsoft.

First of all, I'm glad you've solved your problem and now has the working bootable DVD you sought! I decided to keep out of the discussion in the last two days, so as to let it progress unhindered, because I firmly believe in "too many doctors have killed a king!", the purported last words of the Emperor Hadrian. Now I feel I must add some comments, about one thing that remained unsaid: But it will, rest assured it will!And while I agree with jaclaz: and I much less want to be the starter of such a flame war, I'll say that the reason for recommending quite strongly SHSUCDX is simply that it was written to be much more forgiving than MSCDEX, so that it can read many optical media that are beyond MSCDEX strict format requirements. Even if you don't feel like testing it right now, do have a copy of it in your toolbox, because, sooner or later, you'll find it quite handy. And because it's open source and very well documented (although you'd have to gather at least three versions to have access to all existing documentation: John McCoy's 1.4b, Jason Hood's 3.02 and Jack Ellis' 3.03E, which is the current one). And because it's still supported and actively developed (at least until last year).

Welcome to MSFN, n00bie! You got my attention, but unfortunately all our crystal balls are at the repair shop at the moment... So, in order to be able to help you, I need more info (specifics, mind you, not generics): which laptop exactly are you having trouble with? which windows do you want to install in it? Cheers! BTW, buy yourself a couple of RWs... that'll stop the coaster factory.

It's complicated... Which driver causes the shutdown problem seems to depend on which nVidia Card one has. And it *is* possible to mix files from different versions, but some experimenting is necessary. For my rather ancient GeForce2 MX400, the right mix is using the 29.42 drivers, but with nvdd32.dll and nvopengl.dll from version 32.20, for added compatibility with DirectX and OpenGL (see post #69, above). RLoew has found a viable mix for the 6200 card, reported in his posts #294 and #303, above, from which I now quote: For those who decide to experiment with the nVidia drivers (as I said in my post #290, above), I recommend not to remove the nVidia drivers with add/remove or unistall, but, instead, to use the great freeware Driver Cleaner Pro Version 1.5 (*NOT* Driver Cleaner .NET !!!). Version 1.5 supports Win 9x/ME, despite that not being explicit in the on-site information. The Add/Remove applet or nVidia's own uninstallers don't do quite a perfect job in removing previous nVidia drivers, only Driver Cleaner Pro is able to remove them completely. I consider this the safest way to test nVidia drivers. Even so, before begining to experiment with video card drivers, do create a full backup of your system!

Anything from (1.5 x amt of RAM) up should work OK, AFAIK. From 1.5 x down to 1 x works also, but is more controversial (I use fixed 1:1)... Less than the installed amt of RAM is asking for problems, IMO.

Hang loose, jaclaz! Since nobody explained why JO.SYS didn't load, I did it. But after he did what you recommended, the DVD remained unreachable, and this gives me an idea... @LoneCrusader: does your floppy image load MSCEDEX? If so, do substitute it by SHSUCDX V3.03E, and let's see what happens.

For what it's worth, if you chainloader (fd0)+1 instead of chainloader /io.sys, jo.sys will run, because it's called from the floppy boot sector.

Neither did I... but that isn't enough to stop me from buying tickets, since the sheer possibility of winning an unimaginably huge amount of money is too seductive to be ignored.

Note that the "paste -> font enlargening + nothing pasted" (that I'm glad you can reproduce) wasn't reported on Vista. What was reported is the rarer form of the bug (sometimes it won't manifest for me for weeks on end): "paste to search bar -> nothing gets pasted", and this form of the bug won't go away by simple repasting, when it manifests. You've got to paste elsewhere (say, Notepad), copy again and try to paste again to the address bar, at least twice, before anything gets pasted. And when it gets pasted, a long time will elapse before it manifests again, although once or twice I've seen this happen twice on the same day, but this is very uncommon.

Yes, you've noticed a forum issue we're having since perhaps the last month. And the only presently known workaround to it: relogin. This issue is being investigated and should be solved shortly, or so we hope. Sorry for the inconvenience.

No the fist byte is also a version number change. MS specification for the file version structure indicates there must be both a hexadecimal and an ascii version number present. In the hexadecimal version number 0x02B1 = 2225 and 0x02B6 =02230. A common reversioning mistake is to change just the ascii version number, while forgetting about the hexadecimal one. But I think you are misreading me, MDGx: the LLXX patch is much longer than one byte, but here I'm talking about her patched version 4.10.0.2225 (as downloadable from her thread or from your site) vs. version 4.10.0.2230 (present in BHDD31.ZIP), which is the same file, but reversioned by Maximus-Decim. Now, if you compare the original MS 4.10.0.2225 vs. LLXX's patched 4.10.0.2225, you'll find lots of differences, although they have almost the same size, because she made her patch fit in areas that, in the original file, contain only zeroes. The simplest way to recognize the LLXX's patched file is by the presence of her signature, starting at hexadecimal offset 0x26E3, since the original file has only zeroes in that same region; moreover, the file patched by LLXX is exacltly 24.431 bytes long, ending with 0x32, the ascii char for number 2, whereas the original MS file is just 24.430 bytes long. HTH.

But Vista cannot be ruled out! While cluberti never saw it happen in Vista, the original precedent I cited, quoting from another forum, is from a IE7 on Vista Business user. Scanty as the evidence is, we haven't up to now, any evidence for its occurrence on Win 7, but it clearly is found, if rarely, from Vista down to 98SE.

No, it's not related to copying a multi-line source and then pasting it. I see it happen in my system too, and I'm 100% sure it happened to me in situations where I had just one line to copy from, for instance, something from the address bar copied onto the search bar. And I'm sure the bug reported by bauxite is related to the one I described in my 1st post, or is the same bug, but the "enlarging" only occurs when pasting to the seach bar. When text from elsewhere is pasted onto the address bar, the contents of it just disappear, and the "enlarging" is not observable. I've also seen this kind of "refusal to paste" occur when trying to past to the search box of regedit and also to the search bar of "Registry Search & Replace" v. 2.11, a shareware of which I'm a registered user.

As I said elsewhere, ModifyPE gives invariably the "Invalid parameter, type modifype for help" error and refuses to work when run under Vista (and, presumably, also Win 7)... You asked for ideas, here above are two of them. Good luck! ...and keep us posted on your results.

I like Fredledingue's solution. But I'd like to add that all you need is one CD-RW to put it in practice as a general solution: burn, copy (or rip) all that interests you, then erase the CD-RW, and you're all set to start anew with another such file.

@Queue, SlugFiller and timofonic: This is the KernelEx thread, which is, by itself, already huge! Let's not get off-topic! If you want it badly, let me know and I'll split your latest posts into a new thread (in this case do PM me about it). But I'd much rather avoid the potential development of yet another this-vs.-that flamefest, if you don't mind letting it go.

Have you ever heard of the Wayback Machine? The DOS-LOGO project DOS-LOGO Direct Download Links: DOS-LOGO.SYS Device Driver Version 1.0 DOS-LOGO.ASM Source 1.0(LGPL)

Do consider also adding 7-zip to your toolbox, AnnieMS. It's the king of all file archivers, and it's freeware. At the moment, the right version to get is 4.65, the latest stable version. HTH

Suzi Quattro - If you can't give me love Kansas - Dust in the wind Don McLean - American pie

Never post a live link to any site offering malicious content! Consider yourself warned! Never trust pop-ups of unknown origin, because they almost always are scams temselves! There's no virus at Rojack's page. I checked that myself right now. As for the specific pop-up you saw, it *is* a scam. You'd really be in trouble if you had downloaded and installed their "anti-virus", which is in fact a malware. Read more about it here (link). But since you didn't trust it and downloaded nothing from it, you're probably on the safe side. No need to dig any deeper, in what regards to that pop-up, unless it keeps on appearing on other unrelated sites (in which case you may have got a browser hijacker added to your browser).

I agree with cdob. You should try another burner. And since Nero 6 will work OK with USB burners, consider getting a PATA/SATA-2-USB adapter and testing the new burner without opening the case. If all goes well, then you can replace the burner at a convenient time and keep the adapter, which is great also for (re)formatting and (re)partitioning HDD's without having to mount them physically inside the case.

AT power supplies cannot be turned off by software. Digerati's idea is feasible, but it'll just cut the power to the machine... so, unless someone turns it off by hand at the hard power-switch, prior to shipping, you'll be shipping your machines turned on and they'll boot the instant they're plugged into a live power outlet, which is not desirable. I see no satisfactory automated solution to your problem. If you have to stick to non-ATX power supplies, you'll have to live with having someone go the rounds turning them off by hand, after image deployment. I'm sorry!

You all may find Multibooter's SDHC & micro-SDHC card readers for Windows 98 thread of interest. Although his emphasis is on SDHC cards, it has lots of interesting info on multicard readers. This other thread, Multiple-drive-letter-problem, also by Multibooter, is less general, but I think may also be of interest.

But, if you're using GRUB4DOS, remember it understands GZipped ISOs! And I bet GZipping your ISOs may be enough to get your project back to under 4 GiB, so FAT-32 might be enough.