VS 2013 Community ISO file size is enormous
-
Shoot. You just shifted my paradigm. :doh:
Well run it up the flagpole, and see if anyone salutes it!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
Thanks for the experience. I only have three words to say: MOVE TO PYTHON! Quickly!!
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
You can copy it to your USB-stick. You only have to 'unzip' your ISO-file and then copy the unzipped folder to your USB-stick; you'll see it'll work.
-
Thanks, but I've already reformatted the flash drive to NTFS and watching the copy nearing completion. I have no dual-layer DVD as I've never needed one before. I suppose there must be a downside to NTFS on a flash drive...probably won't work with '98 or something! :laugh:
"Go forth into the source" - Neal Morse
Well, vs2013 will not work on 98 either. No worry about that.
-
kmoorevs wrote:
'the file is too large for the destination file system'
Which probably means the flash drive is formatted FAT32 - so the maximum file size is 4GB. Reformat it to NTFS and the problem should go away.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
... or ExFAT if you want to make cross platform use easier.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
Um, when I first started playing computer games, it was 1K, not a whole meg! A meg was HUGE! By 'eck, it were Luxury!
I wanna be a eunuchs developer! Pass me a bread knife!
This is rapidly becoming that classic monty python sketch... "You had kilobytes?! Ooooooh....pure heaven. We used to have to fight over individual bytes to hold our data!" "Whaaaaat?? You had entire bytes?! Pah, your life was EASY...if we had a singular bit to call our own, we was happy." "Oh really!? My whole neighborhood shared a single floppy disk!" "HRMPH....you mean you had a computer?? Well..."
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
kmoorevs wrote:
...does anyone else consider 6.88GB to be bloated?
Nah... it's just feature-rich! (For the record: keep in mind that there is no such thing as a "bug" - everything is a feature!)
Anything that could possibly go wrong in some moment, will definitely go wrong in the worst possible moment...
In the worst way that could be possible!–Finagle's corollary to Murphy's Law (paraphrased).
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
kmoorevs wrote:
does anyone else consider 6.88GB to be bloated?
totally. But then again I read somewhere that most shops think disk space is cheap; I for one do not agree with this mentality. There feels like an ever increasing 'glut' going on. I try to keep the installs small (around 1mb or 2) and have optional add on installers for any extras someone may want.
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
-
You can copy it to your USB-stick. You only have to 'unzip' your ISO-file and then copy the unzipped folder to your USB-stick; you'll see it'll work.
-
That is why I and many more like me use Visual Basic 6.0. It is small (portable version ~6M) and very fast. :-D
-
I also still use VB6 for a lot of stuff. Too bad it won't install on anything past Win7. :(( I'm sure I will be needing a dedicated VM in the near future!
"Go forth into the source" - Neal Morse
Visual Basic 6.0 can be installed on any Windows: http://nuke.vbcorner.net/Home/tabid/36/language/en-US/Default.aspx[^] See more here: https://www.facebook.com/MicrosoftVB[^]
-
Visual Basic 6.0 can be installed on any Windows: http://nuke.vbcorner.net/Home/tabid/36/language/en-US/Default.aspx[^] See more here: https://www.facebook.com/MicrosoftVB[^]
-
To keep it short, I downloaded the VS 2013 Community ISO with the intention of burning to a DVD for my dad, who I'm driving to see in a couple of days, and who recently expressed a desire to try some hobby programming. I should have checked the size of the thing first, but it was on my laptop, and it was not on my bandwidth, and besides, I've done this before, and never had an issue. 5 hours later, the download finished and I now had a behemoth 6.9GB file sitting on my desktop! :wtf: Really? WTE have they packaged into this thing? (I did a search, but my google foo has failed) Well, that'll never fit on a DVD...time to get out the 16 GB (practically empty) flash drive...and fail! 'the file is too large for the destination file system' :wtf: This maybe an excuse to get a bigger flash drive, but still, does anyone else consider 6.88GB to be bloated?
"Go forth into the source" - Neal Morse
Your flash drive is formatted FAT32, which has a max file size limit of 4GB. Any larger flash drive will have the same problem. Change it to NTFS (format or use the convert command) and then it'll fit. You'll also get about 1/2 the write performance to it.. hence the FAT32. Oh, and you can only go back to FAT32 via a full format of it. OR.. go buy a dual layer writable DVD. It'll fit on that too and your burner can probably write to it.
We can program with only 1's, but if all you've got are zeros, you've got nothing.
-
Thanks, but I've already reformatted the flash drive to NTFS and watching the copy nearing completion. I have no dual-layer DVD as I've never needed one before. I suppose there must be a downside to NTFS on a flash drive...probably won't work with '98 or something! :laugh:
"Go forth into the source" - Neal Morse
kmoorevs wrote:
I suppose there must be a downside to NTFS on a flash drive
There is a fairly major one - to do the format in the first place, you have to turn on write caching for the thumb drive, which means you run the risk of losing data if you yank the drive without ejecting it first.
-
This is rapidly becoming that classic monty python sketch... "You had kilobytes?! Ooooooh....pure heaven. We used to have to fight over individual bytes to hold our data!" "Whaaaaat?? You had entire bytes?! Pah, your life was EASY...if we had a singular bit to call our own, we was happy." "Oh really!? My whole neighborhood shared a single floppy disk!" "HRMPH....you mean you had a computer?? Well..."
Atcherley, it's a sketch from "At Last, the 1948 Show", which was repeated (almost word for word) in a Python show by largely the same people (one notable absence being Tim Brooke-Taylor, who AIRI wrote the sketch).
I wanna be a eunuchs developer! Pass me a bread knife!
-
Wow! Thanks, I am bookmarking as I have a co-worker with a 8.1 laptop unable to open legacy projects. :)
"Go forth into the source" - Neal Morse
You're welcome :) Microsoft says that Visual Basic 6.0 is supported until 2024. This is cool to: http://vb6awards.blogspot.com
-
I remember whenever games console memory cards where 1MB, and you were outraged when a single game took up the full 1MB storage space (or close to it!) Now 40GB is meh.
I remember when I installed Turbo C for the first time and it took up half of my 40GB hard drive. I was pissed.
-
Up until last year, the largest game only required 20 GB. That's where most of them have been hovering. I've given up on buying games in the store, as cool as it is to physically possess something. When I install, its just going to initiate the download over the Internet anyway. I'm curious how much of that content is not related to the installer that needs to setup the correct environment. Then I'm curious how much of the remaining content is executable code and not embedded resources, configuration files, images etc.
Just a wild guess: the executable is several megabytes, with several dozen more for DLLs of auxiliary libraries. Most of the other things are audio, video, meshes and, most importantly *textures*. Those things really get huge and there is no meaningful way to reduce them in size if you don't want blocky graphics. Trust me, I'm a (game) engineer. As for VS, there is only one reason for it to be this big - code bloat of useless features that are very rarely used, but require multiple external libraries to be included
