j7n

Thank you. Shell32.dll in v2.1a has the altered logo.

There are two parts in FileZilla, the "server" and the "client".

Service Pack 2 changed Windows logo in the system-wide About box. The new picture was an ugly 16-color WinXP logo. Perhaps it is not a good idea to apply XP artwork to 98?

Rank 1: Need for Speed Underground 2 Rank 2: Grand Theft Auto: San Andreas (shouldn't run on Win98 but runs anyway) I wonder why GTA-SA has Win2000 as a system requirement. It could be possible that some secondary bloat bundled with the game requires WinNT, while the real game itself runs. Is there a Steamless HL2? Perhaps specify exactly how old games may be listed.

MP2 is usually assigned to audio-only MPEGs. If there is video in your files, just rename them to *.mpg later. It's not a big deal actually. Even if you did download 200 of these files, a mass rename tool such as Total Commander can do the job. I don't believe that the format has been changed, only filename.

LAST - $$$$ - Sonic Foundry Sound Forge 6.0 --- The authors sold themselves out to Sony. Hardly obtainble legally. LAST - FREE - FileZilla Server 0.9.12c --- http://downloads.sourceforge.net/filezilla...ver-0.9.12c.exe There is a higher version number of FileZilla installing on Win98. But it does not save its settings properly, and effectively does not work. FileZilla authors wouldn't say which version can be used on Win98 because of "security issues" in older builds.

Why don't you setup a controlled network at home and check the speeds? From my experience transfer speed over the network may be bottlenecked by older hard drives on PCI bus, not so much the NIC.

The thin client vendors have to install a bloaty SQL server for the runtime image creation. This also requires filesharing to be enabled on the system. nLite on the other hand only needs itself and selected NET Framework libraries. The two key components of XPe – minlogon and ewf – can be transplanted into regular Windows XP. Lite Windows XP can also be made small (but not as small as Win2k).

When first I heard about XPe, I thought it has to be small like Win2k. In fact all the graphical bloat is still there intact: shell32 is 8 Megs, and explorer is 1 Meg. IMO, the best embedded system can be created from lite 2000, or maybe mini Win98 if the hardware is compatible.

LOL. Fast Ethernet is 100 Megabits. If you force a network interface to full duplex make sure you do that for every device on the network or not at all. Otherwise duplex mismatch will occur.

Unless you have a Gigabit router, you can't expect more.

If this were true I guess all of machines here would be running Win98 and I would be purchasing alot of VIA mainbords.

The best system is the one you're most familiar with and therefore can work most efficiently on it.

(1) Assuming your WinXP installation is very important but programs are NOT stored in \Program Files. I'm not sure how to properly move an installed WinXP from \WINDOWS to \WINNT. I would try installing Win98 to something like \WIN98 (possible incompatibilities later since some tools assume \WINDOWS). 1. Backup your system to another place. 2. Wipe the partition. 3. Install Win98. 4. Setup a BIOS password (to halt booting). Run WinXP installer and wait until it reboots the PC. NT boot sector and system files are now written. Do not let the XP setup continue (since we don't need this clean XP). 5. Delete the newly created directories by the XP installer in C: root. 6. Restore your original WinXP directory from the backup. Edit boot.ini so that it has 2 entries, one pointing to WINDOWS, and one to C:\BOOTSECT.DOS This approach has 2 problems: the \WIN98 directory name and lost \Program Files contents. It is no big deal if software had been installed to another partition such as D. You can also try restoring original \Program Files but I'm not sure if Win98 would be happy with some NT-specific DLLs there. Most likely Win98 will boot Ok though, I think. (2) It's much easier to install everything clean and organize your folder structure like this: C:\WINDOWS - Win98 C:\Program Files - contents installed by Win98 and application shared files C:\WINNT - WinXP C:\TEMP - common temp dir (instead of deep inside Documents and Settings) D:\SOMETHING - Applications, maybe addition folders for Games and shared files like Codecs that are installed by the user. Applications may be common to both OSes. E:\ - Virtual Memory F:\ [G: H: ...] - User files N:\ - An NTFS partition (or physical disk) for large files such as when doing video editing. All partitions except one (or more if you have a monster computer with like 5 hdds) are FAT32 for interoperability. This partition structure enables you to make backup of you operating system and applications without worrying about swap and user files. User files are often large and are better backuped separately. It's not absolutely necessary to have applications on D. Though I find it useful myself. In case C: or D: gets fragmented your user files on other disks won't suffer. When you install applications you'll have to do it 2 times – for each system once. Except for programs that require NT, you obviously don't need to install the on 98. Some software use INI files in %Windir%. They may provide an option to pass the ini filename as command line parameter, so you can still share their config between both systems. I would also make common Start menus and the Desktop (later less important). This can be done using TweakUI XP by changing special folder locations to "C:\Windows\Start Menu" and so on. I have installed three systems this way. Takes hellalot of time and drives nuts since you have to do twice the work. But it can be done. This dualboot setup comes useful when you need to fix one of the systems. Just boot into the other one. No need for slow boot CDs most of the time. Example boot ini for this configuration: [boot loader] timeout=6 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Windows XP SP1" /noguiboot /fastdetect C:\bootsect.dos="Windows 98SE"

I haven't heard of good quality DOS soundcard & VESA video emulation, except VDMSound which I was unable to install properly. VMware 5.5 certainly doesn't have any good audio for Win98. The driver I found is unstable, has no MIDI, and no legacy support. Under VMWare the Windows GUI is does not work smoothly, so even if VESA was available it would play at least as jerky and unsuitable for gaming experience.

Win98 was used without a license on that computer. We found another machine, which happened to have a proof of purchase sticker on its case.

If you don't have a working system at the moment, you just install both OSes. If you already have WinXP installed and want to keep, it's more complicated. I find it best if both systems ar located on a single FAT32 partition. You will have to use nLite to modify installation path of Windows XP. First install Windows 98 to \WINDOWS and then Windows XP to say \WINNT. WinXP will see that the system contains DOS and will dump the current boot sector to a file called bootsect.dos. Later you can add an entry to boot.ini to use this file for loading Windows 98.

Things like this are usually done from a boot CD, so that nothing gets installed on any of the partitions in question. It's not morally worse to use an illegal boot disk compared to installing a trial version for the sole purpose of taking advantage of it (instead of evaluation). Cloning become easier if you have assigned individual partitions for your SYSTEM, PROGRAMS and FILES. In this case you clone only the OS (depending on if mobo is the same), only applications or opt to reoganize USER FILES by copying them manually. lol

The point was to have 2 systems working parallel, one clean and another possibly misconfigured. You could tell if complete reinstall would solve the problem. You don't need another partition AFAIK. As I said, from my experience WinXP and Win2k would create directories WINNT.1 and WINNT.2 if directed to the same existing directory WINNT.

To determine if the problem is in software configuration or network adapter itself you can install another clean copy of WinXP with only the network driver. Windows should install in different directory called WINDOWS.1 and you may switch back to the previous OS at anytime.

If they are not your computers, autorun might have been (should be) disabled for security.

Removed DHCP client might indeed be the cause, athough DHCP as such is not needed on the network. I will test this once I get the opportunity. Found out also about /SOS switch. It might provide some info on which specific file XP hangs. Minlogon is good since I don't approve multiuser PCs (personal computers). But this boot delay cannot be influenced by winlogon, as it happens way before logging on.

Yes, this pack is distrubuted along the driver. By installing it I got an older ADI (on i915) recognized under XP without an additional driver. But this is not possible with Realtek. One of the reasons for pushing the UAA (apart from possible user lock-in to WinNT and DRM) was to get rid of separate device drivers for every device. The crap is contained inside the driver itself. Core SYS file alone is 4 Megs. Maybe there is a way to modify the UAA so that it accepts ALC8xx. Basic audio output is enough. An enthusiast or audio expert would need proper soundcard anyway.

Is it possible to make Realtek onboard sound on HDA bus just work without installing the whole "HD" driver? Version R1.84 is 15 Megs compressed. I've come across integrated codecs by ADI and STAC. Both installed nicely using 500k and 100k drivers.

Load the system from a boot CD and have all files accessible. In cases like this when you need to patch WinXP it's handy to have a second os like Win98 installed. But boot disks work fine too.