Poop Adobe Poop
-
Those are the cross tools: compiler compiled for x86, compiling your code for amd64. Useful if you have some ancient 16-bit version of WISE Installer or some shit so you're stuck on 32-bit.
Filed under: Norton Utilities for Windows 3.11
-
A year or two ago, it didn't support JavaScript.
That was a Good Thing™ in my book.
There was no 64-bit 386, you young whippersnapper. Now get off @boomzilla's lawn.
There could be. Given a big enough hammer.
I would've sworn at some point there was an x86_64 and/or x64 target that didn't have "amd" in it but I can't find that.
There is something like that on some Linux distros. As in, that's how the packages are marked.
Actually, stuff like Debian packages use amd64 to list the architecture
I think they don't any more. Ubuntu might, I think multiarch is still disabled on it. Debian uses, from what I can discern, something like
lib32xxx-xxx.debthese days, or you can sayaptitude install package:i386to get the 32bit version on a 64bit system.
-
Debian uses, from what I can discern, something like lib32xxx-xxx.deb these days, or you can say aptitude install package:i386 to get the 32bit version on a 64bit system.
But I think that's still how the architecture is specified:
https://wiki.debian.org/IntroDebianPackaging
#Architecture
Specifies which computer architectures the binary package is expected to work on: i386 for 32-bit Intel CPUs, amd64 for 64-bit, armel for ARM processors, and so on. Debian works on about a dozen computer architectures in total, so this architecture support is crucial. The "Architecture" field can contain names of particular architectures, but usually it contains one of two special values.Try:
$ dpkg-architecture -L
-
Useful if you have some ancient 16-bit version of WISE Installer or some shit so you're stuck on 32-bit.
Hah, that is exactly the 16-bit app my company's stuck on.
They won't pay the $1500 or whatever the current version of InstallShield costs, and my boss almost gets hives at the thought of using NSIS, because it's Open Source, and what would happen if one of our customers had a problem? (He didn't like my point that the answer is "the same thing that happens now, since WISE is dead.")
Either way, we'd have to rewrite part of our application, because it generates WISE installation scripts, so we'd have to change that to NSIS format or whoever we went with.
-
That was a Good Thing™ in my book.
That's probably true. Except we produce a PDF a lot of our customers use that requires the feature (we spit out a PDF with form fields on it, and use JS embedded in the PDF to parse the query string to fill the fields) and that meant Chrome people couldn't use that feature...and it was an important feature, so we had to tell people "Chrome is not supported unless you disable it's built-in reader."
-
I went and checked VS 2005, which we have the full version of, on an old server, and it used amd64 too. I would've sworn at some point there was an x86_64 and/or x64 target that didn't have "amd" in it but I can't find that. Maybe it was an Express Edition.
I seem to remember that too (x86_64)... Either Express or the Platform SDK.
-
Go uses amd64 as an architecture. It also has amd64p32 for 64-bit processors that use 32-bit memory addresses.
-
my boss almost gets hives at the thought of using NSIS, because it's Open Source
Get your Epi-Pen ready: Orcas (the MSI editor) and WiX (a suite of XML-based MSI building tools) are open source! From Microsoft! Used for Microsoft's own installers!
-
They won't pay the $1500 or whatever the current version of InstallShield costs, and my boss almost gets hives at the thought of using NSIS, because it's Open Source, and what would happen if one of our customers had a problem? (He didn't like my point that the answer is "the same thing that happens now, since WISE is dead.")
Either way, we'd have to rewrite part of our application, because it generates WISE installation scripts, so we'd have to change that to NSIS format or whoever we went with.
Where's the
button?
-
Get your Epi-Pen ready: Orcas (the MSI editor) and WiX (a suite of XML-based MSI building tools) are open source! From Microsoft! Used for Microsoft's own installers!
I looked at Orcas once, too briefly to be able to make heads or tails of how to use it.
-
Ok, so at @boomzilla's suggestion I listed the platforms... Have a loooong list:
Architectures
``` onyx@jarvis ~> dpkg-architecture -L uclibc-linux-armel uclibc-linux-i386 uclibc-linux-ia64 uclibc-linux-alpha uclibc-linux-amd64 uclibc-linux-armeb uclibc-linux-arm uclibc-linux-arm64 uclibc-linux-avr32 uclibc-linux-hppa uclibc-linux-m32r uclibc-linux-m68k uclibc-linux-mips uclibc-linux-mipsel uclibc-linux-mips64 uclibc-linux-mips64el uclibc-linux-or1k uclibc-linux-powerpc uclibc-linux-powerpcel uclibc-linux-ppc64 uclibc-linux-ppc64el uclibc-linux-s390 uclibc-linux-s390x uclibc-linux-sh3 uclibc-linux-sh3eb uclibc-linux-sh4 uclibc-linux-sh4eb uclibc-linux-sparc uclibc-linux-sparc64 musl-linux-armhf musl-linux-i386 musl-linux-ia64 musl-linux-alpha musl-linux-amd64 musl-linux-armeb musl-linux-arm musl-linux-arm64 musl-linux-avr32 musl-linux-hppa musl-linux-m32r musl-linux-m68k musl-linux-mips musl-linux-mipsel musl-linux-mips64 musl-linux-mips64el musl-linux-or1k musl-linux-powerpc musl-linux-powerpcel musl-linux-ppc64 musl-linux-ppc64el musl-linux-s390 musl-linux-s390x musl-linux-sh3 musl-linux-sh3eb musl-linux-sh4 musl-linux-sh4eb musl-linux-sparc musl-linux-sparc64 armhf armel mipsn32 mipsn32el mips64 mips64el powerpcspe x32 i386 ia64 alpha amd64 armeb arm arm64 avr32 hppa m32r m68k mips mipsel or1k powerpc powerpcel ppc64 ppc64el s390 s390x sh3 sh3eb sh4 sh4eb sparc sparc64 kfreebsd-i386 kfreebsd-ia64 kfreebsd-alpha kfreebsd-amd64 kfreebsd-armeb kfreebsd-arm kfreebsd-arm64 kfreebsd-avr32 kfreebsd-hppa kfreebsd-m32r kfreebsd-m68k kfreebsd-mips kfreebsd-mipsel kfreebsd-mips64 kfreebsd-mips64el kfreebsd-or1k kfreebsd-powerpc kfreebsd-powerpcel kfreebsd-ppc64 kfreebsd-ppc64el kfreebsd-s390 kfreebsd-s390x kfreebsd-sh3 kfreebsd-sh3eb kfreebsd-sh4 kfreebsd-sh4eb kfreebsd-sparc kfreebsd-sparc64 knetbsd-i386 knetbsd-ia64 knetbsd-alpha knetbsd-amd64 knetbsd-armeb knetbsd-arm knetbsd-arm64 knetbsd-avr32 knetbsd-hppa knetbsd-m32r knetbsd-m68k knetbsd-mips knetbsd-mipsel knetbsd-mips64 knetbsd-mips64el knetbsd-or1k knetbsd-powerpc knetbsd-powerpcel knetbsd-ppc64 knetbsd-ppc64el knetbsd-s390 knetbsd-s390x knetbsd-sh3 knetbsd-sh3eb knetbsd-sh4 knetbsd-sh4eb knetbsd-sparc knetbsd-sparc64 kopensolaris-i386 kopensolaris-ia64 kopensolaris-alpha kopensolaris-amd64 kopensolaris-armeb kopensolaris-arm kopensolaris-arm64 kopensolaris-avr32 kopensolaris-hppa kopensolaris-m32r kopensolaris-m68k kopensolaris-mips kopensolaris-mipsel kopensolaris-mips64 kopensolaris-mips64el kopensolaris-or1k kopensolaris-powerpc kopensolaris-powerpcel kopensolaris-ppc64 kopensolaris-ppc64el kopensolaris-s390 kopensolaris-s390x kopensolaris-sh3 kopensolaris-sh3eb kopensolaris-sh4 kopensolaris-sh4eb kopensolaris-sparc kopensolaris-sparc64 hurd-i386 hurd-ia64 hurd-alpha hurd-amd64 hurd-armeb hurd-arm hurd-arm64 hurd-avr32 hurd-hppa hurd-m32r hurd-m68k hurd-mips hurd-mipsel hurd-mips64 hurd-mips64el hurd-or1k hurd-powerpc hurd-powerpcel hurd-ppc64 hurd-ppc64el hurd-s390 hurd-s390x hurd-sh3 hurd-sh3eb hurd-sh4 hurd-sh4eb hurd-sparc hurd-sparc64 darwin-i386 darwin-ia64 darwin-alpha darwin-amd64 darwin-armeb darwin-arm darwin-arm64 darwin-avr32 darwin-hppa darwin-m32r darwin-m68k darwin-mips darwin-mipsel darwin-mips64 darwin-mips64el darwin-or1k darwin-powerpc darwin-powerpcel darwin-ppc64 darwin-ppc64el darwin-s390 darwin-s390x darwin-sh3 darwin-sh3eb darwin-sh4 darwin-sh4eb darwin-sparc darwin-sparc64 dragonflybsd-i386 dragonflybsd-ia64 dragonflybsd-alpha dragonflybsd-amd64 dragonflybsd-armeb dragonflybsd-arm dragonflybsd-arm64 dragonflybsd-avr32 dragonflybsd-hppa dragonflybsd-m32r dragonflybsd-m68k dragonflybsd-mips dragonflybsd-mipsel dragonflybsd-mips64 dragonflybsd-mips64el dragonflybsd-or1k dragonflybsd-powerpc dragonflybsd-powerpcel dragonflybsd-ppc64 dragonflybsd-ppc64el dragonflybsd-s390 dragonflybsd-s390x dragonflybsd-sh3 dragonflybsd-sh3eb dragonflybsd-sh4 dragonflybsd-sh4eb dragonflybsd-sparc dragonflybsd-sparc64 freebsd-i386 freebsd-ia64 freebsd-alpha freebsd-amd64 freebsd-armeb freebsd-arm freebsd-arm64 freebsd-avr32 freebsd-hppa freebsd-m32r freebsd-m68k freebsd-mips freebsd-mipsel freebsd-mips64 freebsd-mips64el freebsd-or1k freebsd-powerpc freebsd-powerpcel freebsd-ppc64 freebsd-ppc64el freebsd-s390 freebsd-s390x freebsd-sh3 freebsd-sh3eb freebsd-sh4 freebsd-sh4eb freebsd-sparc freebsd-sparc64 netbsd-i386 netbsd-ia64 netbsd-alpha netbsd-amd64 netbsd-armeb netbsd-arm netbsd-arm64 netbsd-avr32 netbsd-hppa netbsd-m32r netbsd-m68k netbsd-mips netbsd-mipsel netbsd-mips64 netbsd-mips64el netbsd-or1k netbsd-powerpc netbsd-powerpcel netbsd-ppc64 netbsd-ppc64el netbsd-s390 netbsd-s390x netbsd-sh3 netbsd-sh3eb netbsd-sh4 netbsd-sh4eb netbsd-sparc netbsd-sparc64 openbsd-i386 openbsd-ia64 openbsd-alpha openbsd-amd64 openbsd-armeb openbsd-arm openbsd-arm64 openbsd-avr32 openbsd-hppa openbsd-m32r openbsd-m68k openbsd-mips openbsd-mipsel openbsd-mips64 openbsd-mips64el openbsd-or1k openbsd-powerpc openbsd-powerpcel openbsd-ppc64 openbsd-ppc64el openbsd-s390 openbsd-s390x openbsd-sh3 openbsd-sh3eb openbsd-sh4 openbsd-sh4eb openbsd-sparc openbsd-sparc64 solaris-i386 solaris-ia64 solaris-alpha solaris-amd64 solaris-armeb solaris-arm solaris-arm64 solaris-avr32 solaris-hppa solaris-m32r solaris-m68k solaris-mips solaris-mipsel solaris-mips64 solaris-mips64el solaris-or1k solaris-powerpc solaris-powerpcel solaris-ppc64 solaris-ppc64el solaris-s390 solaris-s390x solaris-sh3 solaris-sh3eb solaris-sh4 solaris-sh4eb solaris-sparc solaris-sparc64 uclinux-armel uclinux-i386 uclinux-ia64 uclinux-alpha uclinux-amd64 uclinux-armeb uclinux-arm uclinux-arm64 uclinux-avr32 uclinux-hppa uclinux-m32r uclinux-m68k uclinux-mips uclinux-mipsel uclinux-mips64 uclinux-mips64el uclinux-or1k uclinux-powerpc uclinux-powerpcel uclinux-ppc64 uclinux-ppc64el uclinux-s390 uclinux-s390x uclinux-sh3 uclinux-sh3eb uclinux-sh4 uclinux-sh4eb uclinux-sparc uclinux-sparc64 mint-m68k ```
-
Get your Epi-Pen ready: Orcas (the MSI editor) and WiX (a suite of XML-based MSI building tools) are open source! From Microsoft! Used for Microsoft's own installers!
Even better than Orca, InstEd (they have a free and pro version - the free version rocks).
-
I looked at Orcas once, too briefly to be able to make heads or tails of how to use it.
It's a good tool for debugging what may have gone wrong in the msi build process. Or for a quick test where you want to change the condition on a custom action without rebuilding the msi.
-
What has this to do with the fact that it freezes up my pc?
If the option is still there, have you tried to enable or disable flattening and rasterizing of the pages before sending it off to the printer? That used to be a compatibility option for printers that completely hung up on complex PostScript or had bugs in certain features and would output gibberish.
Reader is possibly trying to read PostScript features of the printer or use unsupported or badly supported features and is somehow locking everything into a busy loop that eats your CPU cycles. Could be due to Reader, could be due to the printer driver.
As mentioned by others, it could also be the other way around: Reader could be trying to stuff a massive rasterized graphic to the printer. My personal experience is that if the option I mentioned is enabled, it rasterizes things on a page-by-page basis though. Maybe try editing the print DPI?
-
It's a good tool for debugging what may have gone wrong in the msi build process.
I'm not sure, but I don't think WISE even built MSI-based installers. We use...looks like the manual says version 6. Yes, that ancient look turns off customers a bit. No, I can't convince people above me that that matters.
Semi-funny related thought: A potential customer claimed our software looked dated (it does, a bit) last year, partially because the installation instructions use Windows XP screenshots. I don't know why you'd judge software on that, but I told the person who maintains those files that when she updates them next--which she's doing now--to pass 'em on to me when she's mostly done, and I'd retake all the screenies in Win 10, and let people complain they look dated then.
-
It's a good tool for debugging what may have gone wrong in the msi build process. Or for a quick test where you want to change the condition on a custom action without rebuilding the msi.
Also: that sounds pretty useful.
IIRC NSIS doesn't build MSI-based installers either. That was the only installer other than WISE I've ever used myself.
-
I'm not sure, but I don't think WISE even built MSI-based installers.
Sorry, I'd moved on to what Orca was good for (msi), not your process. So, yeah, orca/insted are pretty much useless for you. (Personally, I've never used NSIS or WISE. whew. When I was at VMware, we were migrating from InstallShield to WiX)
-
Sorry, I'd moved on to what Orca was good for (msi), not your process.
Oh, no problem. I'm considering what we do in the future, because eventually MS will probably making 32-bit client windows the way they stopped making 32-bit server versions. We're already at the point where the guy who does the build does it in a 32-bit Win7 VM.
-
Then there's this whole win32-apps-in-Windows-Store thing that's rather intriguing...
-
TRWTF is that that binary is even present in what should be a linux 64-bits install directory.
man -- how did you get a pre-ELF SPARC binary on an x86_64 Linux box?This is likely an issue with the particular PDF and your printer driver being miles apart. Windows' driver model lives and breathes PostScript.
PDF is basically heavily extended PostScript, so the PDF reader has a pretty straightforward job.
PostScript is very good at vectors and text, but absolutely terrible at raster graphics. The PDF reader has to transliterate your raster graphics into a rather shit bitmaplike format.
Many printers don't do PostScript. Their driver has to convert the PostScript to whatever the fuck they do support. Many of these choke on raster graphics beyond a certain size.
Pretty much...
-
man -- how did you get a pre-ELF SPARC binary on an x86_64 Linux box?It's in a utilities directory on a mounted NFS share. I think everything else in that dir is shell scripts so it probably got grandfathered in somewhere.
I still agree that both the fact that binary is present and the fact it's in the $PATH are
-
And then turned around and used the Intel based name for everything anyways.
Only kinda. "amd64" is somewhat common as FrostCat says, but even more than that, I consider "x86" and "x86-64" to be pretty generic. And basically no one outside of Intel uses the names Intel tried to give it, EM64T or IA-32e (or even "Intel 64", which is apparently the official moniker now).
-
It's mostly heavily restricted. All the fun things that make PostScript a real (but really annoying) language are turned off in PDF.
Instead some moron added embedded Javascript.
But PDFs have a shell execute functionality!
-
And basically no one outside of Intel uses the names Intel tried to give it, EM64T or IA-32e (or even "Intel 64", which is apparently the official moniker now).
I don't think I used those even when I was inside Intel.
-
How do they fit a @HardwareGeek inside 410 transistors?
-
A photo caption in a previous version of this story incorrectly stated that the Core 2 Duo processor with 410 transistors made its debut in 2002; it actually made its debut in 2008
Looks like they've now noticed the silly transistor number as well. Fun's over
-
Or as a placeholder for 2, 3, 4, then there was apparently 80586 named Pentium, 80686 stood for Pentium Pro's architecture, and then it seems Intel gave up with numbering.
Don't forget the 80186. That guy is 16 bit though.
-
Microsoft Office Word is an application/program. WinWord.exe, EquEdit.exe, WordArt.exe, and the other one I'm forgetting, are
programsexecutables that make up the Word application/program, with WinWord.exe being the main one.At least that's how I use the terms.
-
80x86 means "any one of 80186, 80286, 80386, etc, possibly including the 8086".
80x86 does not mean the 80186. That wasn't a compatible part in some crucial way (that I never really understood, and haven't been bothered about for at least 20 years). We had 80186 machines at school — I think they were RM Nimbus systems — and all I know for sure is that they really sucked and I tried to avoid using them.
-
It has no mmu as far as I remember.
-
There was some way in which they weren't compatible with the 8086 too, and that also didn't have an MMU. It was just enough to cause problems; you couldn't copy code from one to another and hope to have it work.
-
There was some way in which [80186 processors] weren't compatible with the 8086 too, and that also didn't have an MMU. It was just enough to cause problems; you couldn't copy code from one to another and hope to have it work.
According to Wikipedia it's an "integrated hardware" incompatibility issue:
I have no idea what that means though.
-
-
I have no idea what that means though.
Wikipedia says it was intended to be used as a microcontroller, so it contained a clock generator and a bunch of other features that normally would've been implemented as separate chips.
That would mean a pretty hefty motherboard redesign back then, probably.
-
Also, TIL Intel didn't stop producing the '386 until 2007.
-
Fun fact : It was a problem for NASA with the 486 because they needed them in the shuttles.
Afaik they resorted to buying them on eBay..
-
According to Wikipedia it's an "integrated hardware" incompatibility issue:
Yeah -- the '186 has built-in peripherals for things like interrupt handling, DMA, chip select decoding, clock generation, and a few other things (newer variants even had an on-board UART hanging around), but none of them are PC-compatible (the I/O port map is rather different).
Intel 80186 - Wikipedia
