Search the Community
Showing results for tags 'file'.
-
There has been many threads and topics devoted to the colors of WinVice on a variety of forums; particularly for the NTSC region. The developers have certainly done tremendous work with the emulator and it is commendable. Even relatively recently, the following was performed respecting the video display: http://www.lemon64.com/forum/viewtopic.php?p=596300#596300 It brought contrast and saturation to a default value of 1.250. It makes the current NTSC default display appear as follows: While indeed appreciated as a rather 'dull/muted' look is part of the issue with the way the NTSC display appears, there is another issue which was brought up previously that cannot be corrected properly through the video options offered via WinVice. The default red and blue ratios are not what many NTSC users experience. The worst and most evident being the amount of red applied to blue as noticed on the boot screen, but there are other issues as well. The testimony of many NTSC users on these boards as well as numerous online examples of the actual NTSC hardware running on official Commodore equipment (I.E. 1702) as well as other CRT displays makes this clearly evident: A shift of the tint value (More green/less red) will correct this (improperly) to a degree, but it also impacts the entire palette and will cause greys to look greenish as well as a slew of other undesired adjustments. Again, the main issue is red and blue ratio values, not something a tint/hue control can address the right way. So here is hopefully something to assist those NTSC users. This is not hand-picked or manually manipulated palette colors. Rather we take the default.vpl file values from WinVice and offer up the following comparison: Quickly looking over the chart especially the first three (Default, Default15, Default30) one may not notice much if any difference, but there is as we compare the various boot screens with the default and variety of ratio adjustments using the default user adjustable video option values of WinVice. *Note: All screen captures going forward are in the following order: default.vpl default15.vpl --> default30.vpl --> default15-15.vpl --> default30-30.vpl. Once an individual can figure approximately where their display falls in the spectrum, then other adjustments can be applied (Contrast, Brightness, Saturation, Tint). Here is what further difference the boot screen can appear with just contrast bumped up: You'll notice from the boot screen that the default15 and default15-15 does not appear to look different; ditto with the default30 and default 30-30. To truly notice the full range of what has changed and not changed (Or hardly changed) let's take two popular titles utilizing again the default user video option values: Bruce Lee G.I. Joe The differences from default and the four new default values should hopefully be much clearer. The issue (red/blue portions) is not unique to the C64 under the NTSC region. All three Atari systems (2600/5200/7800) and the NES (Both with vastly different ways of how their palettes are generated) experience a similar phenomenon. The only proper way to address it is with the option of modifying red, green, and blue ratio proportions, once a set of default values are obtained from the appropriate performed calculations. You'll notice that the percentage of 15% and 30% were utilized. Every 15% is where a very significant difference becomes apparent as highlighted in the captures. A higher percentage is possible but evidence of any online examples or personal experience of the ratios within a range greater than 30% is lacking. How to apply the different palettes: Copy the palette files to the C64 sub-folder found within the main folder where the main executable resides. (I.E. C:\WinVICE\C64) After copying the files you normally should be able to select them via the GUI interface: 'Settings' --> 'Video Settings' --> 'VICII Palette' tab. However, that appears not to work. An easy method is to just open the vice.ini file (Found in the main directory where the executable resides - i.e. C:\WinVICE) with Notepad and about a third of the way down you will find two lines: VICIIPaletteFile="default" VICIIExternalPalette=0 Change "default" to one of the new default files and change the 0 to 1. So for example if you wanted to try the "default15-15.vpl" file, the lines would be modified to: VICIIPaletteFile="default15-15" VICIIExternalPalette=1 Please make sure you save the file. Proceed then to launch WinVice and make whatever additional video changes you desire - contrast, brightness, saturation, etc. It would be wonderful to perhaps see these options/values incorporated and included in the WinVice distribution. To assist further and in aiding any who believe or desire to make manual adjustments to the default calculations here is the complete chart of palette values: Download the chart in Excel format here: CHARTDELTAS.zip Finally, the four new default palette files for WinVice can be downloaded here: WinVice_Default_Palettes_20131207.zip
-
I am writing as an ancient original TI user, not adept with hardware and very fond of the original TI concept of plug n play. Not keen on changing the original hardware. My original iron works, I have a sidecar 32k, and FG99. My ancient TI floppy drives are now temperamental and unreliable (the original disks even more so). I can write TI programs with emulators, but I am not able now to reliably write programs and save them or use programs that need disk storage on the original hardware. I have kept up as best I can with the TIPI project and deduced this is absolutely not for me - I don't have a Windows machine, and its setup and use has been written up to be horrendously difficult. The MBX works (which is an external CPU), it just plugs in and works, no problems. So- still looking for something to plug into the sideport that I can store files on. The CF7 seems to use a memory card that is very expensive or hard to source here- I'd like something that used an SDHC card not unlike the FG99. And was easy to use, plug in, put in SDHC card, save file (well, maybe use a disk formatter - perhaps on-board? or something). Oh yes- my 32k sidecar is not extendable, so any new device sidecar would need a connecter for the 32k to plug into! or have its own 32k replacement on board. Just a wish list! Stephen
-
This is how the data is stored in files on this type of computer. NOTE: This is a work in progress. I will be updating this post as I think of stuff to put on here. Bytes $20-$7F represent the standard ASCII character set. Character $7F represents the cursor symbol. Bytes $00-$1F are control codes. $00 - ROM Section Header $01 - Palette $02 - Graphics $03 - Mappings $04 - $05 - $06 - $07 - $08 - Set Tab Width $09 - Tab $0A - Line Feed $0B - Comment Tab $0C - $0D - Carriage Return (same as $0A) $0E - $0F - $10 - $11 - $12 - $13 - $14 - $15 - $16 - $17 - $18 - $19 - $1A - $1B - $1C - $1D - Change Label Line Color $1E - Change Label Line Toggle $1F - Toggle Show/Hide Labels Characters $80-$FF are more control codes. When the file is saved, it is compressed using LZSS.
-
Is there one particular place that you can find all of the file format descriptions for Atari 8-bit computers? If not, here can be! It'd be great if this was more of a factual thread, with less chatter but more of a place to come when you want to know a file format. This will become very useful for programmers to use as a thread. A collection of links would be fine, they don't all have to be written here. Information required is the name of the file format, what it does and then what each byte (or group of bytes) in the files describes. Examples for great formats to list are: .xex, .atr, .dcm, .g2f etc.
- 6 replies
-
- file formats
- format
-
(and 1 more)
Tagged with:
-
Hi Guys! I try to get a possibility to convert any Gram Kracker Dump File and reuse it for other Gram Devices or resuse it as cartridge within any emulator or resuse it for burning eproms. Basically I want any format to be convertable to any other format. For this I started developing a new tool. Now I got stuck with a few of the .grm Files that seem to be cartridge image files created with the Gramulator and meant to be running with Pc99 Emulator. Their 6 byte header doesn't seem to fit the specifications I read about so far. I don't mean the Grom Header starting with "AA ..." that is the first byte from the Grom Memory content, I mean the 6 byte pre header that is added up front by most Gram Devices in order to properly know where to place the various files in its ram chips. Example: phm3058.grm, Mini Memory "FF 20 20 00 60 00 AA 00 ..." The problematic byte is the second (Byte 1) which defines the Bank (Destination Indicator). According to GramKracker Specs legal values are: >01->08 for Grom0-Grom7 >09 or >0A for Rom0 or Rom1 >00 or >FF for Memory Expansion Gramulator Specs extended the former list of legal values to support MBX Carts with: >0B for MBX Ram Bank 0 >0C for MBX Ram Bank 1 >0D for MBX Ram Bank 2 >0E for MBX Ram Bank 3 So what does the value >20 for the Bank Byte mean? I also know about a tool from Cadd called "Universal Gram File Converter". Anybody has the manual or the program? Klaus
-
Please inspect post http://atariage.com/forums/topic/162372-his-dark-majesty/page-5#entry2953919 and following ones for background information...