Closed Bug 10359 Opened 27 years ago Closed 27 years ago

[8.3] raptor .DLL names too long for Win9x

Categories

(Core :: Layout, defect, P3)

x86
Windows 95
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: dveditz, Assigned: dveditz)

References

Details

Raptor .DLL names need to be 8.3 on Win9x. See bug 10355 They probably shouldn't say "raptor" anymore, anyway...
Blocks: 10355
specifically - raptorhtmlpars.dll - raptorplugin.dll - raptorgfxwin.dll - raptorview.dll - raptorweb.dll - raptorhtml.dll
Status: NEW → RESOLVED
Closed: 27 years ago
Resolution: --- → WONTFIX
I'm not the right one to fix this, plus I'm perfectly happy with the names the way they are now. If it's an installer problem, then let's fix the installer or get someone on the release team to help make the change
Status: RESOLVED → REOPENED
No it's not an installer problem, it is a Win9x problem. It has a mechanism for replacing in-use files, and that mechanism requires 8.3 names. Those are the OS rules, and we have to live with them. If you're not the right default contact for layout you should contact the bugzilla folks. If you are the right default contact then part of that job is reassigning bugs to the right people, not just closing them because you ain't it.
Status: REOPENED → RESOLVED
Closed: 27 years ago27 years ago
Status: RESOLVED → REOPENED
Troy: there is a legitimate problem here and saying "WONTFIX" doesn't make it go away. I can appreciate that YOU don't want to do the work, but you could at least assign it to someone else, or give permission for someone who cares to make the change. Since bugzilla thinks you own layout, are you saying - it's OK if someone else changes the name - don't change the name--and YOU will invent an alternate mechanism for the installer to get around Win9x lameness (we don't have time) or are we going to wait for this problem to surface in the Beta and THEN say "Oh shit"? If the first one reassign it to me, I don't care, but I'm not going to change layout code without some sort of permission from some sort of nominal owner.
- I question whether this is in fact really necessary. All filenames have an 8.3 name in Windows, even those with long filenames. Why can't you just use the 8.3 name, e.g., raptor~1.dll (or whatever the file system tells you it is), when replacing the DLL? - you have my permission to change the DLL names if you really need to
Unfortunately the MS implementation must be to delete the old file first and then copy the new file -- long file information is completely lost (at least on Win95, I should check Win98). This means .DLLs loaded from an import lib don't get found because they now have ONLY the mangled short name. Ditto for everything we regiser in the component registry, though that is theoretically under our control and could be changed.
Assignee: troy → dveditz
Status: REOPENED → NEW
Status: NEW → ASSIGNED
M9 would be great, M10 at the latest.
Resolution: WONTFIX → ---
Hey dp, weren't you gonna fix these overlong, trademark-abusing names? /be
Target Milestone: M10 → M11
Fixed 10/9
Blocks: 16654
Status: RESOLVED → VERIFIED
Based on Dveditz comments, marking as verified fixed in the Oct 21 build.
You need to log in before you can comment on or make changes to this bug.