LoneCrusader

Unicode if I remember correctly...

I have not attempted altering the Tape Detection entries in the registry yet, but I will look into it further later tonight. I'm not using the USP, but I'm using my own slipstreamed build of 98SE that contains many of the same things... I always have that tool selected when I install 98SE. No particular reason, I don't use it, but I guess it sounded nice. Strange that the results are different on different machines for the exact same hardware. We need to test this file on a wider range of hardware. My only testing so far has been in a VM. Well, I'm an Aries so maybe that explains something as well...

Yes, far too much information has already been lost. For the record, the old Borland Resource Workshop 4.5 can be used on many of the older type files, but it crashes when trying to load SYSDM.CPL. I have no programming experience, so writing my own tool would be out of the question, lol. Never seen anything like that before. Only the Tape Device icon on my system. The only place I've seen that Icon (19 in SETUPX.DLL as well) associated with USB is under Windows 95. Windows 95 does not contain a USB Icon or SETUPAPI.DLL by default, so it defaults to Icon 19 instead of Icon 20. I think we should examine the .INF's for Tape Detection and USB2 to see if something "similar" is being set for these devices that might cause overlap... ...or maybe that's a dumb idea... if INF's are causing it it SHOULD be present with the 98SE version...

No, I didn't find the source of the icon problem. But, as it affects all ME versions and is not caused by a Mod, I figure we will address it as a new project, but still within the scope of this discussion and thread. I have however, after much trial and error, managed to get all of the ME specific items removed and strings fixed. (The story...) I discovered that my original versions 1-3 modified with eXeScope did not suffer from the "New Hardware not centered" bug. It was only with version 4, when I started using Open Watcom, that the bug appeared. I opened the original ME HotFix file with Open Watcom and saved it without making ANY changes. Then I compared the original and the saved version with a Hex Editor. Open Watcom added 32 sequential bytes of rubbish, nothing but NULL characters, into the file and changed 222 other bytes (increased all by 2 dec.) that I assume are some type of data "offsets" or "addresses" for the rest of the file. The file now had the "not centered" bug. I took my v03 and modified ONE single item with Open Watcom (unchecked "Visible" for the "Disable System Restore" option) and saved it. Then I compared that file against my v03 with a Hex Editor. Open Watcom had added 16 bytes of rubbish this time, along with the "offset" changes, but I was able to figure out which 2 bytes had been changed that were important. I returned to my v03, and used the Hex Editor to change ONLY those two bytes. This file worked properly, with the "Disable" option hidden, and no "not centered" bug. I repeated this process, changing things with Open Watcom; comparing the changes against the file modified directly with a Hex Editor; figuring out what bytes were relevant; and then applying them to the Hex Edited file. It took a while, but I now have all of the ME options hidden, all of the ME strings changed to 98, and no errors caused by modding that I am aware of. This file should be tested thoroughly as well though. SYSDMCPL.ZIP - V06

What, no testers? Maybe I should just not post the new, final, fixed version?

I've retested my previous v01, v02, and v03 files. They do NOT have the "not centered" bug on my system. I'm reposting a link to my v03. Please retest and see if you all are still getting the "New Hardware not centered" bug... EDIT: V03 link removed.

All of my modifications were done on the original file extracted from the ME HotFix rather than the one extracted from NUSB, although I'm sure they're identical.

Bizarre. Neither the original USB Icon nor the Icon I'm seeing are present in SYSDM.CPL at all. I agree one problem at a time, but I went ahead and mentioned it because whatever is causing it is already in the official ME version and is not caused by a mod...

I have checked my original "version 01" that was done with eXeScope and contained only modifications to the System/General tab (Dialog 503). It does NOT have the bug. Since this is the case, and the special version I sent to PROBLEMCHYLD DOES have the bug, then it must have been caused by the String edits. (special version is v01 mods {general tab} + v03 mods {strings} without v02 mods {sys restore disk slider}) I'm still investigating. @PROBLEMCHYLD Could you check something else for me? In the screenshot you posted, I see an Intel USB controller is being reinstalled. I have the exact same controller on the VM I'm testing with. When that particular device is reinstalled, does it show a normal USB Icon in the Device Manager when using the ME SYSDM.CPL? I'm seeing a different Icon for it when using the ME version than the normal USB Icon I see with the 98SE version... @dencorso I didn't expect this issue to be so involved or require so much work. I don't want to hijack this thread, so it may be best to split my original SYSDM.CPL post (#732) and the rest of this off into a new thread, say, "Modified SYSDM.CPL 4.90.3001 for 98SE"?

Thanks Strange.. I didn't touch any of the other dialogs. I will look into this, don't know whether I will have any results tonight though, I have some important things to do early in the morning. Stay tuned! EDIT: Examined the 98SE, ME, and my "Final" versions in Open Watcom and eXeScope. No differences are apparent in the affected dialog between the three versions, and the "Test" mode for each file in both programs displays the dialog properly in the center of the screen. The "Center" attribute is set for the dialog already in both programs. Disabling and reenabling it with Open Watcom results in a binary-identical file as the "Final" version and the same bug. Disabling and reenabling it with eXeScope results in a file with 2 bytes different from "Final" but a worse bugged dialog with the icon missing. :wacko: @PROBLEMCHYLD I assume that the special version I sent you has this bug as well? If that's the case then this bug is caused by changes back in my 1st or 3rd version and has been carried over to the later versions. No idea what is causing it, but I'm going to start completely over tomorrow using Open Watcom for all changes rather than eXeScope.

I'm working on the final version right now. Thanks loblo, Open Watcom seems to do the trick with SYSDM.CPL renamed to .DLL I will edit this post with a link to the "Final" version for testing as soon as I'm done. EDIT: Here's a link to the Final version. {Old link to Bugged File Removed} File version number has been increased to 4.90.3002, but note that this file is customized for 98SE ONLY. Do NOT use with Windows ME. It contains nothing useful for Windows ME and has ME-specific items removed. All changes to this file have been cosmetic, but it should be tested in various situations, such as: removing and installing devices/drivers, and enabling/disabling items on the various "File System" dialogs to be sure there are no unseen side effects. Report any and all bugs here.

My original linked version in my first post about SYSDM.CPL (timestamped 3:00:00 AM, it was my own internal 3rd version) has all of the modifications to make the file correct for 98SE with ONE exception - the "Disable System Restore" option is still present on the Troubleshooting dialog. ONLY the bare minimum of modifications required to make the file correct for 98SE were made; I didn't even increase the version number (will leave that for when this is finalized.) My goal is to get that one thing hidden, with the minimum amount of changes possible, and I will consider it to be "final." Any other modifications would be up to users. {offtopic} IIRC, PROBLEMCHYLD, you use a backported version of ME's System Restore on your own 98SE don't you? If you like I will take one of my older builds and only modify the System/General Tab and the Strings so that you can have & use the System Restore controls on your own system. {/offtopic}

Ok, that's cool. I fully support "personalization" but I prefer it be left up to each user. Some Icons I update on my own 98SE, some I don't, etc etc. As long as there is a "bare minimum" modification version in existence before other changes are made, I'm happy.

So this version only has two changes - remove the WS_VISIBLE style and rebuild the CDROM icon, right? Now eXeScope is reporting bogus sizes and color depths for the CDROM icon. - all sizes reported are "rectangles" not "squares" and it claims they are all 4 or 8 colors. I have frequently seen icon depths "out of order" on other 9x files, why would it be causing a problem now? Please no. Why does someone always have to "personalize" these things? Not everyone wants their icons or their bitmaps changed. Why can't we just get a simple, plain version with no changes other than the ME specific tools and "styles" hidden and the 98SE "General" tab restored (all of which is already accomplished by my first linked version except hiding the "Disable System Restore" option) before someone starts personalizing it?

Here's another copy with all of the Dialog sizes edited to exactly match the 98SE version. (I open 3 windows of eXeScope, one with the 98 version, one with the copy I'm actually editing, and one with the ME version so I can always see what is different and what the original setting was.) The Troubleshooting Dialog is of course messed up in this copy because of the size edits. But, a minimum patch to this copy should result in a Dialog exactly like the 98SE one. EDIT: Removed old link.

Good job, looks like you successfully eliminated the Disable System Restore option ..But too many changes at once If you change the size of the group box for that dialog, you must also shorten it for the "Hard Disk" Floppy Disk" "CD-ROM" and "Removable Disk" dialogs as well, because now they are all truncated at the bottom. I had planned to just hide the option, making the absolute minimum changes necessary to get a 98SE-correct version. Then later mods would be up to users. Edit: Also noticed that somehow the CDROM Icon on the CDROM dialog is messed up somehow. Don't know what would cause that. I do agree that the dialogs should be shortened to be equal to the 98SE version. I just like to do things one step at a time and test each step. It took me 3 versions to get to the one I posted.

eXeScope is the only tool I have that will open SYSDM.CPL so I'm limited to what it allows me to do I can't edit the text, unless I tried directly hex-editing it... Repositioning might work, if one could make sense of the positioning coordinates for the other options. Many of them are negative. I can't resize the box because it doesn't seem to be treated as a text box. A bit over my head, I'm no programmer. eXeScope has a checkbox for "Visible" on this item, but it's already not checked by default. (Tried this because it worked for the slider bar on the other dialog.) Thanks for the help guys.. any more ideas?

I have modified the Windows ME SYSDM.CPL 4.90.3001 to correct a few cosmetic errors when it is used under 98. Not perfect yet, but what I have changed so far seems fine. Need some testers and maybe someone can fix the one thing I've not been able to? Changes so far: - Fixed the General tab under System to show "98" and "Second Edition" instead of "Me" - Removed System Restore disk space slider bar from the File System / Hard Disk dialog. - Fixed all Strings to read "Windows 98" instead of "Windows Millennium Edition" What needs fixing: - Remove "Disable System Restore" option from the Troubleshooting tab. (everything I've tried messes up the rest of the Dialog) Comments anyone? EDIT: Removed old link.

Had about 6 inches of very wet snow here. Thankfully the power stayed on, but my internet has been out all day. At least it's back now

I extracted the package with Universal Extractor on an XP machine. submix8c is right, all of the .INF files have "Signature="$Windows NT$"" and the package makes no mention of 9x/ME anywhere inside. However... It looks like all this package (and the last working package for 9x) contains is a bunch of .INF and .CAT files. Unless I'm missing something here, all one should have to do is modify the .INF's to be 9x-compatible (as xrayer has done), because the only purpose they are serving is to specifically identify the devices on the motherboard. I'm not seeing any .SYS files or the like that would require Windows 2K/XP for compatibility. The real problem would seem to be finding drivers for video, sound, ethernet, and other integrated devices that actually have driver files other than .INF's. (Or am I REALLY missing something here?? )

IMO there should be two separate categories here. One for "working" hardware that can run, but doesn't have a full set of drivers, and another for "compatible" hardware that has a full set of drivers. I would consider having to use the VBE9X driver a serious limitation. It's a good driver, and has many uses, but the lack of being able to use non-full screen DOS boxes is an irritating problem. (Sorry I don't have more to add at the moment guys, I need to see if I have any hardware laying around that uses these chipsets and find the time to do some testing. I've been content to build all of my 9x systems with 845/865/875 chipsets so I haven't looked into the issue before.)

Examine SHELL32.DLL with Resource Hacker. I don't know what would cause the particular condition you've found, but you can examine the Shortcut Arrow Bitmap in the .DLL and see if it has been altered...

Adding the ME USB 1.1 stack enables the use of USBCCGP.SYS. (Remember RetroOS's USB Composite Device experiment?) However, if changing the USB 1.1 stack is going to cause widespread problems, then it is best to revert back to using the updated 98SE stack. Using the ME stack can be reserved to use in specific situations only, or can be added during a fresh install as I outlined above if desired.

Hmmm... Well, I do have an idea that should solve the issues at hand and keep you from having to remove all of the USB updates. (rloew please comment on this and confirm whether or not it should work ) Replacing the USB 1.1 drivers seems to be causing this issue. If you revert back to the Windows 98SE USB Updates/HotFixes for USB 1.1 WITHOUT using the Windows ME USB 1.1 stack (back to NUSB 3.3) and remove my combined USB.INF, then users should not have to remove USB 1.1 devices & controllers and should not have this problem. Having the updated 98SE HotFix versions is better than having no USB updates at all, and this would prevent you from having to remove the USB2 and USB Storage files. If users want to use the ME USB 1.1 stack then they will have to have PS2 Keyboards & Mice, or they will have to put the combined USB.INF & ME USB stack in their \WIN98 folder when doing a clean install. (This would override the 98SE versions from the beginning, leaving no errors from changing them later.)

Try this package. I can't say for sure that it supports that particular chip, but I believe it does. I once tried to install Windows 98SE on a Compaq computer that had this particular motherboard for a friend of mine. It was a nightmare. At the time, I was never able to get everything working correctly, but it's been so long ago I don't remember what the problem was.