Thread View: comp.sys.next.misc
3 messages
3 total messages
Started by Jon H. Bohlke
Wed, 12 Aug 1992 01:27
ModPlayer?
Author: Jon H. Bohlke
Date: Wed, 12 Aug 1992 01:27
Date: Wed, 12 Aug 1992 01:27
6 lines
598 bytes
598 bytes
Hey, How do I unpack this stuff? I have this ModPlayer.squfold file, what utility do I use? Jon
Re: ModPlayer?
Author: David Lemson
Date: Wed, 12 Aug 1992 02:26
Date: Wed, 12 Aug 1992 02:26
16 lines
1055 bytes
1055 bytes
bohlkejh@NeXTwork.Rose-Hulman.Edu (Jon H. Bohlke) writes: >Hey, > How do I unpack this stuff? I have this ModPlayer.squfold file, what >utility do I use? Use 'UnSquashOnly', available from the pub/next/2.0-release/binaries directory on sonata.cc.purdue.edu. I think this probably belongs in the FAQ (what to do with a .squfold file). -- David Lemson (217) 244-1205 University of Illinois NeXT Campus Consultant / CCSO NeXT Lab System Admin Internet : lemson@uiuc.edu UUCP :...!uiucuxc!uiucux1!lemson NeXTMail accepted BITNET : LEMSON@UIUCVMD
Re: ModPlayer? (Plus commentary)
Author: Gordon Van Huizen
Date: Wed, 12 Aug 1992 17:00
Date: Wed, 12 Aug 1992 17:00
39 lines
2270 bytes
2270 bytes
In article <1992Aug12.012734.5064@cs.rose-hulman.edu> bohlkejh@NeXTwork.Rose-Hulman.Edu (Jon H. Bohlke) writes: > > Hey, > How do I unpack this stuff? I have this ModPlayer.squfold file, what > utility do I use? > > Jon It's compressed with a utility called Squash. A free-ware decompressor called UnSquashOnly is available on the archives. There are some comments in the MOD Player FAQ (which is by now a decent candidate for sumbission to the archives itself) about which mode of UnSquashOnly to use (I believe it's Extract Bundle). THIS IS EXACTLY WHY using non-standard file compression techniques is problematic. How many times has this question been asked now about this ONE file? While the goal of shrinking files as much as possible is a noble goal, it leads to all this confusion. My guess is that the net bandwidth of answering questions about files compressed by alternate compressors is larger than the amount of bandwidth saved by using a tighter compresstion technique! And the ironic thing is that it's EVERYBODY'S resources being affected - not just the supplier and user of the compressed file. Is this REALLY in our mutual best interests? A note in the README file about how to decompress the thing would be some help, but only if the README file gets downloaded/shipped around/read. Things like Squash are great as long as all parties concerned are aware it's being used. But out in the open world I think the benefits go to waste. Maybe if the extension was UnSquashMe... :-) Gordon -- ---------------------------------------------------------------- Gordon Van Huizen vox: 619.488.9411 fax: 619.488.3045 Metrosoft gvh@metrosoft.com [NeXTmail welcome] ----------------------------------------------------------------
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads