How To View Compressed Zip File

0 views
Skip to first unread message

Ilse Marseau

unread,
Aug 3, 2024, 12:19:04 PM8/3/24
to twanacovgroc

The compressed file will look like rubbish (except for entry names in .zip archives for instance). You can open it in any text editor. If the contents are not looking random, the compression was very unefficient - or there was no compression at all (e.g. format "Store" in .zip archives).

There are many ways to view the contents of a compressed file without extracting/decompressing it. That all depends on the type of compressed file it is and which applications can support it. There are probably hundreds of different compressed file types and thousands of applications that can read them, so an exact answer to this question isn't possible.

Hey guys im having a problem opening folders I have downloaded from dropbox. I have since deleted it from dropbox (so cant try reloading the files). I have tried opening it 3 on different computers and im getting the same message. I tried using both windows 7 and windows 8.1

How big is this Zip file? Dropbox is known to have problems creating Zip files larger than 1GB or so. If you're using the built-in Zip support that Windows has, I would try a program like WinRAR, 7Zip or WinZip. Otherwise you may be out of luck.

Same here. Only, my compressed folders are from 1 to 116 MB. Not very large... I can't open any of the files when extracted, all broken. Pictures, txt files, pdf files, html files, mp3 files, nothing opens...

A strange thing happed to me... I've kept the broken zip archives - and they all work now, four weeks later. I changed my OS in the meantime (Mint to Ubuntu) but I don't know if that made any difference... I tried extracting one file at a time and all at once and it works, no problems whatsoever. Maybe you should try extracting one file at a time from the broken archive or something like that, or change the OS xD

Thanks so much for this answer. It worked for me and i have recovered hundreds of photos from my travels. If you are ever in nz let me know and i will buy you a beer!

Big shout out to mactorque who sorted it for me since i can hardly even turn a Mac on!

Its crazy that dropbox was not able to help with this issue.

Before you posted this I managed to get in touch with dropbox customer support which took a bit of hunting! However they repeatedly told me the fault was my doing, didn't believe what was happening to me and offered no solution!

Thanks so much!

We have some tables that are extremely big. I can only see a view of that table and it takes usually about 15min to query from that view. I would like to find if there is a better way of using it to get results faster.

My understanding of SAS storage is that if variable is defined as 4000 characters and it only contains 4 character it will still use 4000 bytes on disk if it is not compressed or actual length of 4 bytes if it uses compress.

Is there a way I can improve speed for querying from my original view that takes 15mins? Initially I thought that querying from view that says data is not compressed (proc contents) is making things slow, but after doing my own test it doesn't look like it is any slower. What am I not understanding correctly here?

Note that I added quit statements, so that the NOTEs follow the code immediately (important for the last step, or otherwise the NOTE is triggered by the "magic line" that EG sends, and only appears after other code).

As for the compression: That's on disk and it saves disk space and disk and eventually network i/o which is normally the slowest bit of your process. The variable gets still fully expanded/uncompressed when loaded into memory/PDV (and this expanding actually adds CPU overhead).

The only explanation I'm having why in your test using the view was that much quicker than using the physical table is that the data must still have been available in the disk cash and for this reason i/o was much quicker.

I have ran all the examples again and this time I got the same results as you. Querying from view with compressed underlying dataset gave me the same timing as querying directly from compressed dataset.

Content-encoding still showed as gzip, but the response size in postman is always uncompressed/original response size. This made me wonder is response compressed or not. Only after checking in chrome realised, Postman always showed uncompressed response size.

Wanted to know why postman always shows uncompressed/original response size..? Is there a option to view compressed response size in Postman..? or Is postman not the right tool to measure response size..?

Postman is actually using Jquery-style stuff to POST/GET/PUSH... data, then show result somehow. and the Network tab is not always working well. In my case, it never shows once how much data was transferred back, same in my teammates' environments.

After the iOS updates the items on my screen are compressed horizontally by about 30%, leaving very wide margins on right and left sides of screen. I have changed the icon/information size without any difference being noted. Besides wasting a lot of space it looks really stupid! Any ideas?

While all of this is comforting, there does remain one minor drawback. A new tighter screen estate design, imposed by iPadOS 15, now means a small portion of your iPad Home Screen will be compelled to stay barren when the remodelling methods detailed here are deployed.

Nevertheless, many iPadOS 15 Updaters believe it is a very small price to pay to expand and restore all their cherished and carefully curated Home Screen icons to how they were previously arranged in previous iPad operating systems.

As such, it is all good news. Once you have completed the steps detailed below, you will then be able to enjoy the swish popular elan of the iPadOS 14 5x4 20-icon grid pattern as now combined with truly brilliant new features in iPadOS 15.

But before getting started, take a long look at the screenshots below. Make special note of the 12mm horizontal minimum gaps between icons in the iPadOS 14 Home Screens. Now compare those gaps to the tightly compacted 4mm horizontal gaps in iPadOS 15 that contract when Updaters remove their widgets.

5. Drag Post-it app to separate Home Screen page. Open App. Tap Create. Tap small default yellow note. Tap personal colour choice from fanned deck. Tap Add + . Tap Cancel. Tap chosen colour square. Tap hollow star. Check star has turned solid black. Quit and forget main Post-it app.

6 Touch and hold Home Screen workaround page. Tap +. Open Post-it widget. Select Single Note widget style (as shown arrowed below). Tap Add Widget. Repeat Tap +, Open Post-it widget, Tap Add Widget sequence until four widgets are added.

7. (1) Rotate iPad to portrait view. (2) Drag four widgets to top of Home Screen workaround page. Tap Done. (3) Use iPad in any orientation. (4) Icon herders can be placed to left or right in landscape view or top or bottom in portrait view. (5) Screenshoot icon herder colour as wallpaper to make them vanish.

After developing the above techniques in October 2021, I have since made further advances with onscreen photo apps that can make icon herder widgets completely invisible against any original screen wallpaper of choice.

When I am in a meeting, all the participants' faces look wrong -- they are either very small or compressed depending on the view -- and this is making Zoom unusable. I have searched Google, Support, the Zoom Community, and used the Zoom Chatbot and haven't found a solution to this.

In Gallery View, faces only take up the top left portion of the yellow box and are very small. They are not filling the entire yellow box, but are taking about 1/8th of the space. Faces are only about 1" wide.

In Speaker View, the speaker's face looks normal and takes the normal amount of space. But the other participants faces along the top of the screen are extremely compressed such that I cannot identify people. Each person's face is about 1/2" wide when it should be much wider. I have example screen shots of both scenarios, and both occur when the Zoom window is maximized or not.

c80f0f1006
Reply all
Reply to author
Forward
0 new messages